Sha256: 184a7ef98a2e4e9830f58f4378b83ef14a4361c0e5f3343968861e37541afed8
Contents?: true
Size: 1.69 KB
Versions: 16
Compression:
Stored size: 1.69 KB
Contents
Feature: Strict mode
Using the `--strict` flag will cause cucumber to fail unless all the
step definitions have been defined.
Background:
Given a file named "features/missing.feature" with:
"""
Feature: Missing
Scenario: Missing
Given this step passes
"""
And a file named "features/pending.feature" with:
"""
Feature: Pending
Scenario: Pending
Given this step is pending
"""
Scenario: Fail with --strict due to undefined step
When I run `cucumber -q features/missing.feature --strict`
Then it should fail with:
"""
Feature: Missing
Scenario: Missing
Given this step passes
Undefined step: "this step passes" (Cucumber::Undefined)
features/missing.feature:3:in `Given this step passes'
1 scenario (1 undefined)
1 step (1 undefined)
"""
Scenario: Fail with --strict due to pending step
Given the standard step definitions
When I run `cucumber -q features/pending.feature --strict`
Then it should fail with:
"""
Feature: Pending
Scenario: Pending
Given this step is pending
TODO (Cucumber::Pending)
./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
features/pending.feature:3:in `Given this step is pending'
1 scenario (1 pending)
1 step (1 pending)
"""
Scenario: Succeed with --strict
Given the standard step definitions
When I run `cucumber -q features/missing.feature --strict`
Then it should pass with:
"""
Feature: Missing
Scenario: Missing
Given this step passes
1 scenario (1 passed)
1 step (1 passed)
"""
Version data entries
16 entries across 16 versions & 2 rubygems