busser-behave 0.1.3

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

@@ -0,0 +1,69 @@
+@issue
+Feature: Issue #83: behave.__main__:main() Various sys.exit issues
+
+  . Currently, the main function has several issues related
+  . to sys.exit() returncode usage:
+  .
+  . 1. sys.exit("string") is invalid, a number must be used:
+  .    => Used in exception cases after run (ParseError, ConfigError)
+  .
+  . 2. On success, the main() function returns implicitly None
+  .    instead of using sys.exit(0)
+  .    => No statement at end of function after failed case.
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+        """
+        from behave import step
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+        """
+
+  Scenario: Successful test run
+    Given a file named "features/passing.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given a step passes
+            When  a step passes
+            Then  a step passes
+        """
+    When I run "behave -c features/passing.feature"
+    Then it should pass
+    And  the command returncode is "0"
+
+  Scenario: ParseError occurs
+    Given a file named "features/invalid_with_ParseError.feature" with:
+        """
+        Feature:
+          Scenario: Invalid scenario which raises ParseError
+            Given a step passes
+            When2 a step passes
+        """
+    When I run "behave -c features/invalid_with_ParseError.feature"
+    Then it should fail
+    And  the command returncode is non-zero
+    And  the command output should contain:
+        """
+        Failed to parse "{__WORKDIR__}/features/invalid_with_ParseError.feature"
+        """
+
+  Scenario: ConfigError occurs
+    Given a new working directory
+    And   a file named "features/passing2.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given a step passes
+        """
+    When I run "behave -c features/passing2.feature"
+    Then it should fail
+    And  the command returncode is non-zero
+    And  the command output should contain:
+        """
+        No steps directory in '{__WORKDIR__}/features'
+        """

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

@@ -0,0 +1,69 @@
+@issue
+Feature: Issue #84: behave.runner behave does not reliably detected failed test runs
+
+  . Behave does currently not reliably detected failed test runs and
+  . therefore returns not sys.exit(1) at end of main().
+  .
+  . 1. behave.runner:Runner.run_with_paths() returns failed==True
+  .    if last feature was successful and test runner does not stop
+  .    after first failing feature.
+  .
+  . 2. Issue #64: Same problem in behave.model.Feature.run() with scenarios
+
+  Scenario: Test Setup
+    Given a new working directory
+    And   a file named "features/passing.feature" with:
+        """
+        Feature: Passing
+          Scenario:
+            Given a step passes
+            When  a step passes
+            Then  a step passes
+        """
+    And   a file named "features/failing.feature" with:
+        """
+        Feature: Failing
+          Scenario:
+            Given a step fails
+            When  a step fails
+            Then  a step fails
+        """
+    And   a file named "features/steps/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, "step: a step fails"
+        """
+
+  Scenario: First feature fails, second feature passes
+    When I run "behave -f plain features/failing.feature features/passing.feature"
+    Then it should fail with:
+        """
+        1 feature passed, 1 failed, 0 skipped
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 2 skipped, 0 undefined
+        """
+
+  Scenario: First feature passes, second feature fails
+    When I run "behave -f plain features/passing.feature features/failing.feature"
+    Then it should fail with:
+        """
+        1 feature passed, 1 failed, 0 skipped
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 2 skipped, 0 undefined
+        """
+
+  Scenario: First feature passes, second fails, last passes
+    When I run "behave -f plain features/passing.feature features/failing.feature features/passing.feature"
+    Then it should fail with:
+        """
+        2 features passed, 1 failed, 0 skipped
+        2 scenarios passed, 1 failed, 0 skipped
+        6 steps passed, 1 failed, 2 skipped, 0 undefined
+        """

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

@@ -0,0 +1,119 @@
+@issue
+Feature: Issue #85: AssertionError with nested regex and pretty formatter
+
+    | When --format=pretty is used
+    | an AssertationError occurs for missing optional/nested-groups.
+    | When --format=plain is used, everything is fine
+
+  Scenario: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/regexp_steps.py" with:
+        """
+        from __future__ import print_function
+        from behave import given, when, then, use_step_matcher
+        @given(u'a {re_category} regular expression "{pattern}"')
+        def impl(context, re_category, pattern):
+            pass
+
+        @then(u'the parameter "{name}" is "{expected_value}"')
+        def impl(context, name, expected_value):
+            actual_value = getattr(context, name, None)
+            if actual_value is None:
+                actual_value = ""
+            assert hasattr(context, name)
+            assert actual_value == expected_value, "MISMATCH: actual({0}) == expected({1})".format(actual_value, expected_value)
+
+        @then(u'the parameter "{name}" is none')
+        def impl(context, name):
+            actual_value = getattr(context, name, None)
+            assert hasattr(context, name)
+            assert actual_value is None, "MISMATCH: actual({0}) == None)".format(actual_value)
+
+        def store_in_context(context, data):
+            for name, value in data.items():
+                setattr(context, name, value)
+
+        use_step_matcher('re')
+
+        @when(u'I try to match "(?P<foo>foo and more)"')
+        def impl(context, **kwargs):
+            kwargs["regexp_case"] = "simple"
+            print("CASE UNNESTED: {0}".format(kwargs))
+            store_in_context(context, kwargs)
+
+        @when(u'I try to match "(?P<foo>foo(?P<bar>bar)?)"')
+        def impl(context, **kwargs):
+            kwargs["regexp_case"] = "nested"
+            print("CASE NESTED: {0}".format(kwargs))
+            store_in_context(context, kwargs)
+
+        @when(u'I try to match "(?P<foo>foo) (?P<bar>bar)?"')
+        def impl(context, **kwargs):
+            kwargs["regexp_case"] = "optional"
+            print("CASE OPTIONAL: {0}".format(kwargs))
+            store_in_context(context, kwargs)
+        """
+    And   a file named "features/matching.feature" with:
+        """
+        Feature: Using regexp matcher with nested and optional parameters
+
+            Scenario: regex, no nested groups, matching
+                Given a simple regular expression "(?P<foo>foo and more)"
+                When I try to match "foo and more"
+                Then the parameter "regexp_case" is "simple"
+                And  the parameter "foo" is "foo and more"
+
+            Scenario: Nested groups without nested match
+                Given a nested-group regular expression "(?P<foo>foo(?P<bar>bar)?)"
+                When I try to match "foo"
+                Then the parameter "regexp_case" is "nested"
+                And  the parameter "foo" is "foo"
+                And  the parameter "bar" is none
+
+            Scenario: Nested groups with nested match
+                Given a nested-group regular expression "(?P<foo>foo(?P<bar>bar)?)"
+                When I try to match "foobar"
+                Then the parameter "regexp_case" is "nested"
+                And  the parameter "foo" is "foobar"
+                And  the parameter "bar" is "bar"
+
+            Scenario: Optional group without match
+                Given a optional-group regular expression "(?P<foo>foo) (?P<bar>bar)?"
+                When I try to match "foo "
+                Then the parameter "regexp_case" is "optional"
+                And  the parameter "foo" is "foo"
+                And  the parameter "bar" is none
+
+            Scenario: Optional group with match
+                Given a optional-group regular expression "(?P<foo>foo) (?P<bar>bar)?"
+                When I try to match "foo bar"
+                Then the parameter "regexp_case" is "optional"
+                And  the parameter "foo" is "foo"
+                And  the parameter "bar" is "bar"
+        """
+
+  Scenario: Run regexp steps with --format=plain
+    When I run "behave --format=plain features/matching.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        5 scenarios passed, 0 failed, 0 skipped
+        24 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+
+  Scenario: Run regexp steps with --format=pretty
+    When I run "behave -c --format=pretty features/matching.feature"
+    Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        5 scenarios passed, 0 failed, 0 skipped
+        24 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And  the command output should not contain
+        """
+        assert isinstance(text, unicode)
+        """
+    And  the command output should not contain
+        """
+        AssertationError
+        """

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

@@ -0,0 +1,66 @@
+@issue
+Feature: Issue #92: Output from --format=plain shows skipped steps in next scenario
+
+    . DUPLICATED, FIXED-BY: issue #35 solution.
+    .
+    . Given a feature has more than one scenario
+    . When the --format=plain option is used
+    .   and a middle step of a scenario fails
+    . Then the skipped steps appear under the next scenario
+
+
+  Scenario:
+    Given a new working directory
+    And   a file named "features/issue92_syndrome.feature" with:
+        """
+        Feature: Testing Plain Output
+            Reproduces bug where output from previous scenario appears before current.
+
+            Scenario: First example
+                Given this step works
+                When this step fails
+                Then this step appears in the wrong place
+
+            Scenario: Second example
+                Given this step works
+                When this step fails
+                Then this step appears in the wrong place
+        """
+    And   a file named "features/steps/steps.py" with:
+        """
+        from behave import step
+
+        @step(u'this step works')
+        def working(context):
+            pass
+
+
+        @step(u'this step fails')
+        def failing(context):
+            assert False, 'step failed'
+
+
+        @step(u'this step appears in the wrong place')
+        def missing(context):
+            pass
+        """
+    When I run "behave --no-timings --format=plain features/issue92_syndrome.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:
+        """
+        Feature: Testing Plain Output
+           Scenario: First example
+               Given this step works ... passed
+                When this step fails ... failed
+           Assertion Failed: step failed
+
+           Scenario: Second example
+               Given this step works ... passed
+                When this step fails ... failed
+           Assertion Failed: step failed
+        """

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

@@ -0,0 +1,173 @@
+@issue
+Feature: Issue #96: Sub-steps failed without any error info to help debug issue
+
+    . I am trying to run execute_steps. One of them fails, but the error output
+    . from behave has no details whatsoever. It is virtually impossible
+    . to figure out why it failed. as no error output is present except the
+    . final error message
+    .
+    .   def before_scenario(context,scenario):
+    .       context.execute_steps(u'''
+    .           When "admin:admin" sends POST "/tasks/testStart"
+    .           Then I expect HTTP code 200
+    .       ''')
+    .
+    . File ".../behave/runner.py", line 262, in execute_steps
+    .  assert False, "FAILED SUB-STEP: %s" % step
+    .  AssertionError: FAILED SUB-STEP: When "admin:admin" sends POST "/tasks/testStart"
+    .
+    .  All we get is the "sub-step failed" but no info whatsoever
+    .  as to why it failed...
+
+
+
+  Background:
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+        """
+        from behave import step
+        import sys
+
+        @step(u'a step passes')
+        def step_passes(context):
+            pass
+
+        @step(u'a step fails')
+        def step_fails(context):
+            assert False, 'EXPECT: Step fails.'
+
+        @step(u'a step fails with stdout "{message}"')
+        def step_fails_with_stdout(context, message):
+            sys.stdout.write("%s\n" % message)
+            assert False, 'EXPECT: Step fails with stdout.'
+
+        @step(u'a step fails with stderr "{message}"')
+        def step_fails_with_stderr(context, message):
+            sys.stderr.write("%s\n" % message)
+            assert False, 'EXPECT: Step fails with stderr.'
+
+        @step(u'a step raises an error "{message}"')
+        def step_raises_exception(context, message):
+            raise RuntimeError(message)
+
+        @step(u'the following steps should pass')
+        def step_following_steps_should_pass(context):
+            context.execute_steps(context.text.strip())
+        """
+
+  Scenario: Execute steps and one fails (EXPECTATION-MISMATCH: Assert fails)
+    Given a file named "features/issue96_case1.feature" with:
+        '''
+        Feature:
+            Scenario:
+                When the following steps should pass:
+                   """
+                   Given a step passes
+                   When  a step fails
+                   Then  a step passes
+                   """
+        '''
+    When I run "behave -c features/issue96_case1.feature"
+    Then it should fail with:
+        """
+        Assertion Failed: FAILED SUB-STEP: When a step fails
+        Substep info: Assertion Failed: EXPECT: Step fails.
+        """
+
+  Scenario: Execute steps and error occurs (UNEXPECTED: exception is raised)
+    Given a file named "features/issue96_case2.feature" with:
+        '''
+        Feature:
+            Scenario:
+                When the following steps should pass:
+                   """
+                   Given a step passes
+                   When a step raises an error "Alice is alive"
+                   Then a step passes
+                   """
+        '''
+    When I run "behave -c features/issue96_case2.feature"
+    Then it should fail with:
+        """
+        RuntimeError: Alice is alive
+        """
+    And the command output should contain:
+        """
+        Assertion Failed: FAILED SUB-STEP: When a step raises an error "Alice is alive"
+        Substep info: Traceback (most recent call last):
+        """
+
+  Scenario: Execute steps and one fails with stdout capture
+    Given a file named "features/issue96_case3.feature" with:
+        '''
+        Feature:
+            Scenario:
+                When the following steps should pass:
+                   """
+                   Given a step passes
+                   When a step fails with stdout "STDOUT: Alice is alive"
+                   Then a step passes
+                   """
+        '''
+    When I run "behave -c features/issue96_case3.feature"
+    Then it should fail with:
+        """
+        Assertion Failed: FAILED SUB-STEP: When a step fails with stdout "STDOUT: Alice is alive"
+        Substep info: Assertion Failed: EXPECT: Step fails with stdout.
+        """
+    And the command output should contain:
+        """
+        Captured stdout:
+        STDOUT: Alice is alive
+        """
+
+
+  Scenario: Execute steps and one fails with stderr capture
+    Given a file named "features/issue96_case4.feature" with:
+        '''
+        Feature:
+            Scenario:
+                When the following steps should pass:
+                   """
+                   Given a step passes
+                   When a step fails with stderr "STDERR: Alice is alive"
+                   Then a step passes
+                   """
+        '''
+    When I run "behave -c features/issue96_case4.feature"
+    Then it should fail with:
+        """
+        Assertion Failed: FAILED SUB-STEP: When a step fails with stderr "STDERR: Alice is alive"
+        Substep info: Assertion Failed: EXPECT: Step fails with stderr.
+        """
+    And the command output should contain:
+        """
+        Captured stderr:
+        STDERR: Alice is alive
+        """
+
+  Scenario: Execute steps and fail in before_scenario hook
+    Given a file named "features/issue96_case5.feature" with:
+        """
+        Feature:
+            Scenario:
+                Given a step passes
+                When  a step passes
+                Then  a step passes
+        """
+    And a file named "features/environment.py" with:
+        """
+        def before_scenario(context, scenario):
+            context.execute_steps(u'''
+               Given a step passes
+               When a step passes
+               Then a step fails
+            ''')
+        """
+    When I run "behave -c features/issue96_case5.feature"
+    Then it should fail with:
+        """
+        HOOK-ERROR in before_scenario: AssertionError: FAILED SUB-STEP: Then a step fails
+        Substep info: Assertion Failed: EXPECT: Step fails.
+        """
+