busser-behave 0.1.3

data/vendor/behave/issue.features/issue0042.feature

@@ -0,0 +1,230 @@
+@issue
+Feature: Issue #42 Nice to have snippets for all unimplemented steps taking into account of the tags fltering
+
+  As a user
+  I want that all undefined steps are reported,
+  not only just the first one in a scenario.
+
+  In addition, all known steps after the first undefined step in a scenario
+  should be marked as skipped (even failing ones).
+
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'I enter a "{name}"')
+      def step(context, name):
+          context.name = name
+
+      @when(u'I enter a "{name}"')
+      def step(context, name):
+          context.name = name
+
+      @then(u'the name is "{name}"')
+      def step(context, name):
+          assert context.name == name
+      """
+
+  Scenario: One undefined step in a scenario
+    Given a file named "features/issue42_missing1.feature" with:
+      """
+      Feature: Missing Given-Step in a Scenario
+        Scenario:
+          Given an unknown step
+          When  I enter a "Alice"
+          Then  the name is "Alice"
+      """
+    When I run "behave -f plain features/issue42_missing1.feature"
+    Then it should fail with:
+      """
+      0 steps passed, 0 failed, 2 skipped, 1 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+      """
+
+  Scenario: Two undefined steps in a scenario
+    Given a file named "features/issue42_missing2.feature" with:
+      """
+      Feature: Missing Given and When steps in a Scenario
+        Scenario:
+          Given an unknown step
+          When  another unknown step
+           And  I enter a "Alice"
+          Then  the name is "Alice"
+      """
+    When I run "behave -f plain features/issue42_missing2.feature"
+    Then it should fail with:
+      """
+      0 steps passed, 0 failed, 2 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+
+      @when(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When another unknown step')
+      """
+
+  Scenario: Two undefined steps in the middle with passing steps
+    Given a file named "features/issue42_missing3.feature" with:
+      """
+      Feature: Missing 2 When steps after passing step
+        Scenario:
+          When I enter a "Alice"
+          And  an unknown step
+          And  another unknown step
+          Then the name is "Alice"
+      """
+    When I run "behave -f plain features/issue42_missing3.feature"
+    Then it should fail with:
+      """
+      1 step passed, 0 failed, 1 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @when(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When an unknown step')
+
+      @when(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When another unknown step')
+      """
+
+  Scenario: Undefined steps are detected if they occur after a failing step
+    Given a file named "features/issue42_missing4.feature" with:
+      """
+      Feature: Missing 2 When steps after passing step
+        Scenario:
+          When I enter a "Alice"
+          Then the name is "Bob"
+          And  an unknown step
+          And  another unknown step
+      """
+    When I run "behave -f plain features/issue42_missing4.feature"
+    Then it should fail with:
+      """
+      1 step passed, 1 failed, 0 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @then(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then an unknown step')
+
+      @then(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then another unknown step')
+      """
+
+  Scenario: Failing step after first undefined step should be marked as skipped
+    Given a file named "features/issue42_missing4.feature" with:
+      """
+      Feature: Missing 2 When steps after passing step
+        Scenario:
+          When I enter a "Alice"
+          And  an unknown step
+          Then the name is "Bob"
+          And  another unknown step
+      """
+    When I run "behave -f plain features/issue42_missing4.feature"
+    Then it should fail with:
+      """
+      1 step passed, 0 failed, 1 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @when(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When an unknown step')
+
+      @then(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then another unknown step')
+      """
+
+  Scenario: Two undefined steps in scenario outline
+    Given a file named "features/issue42_missing5.feature" with:
+      """
+      Feature: Missing Given and When Step in a Scenario Outline
+        Scenario Outline:
+          Given an unknown step
+          When  another unknown step
+           And  I enter a "<name>"
+          Then  the name is "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -f plain features/issue42_missing5.feature"
+    Then it should fail with:
+      """
+      0 steps passed, 0 failed, 4 skipped, 4 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+
+      @when(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When another unknown step')
+      """
+
+  Scenario: Two undefined steps and run with tags
+    Given a file named "features/issue42_missing6.feature" with:
+      """
+      Feature: Missing steps in tagged scenarios
+        @tag1
+        Scenario:
+          When I enter a "Alice"
+          And  an unknown step
+          Then the name is "Bob"
+
+        @tag1
+        Scenario:
+          When I enter a "Alice"
+          And  another unknown step
+          Then the name is "Bob"
+
+        @another_tag
+        Scenario:
+          When  I enter a "Alice"
+          And   yet another unknown step
+          Then  the name is "Bob"
+      """
+    When I run "behave -f plain --tags tag1 features/issue42_missing6.feature"
+    Then it should fail with:
+      """
+      2 steps passed, 0 failed, 5 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @when(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When an unknown step')
+
+      @when(u'another unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When another unknown step')
+      """

data/vendor/behave/issue.features/issue0044.feature

@@ -0,0 +1,51 @@
+@issue
+Feature: Issue #44 Shell-like comments are removed in Multiline Args
+
+  As I user
+  I want that multiline arguments (docstrings) contents are preserved.
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+      from hamcrest import assert_that, equal_to
+
+      @given(u'a multiline text argument with')
+      def step(context):
+          context.expected_text = context.text
+
+      @then(u'the multiline text argument should be')
+      def step(context):
+          assert_that(context.text, equal_to(context.expected_text))
+      """
+
+  Scenario: Ensure shell comment lines are not filtered out in multiline text
+    Given a file named "features/issue44_test.feature" with:
+      '''
+      Feature: Multiline text with shell comment lines
+        Scenario:
+          Given a multiline text argument with:
+            """
+            Lorem ipsum.
+            # THIS IS A SHELL COMMENT.
+            Ipsum lorem.
+            """
+          Then the multiline text argument should be:
+            """
+            Lorem ipsum.
+            # THIS IS A SHELL COMMENT.
+            Ipsum lorem.
+            """
+      '''
+    When I run "behave -c -f pretty features/issue44_test.feature"
+    Then it should pass
+    And  the command output should contain:
+        """
+        # THIS IS A SHELL COMMENT.
+        """
+    But  the command output should not contain:
+        """
+        Lorem ipsum.
+        Ipsum lorem.
+        """

data/vendor/behave/issue.features/issue0046.feature

@@ -0,0 +1,77 @@
+@issue
+Feature: Issue #46 Behave returns 0 (SUCCESS) even in case of test failures
+
+  As I behave user
+  I want to detect test success or test failures
+  By using the process return value, 0 (SUCCESS) and non-zero for failure.
+
+  Background: Test Setup
+    Given a new working directory
+    Given a file named "features/steps/steps.py" with:
+      """
+      from behave import given
+
+      @given(u'passing')
+      def step(context):
+          pass
+
+      @given(u'failing')
+      def step(context):
+          assert False, "failing"
+      """
+
+  Scenario: Successful Execution
+    Given a file named "features/passing.feature" with:
+      """
+      Feature: Passing
+        Scenario: Passing Scenario Example
+          Given passing
+      """
+    When I run "behave -c -q features/passing.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      1 step passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Failing Execution
+    Given a file named "features/failing.feature" with:
+      """
+      Feature: Failing
+        Scenario: Failing Scenario Example
+          Given failing
+      """
+    When I run "behave -c -q features/failing.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 0 skipped
+      0 steps passed, 1 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Passing and Failing Execution
+    Given a file named "features/passing_and_failing.feature" with:
+      """
+      Feature: Passing and Failing
+        Scenario: Passing Scenario Example
+          Given passing
+        Scenario: Failing Scenario Example
+          Given failing
+      """
+    When I run "behave -c -q features/passing_and_failing.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      1 scenario passed, 1 failed, 0 skipped
+      1 step passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Feature: Passing and Failing
+        Scenario: Passing Scenario Example
+          Given passing
+        Scenario: Failing Scenario Example
+          Given failing
+            Assertion Failed: failing
+      """

data/vendor/behave/issue.features/issue0052.feature

@@ -0,0 +1,66 @@
+@issue
+Feature: Issue #52 Summary counts are wrong with option --tags
+
+  Wrong summary counts are shown for skipped and failed scenarios
+  when option --tags=done is used (and some scenarios are skipped).
+
+
+  Background: Test Setup
+    Given a new working directory
+    Given a file named "features/steps/steps.py" with:
+      """
+      from behave import given
+
+      @given(u'passing')
+      def step(context):
+          pass
+
+      @given(u'failing')
+      def step(context):
+          assert False, "failing"
+      """
+
+  Scenario: Successful Execution of Tagged Scenario
+    Given a file named "features/tagged_scenario1.feature" with:
+      """
+      Feature: Passing tagged Scenario
+        @done
+        Scenario: P1
+          Given passing
+
+        @unimplemented
+        Scenario: N1
+          Given passing
+        @unimplemented
+        Scenario: N2
+          Given passing
+      """
+    When I run "behave --junit -c --tags @done features/tagged_scenario1.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 2 skipped
+      """
+
+  Scenario: Failing Execution of Tagged Scenario
+    Given a file named "features/tagged_scenario2.feature" with:
+      """
+      Feature: Failing tagged Scenario
+        @done
+        Scenario: F1
+          Given failing
+
+        @unimplemented
+        Scenario: N1
+          Given passing
+        @unimplemented
+        Scenario: N2
+          Given passing
+      """
+    When I run "behave --junit -c --tags @done features/tagged_scenario2.feature"
+    Then it should fail
+    And  the command output should contain:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 2 skipped
+      """

data/vendor/behave/issue.features/issue0059.feature

@@ -0,0 +1,29 @@
+@issue
+Feature: Issue #59 Fatal error when using --format=json
+
+  Using the JSON formatter caused a fatal error.
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given
+
+      @given(u'passing')
+      def step(context):
+          pass
+      """
+    And   a file named "features/issue59_test.feature" with:
+      """
+      Feature: Passing tagged Scenario
+        Scenario: P1
+          Given passing
+      """
+
+  Scenario: Use the JSONFormatter
+    When I run "behave --format=json features/issue59_test.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      """