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
If there is a mismatch between the *.feature file and the the steps defined, we'll see an output like.
[Cucumber v0.8.4]
Feature: Animal feature features/animal.feature:1:1
Scenario: If we feed a hungry cat it will no longer be hungry features/animal.feature:3:3
✔ Given A hungry cat features/animal.feature:4:5
✔ When I feed the cat features/animal.feature:5:5
- Then The cat is not hungry!!!! features/animal.feature:6:5
⚡ Not yet implemented (skipped)
[Summary]
1 features
1 scenarios (1 skipped, 0 passed)
6 steps (1 skipped, 2 passed)
And the command line returns 0 (success).
But I don't want to have this to pass the CI and sneak in the main branch.
Ideally if any test was not implemented, the command line should return a failure. Eventually this could be a configurable behavior.
The text was updated successfully, but these errors were encountered:
bbqsrc
changed the title
Consider not-implemented tests as failure
Add a configuration option for making not-implemented tests failures
Jul 19, 2021
If there is a mismatch between the
*.feature
file and the the steps defined, we'll see an output like.And the command line returns
0
(success).But I don't want to have this to pass the CI and sneak in the main branch.
Ideally if any test was not implemented, the command line should return a failure. Eventually this could be a configurable behavior.
The text was updated successfully, but these errors were encountered: