[MGNLTEST-25] Test Framework provides a facility for asserting HTTP response codes Created: 18/Sep/19  Updated: 16/Mar/21  Resolved: 16/Mar/21

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: QA&Testing, ui-test-fwk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLTEST-86 Simplify checking for custom error pages Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: core-TF-features-bugs-improvements

 Description   

Use cases

  • Public User Registration module
  • various "security related" tests

"Problem"

Looks like the selenium doesn't suport this feature out-of-the-box ... or ... at least for chrome and firefox only.

Resources



 Comments   
Comment by Christoph Meier [ 18/Sep/19 ]

If "impossible" - a possible work-around could be to define proper error pages and analyze the response body via DEV-1349

Comment by Christoph Meier [ 18/Sep/19 ]

... ideally you want to test more than just the response code; I'm finding RESTassured to be a pretty good fit for such cases; worth checking out rest-integration-tests for examples; one thing we could abstract away is the base query building against the proper instance URL, and make it injectable in tests as well with another jupiter extension

(Mika, via slack, https://magnolia-cms.slack.com/archives/CG69M3JGG/p1568805489017100)

Comment by Michael Duerig [ 22/Sep/20 ]

See MGNLTEST-86 re. error pages.

Comment by Christoph Meier [ 16/Mar/21 ]

This is tackled by MGNLTEST-104

Generated at Mon Feb 12 07:44:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.