[MGNLTEST-86] Simplify checking for custom error pages Created: 18/Aug/20 Updated: 05/Oct/20 Resolved: 05/Oct/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | QA&Testing, ui-test-fwk | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||
| Sprint: | TE 12 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Checking for the presence of a custom error page needs to be explicitly coded currently:
expect.renderedPage("").hasText("Custom 404 Page");
Devise and implement an API that allows to check for custom error pages on a higher, more semantic level. Something along the lines of expect.renderedPage().isErrorPage();
|
| Comments |
| Comment by Michael Duerig [ 18/Aug/20 ] |
|
/cc cmeier |
| Comment by Mikaël Geljić [ 05/Oct/20 ] |
|
implemented as expect.errorPage(); |