busser-behave 0.1.3

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

@@ -0,0 +1,76 @@
+@issue
+Feature: Issue #383 -- Handle (custom) Type parsing errors better
+
+  . Custom type parsing errors that occur during step matching
+  . lead currently to abortion of the test run.
+  . In addition, the actual reason what occured is very low-level.
+  .
+  . DESIRED:
+  .   * Protect test runner/execution logic
+  .   * Improve handling of these kind of errors
+  .   * Provide better diagnostics
+  .   * Continue to run tests (if possible)
+  .
+  . NOTE:
+  . This kind of problem is often caused by regular expressions that
+  . are not specific enough for the type conversion (LAZY-REGEXP DESIGN).
+  . Therefore, the problem occurs during type conversion/parsing phase
+  . and not in the initial step detection/matching phase.
+  .
+  . RELATED: features/step_param.custom_types.feature
+
+
+  Scenario: Type conversion fails
+    Given a new working directory
+    And a file named "features/steps/bad_type_converter_steps.py" with:
+        """
+        from behave import step, register_type
+        import parse
+
+        @parse.with_pattern(r".*")  # -- NOTE: Wildcard pattern, accepts anything.
+        def parse_fails(text):
+            raise ValueError(text)
+
+        register_type(BadType=parse_fails)
+
+        @step('a param with "BadType:{value:BadType}"')
+        def step_param_with_badtype_value(context, value):
+            assert False, "SHOULD_NEVER_COME_HERE: BadType converter raises error."
+        """
+    And a file named "features/steps/reused_steps.py" with:
+        """
+        from behave4cmd0 import passing_steps
+        """
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        show_timings = false
+        """
+    And a file named "features/example.type_conversion_fails.feature" with:
+        """
+        Feature: Type Conversion Fails
+          Scenario: BadType raises ValueError during type conversion
+            Given a param with "BadType:BAD_VALUE"
+
+          Scenario: Ensure other scenarios are executed
+            Then another step passes
+        """
+    When I run "behave -f plain features/example.type_conversion_fails.feature"
+    Then it should fail with:
+        """
+        1 scenario passed, 1 failed, 0 skipped
+        1 step passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Scenario: BadType raises ValueError during type conversion
+          Given a param with "BadType:BAD_VALUE" ... failed
+        Traceback (most recent call last):
+        """
+    And the command output should contain:
+        """
+        File "features/steps/bad_type_converter_steps.py", line 6, in parse_fails
+          raise ValueError(text)
+        """
+    And the command output should contain "ValueError: BAD_VALUE"
+    And the command output should contain "StepParseError: BAD_VALUE"

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

@@ -0,0 +1,103 @@
+@issue
+Feature: Issue #384 -- Active Tags fail with ScenarioOutline
+
+  . ScenarioOutline can currently not be used with active-tag(s).
+  . REASON: Template mechanism transforms active-tag into invalid active-tag per example row.
+  .
+  . RELATED: features/tag.active_tags.feature
+
+
+    Background:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+
+        # -- REUSE: Step definitions.
+        from behave4cmd0 import note_steps
+        """
+      And a file named "features/environment.py" with:
+        """
+        from behave.tag_matcher import ActiveTagMatcher, setup_active_tag_values
+        import sys
+
+        # -- ACTIVE TAG SUPPORT: @use.with_{category}={value}, ...
+        active_tag_value_provider = {
+            "browser":   "chrome",
+            "webserver": "apache",
+        }
+        active_tag_matcher = ActiveTagMatcher(active_tag_value_provider)
+
+        def before_all(context):
+            setup_active_tag_values(active_tag_value_provider, context.config.userdata)
+
+        def before_scenario(context, scenario):
+            if active_tag_matcher.should_exclude_with(scenario.effective_tags):
+                sys.stdout.write("ACTIVE-TAG DISABLED: Scenario %s\n" % scenario.name)
+                scenario.skip(active_tag_matcher.exclude_reason)
+        """
+      And a file named "behave.ini" with:
+        """
+        [behave]
+        default_format = pretty
+        show_timings = no
+        show_skipped = no
+        color = no
+        """
+      And a file named "features/outline.active_tags.feature" with:
+        """
+        Feature:
+
+          @use.with_browser=chrome
+          Scenario Outline: Alice -- <name>, <language>
+            Given a step passes
+            But note that "<name> can speak <language>"
+
+            Examples:
+              | name     | language |
+              | Anna     | German   |
+              | Arabella | English  |
+        """
+
+
+    Scenario: ScenarioOutline with enabled active-tag is executed
+      When I run "behave -D browser=chrome features/outline.active_tags.feature"
+      Then it should pass with:
+        """
+        2 scenarios passed, 0 failed, 0 skipped
+        4 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+      And the command output should contain:
+        """
+        @use.with_browser=chrome
+        Scenario Outline: Alice -- Anna, German -- @1.1   # features/outline.active_tags.feature:10
+          Given a step passes                             # features/steps/pass_steps.py:3
+          But note that "Anna can speak German"           # ../behave4cmd0/note_steps.py:15
+
+        @use.with_browser=chrome
+        Scenario Outline: Alice -- Arabella, English -- @1.2   # features/outline.active_tags.feature:11
+          Given a step passes                                  # features/steps/pass_steps.py:3
+          But note that "Arabella can speak English"           # ../behave4cmd0/note_steps.py:15
+        """
+      And the command output should not contain "ACTIVE-TAG DISABLED: Scenario Alice"
+      But note that "we check now for the specific syndrome"
+      And the command output should not contain "@use.with_browserchrome"
+      But the command output should contain "@use.with_browser=chrome"
+
+
+    Scenario: ScenarioOutline with disabled active-tag is skipped
+      When I run "behave -D browser=other features/outline.active_tags.feature"
+      Then it should pass with:
+        """
+        0 scenarios passed, 0 failed, 2 skipped
+        0 steps passed, 0 failed, 4 skipped, 0 undefined
+        """
+      And the command output should contain:
+        """
+        ACTIVE-TAG DISABLED: Scenario Alice -- Anna, German -- @1.1
+        ACTIVE-TAG DISABLED: Scenario Alice -- Arabella, English -- @1.2
+        """

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

@@ -0,0 +1,109 @@
+@issue
+@change_request
+Feature: Issue #385 -- before_scenario called too late
+
+    . RATIONALE:
+    . Due to:
+    .
+    .   * skip scenario/feature support in before_scenario (and before_feature) hooks
+    .   * active-tags
+    .
+    . formatters are now called to early (for before feature/scenario functionality).
+    . Formatters should be called after the before-hooks are processed.
+    .
+    . NOTES:
+    .  * Test uses show_skipped=false to ensure that at least the
+    .    scenario/feature title is shown with plain formatter.
+
+    @setup
+    Scenario:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/environment.py" with:
+        """
+        from __future__ import print_function
+
+        def before_feature(context, feature):
+            if "skip" in feature.tags:
+                print("SKIP-FEATURE: %s" % feature.name)
+                feature.mark_skipped()
+
+        def before_scenario(context, scenario):
+            if "skip" in scenario.tags:
+                print("SKIP-SCENARIO: %s" % scenario.name)
+                scenario.mark_skipped()
+        """
+      And a file named "behave.ini" with:
+        """
+        [behave]
+        show_skipped = false
+        """
+
+    Scenario: Formatter is not called with skip in before_scenario hook
+      Given a file named "features/alice.feature" with:
+        """
+        Feature: Alice
+
+          @skip
+          Scenario: Alice and Bob
+            Given a step passes
+
+          Scenario: Alice in China
+            When another step passes
+        """
+      When I run "behave -f plain features/alice.feature"
+      Then it should pass with:
+        """
+        1 scenario passed, 0 failed, 1 skipped
+        """
+      And the command output should contain:
+        """
+        SKIP-SCENARIO: Alice and Bob
+
+        Scenario: Alice in China
+          When another step passes ... passed
+        """
+      But the command output should not contain:
+        """
+        Scenario: Alice and Bob
+        SKIP-FEATURE: Alice and Bob
+        """
+      And the command output should not contain "Scenario: Alice and Bob"
+
+
+    Scenario: Formatter is not called with skip in before_feature hook
+      Given a file named "features/bob.feature" with:
+        """
+        @skip
+        Feature: Bob
+
+          Scenario: Bob and Alice
+            Given a step passes
+
+          Scenario: Bob in China
+            When another step passes
+        """
+      When I run "behave -f plain features/bob.feature"
+      Then it should pass with:
+        """
+        SKIP-FEATURE: Bob
+
+        0 features passed, 0 failed, 1 skipped
+        0 scenarios passed, 0 failed, 2 skipped
+        """
+      But the command output should not contain:
+        """
+        Feature: Bob
+        SKIP-FEATURE: Bob
+        """
+      And the command output should not contain "Feature: Bob"
+      And the command output should not contain "Scenario: Bob and Alice"
+      And the command output should not contain "Scenario: Bob in China"
+      And note that "all scenarios of the feature are also skipped"

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

@@ -0,0 +1,66 @@
+@issue
+@unicode
+Feature: Issue #424 -- Unicode output problem when fails in nested steps
+
+    . HINTS:
+    .   * Python step file should have encoding line (# -*- coding: ... -*-)
+    .   * Assert failure message should use unicode-string instead of byte-string
+
+    Scenario:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/steps/steps.py" with:
+        """
+        # -*- coding: UTF-8 -*-
+        # NOTE: Python2 requires encoding to decode special chars correctly.
+        from behave import step
+
+        @step('I press the big red button')
+        def step_press_red_button(context):
+            assert False, u"Ungültiger Wert"  # HINT: Special chars require Unicode.
+
+        @step('I call the nested step with the "red button"')
+        def step_press_red_button(context):
+            context.execute_steps(u'When I press the big red button')
+        """
+      And a file named "behave.ini" with:
+          """
+          [behave]
+          show_timings = false
+          """
+      And a file named "features/alice.feature" with:
+        """
+        Feature:
+
+          Scenario: Use step directly
+            When I press the big red button
+
+          Scenario: Use nested step
+            Given another step passes
+            When I call the nested step with the "red button"
+        """
+      When I run "behave -f plain features/alice.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 2 failed, 0 skipped
+        1 step passed, 2 failed, 0 skipped, 0 undefined
+        """
+      And the command output should contain:
+        """
+        Scenario: Use step directly
+          When I press the big red button ... failed
+        Assertion Failed: Ungültiger Wert
+
+        Scenario: Use nested step
+          Given another step passes ... passed
+          When I call the nested step with the "red button" ... failed
+        Assertion Failed: FAILED SUB-STEP: When I press the big red button
+        Substep info: Assertion Failed: Ungültiger Wert
+        """

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

@@ -0,0 +1,116 @@
+@issue
+@junit
+Feature: Issue #446 -- Support scenario hook-errors with JUnitReporter
+
+  . Currently, when a hook error occurs in:
+  .
+  .   * before_scenario()
+  .   * after_scenario()
+  .
+  . a sanity check in the JUnitReporter prevents sane JUnit XML output.
+
+
+    @setup
+    Scenario: Skip scenario without steps
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/before_scenario_failure.feature" with:
+        """
+        Feature: Alice
+          @hook_failure.before_scenario
+          Scenario: A1
+            Given a step passes
+        """
+      And a file named "features/after_scenario_failure.feature" with:
+        """
+        Feature: Bob
+          @hook_failure.after_scenario
+          Scenario: B1
+            Given another step passes
+        """
+      And a file named "features/environment.py" with:
+        """
+        def cause_hook_failure():
+            raise RuntimeError("OOPS")
+
+        def before_scenario(context, scenario):
+            if "hook_failure.before_scenario" in scenario.tags:
+                cause_hook_failure()
+
+        def after_scenario(context, scenario):
+            if "hook_failure.after_scenario" in scenario.tags:
+                cause_hook_failure()
+        """
+      And a file named "behave.ini" with:
+        """
+        [behave]
+        show_timings = false
+
+        [behave.userdata]
+        behave.reporter.junit.show_timestamp = False
+        behave.reporter.junit.show_hostname = False
+        """
+
+    Scenario: Hook error in before_scenario()
+      When I run "behave -f plain --junit features/before_scenario_failure.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        """
+      And the command output should contain:
+        """
+        HOOK-ERROR in before_scenario: RuntimeError: OOPS
+        """
+      And the file "reports/TESTS-before_scenario_failure.xml" should contain:
+        """
+        <testsuite errors="1" failures="0" name="before_scenario_failure.Alice" skipped="0" tests="1"
+        """
+      And the file "reports/TESTS-before_scenario_failure.xml" should contain:
+        """
+        <error message="HOOK-ERROR in before_scenario: RuntimeError: OOPS" type="RuntimeError">
+        """
+      And the file "reports/TESTS-before_scenario_failure.xml" should contain:
+        """
+        File "features/environment.py", line 6, in before_scenario
+          cause_hook_failure()
+        File "features/environment.py", line 2, in cause_hook_failure
+          raise RuntimeError("OOPS")
+        """
+      And note that "the traceback is contained in the XML element <error/>"
+
+
+    Scenario: Hook error in after_scenario()
+      When I run "behave -f plain --junit features/after_scenario_failure.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        """
+      And the command output should contain:
+        """
+          Scenario: B1
+            Given another step passes ... passed
+        HOOK-ERROR in after_scenario: RuntimeError: OOPS
+        """
+      And the file "reports/TESTS-after_scenario_failure.xml" should contain:
+        """
+        <testsuite errors="1" failures="0" name="after_scenario_failure.Bob" skipped="0" tests="1"
+        """
+      And the file "reports/TESTS-after_scenario_failure.xml" should contain:
+        """
+        <error message="HOOK-ERROR in after_scenario: RuntimeError: OOPS" type="RuntimeError">
+        """
+      And the file "reports/TESTS-after_scenario_failure.xml" should contain:
+        """
+        File "features/environment.py", line 10, in after_scenario
+          cause_hook_failure()
+        File "features/environment.py", line 2, in cause_hook_failure
+          raise RuntimeError("OOPS")
+        """
+      And note that "the traceback is contained in the XML element <error/>"