MNT Add @retry to commonly-failing behat feature
#1679
Merged
Conversation
This file contains 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.
This behat feature fails quite frequently, and it's a pain to have to retry the whole behat run just for the one feature.
Adding
@retryto any feature or scenario will cause any failing steps to retry continuously for a set number of seconds (default 3 seconds).If the failures are caused by (for example) trying to see an element before the page has finished loading, then this
@retrytag could resolve many failures for us.It won't resolve problems if something went wrong with setting up a test, but those sorts of failures are much less likely to be intermittent anyway.
Issue