busser-behave 0.1.3

data/vendor/behave/features/runner.dry_run.feature

@@ -0,0 +1,184 @@
+@sequential
+Feature: Runner should support a --dry-run option
+
+    As a tester
+    I want to check if behave tests are syntactically correct
+    And all step definitions exist
+    Before I actually run the tests (by executing steps).
+
+    . SPECIFICATION: Dry-run mode
+    .   * Undefined steps are detected
+    .   * Marks steps as "untested" or "undefined"
+    .   * Marks scenarios as "untested"
+    .   * Marks features as "untested"
+    .   * Causes no failed scenarios, features
+    .   * Causes failed test-run when undefined steps are found.
+
+    @setup
+    Scenario: Feature 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
+
+            @step('a step fails')
+            def step_fails(context):
+                assert False, "XFAIL"
+            """
+        And a file named "features/alice.feature" with:
+            """
+            Feature: Alice
+
+                @selected
+                Scenario: A1
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+
+                @other_selected
+                Scenario: A2
+                    Given a step passes
+                    When a step fails
+                    Then a step passes
+
+                @selected
+                Scenario: A3
+                    Given a step passes
+
+                @selected
+                Scenario: A4
+                    Given a step fails
+            """
+        And a file named "features/bob.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+
+                Scenario: B2
+                    Given a step passes
+                    When a step fails
+                    Then a step passes
+            """
+        And a file named "features/undefined_steps.feature" with:
+            """
+            Feature: Undefined Steps
+
+                @selected
+                Scenario: U1
+                    Given a step passes
+                    When a step is undefined
+                    Then a step fails
+
+                @other_selected
+                Scenario: U2 fails
+                    Given a step is undefined
+                    When a step passes
+                    And  a step fails
+                    Then a step is undefined
+            """
+
+
+    Scenario: Dry-run one feature should mark feature/scenarios/steps as untested
+        When I run "behave -f plain --dry-run features/alice.feature"
+        Then it should pass with:
+            """
+            0 features passed, 0 failed, 0 skipped, 1 untested
+            0 scenarios passed, 0 failed, 0 skipped, 4 untested
+            0 steps passed, 0 failed, 0 skipped, 0 undefined, 8 untested
+            """
+        And the command output should contain
+            """
+            Scenario: A1
+            """
+        And the command output should contain:
+            """
+            Scenario: A2
+            """
+        And the command output should contain:
+            """
+            Scenario: A3
+            """
+        And the command output should contain:
+            """
+            Scenario: A4
+            """
+        And note that "all scenarios of this feature are contained"
+
+    Scenario: Dry-run one feature with tags should mark skipped scenario/steps as skipped
+        When I run "behave -f plain --dry-run --tags=@selected --no-skipped features/alice.feature"
+        Then it should pass with:
+            """
+            0 features passed, 0 failed, 0 skipped, 1 untested
+            0 scenarios passed, 0 failed, 1 skipped, 3 untested
+            0 steps passed, 0 failed, 3 skipped, 0 undefined, 5 untested
+            """
+        And the command output should contain:
+            """
+            Scenario: A1
+            """
+        And the command output should contain:
+            """
+            Scenario: A3
+            """
+        And the command output should contain:
+            """
+            Scenario: A4
+            """
+        But the command output should not contain:
+            """
+            Scenario: A2
+            """
+        And note that "only tagged scenarios of this feature are contained (3 of 4)"
+
+
+    Scenario: Dry-run two features
+        When I run "behave --dry-run features/alice.feature features/bob.feature"
+        Then it should pass with:
+            """
+            0 features passed, 0 failed, 0 skipped, 2 untested
+            0 scenarios passed, 0 failed, 0 skipped, 6 untested
+            0 steps passed, 0 failed, 0 skipped, 0 undefined, 14 untested
+            """
+
+    Scenario: Dry-run one feature with undefined steps
+        When I run "behave --dry-run features/undefined_steps.feature"
+        Then it should fail with:
+            """
+            0 features passed, 0 failed, 0 skipped, 1 untested
+            0 scenarios passed, 0 failed, 0 skipped, 2 untested
+            0 steps passed, 0 failed, 0 skipped, 3 undefined, 4 untested
+            """
+
+    Scenario: Dry-run two features, one with undefined steps
+        When I run "behave --dry-run features/alice.feature features/undefined_steps.feature"
+        Then it should fail with:
+            """
+            0 features passed, 0 failed, 0 skipped, 2 untested
+            0 scenarios passed, 0 failed, 0 skipped, 6 untested
+            0 steps passed, 0 failed, 0 skipped, 3 undefined, 12 untested
+            """
+
+    Scenario: Dry-run two features, one with undefined steps and use tags
+        When I run "behave --dry-run --tags=@selected features/alice.feature features/undefined_steps.feature"
+        Then it should fail with:
+            """
+            0 features passed, 0 failed, 0 skipped, 2 untested
+            0 scenarios passed, 0 failed, 2 skipped, 4 untested
+            0 steps passed, 0 failed, 7 skipped, 1 undefined, 7 untested
+            """
+
+    Scenario: Dry-run two features, one with undefined steps and use other tags
+        When I run "behave --dry-run --tags=@other_selected features/alice.feature features/undefined_steps.feature"
+        Then it should fail with:
+            """
+            0 features passed, 0 failed, 0 skipped, 2 untested
+            0 scenarios passed, 0 failed, 4 skipped, 2 untested
+            0 steps passed, 0 failed, 8 skipped, 2 undefined, 5 untested
+            """

data/vendor/behave/features/runner.feature_listfile.feature

@@ -0,0 +1,223 @@
+@sequential
+Feature: Feature Listfile (List of feature filenames/directories)
+
+    As a tester
+    I want to run a list of features together
+    And I do not want to provide the list each time
+    But provide a text file that contains the list of features.
+
+    . SPECIFICATION: behave file args
+    .  * Prepend an '@' char (AT) to the feature configfile name to classify it.
+    .
+    . SPECIFICATION: Feature listfile (text file)
+    .  * Each line contains a feature filename or directory with features
+    .  * Feature filenames/dirnames are relative to the feature configfile
+    .  * Empty lines are removed while reading
+    .  * Comment lines are removed while reading (start with '#' char)
+    .  * Wildcards are expanded to select 0..N files or directories.
+    .  * Wildcards for file locations are not supported (only filenames or dirs).
+    .
+    . SPECIFICATION: Runner
+    .  * Feature configfile with unknown/not found feature files
+    .    cause runner to fail.
+    .
+    . NOTE: Also supported by Cucumber.
+    . RELATED: issue #75
+
+
+  @setup
+  Scenario: Test 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/alice.feature" with:
+      """
+      Feature: Alice
+        Scenario:
+          Given a step passes
+      """
+    And   a file named "features/bob.feature" with:
+      """
+      Feature: Bob
+        Scenario:
+          Given a step passes
+      """
+
+
+  Scenario: Use @feature_listfile in WORKDIR directory (above features/)
+    Given a file named "alice_and_bob2.txt" with:
+      """
+      features/alice.feature
+      features/bob.feature
+      """
+    When I run "behave @alice_and_bob2.txt"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      2 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+
+  Scenario: Use @feature_listfile in features/ subdirectory (Case 2)
+    Given a file named "features/alice_and_bob.txt" with:
+      """
+      alice.feature
+      bob.feature
+      """
+    When I run "behave @features/alice_and_bob.txt"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      2 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Use @feature_listfile with some empty lines
+    Given a file named "features/alice_and_bob_with_empty_lines.txt" with:
+      """
+      alice.feature
+
+      bob.feature
+      """
+    When I run "behave @features/alice_and_bob_with_empty_lines.txt"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      2 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Use @feature_listfile with some comment lines
+    Given a file named "features/alice_and_bob_with_comment_lines.txt" with:
+      """
+      alice.feature
+      # -- USE: bob (comment line)
+      bob.feature
+      """
+    When I run "behave @features/alice_and_bob_with_comment_lines.txt"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      2 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Use @feature_listfile with wildcards (Case 1)
+
+    Use feature list-file with wildcard pattern to select features.
+
+    Given a file named "with_wildcard_feature.txt" with:
+      """
+      features/a*.feature
+      """
+    When I run "behave -f plain --no-timings @with_wildcard_feature.txt"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Alice
+
+        Scenario:
+          Given a step passes ... passed
+      """
+
+  Scenario: Use @feature_listfile with wildcards (Case 2)
+
+    Use feature list-file with:
+      - normal filename
+      - wildcard pattern to select features
+
+    Given a file named "with_wildcard_feature2.txt" with:
+      """
+      features/alice.feature
+      features/b*.feature
+      """
+    When I run "behave -f plain --no-timings @with_wildcard_feature2.txt"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Alice
+
+        Scenario:
+          Given a step passes ... passed
+
+      Feature: Bob
+
+        Scenario:
+          Given a step passes ... passed
+      """
+
+  Scenario: Use @feature_listfile with wildcards for file location (not supported)
+
+    Note that wildcards are not supported when file locations are used.
+
+    Given a file named "with_wildcard_location.txt" with:
+      """
+      features/a*.feature:3
+      """
+    When I run "behave -f plain --no-timings @with_wildcard_location.txt"
+    Then it should fail with:
+      """
+      ConfigError: No steps directory in '{__WORKDIR__}'
+      """
+
+
+  Scenario: Use empty @feature_listfile (Case 1)
+    Given an empty file named "empty.txt"
+    When I run "behave @empty.txt"
+    Then it should fail with:
+      """
+      No steps directory in '{__WORKDIR__}'
+      """
+
+  Scenario: Use empty @feature_listfile in features subdirectory (Case 2)
+    Given an empty file named "features/empty.txt"
+    When I run "behave @features/empty.txt"
+    Then it should pass with:
+      """
+      0 features passed, 0 failed, 0 skipped
+      """
+
+  Scenario: Use @feature_listfile with unknown feature file (Case 1)
+    Given a file named "with_unknown_feature.txt" with:
+      """
+      features/alice.feature
+      features/UNKNOWN.feature
+      """
+    When I run "behave @with_unknown_feature.txt"
+    Then it should fail with:
+      """
+      Error: [Errno 2] No such file or directory: '{__WORKDIR__}/features/UNKNOWN.feature'
+      """
+
+  Scenario: Use @feature_listfile with unknown feature file (Case 2)
+    Given a file named "features/with_unknown_feature2.txt" with:
+      """
+      UNKNOWN.feature
+      """
+    When I run "behave @features/with_unknown_feature2.txt"
+    Then it should fail with:
+      """
+      Error: [Errno 2] No such file or directory: '{__WORKDIR__}/features/UNKNOWN.feature'
+      """
+
+  Scenario: Use unknown @feature_listfile
+    When I run "behave @unknown_feature_configfile.txt"
+    Then it should fail with:
+      """
+      FileNotFoundError: unknown_feature_configfile.txt
+      """

data/vendor/behave/features/runner.hook_errors.feature

@@ -0,0 +1,382 @@
+Feature: Hooks processing in case of errors (exceptions)
+
+  . SPECIFICATION:
+  .   * Hook errors in before_all/after_all hook aborts the test run (and fail).
+  .   * Hook errors in before_feature/after_feature causes the feature to fail.
+  .   * Hook errors in before_feature causes feature scenarios to be skipped (untested).
+  .   * Hook errors in before_scenario/after_scenario causes the scenario to fail.
+  .   * Hook errors in before_scenario causes scenario steps to be skipped (untested).
+  .   * Hook errors in before_step/after_step causes step to fail.
+  .   * Hook errors in before_tag/after_tag of a feature  causes feature  to fail.
+  .   * Hook errors in before_tag/after_tag of a scenario causes scenario to fail.
+  .   * If a hook error occurs in a "before_xxx" hook,
+  .     then the "after_xxx" hook will also be called (to cleanup some stuff).
+  .
+  . NOTE:
+  . The --verbose flag can be used to show the exception traceback.
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+      """
+      from behave import step
+
+      @step(u'{word:w} step passes')
+      def step(context, word):
+          pass
+      """
+    And   a file named "features/passing.feature" with:
+        """
+        @foo
+        Feature: Alice
+          @soo
+          Scenario: A1
+            Given a step passes
+        """
+    And a file named "features/environment.py" with:
+        """
+        from __future__ import print_function
+
+        def cause_hook_to_fail():
+            raise RuntimeError("FAIL")
+
+        def before_all(context):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_all":
+                cause_hook_to_fail()
+
+        def after_all(context):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_all":
+                print("called_hook:after_all")
+            if userdata.get("HOOK_ERROR_LOC") == "after_all":
+                cause_hook_to_fail()
+
+        def before_feature(context, feature):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_feature":
+                cause_hook_to_fail()
+
+        def after_feature(context, feature):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_feature":
+                print("called_hook:after_feature")
+            if userdata.get("HOOK_ERROR_LOC") == "after_feature":
+                cause_hook_to_fail()
+
+        def before_scenario(context, scenario):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_scenario":
+                cause_hook_to_fail()
+
+        def after_scenario(context, scenario):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_scenario":
+                print("called_hook:after_scenario")
+            if userdata.get("HOOK_ERROR_LOC") == "after_scenario":
+                cause_hook_to_fail()
+
+        def before_step(context, step):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_step":
+                cause_hook_to_fail()
+
+        def after_step(context, step):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_step":
+                print("called_hook:after_step")
+            if userdata.get("HOOK_ERROR_LOC") == "after_step":
+                cause_hook_to_fail()
+
+        def before_tag(context, tag):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_tag":
+                error_tag = userdata.get("HOOK_ERROR_TAG")
+                if not error_tag or tag == error_tag:
+                    cause_hook_to_fail()
+
+        def after_tag(context, tag):
+            userdata = context.config.userdata
+            if userdata.get("HOOK_ERROR_LOC") == "before_tag":
+                error_tag = userdata.get("HOOK_ERROR_TAG")
+                if tag == error_tag:
+                    print("called_hook:after_tag: tag=%s" % tag)
+            if userdata.get("HOOK_ERROR_LOC") == "after_tag":
+                error_tag = userdata.get("HOOK_ERROR_TAG")
+                if not error_tag or tag == error_tag:
+                    cause_hook_to_fail()
+        """
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        show_skipped = false
+        show_timings = false
+        """
+
+
+    @hook.before_all
+    Scenario: Hook error in before_all
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_all features/passing.feature"
+      Then it should fail with
+          """
+          HOOK-ERROR in before_all: RuntimeError: FAIL
+
+          ABORTED: By user.
+          called_hook:after_all
+          0 features passed, 0 failed, 0 skipped, 1 untested
+          0 scenarios passed, 0 failed, 0 skipped, 1 untested
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 1 untested
+          """
+      But note that "the after_all hook is called, too"
+
+
+    @hook.after_all
+    Scenario: Hook error in after_all
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_all features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... passed
+
+          HOOK-ERROR in after_all: RuntimeError: FAIL
+          1 feature passed, 0 failed, 0 skipped
+          1 scenario passed, 0 failed, 0 skipped
+          1 step passed, 0 failed, 0 skipped, 0 undefined
+          """
+
+
+    @hook.before_feature
+    Scenario: Hook error in before_feature
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_feature features/passing.feature"
+      Then it should fail with:
+          """
+          HOOK-ERROR in before_feature: RuntimeError: FAIL
+          Feature: Alice
+          called_hook:after_feature
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 0 failed, 0 skipped, 1 untested
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 1 untested
+          """
+      But note that "the after_feature hook is called, too."
+
+
+    @hook.after_feature
+    Scenario: Hook error in after_feature
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_feature features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+            Scenario: A1
+              Given a step passes ... passed
+          HOOK-ERROR in after_feature: RuntimeError: FAIL
+
+          0 features passed, 1 failed, 0 skipped
+          1 scenario passed, 0 failed, 0 skipped
+          1 step passed, 0 failed, 0 skipped, 0 undefined
+          """
+
+
+    @hook.before_scenario
+    Scenario: Hook error in before_scenario
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_scenario features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+          HOOK-ERROR in before_scenario: RuntimeError: FAIL
+            Scenario: A1
+          called_hook:after_scenario
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 1 untested
+          """
+      But note that "the after_scenario hook is called, too."
+
+
+    @hook.after_scenario
+    Scenario: Hook error in after_scenario
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_scenario features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... passed
+          HOOK-ERROR in after_scenario: RuntimeError: FAIL
+
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          1 step passed, 0 failed, 0 skipped, 0 undefined
+          """
+
+    @hook.before_step
+    Scenario: Hook error in before_step
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_step features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... failed
+
+          Captured stdout:
+            HOOK-ERROR in before_step: RuntimeError: FAIL
+            called_hook:after_step
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          0 steps passed, 1 failed, 0 skipped, 0 undefined
+          """
+      But note that "the after_step hook is called, too."
+
+
+    @hook.after_step
+    Scenario: Hook error in after_step
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_step features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... failed
+
+          Captured stdout:
+            HOOK-ERROR in after_step: RuntimeError: FAIL
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          0 steps passed, 1 failed, 0 skipped, 0 undefined
+          """
+
+
+    @hook.before_tag
+    Scenario: Hook error in before_tag for feature
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_tag -D HOOK_ERROR_TAG=foo features/passing.feature"
+      Then it should fail with:
+          """
+          HOOK-ERROR in before_tag(tag=foo): RuntimeError: FAIL
+          Feature: Alice
+          called_hook:after_tag: tag=foo
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 0 failed, 0 skipped, 1 untested
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 1 untested
+          """
+      And the command output should contain:
+          """
+          HOOK-ERROR in before_tag(tag=foo): RuntimeError: FAIL
+          Feature: Alice
+          """
+      But note that "the hook-error in before_tag of the feature causes it to fail and be skipped (untested)"
+      And note that "the after_tag hook is still called"
+
+
+    @hook.after_tag
+    Scenario: Hook error in after_tag for feature
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_tag -D HOOK_ERROR_TAG=foo features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... passed
+          HOOK-ERROR in after_tag(tag=foo): RuntimeError: FAIL
+
+          0 features passed, 1 failed, 0 skipped
+          1 scenario passed, 0 failed, 0 skipped
+          1 step passed, 0 failed, 0 skipped, 0 undefined
+          """
+      But note that "the hook-error in after_tag of the scenario causes it to fail"
+
+
+    @hook.before_tag
+    Scenario: Hook error in before_tag for scenario
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_tag -D HOOK_ERROR_TAG=soo features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+          HOOK-ERROR in before_tag(tag=soo): RuntimeError: FAIL
+            Scenario: A1
+          called_hook:after_tag: tag=soo
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 1 untested
+          """
+      But note that "the hook-error in before_tag of the scenario causes it to fail and be skipped (untested)"
+      And note that "the after_tag hook is still called"
+
+
+    @hook.after_tag
+    Scenario: Hook error in after_tag for scenario
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_tag -D HOOK_ERROR_TAG=soo features/passing.feature"
+      Then it should fail with:
+          """
+          Feature: Alice
+
+            Scenario: A1
+              Given a step passes ... passed
+          HOOK-ERROR in after_tag(tag=soo): RuntimeError: FAIL
+
+          Failing scenarios:
+            features/passing.feature:4  A1
+
+          0 features passed, 1 failed, 0 skipped
+          0 scenarios passed, 1 failed, 0 skipped
+          1 step passed, 0 failed, 0 skipped, 0 undefined
+          """
+      But note that "the hook-error in after_tag of the scenario causes it to fail"
+
+
+    @skipped.hook.after_feature
+    Scenario: Skipped feature with potential hook error (hooks are not run)
+
+      This goes unnoticed because hooks are not run for a skipped feature/scenario.
+      NOTE: Except if before_feature(), before_scenario() hook skips the feature/scenario.
+
+      When I run "behave -f plain -D HOOK_ERROR_LOC=after_feature -t ~@foo features/passing.feature"
+      Then it should pass with:
+          """
+          0 features passed, 0 failed, 1 skipped
+          0 scenarios passed, 0 failed, 1 skipped
+          0 steps passed, 0 failed, 1 skipped, 0 undefined
+          """
+      But note that "hooks are not executed for skipped features/scenarios"
+
+
+    Scenario: Show hook error details (traceback)
+      When I run "behave -f plain -D HOOK_ERROR_LOC=before_feature --verbose features/passing.feature"
+      Then it should fail with:
+          """
+          HOOK-ERROR in before_feature: RuntimeError: FAIL
+          """
+      And the command output should contain:
+          """
+            self.hooks[name](context, *args)
+          File "features/environment.py", line 21, in before_feature
+            cause_hook_to_fail()
+          File "features/environment.py", line 4, in cause_hook_to_fail
+            raise RuntimeError("FAIL")
+          """
+      But note that "the traceback caused by the hook-error is shown"