-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Retry option not working from profiles #1050
Comments
After banging our heads on the wall for a couple days, I came across this issue to explain why we weren't getting this --retry flag working. We am having the same issues, except we tried it with versions 3.0.0 and I just now also tried with 3.0.1 with no luck. For convenience, we pretty much exclusively use profiles so this is highly frustrating. |
I unfortunately am having the same problem. I can do the retry from the command line but the exact same syntax will not trigger a retry from a profile. Anyone find what the issue is? |
I haven't seen an update to the gem beyond 3.0.1 yet. Any ETA for releasing a version that includes this fix? |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Retry option not working from profiles
Expected Behavior
When adding --retry option to a profile, cucumber should use it and retry the given number of times the failing steps.
Current Behavior
Steps to Reproduce (for bugs)
Context & Motivation
It would be useful to include retry into profiles and not have to write
--retry
on each execution.Your Environment
The text was updated successfully, but these errors were encountered: