busser-behave 0.1.3

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

@@ -0,0 +1,122 @@
+@sequential
+Feature: Runner should stop after first failure if --stop option is used
+
+    As a tester
+    To abort testing early (sometimes)
+    When the first failure occurs.
+
+
+    @setup
+    Scenario: Test Setup
+        Given a new working directory
+        And a file named "features/steps/steps.py" with:
+            """
+            from behave import step
+            import sys
+
+            @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_fails.feature" with:
+            """
+            Feature: Alice
+                Scenario: A1
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+
+                Scenario: A2 fails
+                    Given a step passes
+                    When a step fails
+                    Then a step passes
+
+                Scenario: A3
+                    Given a step passes
+
+                Scenario: A4 fails
+                    Given a step fails
+            """
+        And a file named "features/bob_passes.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+
+                Scenario: B2 fails
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+            """
+
+
+    Scenario: Stop running after first failure with one feature
+        When I run "behave -f plain -T --stop features/alice_fails.feature"
+        Then it should fail with:
+            """
+            Failing scenarios:
+              features/alice_fails.feature:7  A2 fails
+
+            0 features passed, 1 failed, 0 skipped
+            1 scenario passed, 1 failed, 0 skipped, 2 untested
+            4 steps passed, 1 failed, 1 skipped, 0 undefined, 2 untested
+            """
+        And the command output should contain:
+            """
+            Feature: Alice
+                Scenario: A1
+                    Given a step passes ... passed
+                    When a step passes ... passed
+                    Then a step passes ... passed
+
+                Scenario: A2 fails
+                    Given a step passes ... passed
+                    When a step fails ... failed
+                    Assertion Failed: XFAIL
+            """
+        But the command output should not contain:
+            """
+            Scenario: A3
+            """
+
+    Scenario: Stop running after first failure with several features (CASE 1)
+        When I run "behave -f plain -T --stop features/alice_fails.feature features/bob_passes.feature "
+        Then it should fail with:
+            """
+            Failing scenarios:
+              features/alice_fails.feature:7  A2 fails
+
+            0 features passed, 1 failed, 0 skipped, 1 untested
+            1 scenario passed, 1 failed, 0 skipped, 4 untested
+            4 steps passed, 1 failed, 1 skipped, 0 undefined, 8 untested
+            """
+
+    Scenario: Stop running after first failure with several features (CASE 2: Different order)
+        When I run "behave -f plain -T --stop features/bob_passes.feature features/alice_fails.feature"
+        Then it should fail with:
+            """
+            Failing scenarios:
+              features/alice_fails.feature:7  A2 fails
+
+            1 feature passed, 1 failed, 0 skipped
+            3 scenarios passed, 1 failed, 0 skipped, 2 untested
+            10 steps passed, 1 failed, 1 skipped, 0 undefined, 2 untested
+            """
+
+    Scenario: Stop running after first failure with several features (CASE 3: Use directory)
+        When I run "behave -f plain -T --stop features/"
+        Then it should fail with:
+            """
+            Failing scenarios:
+              features/alice_fails.feature:7  A2 fails
+
+            0 features passed, 1 failed, 0 skipped, 1 untested
+            1 scenario passed, 1 failed, 0 skipped, 4 untested
+            4 steps passed, 1 failed, 1 skipped, 0 undefined, 8 untested
+            """

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

@@ -0,0 +1,67 @@
+Feature: Runner Tag logic
+
+  As a tester
+  I want to select scenarios using logical AND/OR of tags
+  In order to conveniently run subsets of these scenarios
+
+  . SPECIFICATION: Tag logic
+  .   See "tag_expression.feature" description.
+  .
+  . RELATED:
+  .  * tag_expression.feature
+
+  Scenario: Select scenarios with 1 tag (@foo)
+    Given a behave model with:
+        | statement  | name | tags              | Comment |
+        | Scenario   | S0   |                   | Untagged    |
+        | Scenario   | S1   | @foo              | With 1 tag  |
+        | Scenario   | S2   | @other            |             |
+        | Scenario   | S3   | @foo @other       | With 2 tags |
+    And note that "are all combinations of 0..2 tags"
+    When I run the behave model with "tags"
+    Then the following scenarios are selected with cmdline:
+        | cmdline        | selected?      | Logic comment |
+        |                | S0, S1, S2, S3 | ALL, no selector |
+        | --tags=@foo    | S1, S3         | @foo          |
+        | --tags=-@foo   | S0, S2         | not @foo      |
+
+
+  Scenario: Use other tag expression variants
+    Given a behave model with:
+        | statement  | name | tags              | Comment |
+        | Scenario   | S0   |                   | Untagged    |
+        | Scenario   | S1   | @foo              | With 1 tag  |
+        | Scenario   | S2   | @other            |             |
+        | Scenario   | S3   | @foo @other       | With 2 tags |
+    Then the following scenarios are selected with cmdline:
+        | cmdline        | selected?      | Logic comment |
+        | --tags=foo     | S1, S3         | @foo,     without optional @  |
+        | --tags=-foo    | S0, S2         | not @foo, without optional @  |
+        | --tags=~foo    | S0, S2         | not @foo, with tilde as minus |
+        | --tags=~@foo   | S0, S2         | not @foo, with tilde and @    |
+    And note that "these tag expression variants can also be used"
+
+
+  Scenario: Select scenarios with 2 tags (@foo, @bar)
+    Given a behave model with:
+        | statement  | name | tags              | Comment |
+        | Scenario   | S0   |                   | Untagged    |
+        | Scenario   | S1   | @foo              | With a tag  |
+        | Scenario   | S2   | @bar              |             |
+        | Scenario   | S3   | @other            |             |
+        | Scenario   | S4   | @foo @bar         | With 2 tags |
+        | Scenario   | S5   | @foo @other       |             |
+        | Scenario   | S6   | @bar @other       |             |
+        | Scenario   | S7   | @foo @bar @other  | With 3 tags |
+    And note that "are all combinations of 0..3 tags"
+    When I run the behave model with "tags"
+    Then the following scenarios are selected with cmdline:
+        | cmdline                    | selected?                      | Logic comment |
+        |                            | S0, S1, S2, S3, S4, S5, S6, S7 | ALL, no selector      |
+        | --tags=@foo,@bar           | S1, S2, S4, S5, S6, S7         | @foo or @bar          |
+        | --tags=@foo,-@bar          | S0, S1, S3, S4, S5, S7         | @foo or not @bar      |
+        | --tags=-@foo,-@bar         | S0, S1, S2, S3, S5, S6         | not @foo or not @bar  |
+        | --tags=@foo  --tags=@bar   | S4, S7                         | @foo and @bar         |
+        | --tags=@foo  --tags=-@bar  | S1, S5                         | @foo and not @bar     |
+        | --tags=-@foo --tags=-@bar  | S0, S3                         | not @foo and not @bar |
+

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

@@ -0,0 +1,23 @@
+Feature: When an unknown formatter is used
+
+
+  Scenario: Unknown formatter is used
+    When I run "behave -f unknown1"
+    Then it should fail with:
+      """
+      behave: error: format=unknown1 is unknown
+      """
+
+  Scenario: Unknown formatter is used together with another formatter
+    When I run "behave -f plain -f unknown1"
+    Then it should fail with:
+      """
+      behave: error: format=unknown1 is unknown
+      """
+
+  Scenario: Two unknown formatters are used
+    When I run "behave -f plain -f unknown1 -f tags -f unknown2"
+    Then it should fail with:
+      """
+      behave: error: format=unknown1, unknown2 is unknown
+      """

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

@@ -0,0 +1,126 @@
+Feature: Use Alternate Step Implementations for Each Test Stage
+
+  As I tester and test writer
+  I want to run the same feature with other step implementations during different testing stages
+  So I can run quick checks in a development environment and detailed checks in a testlab.
+
+  . CONCEPT: TEST STAGE
+  .   A test stage allows you to use different step/environment implementations
+  .   compared to other test stage or the default, unnamed test stage.
+  .
+  .   Examples for test stages are:
+  .     * develop (using the development environment with more diagnostics)
+  .     * product (using the product database, ...)
+  .     * systemtest
+  .     * systemint (system integration)
+  .     * ...
+  .
+  .   NOTE:
+  .   Test stages can be used to adapt to different test environments
+  .   while using these test stages.
+  .
+  .
+  . EXAMPLE DIRECTORY LAYOUT (with default stage and stage=testlab):
+  .
+  .   features/
+  .       +-- steps/                # -- Step implementations for default stage.
+  .       |   +-- foo_steps.py
+  .       +-- testlab_steps/        # -- Step implementations for stage=testlab.
+  .       |   +-- foo_steps.py
+  .       +-- *.feature
+  .       +-- environment.py          # -- Environment for default stage.
+  .       +-- testlab_environment.py  # -- Environment for stage=testlab.
+
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+      And a file named "features/example1.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given I do something in a test stage
+        """
+      And a file named "features/environment.py" with:
+        """
+        def before_all(context):
+            context.use_develop_environment = False
+        """
+      And a file named "features/steps/foo_steps.py" with:
+        """
+        from behave import step
+
+        @step('I do something in a test stage')
+        def step_do_something(context):
+            assert not context.config.stage
+            assert not context.use_develop_environment
+        """
+      And I remove the environment variable "BEHAVE_STAGE"
+
+  Scenario: Use stage=develop
+    Given a file named "features/develop_environment.py" with:
+        """
+        def before_all(context):
+            context.use_develop_environment = True
+        """
+    And a file named "features/develop_steps/foo_steps.py" with:
+        """
+        from behave import step
+
+        @step('I do something in a test stage')
+        def step_do_something(context):
+            assert context.config.stage == "develop"
+            assert context.use_develop_environment
+        """
+    When I run "behave -c --stage=develop features/example1.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
+        """
+    And the command output should contain:
+        """
+        Scenario:                              # features/example1.feature:2
+          Given I do something in a test stage # features/develop_steps/foo_steps.py:3
+        """
+
+  Scenario: Use default stage
+    Given I remove the environment variable "BEHAVE_STAGE"
+     When I run "behave -c features/example1.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
+        """
+    And the command output should contain:
+        """
+        Scenario:                              # features/example1.feature:2
+          Given I do something in a test stage # features/steps/foo_steps.py:3
+        """
+
+  Scenario: Use the BEHAVE_STAGE environment variable to define the test stage
+    Given I set the environment variable "BEHAVE_STAGE" to "develop"
+    When I run "behave -c features/example1.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
+        """
+    And the command output should contain:
+        """
+        Scenario:                              # features/example1.feature:2
+          Given I do something in a test stage # features/develop_steps/foo_steps.py:3
+        """
+    But note that "I should better remove it again (TEARDOWN PHASE)"
+    And I remove the environment variable "BEHAVE_STAGE"
+
+
+  Scenario: Using an unknown stage
+    When I run "behave -c --stage=unknown features/example1.feature"
+    Then it should fail with:
+        """
+        ConfigError: No unknown_steps directory
+        """

data/vendor/behave/features/scenario.description.feature

@@ -0,0 +1,171 @@
+Feature: Scenario Description
+
+    As a tester
+    I want to explain the rationale of a test scenario or scenario outline
+    Before I actually execute the steps.
+
+    . SPECIFICATION: Scenario Description
+    .   * Scenario descriptions are in optional section between
+    .     Scenario line and the first step.
+    .   * All description lines are added to the scenario description.
+    .   * Empty lines are not part of the scenario description (are removed).
+    .   * Comment lines are not part of the scenario description (are removed).
+    .   * A Scenario/ScenarioOutline with a scenario description,
+    .     but without steps is valid (to support preparation of scenarios).
+    .
+    . SPECIFICATION: A scenario description line...
+    .   * must not start with step keywords, like:
+    .
+    .       Given, When, Then, And, But, etc.
+    .       (including lower-case versions)
+    .
+    .   * must not start with '*' (ASTERISK) due to generic step keyword ambiguity
+    .   * must not start with '@' (AT) due to tag ambiguity
+    .     (supporting: scenario without steps but with step description).
+    .   * may start with '|' (table-cell-separator).
+    .   * does not contain only whitespace chars (empty line, filtered-out).
+    .   * does not start with '#' (HASH) after whitespace chars (comment line).
+    .
+    . GRAMMAR STRUCTURE:
+    .   Scenario-Line : 1
+    .       Scenario-Description-Line : 0 .. N
+    .       Step-Line : 0 .. N
+    .
+    .   Scenario-Line := Scenario-Keyword ':' Scenario-Name
+    .   Scenario-Description-Line := Line does not start with Step-Keyword
+    .   Step-Line := Step-Keyword Words+
+
+
+    @setup
+    Scenario: Feature Setup
+      Given a new working directory
+      And a file named "features/steps/steps.py" with:
+        """
+        from behave import step
+        import sys
+
+        @step('a step passes')
+        def step_passes(context):
+            pass
+
+        @step('a step passes with "{comment}"')
+        def step_passes(context, comment):
+            sys.stdout.write("PASSING-STEP: %s;\n" % comment)
+
+        @step('a step fails')
+        def step_fails(context):
+            assert False, "XFAIL-STEP"
+        """
+
+
+    Scenario: First Example for a Scenario Description
+      Given a file named "features/example_description1.feature" with:
+        """
+        Feature:
+          Scenario: E1
+
+            This is a simple scenario description before the steps start.
+            It explains why this scenario is important.
+
+            Here another scenario description line after an empty line.
+
+                Given a step passes with "Alice"
+                When a step passes with "Bob"
+                Then a step passes with "Charly"
+        """
+      When I run "behave -f plain -T features/example_description1.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 command output should contain:
+        """
+        Feature:
+          Scenario: E1
+            Given a step passes with "Alice" ... passed
+            When a step passes with "Bob" ... passed
+            Then a step passes with "Charly" ... passed
+        """
+
+
+    Scenario: Inspect the Scenario Description by using JSON
+      Given a file named "features/example_description1.feature" exists
+      When I run "behave -f json.pretty -o example1.json -f plain -T features/example_description1.feature"
+      Then it should pass
+      And the file "example1.json" should contain:
+        """
+            "description": [
+              "This is a simple scenario description before the steps start.",
+              "It explains why this scenario is important.",
+              "Here another scenario description line after an empty line."
+            ],
+            "keyword": "Scenario",
+            "location": "features/example_description1.feature:2",
+            "name": "E1",
+        """
+
+
+    Scenario: Second Example with 2 scenario with scenario descriptions
+      Given a file named "features/example_description2.feature" with:
+        """
+        @one
+        Feature: F2
+
+           Feature description line 1.
+           Feature description line 2.
+
+          @foo
+          Scenario: S2.1
+
+            Scenario description line S2.1-1.
+              Scenario description line S2.1-2 (indentation is removed).
+
+                Given a step passes with "Alice"
+                Then a step passes with "Charly"
+
+          @foo
+          @bar @baz
+          Scenario: S2.2
+
+            Scenario description line S2.2-1.
+
+                When a step passes with "Bob"
+        """
+      When I run "behave -f json.pretty -o example2.json -f plain -T features/example_description2.feature"
+      Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        2 scenarios passed, 0 failed, 0 skipped
+        3 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+      And the command output should contain:
+        """
+        Feature: F2
+          Scenario: S2.1
+            Given a step passes with "Alice" ... passed
+            Then a step passes with "Charly" ... passed
+
+          Scenario: S2.2
+            When a step passes with "Bob" ... passed
+        """
+      And the file "example2.json" should contain:
+        """
+            "description": [
+              "Scenario description line S2.1-1.",
+              "Scenario description line S2.1-2 (indentation is removed)."
+            ],
+            "keyword": "Scenario",
+            "location": "features/example_description2.feature:8",
+            "name": "S2.1",
+        """
+      And the file "example2.json" should contain:
+        """
+            "description": [
+              "Scenario description line S2.2-1."
+            ],
+            "keyword": "Scenario",
+            "location": "features/example_description2.feature:18",
+            "name": "S2.2",
+        """