features/cucumber_cli.feature in cucumber-0.3.6 vs features/cucumber_cli.feature in cucumber-0.3.7

- old
+ new

@@ -1,11 +1,9 @@ Feature: Cucumber command line In order to write better software Developers should be able to execute requirements as tests - - Scenario: Run single scenario with missing step definition When I run cucumber -q features/sample.feature:5 Then it should pass with """ @one @@ -54,10 +52,11 @@ 1 scenario (1 passed) 1 step (1 passed) """ + @mri186 Scenario: Specify 2 line numbers where one is a tag When I run cucumber -q features/sample.feature:5:14 Then it should fail with """ @one @@ -115,10 +114,11 @@ 1 scenario (1 passed) 1 step (1 passed) """ + @mri186 Scenario: Run all with progress formatter When I run cucumber -q --format progress features/sample.feature Then it should fail with """ U.F @@ -404,9 +404,10 @@ 2 scenarios (1 undefined, 1 passed) 2 steps (1 undefined, 1 passed) """ + @mri186 Scenario: Run with a tag that exists on 1 feature When I run cucumber -q features --tags one Then it should fail with """ @one