busser-behave 0.1.3

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

@@ -0,0 +1,49 @@
+@issue
+Feature: Issue #125: Duplicate "Captured stdout" if substep has failed
+
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import step
+
+      @step('a step fails with stdout "{message}"')
+      def step_fails_with_stdout(context, message):
+          print(message)
+          assert False, 'EXPECT: Step fails with stdout.'
+
+      @step('substep fails with stdout "{message}"')
+      def substep_fails_with_stdout(context, message):
+          context.execute_steps(u'When a step fails with stdout "%s"' % message)
+      """
+
+  Scenario: Subprocess call shows generated output
+    Given a file named "features/issue125_example.feature" with:
+      """
+      Feature:
+          Scenario:
+              When substep fails with stdout "Hello"
+      """
+    When I run "behave -f plain --no-timings features/issue125_example.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 1 failed, 0 skipped
+      0 steps passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Feature:
+          Scenario:
+              When substep fails with stdout "Hello" ... failed
+
+      Assertion Failed: FAILED SUB-STEP: When a step fails with stdout "Hello"
+      Substep info: Assertion Failed: EXPECT: Step fails with stdout.
+      """
+    And the command output should contain 1 times:
+      """
+      Captured stdout:
+      Hello
+      """
+    But note that "the captured output should not be contained multiple times"
+

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

@@ -0,0 +1,64 @@
+@issue
+Feature: Issue #127: Strip trailing colons
+
+  . Trailing colon in a step is stripped by the Gherkin parser.
+  . Undefined step snippets should not suggest the step with a trailing colon.
+  .
+  . GENERAL RULE (by looking at the parser):
+  .   1. Colon in step in feature file is OK
+  .      (parser strips this for step-with-table or step-with-multiline-text).
+  .   2. Step definitions in Python files should not end with a colon
+  .      (used in @given/@when/@then decorators).
+
+
+  Background:
+    Given a new working directory
+    And   a file named "features/example127.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given the following superusers exist:
+              | Name  | User Id |
+              | Alice | 101     |
+              | Bob   | 102     |
+        """
+
+  Scenario: Step Definition has no trailing colon (GOOD CASE)
+    Given a file named "features/steps/good_steps.py" with:
+        """
+        from behave import given
+
+        @given(u'the following superusers exist')
+        def step_given_following_superusers_exist(context):
+            pass
+        """
+    When I run "behave -f plain features/example127.feature"
+    Then it should pass
+    And the command output should not contain:
+        """
+        You can implement step definitions for undefined steps with these snippets:
+
+        @given(u'the following superusers exist:')
+        def step_impl(context):
+            raise NotImplementedError(u'STEP: Given the following superusers exist:')
+        """
+
+  Scenario: Step Definition has trailing colon (BAD CASE)
+    Given a file named "features/steps/bad_steps.py" with:
+        """
+        from behave import given
+
+        @given(u'the following superusers exist:')
+        def step_given_following_superusers_exist(context):
+            pass
+        """
+    When I run "behave -f plain features/example127.feature"
+    Then it should fail
+    And the command output should contain:
+        """
+        You can implement step definitions for undefined steps with these snippets:
+
+        @given(u'the following superusers exist')
+        def step_impl(context):
+            raise NotImplementedError(u'STEP: Given the following superusers exist')
+        """

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

@@ -0,0 +1,67 @@
+@issue
+@not_reproducible
+Feature: Issue #139: Wrong steps seem to be executed when using --wip
+
+  . RELATED-TO: issue #35
+  . behave --format=plain --tags @one" seems to execute right scenario w/ wrong steps
+  .
+  . If you have a feature file with two scenarios where the second is tagged
+  . with @wip, running behave -w will output step names from the first scenario.
+  . It does seem to run the correct code for the steps.
+
+
+  Scenario:
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+        """
+        from behave import given, when, then, step
+
+        @step('a step passes')
+        def step_passes(context):
+            pass
+
+        @step('a step fails')
+        def step_fails(context):
+            assert False, "XFAIL"
+
+        @when('I run a test step')
+        def step_impl(context):
+            pass
+
+        @when('I run some other test step')
+        def step_impl(context):
+            pass
+
+        @then('I should not see a failure here')
+        def step_impl(context):
+            pass
+        """
+    And a file named "features/issue0139_example.feature" with:
+        """
+        Feature: Bug in wip/behave -w
+
+            Scenario: This is strange
+                Given a step passes
+                When a step passes
+                Then a step fails
+
+            @wip
+            Scenario: Demonstrate bug
+                When I run a test step
+                And I run some other test step
+                Then I should not see a failure here
+        """
+    When I run "behave -w -f plain -T features/issue0139_example.feature"
+    Then it should pass
+    And the command output should contain:
+        """
+        Feature: Bug in wip/behave -w
+          Scenario: This is strange
+          Scenario: Demonstrate bug
+            When I run a test step ... passed
+            And I run some other test step ... passed
+            Then I should not see a failure here ... passed
+        """
+
+
+

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

@@ -0,0 +1,37 @@
+@issue
+@not_reproducible
+Feature: Issue #142: --junit flag fails to output with step table data: TypeError: <Row [u'data', u'value']> is not JSON serializable
+
+      DUPLICATES: issue #67 (already fixed).
+
+  Scenario:
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+        """
+        from behave import given, when, then, step
+
+        @then('use table data with')
+        def step_impl(context):
+            pass
+        """
+    And a file named "features/issue0142_example.feature" with:
+        """
+        Feature:
+            Scenario: Use a table
+             Then use table data with:
+                 | data                             | value |
+                 | behave outputs junit with tables | false |
+        """
+    When I run "behave --junit -f json features/issue0142_example.feature"
+    Then it should pass
+    But the command output should not contain:
+        """
+        TypeError: <Row [u'behave outputs junit with tables', u'false']> is not JSON serializable
+        """
+    And the command output should not contain:
+        """
+        Traceback (most recent call last):
+        """
+
+
+

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

@@ -0,0 +1,54 @@
+@issue
+Feature: Issue #143: Logging starts with a StreamHandler way too early
+
+  . This verifies that some imported library or other item has not made a
+  . call to logging too soon, which would add a StreamHandler.
+
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+        """
+        import logging
+        from behave import given, when, then, step
+
+        @step('I create {count:n} log records')
+        def step_create_log_records(context, count):
+            for i in range(count):
+                logging.debug('Some debug logging')
+        """
+    And a file named "features/issue0143_example.feature" with:
+        """
+        Feature: Logging should not be output unless there is a failure
+
+            Scenario: A passing test
+                Given I create 4 log records
+        """
+
+  Scenario: Ensure that no log-ouput occurs with enabled log-capture
+    Given an empty file named "features/environment.py"
+    When I run "behave -f plain --logcapture features/issue0143_example.feature"
+    Then it should pass
+    And the command output should not contain:
+        """
+        DEBUG:root:Some debug logging
+        """
+
+
+  Scenario: Ensure that log-ouput occurs with disabled log-capture
+    Given a file named "features/environment.py" with:
+        """
+        import logging
+
+        def before_all(context):
+            # -- basicConfig() will not set level if setup is already done.
+            logging.basicConfig()
+            logging.getLogger().setLevel(logging.DEBUG)
+        """
+    When I run "behave -f plain --no-logcapture features/issue0143_example.feature"
+    Then it should pass
+    And the command output should contain:
+        """
+        DEBUG:root:Some debug logging
+        """

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

@@ -0,0 +1,63 @@
+@issue
+Feature: Issue #145: before_feature/after_feature should not be skipped
+
+  Hooks before_feature(), after_feature() (and before_step()) are skipped
+  if --tags options select feature tag and scenario tag.
+
+  SEE ALSO: https://github.com/cucumber/cucumber/wiki/Tags
+
+  @setup
+  Scenario: Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+        """
+        from behave import step
+
+        @step('a step passes')
+        def step_passes(context):
+            pass
+        """
+    And a file named "features/issue0145_example.feature" with:
+        """
+        @feature
+        Feature: Feature-145
+
+          @scenario
+          Scenario: Scenario-145
+            Given a step passes
+            When a step passes
+            Then a step passes
+        """
+    And a file named "features/environment.py" with:
+        """
+        from __future__ import print_function
+
+        def before_feature(context, feature):
+            print("hooks.before_feature: %s called." % feature.name)
+
+        def after_feature(context, feature):
+            print("hooks.after_feature: %s called." % feature.name)
+        """
+
+  Scenario: Select only @scenario tag
+    When I run "behave -f plain -T --tags=@scenario features/issue0145_example.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        1 scenario passed, 0 failed, 0 skipped
+        3 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the behave hook "before_feature" was called
+    And the behave hook "after_feature" was called
+
+  Scenario: Select @feature tag and @scenario tag (logical-and, fails if not fixed)
+    When I run "behave -f plain -T --tags=@feature --tags=@scenario features/issue0145_example.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        1 scenario passed, 0 failed, 0 skipped
+        3 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the behave hook "before_feature" was called
+    And the behave hook "after_feature" was called
+

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

@@ -0,0 +1,105 @@
+@issue
+@already_fixed
+Feature: Issue #148: Substeps do not fail
+
+  FIXED-BY: issue #117 context.execute_steps() should support table and multi-line text.
+  RELATED-TO: issue #96
+
+  @setup
+  Scenario: Setup
+    Given a new working directory
+    And a file named "features/steps/passing_steps.py" with:
+        """
+        @step('a step passes')
+        def step_passes(context):
+            pass
+
+        @step('a step fails')
+        def step_fails(context):
+            assert False, "XFAIL"
+        """
+    And a file named "features/issue0148_example.feature" with:
+        """
+        Feature: Sub steps
+
+          @xfail
+          Scenario: Failing test without substeps
+            Given a step passes
+            When a step fails
+            Then a step passes
+
+          @xfail
+          Scenario: Failing test with substeps
+            Given a step passes
+            When I do something with stupid substeps
+            Then a step passes
+        """
+
+  Scenario: Missing Step Keywords in Substeps
+    Given a file named "features/steps/substeps.py" with:
+        """
+        @When('I do something with stupid substeps')
+        def step(context):
+            context.execute_steps(u'''
+                I do something stupid
+                there is a second stupid step
+            ''')  # Given/When/Then keywords are missing in substeps above.
+        """
+    When I run "behave -f plain -T features/issue0148_example.feature"
+    Then it should fail with:
+        """
+        0 features passed, 1 failed, 0 skipped
+        0 scenarios passed, 2 failed, 0 skipped
+        2 steps passed, 2 failed, 2 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+          Scenario: Failing test without substeps
+            Given a step passes ... passed
+            When a step fails ... failed
+        """
+    And the command output should contain:
+        """
+          Scenario: Failing test with substeps
+            Given a step passes ... passed
+            When I do something with stupid substeps ... failed
+        """
+    And the command output should contain:
+        """
+        ParserError: Failed to parse <string>:
+        Parser failure in state steps, at line 2: "I do something stupid"
+        """
+
+
+  Scenario: Use Step Keywords in Substeps
+    Given a file named "features/steps/substeps.py" with:
+        """
+        @when('I do something with stupid substeps')
+        def step(context):
+            context.execute_steps(u'''
+                When a step fails
+                Then a step fails
+            ''')
+        """
+    When I run "behave -f plain -T features/issue0148_example.feature"
+    Then it should fail with:
+        """
+        0 features passed, 1 failed, 0 skipped
+        0 scenarios passed, 2 failed, 0 skipped
+        2 steps passed, 2 failed, 2 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+          Scenario: Failing test with substeps
+            Given a step passes ... passed
+            When I do something with stupid substeps ... failed
+            Assertion Failed: FAILED SUB-STEP: When a step fails
+            Substep info: Assertion Failed: XFAIL
+        """
+    But the command output should not contain:
+        """
+
+        ParserError: Failed to parse <string>
+        """
+
+

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

@@ -0,0 +1,52 @@
+@issue
+Feature: Issue #152: Fix encoding issues
+
+  . I fixed two encoding issues in pretty formatter and in JUnit serialization.
+  . Now it's possible to use accented letters in feature files and
+  . create JUnit reports from the tests.
+
+
+  Scenario: Ensure JUnit reports can be created from a foreign language
+    Given a new working directory
+    And an empty file named "features/steps/steps.py"
+    And a file named "features/eins.feature" with:
+        """
+        # language: de
+        Funktionalität: Die Welt ist schön
+            Szenario: Was wäre wenn die schöne, neue Welt untergeht
+        """
+    When I run "behave -f plain --junit --no-timings features/eins.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      0 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Funktionalität: Die Welt ist schön
+         Szenario: Was wäre wenn die schöne, neue Welt untergeht
+      """
+
+
+  @reuse.colocated_test
+  Scenario: Ensure JUnit reports can be created from a foreign language
+    Given I use the current directory as working directory
+    When I run "behave -f plain --junit --no-timings tools/test-features/french.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      5 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Fonctionnalité: testing stuff
+         Scénario: test stuff
+           Etant donné I am testing stuff ... passed
+           Quand I exercise it work ... passed
+           Alors it will work ... passed
+         Scénario: test more stuff
+            Etant donné I am testing stuff ... passed
+            Alors it will work ... passed
+      """