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 @retry to 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 @retry tag 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.
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