Created
June 27, 2014 14:03
-
-
Save ChristianPeters/e39bed18299afd278f2a to your computer and use it in GitHub Desktop.
Wait longer in Capybara
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| around { |example| with_wait_time(6) { example.run } } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| def with_wait_time(wait_time = Capybara.default_wait_time) | |
| previous_wait_time = Capybara.default_wait_time | |
| Capybara.default_wait_time = wait_time | |
| yield | |
| ensure | |
| Capybara.default_wait_time = previous_wait_time | |
| end |
Workaround
view.text.include?("HELLO WORLD").should beDid you wrap your workaround into the helper method?
This seems to have been fixed with the wait option: https://www.reddit.com/r/rails/comments/25xrdy/is_there_a_way_to_change_capybaras_wait_time_just/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even if this method is definitely better and more sophisticated than
sleep(x)it won't work for each use case.Example:
wrapping this code in an
aroundblock containing thewith_wait_timestatement. It does only wait forfindand tillhave_contenthas found any type of text, but while client-side code may renders asynchronous timing issues are still not resolved. Of cause this is a mistake by design.Returning to the above example, rspec throws the error: