Sha256: 914b1fefe9efb40a4cd0e6621114c831d758795667828588dbf1a315c6ed2e70
Contents?: true
Size: 1.83 KB
Versions: 3
Compression:
Stored size: 1.83 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' Undefined Scenarios: cucumber features/missing.feature:2 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' Pending Scenarios: cucumber features/pending.feature:2 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
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
cucumber-3.0.1 | features/docs/cli/strict_mode.feature |
cucumber-3.0.0 | features/docs/cli/strict_mode.feature |
cucumber-3.0.0.pre.2 | features/docs/cli/strict_mode.feature |