Skip to content
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

Closed
emmakun opened this issue Oct 27, 2016 · 4 comments
Closed

Retry option not working from profiles #1050

emmakun opened this issue Oct 27, 2016 · 4 comments

Comments

@emmakun
Copy link

emmakun commented Oct 27, 2016

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

Retry option seems to be ignored in profiles.
For instance, if I have a profile like this:

test_profile: --format pretty --retry 2

When running `cucumber -p test_profile`, all steps are executed only once, even if they fail.

Steps to Reproduce (for bugs)

  1. Add --retry option to any profile
  2. Run cucumber with the given profile
  3. See it runs all steps only once, even if they fail

Context & Motivation

It would be useful to include retry into profiles and not have to write --retry on each execution.

Your Environment

  • Version used: 3.0.0.pre.1
  • Operating System and version: macOS 10.11.6 "El Capitan"
@bojingo
Copy link

bojingo commented Oct 2, 2017

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.

@jroger2908
Copy link

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?

@bojingo
Copy link

bojingo commented Oct 10, 2017

I haven't seen an update to the gem beyond 3.0.1 yet. Any ETA for releasing a version that includes this fix?

@lock
Copy link

lock bot commented Oct 24, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants