UnexpectedPages will be checked by PageBrowser.at() to prevent
running in a timeout when waiting for an expected page.
Unexpected PageObjects have normally no URL, are not implementing UrlPage, but this is not required.
Examples are BrowserErrorPage, "404 File Not Found" or "5xx Server Error" Pages.
Also Error Pages delivered by Load Balancers (for example AWS Elastic Load Balancer or CloudFlare)
can be checked here.
There are two groups of unexpected Pages, the first group will cancel the test, the other
group will fail the test.
"File not Found" or "Internal Server Error" should cause a test to fail, but "connection refused"
should cancel the test because test server is not reachable. This is typically an environment problem,
normally not a problem with the test itself.
UnexpectedPages will be checked by
PageBrowser.at()to prevent running in a timeout when waiting for an expected page.Unexpected PageObjects have normally no URL, are not implementing UrlPage, but this is not required.
Examples are BrowserErrorPage, "404 File Not Found" or "5xx Server Error" Pages.
Also Error Pages delivered by Load Balancers (for example AWS Elastic Load Balancer or CloudFlare) can be checked here.
There are two groups of unexpected Pages, the first group will cancel the test, the other group will fail the test.
"File not Found" or "Internal Server Error" should cause a test to fail, but "connection refused" should cancel the test because test server is not reachable. This is typically an environment problem, normally not a problem with the test itself.