busser-behave 0.1.3

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

@@ -0,0 +1,11 @@
+@issue
+Feature: Issue #197: Hooks processing should be more exception safe
+
+  TESTS PROVIDED IN: features/runner.hook_errors.feature
+
+  @reuse.colocated_test
+  Scenario: Hook processing in case of errors
+    Given I use the current directory as working directory
+    When I run "behave -f plain features/runner.hook_errors.feature"
+    Then it should pass
+

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

@@ -0,0 +1,129 @@
+@issue
+Feature: Issue #216: ANSI escape sequences are used while using --wip option
+
+  . ENSURE THAT:
+  .   * Coloring is disabled when --wip option is used.
+  .   * In addition, no colouring is used when using --show-skipped option
+  .   * Undefined step snippets are not "colored".
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        default_format = pretty
+        show_skipped   = false
+        show_timings   = false
+        """
+    And a file named "features/steps/use_behave4cmd_steps.py" with:
+        """
+        import behave4cmd0.passing_steps
+        import behave4cmd0.failing_steps
+        import behave4cmd0.note_steps
+        """
+    And a file named "features/steps/ansi_steps.py" with:
+        """
+        from behave import step, then
+        from behave4cmd0.command_steps import step_command_output_should_not_contain_text
+
+        @then(u'the command output should not contain any ANSI escape sequences')
+        def step_command_ouput_should_not_contain_ansi_sequences(context):
+            CSI = u"\x1b["  #< ANSI CONTROL SEQUENCE INTRODUCER (CSI).
+            step_command_output_should_not_contain_text(context, CSI)
+        """
+    And a file named "features/scenario_with_undefined_steps.feature" with:
+        """
+        Feature:
+
+          @wip
+          Scenario: Alice
+            Given a step passes
+            When a step is undefined
+            Then a step passes
+
+          @foo
+          Scenario: Bob
+            When another step is undefined
+        """
+
+
+  Scenario: When using --wip, coloring is disabled
+    When I run "behave --wip features"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 0 skipped, 1 untested
+      1 step passed, 0 failed, 1 skipped, 1 undefined, 1 untested
+      """
+    And the command output should contain:
+      """
+      Scenario: Alice
+        Given a step passes ... passed
+        When a step is undefined ... undefined
+      """
+    But the command output should not contain any ANSI escape sequences
+    And note that "the plain formatter is used as default formatter"
+
+
+  Scenario: When using --wip and --show-skipped, coloring is disabled
+    When I run "behave --wip --show-skipped features"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 0 skipped, 1 untested
+      1 step passed, 0 failed, 1 skipped, 1 undefined, 1 untested
+      """
+    And the command output should contain:
+      """
+      Scenario: Alice
+        Given a step passes ... passed
+        When a step is undefined ... undefined
+      """
+    But the command output should not contain any ANSI escape sequences
+    And note that "the plain formatter is used as default formatter"
+
+
+  Scenario: When using --wip and --format, coloring is disabled
+    When I run "behave --wip -f pretty features"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 0 skipped, 1 untested
+      1 step passed, 0 failed, 1 skipped, 1 undefined, 1 untested
+      """
+    And the command output should contain:
+      """
+      Feature:  # features/scenario_with_undefined_steps.feature:1
+
+        @wip
+        Scenario: Alice            # features/scenario_with_undefined_steps.feature:4
+          Given a step passes      # ../behave4cmd0/passing_steps.py:23
+          When a step is undefined # None
+          Then a step passes       # None
+      """
+    But the command output should not contain any ANSI escape sequences
+    And note that "the plain formatter is overridden on command-line"
+    And note that "the coloring mode is disabled"
+
+
+  Scenario: When using --wip and --color, coloring is disabled
+    When I run "behave --wip -f pretty --color features"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      0 scenarios passed, 1 failed, 0 skipped, 1 untested
+      1 step passed, 0 failed, 1 skipped, 1 undefined, 1 untested
+      """
+    And the command output should contain:
+      """
+      Feature:  # features/scenario_with_undefined_steps.feature:1
+
+        @wip
+        Scenario: Alice            # features/scenario_with_undefined_steps.feature:4
+          Given a step passes      # ../behave4cmd0/passing_steps.py:23
+          When a step is undefined # None
+          Then a step passes       # None
+      """
+    But the command output should not contain any ANSI escape sequences
+    And note that "the coloring mode is overridden by the wip mode"

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

@@ -0,0 +1,51 @@
+@issue
+@unicode
+Feature: UnicodeDecodeError in tracebacks (when an exception in a step implementation)
+
+  . Exception with non-ASCII character is raised in a step implementation.
+  . UnicodeDecodeError occurs with:
+  .   'ascii' codec can't decode byte 0x82 in position 11: ordinal not in range(128)
+  .
+  . RELATED:
+  .   * features/i18n.unicode_problems.feature
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+      """
+      # -*- coding: UTF-8 -*-
+      from behave import step
+      import six
+      if six.PY2:
+          chr = unichr
+
+      @step(u'a step raises an exception with non-ASCII character "{char_code:d}"')
+      def step_raises_exception_with_non_ascii_text(context, char_code):
+          assert 0 <= char_code <= 255, "RANGE-ERROR: char_code=%s" % char_code
+          raise RuntimeError(u"FAIL:"+ chr(char_code) +";")
+      """
+
+  Scenario Outline: Syndrome with non-ASCII char <char_code> (format=<format>)
+    Given a file named "features/syndrome_0226_<char_code>.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step raises an exception with non-ASCII character "<char_code>"
+      """
+    When I run "behave -f <format> features/syndrome_0226_<char_code>.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 1 failed, 0 skipped
+      0 steps passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      RuntimeError: FAIL:<special_char>;
+      """
+    But the command output should not contain "UnicodeDecodeError"
+
+    Examples:
+      | format | char_code | special_char | comment! |
+      | plain  |    162    |  ¢           | cent     |
+      | pretty |    191    |  ¿           | question-mark on-the-head |

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

@@ -0,0 +1,41 @@
+@feature_request
+@issue
+Feature: Issue #228: Allow before_scenario to determine whether steps should be run.
+
+  Allow before_scenario to call mark_skipped() and early out if the current
+  scenario should be skipped.
+
+  Scenario: Allow before_scenario to skip the current scenario
+
+    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/environment.py" with
+        """
+        def before_scenario(context, scenario):
+            if scenario.name == 'Skip this scenario':
+                scenario.skip()
+        """
+    And a file named "features/issue228_example.feature" with
+        """
+        Feature:
+          Scenario: Skip this scenario
+            Given I'm using an "undefined step"
+
+          Scenario: Run this scenario
+            Given a step passes
+        """
+    When I run "behave -f plain features/issue228_example.feature"
+    Then it should pass
+     And the command output should contain:
+        """
+        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/issue0230.feature

