busser-behave 0.1.3

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

@@ -0,0 +1,130 @@
+@issue
+Feature: Issue #99: Layout variation "a directory containing your feature files" is broken for running single features
+
+    . When I use a layout as described in the 1.2.2 documentation,
+    . I can only specify a whole directory of feature files to run.
+    . Specifying a single feature file results in an error from behave:
+    .
+    .   $ behave -v tests/feature/webui/features/feature_under_test.feature
+    .    ...
+    .    Supplied path: "tests/feature/webui/features/feature_under_test.feature"
+    .    Primary path is to a file so using its directory
+    .    Trying base directory: .../tests/feature/webui/features
+    .    Trying base directory: .../tests/feature/webui
+    .    ERROR: Could not find "steps" directory in your specified path '.../tests/feature/webui/features'
+    .    No steps directory in '.../tests/feature/webui/features'
+    .
+    . My directory layout is as follows:
+    .
+    .   .../tests/feature/webui/
+    .       +-- features/
+    .       +-- steps/
+    .       +-- environment.py
+    .
+    . SEE ALSO:
+    .   * http://packages.python.org/behave/gherkin.html#layout-variations
+
+
+  Background:
+    Given a new working directory
+    And   a file named "root/steps/steps.py" with:
+        """
+        from behave import step
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+        """
+    And   a file named "root/features/alice.feature" with:
+        """
+        Feature: Alice
+          Scenario:
+            Given a step passes
+        """
+    And   a file named "root/features/bob.feature" with:
+        """
+        Feature: Bob
+          Scenario:
+            Given a step passes
+        """
+    And   a file named "root/features2/charly.feature" with:
+        """
+        Feature: Charly
+          Scenario:
+            When a step passes
+        """
+
+  Scenario: Run features with root directory
+    When I run "behave -f plain --no-timings root"
+    Then it should pass with:
+        """
+        3 features passed, 0 failed, 0 skipped
+        3 scenarios passed, 0 failed, 0 skipped
+        3 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature: Alice
+          Scenario:
+            Given a step passes ... passed
+        Feature: Bob
+          Scenario:
+            Given a step passes ... passed
+        Feature: Charly
+          Scenario:
+            When a step passes ... passed
+        """
+
+  Scenario: Run features with root/features directory
+    When I run "behave -f plain --no-timings root/features"
+    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
+        """
+    And the command output should contain:
+        """
+        Feature: Alice
+          Scenario:
+            Given a step passes ... passed
+        Feature: Bob
+          Scenario:
+            Given a step passes ... passed
+        """
+
+  Scenario: Run features with feature files
+    When I run "behave -f plain --no-timings root/features/alice.feature root/features2/charly.feature"
+    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
+        """
+    And the command output should contain:
+        """
+        Feature: Alice
+          Scenario:
+            Given a step passes ... passed
+        Feature: Charly
+          Scenario:
+            When a step passes ... passed
+        """
+
+  Scenario: Run features with feature dir and feature files (other ordering)
+    When I run "behave -f plain --no-timings root/features2 root/features/alice.feature"
+    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
+        """
+    And the command output should contain:
+        """
+        Feature: Charly
+          Scenario:
+            When a step passes ... passed
+        Feature: Alice
+          Scenario:
+            Given a step passes ... passed
+        """

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

@@ -0,0 +1,60 @@
+@issue
+Feature: Issue #109: Insists that implemented tests are not implemented
+
+    . STATUS: Resolved, not a behave problem.
+    .
+    . Following feature file marks implemented step "when I submit the following data"
+    . as not implemented.
+
+
+  Scenario:
+    Given a new working directory
+    And   a file named "features/syndrome109.feature" with:
+        """
+        @wip
+        Feature: Manage accounts from the admin interface
+
+            Scenario: Login successfully via login form
+                Given I navigate to "/admin/"
+                when I submit the following data
+                    | name          | value         |
+                    | username      | admin@foo.bar |
+                    | password      | pass          |
+                then I see the word "Welcome"
+
+            Scenario: Create user via admin user creation form
+                Given I navigate to "/admin/users/user/add/"
+                when I submit the following data
+                    | name           | value                           |
+                    | email          | spaaaaaaaaaaaaaaaaaaam@ham.eggs |
+                    | password1      | pass                            |
+                    | password2      | pass                            |
+                then I see the word "successfully"
+        """
+    And   a file named "features/steps/steps.py" with:
+        """
+        from behave import given, when, then
+
+        @given(u'I navigate to "{url}"')
+        def step_navigate_to_url(context, url):
+            pass
+
+        @when(u'I submit the following data')
+        def step_submit_data(context):
+            pass
+
+        @then(u'I see the word "{word}"')
+        def step_see_word(context, word):
+            pass
+        """
+    When I run "behave -w features/syndrome109.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        2 scenarios passed, 0 failed, 0 skipped
+        6 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should not contain:
+        """
+        You can implement step definitions for undefined steps with these snippets:
+        """

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

@@ -0,0 +1,53 @@
+@issue
+Feature: Issue #111: Comment following @wip tag results in scenario being ignored
+
+    . If a comment is placed after the @wip tag, the following scenario
+    . is ignored by behave:
+    .
+    .   @wip # comment: this is work in progress
+    .   Scenario: test scenario
+    .
+    . results in behave -w not running the "test scenario".
+    . After removing the comment, it runs as expected.
+
+
+  Scenario: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/passing_steps.py" with:
+        """
+        from behave import step
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+        """
+    And   a file named "features/syndrome111.feature" with:
+        """
+        Feature:
+
+          @wip  # Comment: blabla
+          Scenario: S1
+            Given a step passes
+
+          @wip  @one    # Comment: foobar
+          Scenario: S2
+            Given a step passes
+        """
+
+  Scenario: Scenario w/ comment on tag-line should run as normal
+    When I run "behave --wip features/syndrome111.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        2 scenarios passed, 0 failed, 0 skipped
+        2 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+
+  Scenario: Ensure 2nd scenario can be selected with other tag
+    When I run "behave -f plain --tags=one features/syndrome111.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        1 scenario passed, 0 failed, 1 skipped
+        1 step passed, 0 failed, 1 skipped, 0 undefined
+        """

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

@@ -0,0 +1,64 @@
+@issue
+@change_request
+Feature: Issue #112: Improvement to AmbiguousStep error
+
+    . AmbiguousStep could be more useful if it also showed the existing string
+    . with which the new one is clashing. This is particularly useful
+    . if using step parameters.
+
+
+  Background:
+    Given a new working directory
+    And   a file named "features/syndrome112.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given I buy 10 oranges
+        """
+
+  Scenario: Good step ordering -- From specific to generic regular expression
+    Given a file named "features/steps/good_steps.py" with:
+        """
+        from behave import given, when, then
+
+        # -- ORDERING-IMPORTANT: From more specific steps to less specific.
+        @given(u'I buy {number:n} {items:w}')
+        def step_given_I_buy2(context, number, items):
+            pass
+
+        # -- OTHERWISE: Generic step matches all other patterns.
+        @given(u'I buy {amount} {product}')
+        def step_given_I_buy(context, amount, product):
+            pass
+        """
+    When I run "behave -c features/syndrome112.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: Bad step ordering causes AmbiguousStep
+    Given a file named "features/steps/bad_steps.py" with:
+        """
+        from behave import given, when, then
+
+        # -- ORDERING-VIOLATED: Generic step comes first.
+        @given(u'I buy {amount} {product}')
+        def step_given_I_buy(context, amount, product):
+            pass
+
+        # -- AMBIGUOUS-STEP: Will occur here.
+        @given(u'I buy {number:n} {items:w}')
+        def step_given_I_buy2(context, number, items):
+            pass
+        """
+    When I run "behave -c features/syndrome112.feature"
+    Then it should fail
+    And the command output should contain:
+        """
+        AmbiguousStep: @given('I buy {number:n} {items:w}') has already been defined in
+          existing step @given('I buy {amount} {product}') at features/steps/bad_steps.py:4
+        """

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

@@ -0,0 +1,118 @@
+@issue
+@change_request
+Feature: Issue #114: Avoid unnecessary blank lines w/ --no-skipped option
+
+    . Unnessary blank lines appear when you use (for each skipped feature):
+    .
+    .    behave -f progress --tags=@one --no-skipped ...
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And   a file named "features/steps/passing_steps.py" with:
+        """
+        from behave import step
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+        """
+    And   a file named "features/e1.feature" with:
+        """
+        @example
+        Feature: E1
+          Scenario: S1.1
+            Given a step passes
+        """
+    And   a file named "features/e2.feature" with:
+        """
+        @exclude
+        Feature: E2
+          Scenario: S2.1
+            Given a step passes
+        """
+    And   a file named "features/e3.feature" with:
+        """
+        @example
+        Feature: E3
+          Scenario: S3.1
+            Given a step passes
+        """
+
+  Scenario: Run Features with tags and --show-skipped option
+    When I run "behave -f progress --tags=@example"
+    Then it should pass with:
+        """
+        2 features passed, 0 failed, 1 skipped
+        2 scenarios passed, 0 failed, 1 skipped
+        2 steps passed, 0 failed, 1 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        features/e1.feature  .
+        features/e2.feature  S
+        features/e3.feature  .
+        """
+
+  Scenario: Run Features with tag and --no-skipped option (CASE 1)
+    When I run "behave -f progress --tags=@example --no-skipped"
+    Then it should pass with:
+        """
+        2 features passed, 0 failed, 1 skipped
+        2 scenarios passed, 0 failed, 1 skipped
+        2 steps passed, 0 failed, 1 skipped, 0 undefined
+        """
+    And the command output should contain exactly:
+        """
+        features/e1.feature  .
+        features/e3.feature  .
+        """
+    But the command output should not contain exactly:
+        """
+        features/e1.feature  .
+
+        features/e3.feature  .
+        """
+
+  Scenario: Run Features with other tag and --no-skipped option (CASE 2)
+    When I run "behave -f progress --tags=@exclude --no-skipped"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 2 skipped
+        1 scenario passed, 0 failed, 2 skipped
+        1 step passed, 0 failed, 2 skipped, 0 undefined
+        """
+    And the command output should contain exactly:
+        """
+        features/e2.feature  .
+        """
+
+  Scenario: Run Features with tag, --no-skipped and plain formatter (CASE 3)
+    When I run "behave -f plain --tags=@example --no-skipped -T"
+    Then it should pass with:
+        """
+        2 features passed, 0 failed, 1 skipped
+        2 scenarios passed, 0 failed, 1 skipped
+        2 steps passed, 0 failed, 1 skipped, 0 undefined
+        """
+    And the command output should contain exactly:
+        """
+        Feature: E1
+
+          Scenario: S1.1
+            Given a step passes ... passed
+
+        Feature: E3
+
+        """
+    But the command output should not contain exactly:
+        """
+        Feature: E1
+
+          Scenario: S1.1
+            Given a step passes ... passed
+
+
+        Feature: E3
+
+        """

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

@@ -0,0 +1,71 @@
+@issue
+@change_request
+Feature: Issue #116: SummaryReporter shows failed scenarios list
+
+  Scenario: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/passing_failing_steps.py" with:
+        """
+        from behave import step
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+
+        @step(u'a step fails')
+        def step_fails(context):
+            assert False, "FAILS"
+        """
+    And   a file named "features/e1.feature" with:
+        """
+        Feature: E1
+
+          Scenario: E1.1
+            Given a step passes
+
+          @xfail
+          Scenario: E1.2 (XFAIL)
+            Given a step fails
+
+          Scenario: E1.3
+            Given a step passes
+        """
+    And   a file named "features/e2.feature" with:
+        """
+        @example2
+        Feature: E2
+
+          @xfail
+          Scenario: E2.1 (XFAIL)
+            Given a step fails
+
+          Scenario: E2.2
+            Given a step passes
+        """
+
+  Scenario: Summary shows list of failed scenarios when at least one fails
+    When I run "behave -f plain features/"
+    Then it should fail
+    And the command output should contain:
+        """
+        Failing scenarios:
+          features/e1.feature:7  E1.2 (XFAIL)
+          features/e2.feature:5  E2.1 (XFAIL)
+
+        0 features passed, 2 failed, 0 skipped
+        3 scenarios passed, 2 failed, 0 skipped
+        3 steps passed, 2 failed, 0 skipped, 0 undefined
+        """
+
+  Scenario: Summary hides list of failed scenarios when all scenarios pass
+    When I run "behave -f plain --tags=~@xfail features/"
+    Then it should pass with:
+        """
+        2 features passed, 0 failed, 0 skipped
+        3 scenarios passed, 0 failed, 2 skipped
+        3 steps passed, 0 failed, 2 skipped, 0 undefined
+        """
+    But the command output should not contain:
+        """
+        Failing scenarios:
+        """