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.

Sign up for GitHub

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

Jump to bottom

Implement --strict #196

Closed
aslakhellesoy opened this issue Feb 7, 2012 · 3 comments
Closed

Implement --strict #196

aslakhellesoy opened this issue Feb 7, 2012 · 3 comments

Comments

@aslakhellesoy
Copy link
Contributor

It should behave like classic ruby cucumber
@aslakhellesoy
Copy link
Contributor Author

Some more detail: It should cause cucumber to exit with a non-zero exit status if there are pending or undefined steps. The default (when --strict is not specified) is to only exit with non-zero when there are errors.

@aslakhellesoy aslakhellesoy mentioned this issue Mar 19, 2012
Closed
@aslakhellesoy
Copy link
Contributor Author

With the JUnit runner, I also think undefined/pending steps should show up red (failed) instead of skipped (yellow).

klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 30, 2012
@klausbayrhammer
Issue cucumber#196 strict in cucumber-jvm
e72bb71
klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 31, 2012
@klausbayrhammer
Issue cucumber#196 use undefinedStepTracker to detect undefined steps
de3d9ef
klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 31, 2012
@klausbayrhammer
Issue cucumber#196 process pending steps correctly
564d147
klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Apr 1, 2012
@klausbayrhammer
Issue cucumber#196 mark steps and scenarios as failed when there are …
efa1b85 
…pending/undefined steps and --strict is enabled
@lock
Copy link

lock bot commented Oct 25, 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 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aslakhellesoy