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

A passing Cucumber dry run with --strict option returns a bash exit code of 1 #810

Closed
cjryan opened this issue Feb 25, 2015 · 2 comments
Closed

Comments

@cjryan
Copy link

cjryan commented Feb 25, 2015

Hello,

As of cucumber 2.0.0.rc.4, a passed cucumber dry run with the --strict option enabled will return a bash exit code of 1. Previously, (i.e. in cucumber version 1.3.9), this would return 0.

For example:

cucumber -r features --dry --strict features/faildry.feature 
Feature: faildry.feature
  Scenario: faildry.feature # features/faildry.feature:2
    Given I have "3" cukes  # features/step_definitions/cukes.rb:1
1 scenario (1 skipped)
1 step (1 skipped)
0m0.001s

echo $?
1

In cucumber 1.3.9, this would return 0. Also, running without the --strict option in 2.0.0.rc.4 will return 0.

My setup is:
Fedora 21, 3.18.3-201.fc21.x86_64
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
cucumber 2.0.0.rc.4

Thanks!

@cjryan
Copy link
Author

cjryan commented Mar 4, 2015

@brasmusson looks great, thanks so much!

@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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant