features/cucumber_cli.feature in cucumber-0.8.3 vs features/cucumber_cli.feature in cucumber-0.8.4
- old
+ new
@@ -165,41 +165,10 @@
3 scenarios (1 failed, 1 undefined, 1 passed)
3 steps (1 failed, 1 undefined, 1 passed)
"""
- Scenario: Run Norwegian
- Given I am in i18n/no
- When I run cucumber -q features
- Then STDERR should be empty
- Then it should pass with
- """
- # language: no
- Egenskap: Summering
- For å slippe å gjøre dumme feil
- Som en regnskapsfører
- Vil jeg kunne legge sammen
-
- Scenario: to tall
- Gitt at jeg har tastet inn 5
- Og at jeg har tastet inn 7
- Når jeg summerer
- Så skal resultatet være 12
-
- @iterasjon3
- Scenario: tre tall
- Gitt at jeg har tastet inn 5
- Og at jeg har tastet inn 7
- Og at jeg har tastet inn 1
- Når jeg summerer
- Så skal resultatet være 13
-
- 2 scenarios (2 passed)
- 9 steps (9 passed)
-
- """
-
Scenario: --dry-run
When I run cucumber --dry-run --no-source features/*.feature --tags ~@lots
Then it should pass with
"""
Feature: Calling undefined step
@@ -368,19 +337,19 @@
"""
Scenario: Multiple formatters and outputs
When I run cucumber --format progress --out tmp/progress.txt --format pretty --out tmp/pretty.txt --no-source --dry-run features/lots_of_undefined.feature
Then STDERR should be empty
- Then "examples/self_test/tmp/progress.txt" should contain
+ Then "fixtures/self_test/tmp/progress.txt" should contain
"""
UUUUU
1 scenario (1 undefined)
5 steps (5 undefined)
"""
- And "examples/self_test/tmp/pretty.txt" should contain
+ And "fixtures/self_test/tmp/pretty.txt" should contain
"""
Feature: Lots of undefined
Scenario: Implement me
Given it snows in Sahara
@@ -526,74 +495,38 @@
"""
Scenario: Run with limited tag count, blowing it on scenario
When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags @sample_three:1
- Then it should fail with
- """
- @sample_one
- Feature: Tag samples
+ Then it should fail with
+ """
+ @sample_three occurred 2 times, but the limit was set to 1
+ features/tags_sample.feature:11
+ features/tags_sample.feature:16
+ """
- @sample_three
- Scenario Outline:
- Given <state>
-
- Examples:
- | state |
- | missing |
-
- @sample_three @sample_four
- Scenario: Skipped
- Given missing
-
- 2 scenarios (2 undefined)
- 2 steps (2 undefined)
-
- @sample_three occurred 2 times, but the limit was set to 1
- features/tags_sample.feature:9
- features/tags_sample.feature:16
-
- """
-
Scenario: Run with limited tag count, blowing it via feature inheritance
When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags @sample_one:1
- Then STDERR should be empty
Then it should fail with
- """
- @sample_one
- Feature: Tag samples
+ """
+ @sample_one occurred 3 times, but the limit was set to 1
+ features/tags_sample.feature:5
+ features/tags_sample.feature:11
+ features/tags_sample.feature:16
+ """
- @sample_two @sample_four
- Scenario: Passing
- Given missing
+ Scenario: Run with limited tag count using negative tag, blowing it via a tag that is not run
+ When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags ~@sample_one:1
+ Then it should fail with
+ """
+ @sample_one occurred 3 times, but the limit was set to 1
+ """
- @sample_three
- Scenario Outline:
- Given <state>
-
- Examples:
- | state |
- | missing |
-
- @sample_three @sample_four
- Scenario: Skipped
- Given missing
-
- 3 scenarios (3 undefined)
- 3 steps (3 undefined)
-
- @sample_one occurred 3 times, but the limit was set to 1
- features/tags_sample.feature:5
- features/tags_sample.feature:9
- features/tags_sample.feature:16
-
- """
-
Scenario: Reformat files with --autoformat
When I run cucumber --autoformat tmp/formatted features
Then STDERR should be empty
- Then "examples/self_test/tmp/formatted/features/sample.feature" should contain
+ Then "fixtures/self_test/tmp/formatted/features/sample.feature" should contain
"""
# Feature comment
@one
Feature: Sample
@@ -621,10 +554,10 @@
# Fails on 1.9 because of encoding issues.
@fails_on_1_9
Scenario: Generate PDF with pdf formatter
When I run cucumber --format pdf --out tmp/sample.pdf --dry-run features/sample.feature
Then STDERR should be empty
- Then "examples/self_test/tmp/sample.pdf" should match "Pages 2"
+ Then "fixtures/self_test/tmp/sample.pdf" should match "Pages 2"
Scenario: Run feature elements which match a name using -n
When I run cucumber -n Pisang -q features/
Then STDERR should be empty
Then it should pass with