You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
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!
The text was updated successfully, but these errors were encountered: