Skip to content

Implement --strict #196

Closed
aslakhellesoy opened this Issue Feb 7, 2012 · 2 comments

1 participant

@aslakhellesoy
Cucumber member

It should behave like classic ruby cucumber

@aslakhellesoy
Cucumber member

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
Cucumber member

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

@klausbayrhammer klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 30, 2012
@klausbayrhammer klausbayrhammer Issue #196 strict in cucumber-jvm e72bb71
@klausbayrhammer klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 31, 2012
@klausbayrhammer klausbayrhammer Issue #196 use undefinedStepTracker to detect undefined steps de3d9ef
@klausbayrhammer klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Mar 31, 2012
@klausbayrhammer klausbayrhammer Issue #196 process pending steps correctly 564d147
@klausbayrhammer klausbayrhammer added a commit to klausbayrhammer/cucumber-jvm that referenced this issue Apr 1, 2012
@klausbayrhammer klausbayrhammer Issue #196 mark steps and scenarios as failed when there are pending/…
…undefined steps and --strict is enabled
efa1b85
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.