Skip to content

Setting 'atCheckWaiting' to TRUE forces 'at' verification of 'unexpectedPages' #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
geb-bot opened this issue Nov 4, 2013 · 4 comments
Assignees

Comments

@geb-bot
Copy link

geb-bot commented Nov 4, 2013

Originally created by Sumanas Sarma.

I have 2 error pages as Error404Page and Error500Page. In GebConfig.groovy I have set atCheckWaiting = true and unexpectedPages = [Error404Page, Error500Page].

This results in Geb doing an 'at' check for the 404 error page on every page that is loaded by the test. If this loaded page is not a 404 (it's a legit page), then I get a geb.waiting.WaitTimeoutException: condition did not pass in 21.0 seconds (failed with exception)

Removing the atCheckWaiting = true fixes this issue.

@geb-bot
Copy link
Author

geb-bot commented Nov 4, 2013

This issue is duplicated by #290

@geb-bot
Copy link
Author

geb-bot commented Nov 12, 2013

Originally posted by Luke Daley.

Thanks for the report, we'll look into it.

I guess we should not wait when testing for unexpected pages.

@geb-bot
Copy link
Author

geb-bot commented Dec 5, 2013

Originally posted by Craig Atkinson.

I submitted a pull request to not wait in the at-checker when testing for unexpected pages apache/groovy-geb#55

@geb-bot
Copy link
Author

geb-bot commented Dec 15, 2013

Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants