Merged
Conversation
Member
Author
Contributor
|
Ah this is awesome! |
Collaborator
|
Not sure if it's this or #479. If I rebuild the assets on |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In general, active delays in tests are a bad practice. They slow the suite down, and they are unreliable.
Capybara comes with automatic waiting for the built-in helpers, we should always try to use those when possible. E.g: if something changes in the screen, assert with a selector the expected change, so that Capybara waits until it happens.
I added a custom
wait_untilhelper method for custom conditions that we can't cover with capybara.I left a couple of sleeps after pressing keys, since I can't think of a way to avoid those.