Join GitHub today
Add the ability to detect and fail fast when unexpected pages (e.g. 500 error) are encountered #70
Originally posted by Alexander Zolotov.
Why? Error-pages are usually primitive, so the test will not much accelerated if it fails immediately when getting 500 response code. However, in some of my projects it makes sense to validate error-pages (for example check that stacktrace do not displayed for regular users) and this innovation will not let me do this test.
Originally posted by Christoph Neuroth.
Also this might currently be impossible because WebDriver does not expose any HTTP things, see http://code.google.com/p/selenium/issues/detail?id=141
Originally posted by Luke Daley.
It would be nice in a test to have a nice error message to indicate that you ended up at your application's error page instead of getting a less descriptive RequiredPageContentNotFound exception.
If the error message clearly says that you're at the error page, you'd know immediately that the test failed because the system under test error'd.
I imagine it would work something like this�
Then whenever we change the page, Geb would implicitly check we are not at that page.