@@ -0,0 +1,46 @@
+@issue
+@unicode
+Feature: Assert with non-ASCII char causes UnicodeDecodeError
+
+  . Failing assert with non-ASCII character in its message
+  . causes UnicodeDecodeError and silent exit in Python2.
+  .
+  . RELATED:
+  .   * features/i18n.unicode_problems.feature
+
+  @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 fails with non-ASCII character "{char_code:d}"')
+      def step_fails_with_non_ascii_text(context, char_code):
+          assert 0 <= char_code <= 255, "RANGE-ERROR: char_code=%s" % char_code
+          assert False, "FAIL:"+ chr(char_code) +";"
+      """
+
+  Scenario Outline: Syndrome with non-ASCII char <char_code> (format=<format>)
+    Given a file named "features/syndrome_0230_<char_code>.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step fails with non-ASCII character "<char_code>"
+      """
+    When I run "behave -f <format> features/syndrome_0230_<char_code>.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 1 failed, 0 skipped
+      0 steps passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should not contain "UnicodeDecodeError"
+    But the command output should contain:
+      """
+      Assertion Failed: FAIL:
+      """
+
+    Examples:
+      | format | char_code |
+      | plain  |    130    |
+      | pretty |    190    |

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

@@ -0,0 +1,77 @@
+@issue
+@not_reproducible
+Feature: Issue #231: Display the output of the last print command
+
+  . The output of the last print command in a step is not displayed
+  . in the behave output (at least with standard pretty formatter),
+  . unless the string to print ends with newline ('\n').
+  .
+  . ANALYSIS: NOT-REPRODUCIBLE
+  .   Checked print function and stdout without newline.
+  .   Both show the expected capture stdout output when the step fails.
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/syndrome1.feature" with:
+      """
+      Feature:
+        Scenario: Alice
+           Given a step passes
+           When  a step passes
+           Then  I write "ALICE was HERE" without newline to stdout and fail
+      """
+    And a file named "features/syndrome2.feature" with:
+      """
+      Feature:
+        Scenario: Bob
+           Given a step passes
+           Then  I print "BOB was HERE" without newline and fail
+      """
+    And a file named "features/steps/steps.py" with:
+      """
+      from __future__ import print_function
+      from behave import step
+      import sys
+
+      @step('{word:w} step passes')
+      def step_passes(context, word):
+          pass
+
+      @step('I write "{message}" without newline to stdout and fail')
+      def step_write_without_newline_and_fail(context, message):
+          sys.stdout.write(message)
+          assert False, "FAIL: "+ message
+
+      @step('I print "{message}" without newline and fail')
+      def step_print_without_newline_and_fail(context, message):
+          print(message, end="")
+          assert False, "FAIL: "+ message
+      """
+
+
+  Scenario: Write to stdout without newline
+    When I run "behave -f pretty -c -T features/syndrome1.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 1 failed, 0 skipped
+      2 steps passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Captured stdout:
+      ALICE was HERE
+      """
+
+  Scenario: Use print function without newline
+    When I run "behave -f pretty -c -T features/syndrome2.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 1 failed, 0 skipped
+      1 step passed, 1 failed, 0 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Captured stdout:
+      BOB was HERE
+      """

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

@@ -0,0 +1,52 @@
+@issue
+@feature_request
+Feature: Issue #238 Skip a Scenario in a Scenario Outline
+
+    Scenario:
+      Given a new working directory
+      And a file named "features/issue238_1.feature" with:
+        """
+        Feature: Testing Scenario skipping
+            Scenario Outline:
+                Given a set of "<thing>"
+                When I ensure that "<thing>" != invalid
+                Then it should pass
+
+              Examples:
+                | thing   |
+                | valid   |
+                | invalid |
+        """
+      And a file named "features/steps/steps.py" with:
+        """
+        @given('a set of "{thing}"')
+        def step_check_thing_assumption(ctx, thing):
+            if thing == "invalid":
+                ctx.scenario.skip("ASSUMPTION-MISMATCH: INVALID-THING")
+
+        @when('I ensure that "{thing}" != invalid')
+        def step_ensure_that_thing_is_valid(ctx, thing):
+            assert thing != "invalid"
+
+        @then('it should pass')
+        def step_passes(context):
+            pass
+        """
+      When I run "behave -f plain --show-skipped --no-timings"
+      Then it should pass with:
+        """
+        1 feature passed, 0 failed, 0 skipped
+        1 scenario passed, 0 failed, 1 skipped
+        3 steps passed, 0 failed, 3 skipped, 0 undefined
+        """
+      And the command output should contain:
+        """
+        Scenario Outline:  -- @1.1
+          Given a set of "valid" ... passed
+          When I ensure that "valid" != invalid ... passed
+          Then it should pass ... passed
+
+        Scenario Outline:  -- @1.2
+          Given a set of "invalid" ... skipped
+        """
+      But note that "the step that skipped the scenario is also marked as skipped"

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

@@ -0,0 +1,15 @@
+@issue
+@unicode
+Feature: UnicodeDecodeError in model.Step (when step fails)
+
+  . Output of failing step contains non-ASCII characters.
+  .
+  . RELATED:
+  .   * features/i18n.unicode_problems.feature
+
+
+  @reuse.colocated_test
+  Scenario:
+      Given I use the current directory as working directory
+      When I run "behave -f plain --tags=@setup,@problematic.output features/i18n.unicode_problems.feature"
+      Then it should pass

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

@@ -0,0 +1,118 @@
+@issue
+Feature: Issue #280: AmbiguousStep error with similar step definitions and use_step_matcher("re")
+
+  . While using the RegexMatcher with steps that have the same step prefix
+  . an AmbiguousStep exception occurs if the shorter step is registered first.
+  .
+  . EXAMPLE:
+  . Two steps with definitions that have the same step prefix:
+  .
+  .   * I do something
+  .   * I do something more
+  .
+  . cause an AmbiguousStep error to be thrown:
+  .
+  .   behave.step_registry.AmbiguousStep: @when('I do something more') has already
+  .   been defined in existing step @when('I do something') at ...
+  .
+  . SOLUTION: Add regex begin-/end-markers around the step text( '^'+ step + '$')
+  . NOTE: Only RegexMatcher is affected.
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And   a file named "features/steps/calculator_steps1.py" with:
+      """
+      from behave import given, then
+      from hamcrest import assert_that, equal_to
+
+      class SimpleCalculator(object):
+          def __init__(self):
+              self.result = 0
+
+          def add(self, value):
+              self.result += value
+
+      @given(u'a calculator')
+      def step_impl(context):
+          context.calculator = SimpleCalculator()
+
+      @then(u'the calculator result is "{expected_result:d}"')
+      def step_impl(context, expected_result):
+          assert_that(context.calculator.result, equal_to(expected_result))
+      """
+
+  Scenario: Ensure RegexMatcher is not ordering sensitive
+    Given a file named "features/syndrome_280_1.feature" with:
+      """
+      Feature:
+        Scenario: Use both steps
+          Given I do something
+          When  I do something more
+      """
+    And   a file named "features/steps/simple_steps.py" with:
+      """
+      from behave import step, use_step_matcher
+      use_step_matcher("re")
+
+      # -- ORDERING SENSITIVE PART:
+      @step(u'I do something')
+      def step_impl(context):
+          pass
+
+      @step(u'I do something more')
+      def step_impl(context):
+          pass
+      """
+    When I run "behave -f plain features/syndrome_280_1.feature"
+    Then it should pass with:
+      """
+      1 scenario passed, 0 failed, 0 skipped
+      """
+    But the command output should not contain "AmbiguousStep:"
+    And the command output should not contain:
+      """
+      AmbiguousStep: @step('I do something more') has already been defined in
+      existing step @step('I do something') at features/steps/simple_steps.py:5'
+      """
+
+  Scenario: Ensure correct step implementation is selected
+    Given a file named "features/syndrome_280_2.feature" with:
+      """
+      Feature: Steps with same step prefix -- Use correct step implementation
+        Scenario: Use shorter step
+          Given a calculator
+          When I add "2" to it
+          And  I add "3" to it
+          Then the calculator result is "5"
+
+        Scenario: Use longer step
+          Given a calculator
+          When I add "2" to it twice
+          And  I add "3" to it
+          Then the calculator result is "7"
+      """
+    And   a file named "features/steps/calculator_steps2.py" with:
+      """
+      from behave import when, use_step_matcher
+      use_step_matcher("re")
+
+      # -- ORDERING SENSITIVE PART:
+      @when(u'I add "(?P<value>\d+)" to it')
+      def step_impl(context, value):
+          number_value = int(value)
+          context.calculator.add(number_value)
+
+      @when(u'I add "(?P<value>\d+)" to it twice')
+      def step_impl(context, value):
+          number_value = int(value)
+          context.calculator.add(number_value)
+          context.calculator.add(number_value)
+      """
+    When I run "behave -f pretty --no-color features/syndrome_280_2.feature"
+    Then it should pass with:
+      """
+      When I add "2" to it twice        # features/steps/calculator_steps2.py:10
+      And I add "3" to it               # features/steps/calculator_steps2.py:5
+      """
+    But the command output should not contain "AmbiguousStep"