busser-behave 0.1.3

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

@@ -0,0 +1,42 @@
+@issue
+@unicode
+Feature: Issue #449 -- Unicode output problem when fails with Russion text
+
+  . Either Exception text (as summary) or traceback python line shows
+  . special characters correctly.
+
+  Scenario:
+    Given a new working directory
+    And a file named "features/steps/problematic_steps.py" with:
+      """
+      # -*- coding: UTF-8 -*-
+      # NOTE: Python2 requires encoding to decode special chars correctly.
+      from behave import step
+      from hamcrest.core import assert_that, equal_to
+
+      @step("Russian text")
+      def step_russian_text(stop):
+          assert_that(False, equal_to(True), u"Всё очень плохо") # cyrillic
+      """
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        show_timings = false
+        """
+    And a file named "features/syndrome.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given Russian text
+      """
+    When I run "behave -f plain features/syndrome.feature"
+    Then it should fail with:
+      """
+      Scenario:
+        Given Russian text ... failed
+      Assertion Failed: Всё очень плохо
+      """
+    But the command output should not contain:
+      """
+      Assertion Failed: 'ascii' codec can't encode characters in position
+      """

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

@@ -0,0 +1,42 @@
+@issue
+@unicode
+Feature: Issue #453 -- Unicode output problem when Exception is raised in step
+
+  . Either Exception text (as summary) or traceback python line shows
+  . special characters incorrectly.
+  .
+  . Result (of failed step):
+  .     File "features/steps/steps.py", line 8, in foo
+  .        raise Exception(u"по ����ки") <-- This is not
+  .   Exception: по русски <-- This is OK
+
+
+    Scenario:
+      Given a new working directory
+      And a file named "features/steps/problematic_steps.py" with:
+        """
+        # -*- coding: UTF-8 -*-
+        from behave import step
+
+        @step(u'an exception with special chars is raised')
+        def step_exception_raised(context):
+            raise Exception(u"по русски")
+        """
+      And a file named "features/syndrome.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given an exception with special chars is raised
+        """
+      When I run "behave -f plain features/syndrome.feature"
+      Then it should fail with:
+        """
+        Scenario:
+          Given an exception with special chars is raised ... failed
+        """
+      And the command output should contain:
+        """
+          File "features/steps/problematic_steps.py", line 6, in step_exception_raised
+            raise Exception(u"по русски")
+        Exception: по русски
+        """

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

@@ -0,0 +1,65 @@
+@not_reproducible
+@issue
+Feature: Issue #457 -- Double-quotes in error messages of JUnit XML reports
+
+    STATUS: Problem is currently not reproducible.
+    XML attributes are escaped correctly even when double-quotes are used.
+
+    @setup
+    Scenario: Feature Setup
+      Given a new working directory
+      And a file named "features/steps/fail_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step fails with message')
+        def step_fails(context, word):
+            assert context.text
+            assert False, "FAILED: "+ context.text
+
+        @step('{word:w} step fails with error and message')
+        def step_fails2(context, word):
+            assert context.text
+            raise RuntimeError(context.text)
+        """
+
+
+    Scenario: Use failing assertation in a JUnit XML report
+      Given a file named "features/fails1.feature" with:
+        """
+        Feature:
+          Scenario: Alice
+            Given a step fails with message:
+              '''
+              My name is "Alice"
+              '''
+        """
+      When I run "behave --junit features/fails1.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        """
+      And the file "reports/TESTS-fails1.xml" should contain:
+        """
+        <failure message="FAILED: My name is &quot;Alice&quot;"
+        """
+
+    Scenario: Use exception in a JUnit XML report
+      Given a file named "features/fails2.feature" with:
+        """
+        Feature:
+          Scenario: Bob
+            Given a step fails with error and message:
+              '''
+              My name is "Bob" and <here> I am
+              '''
+        """
+      When I run "behave --junit features/fails2.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        """
+      And the file "reports/TESTS-fails2.xml" should contain:
+        """
+        <error message="My name is &quot;Bob&quot; and &lt;here&gt; I am"
+        """

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

@@ -0,0 +1,38 @@
+@issue
+Feature: Issue #462-- Invalid JSON output when --include option selects no features
+
+  . Invalid JSON output is generated when no features are selected in a test-run.
+  . For example, this may be the case when the --include option is used.
+
+
+    Background:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/passing.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given a step passes
+        """
+
+
+    Scenario: Include Option selects no feature files
+      When I run "behave -f json -i __unknown__.feature"
+      Then it should pass with:
+        """
+        0 features passed, 0 failed, 0 skipped
+        0 scenarios passed, 0 failed, 0 skipped
+        """
+      And the command output should contain:
+        """
+        [
+        ]
+        """
+

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

@@ -0,0 +1,39 @@
+@issue
+Feature: Issue #467 -- Scenario status when scenario w/o steps is skipped
+
+  . The scenario.status should be "skipped"
+  . if you try to skip a scenario without any steps.
+
+
+    Scenario: Skip scenario without steps
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/without_steps.feature" with:
+        """
+        Feature:
+          @skip_this
+          Scenario: Without steps
+        """
+      And a file named "features/environment.py" with:
+        """
+        def before_scenario(context, scenario):
+            if "skip_this" in scenario.tags:
+                scenario.skip()
+        """
+      When I run "behave -f plain features/without_steps.feature"
+      Then it should pass with:
+        """
+        Feature:
+          Scenario: Without steps
+
+        0 features passed, 0 failed, 1 skipped
+        0 scenarios passed, 0 failed, 1 skipped
+        """
+      But note that "the scenario without steps is skipped"

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

@@ -0,0 +1,92 @@
+@issue
+@unicode
+@not_reproducible
+Feature: Issue #487 -- UnicodeEncodeError with ZBSP in multi-line text
+
+    . NOTE: I use ZBSP (zero-width space) in multiline text
+    . Traceback (most recent call last):
+    .  File "/usr/bin/behave-2", line 9, in <module>
+    .    load_entry_point('behave==1.2.5', 'console_scripts', 'behave')()
+    .  File "/usr/lib/python2.7/site-packages/behave/__main__.py", line 111, in main
+    .     print(u"ParseError: %s" % e)
+    . UnicodeEncodeError: 'ascii' codec can't encode characters in position 92-103: ordinal not in range(128)
+    .
+    . ANALYSIS:
+    .   ParseError indicates that the problem occured while parsing the
+    .   feature file. Feature file encoding is assumed
+
+    @not.with_ci=appveyor
+    Scenario:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+        """
+      And a file named "features/steps/steps.py" with:
+        """
+        # -*- coding: latin-1 -*-
+        from __future__ import print_function
+        from behave import step
+
+        @step('I use {special_unicode_char:w} in text')
+        def step_use_ZBSP_with_text(context, special_unicode_char):
+            assert context.text
+            print(u"TEXT: %s" % context.text)
+        """
+      And a file named "behave.ini" with:
+          """
+          [behave]
+          show_timings = false
+          """
+      And a file named "features/syndrome.feature" with:
+        """
+        Feature:
+
+          Scenario Outline: Use special unicode char (<comment>)
+            Given I use ZBSP in text:
+              '''
+              HERE we use a ==><special_unicode_char><== SPECIAL UNICODE CHAR.
+              '''
+
+           Examples:
+              | special_unicode_char | comment |
+              | ⌘                    | MACOS command key symbol |
+              | ©                    | copyright sign           |
+              | €                    | Euro sign (currency)     |
+              | xxx XXX              | special space            |
+        """
+      When I run "behave -f plain features/syndrome.feature"
+      Then it should pass with:
+        """
+        4 scenarios passed, 0 failed, 0 skipped
+        """
+      And the command output should contain:
+        '''
+        Scenario Outline: Use special unicode char (MACOS command key symbol) -- @1.1
+          Given I use ZBSP in text ... passed
+            """
+            HERE we use a ==>⌘<== SPECIAL UNICODE CHAR.
+            """
+
+        Scenario Outline: Use special unicode char (copyright sign) -- @1.2
+          Given I use ZBSP in text ... passed
+            """
+            HERE we use a ==>©<== SPECIAL UNICODE CHAR.
+            """
+
+        Scenario Outline: Use special unicode char (Euro sign (currency)) -- @1.3
+          Given I use ZBSP in text ... passed
+            """
+            HERE we use a ==>€<== SPECIAL UNICODE CHAR.
+            """
+
+        Scenario Outline: Use special unicode char (special space) -- @1.4
+          Given I use ZBSP in text ... passed
+            """
+            HERE we use a ==>xxx XXX<== SPECIAL UNICODE CHAR.
+            """
+        '''

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

@@ -0,0 +1,77 @@
+@issue
+@user_error
+@python2.problem
+Feature: Issue #506 -- Behave stops on error
+
+    . ANALYSIS:
+    .   Using exception.__cause__ = original_exception causes problems in Python2
+    .   When you use the Python3 chained-exception mechanism,
+    .   you should better ensure that the "original_exception.__traceback__" attribute
+    .   exists. Otherwise, a new exception (missing attribute) is raised
+    .   when you format the traceback,
+
+    Scenario:
+      Given a new working directory
+      And a file named "features/steps/pass_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word:w} step passes')
+        def step_passes(context, word):
+            pass
+
+        """
+      And a file named "features/steps/steps.py" with:
+        """
+        from behave import when, then
+        from behave._types import ChainedExceptionUtil
+        import copy
+
+        @when('I bad chained-exception causes my step to fail')
+        def step_bad_usage_of_chained_exception(context):
+            # -- BAD IMPLEMENATION:
+            exception = ZeroDivisionError('integer division or modulo by zero')
+            exception.__cause__ = copy.copy(exception)
+            raise exception
+
+        @when('a chained-exception causes my step to fail')
+        def step_chained_exception_causes_failure(context):
+            try:
+                raise ZeroDivisionError("OOPS-1")
+            except ZeroDivisionError as e:
+                e2 = RuntimeError("OOPS-2")
+                ChainedExceptionUtil.set_cause(e2, e)
+                raise e2
+
+        @then('this step must be executed')
+        def step_check_step(context):
+            pass
+        """
+      And a file named "features/syndrome.feature" with:
+        """
+        Feature: Failing step which can lead to stop behave
+
+          @failing
+          Scenario: Run stopping behave scenario
+            When a chained-exception causes my step to fail
+            Then this step must be executed
+        """
+      When I run "behave -f plain features/syndrome.feature"
+      Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        """
+      And the command output should contain:
+        """
+          ZeroDivisionError: OOPS-1
+
+        The above exception was the direct cause of the following exception:
+
+        Traceback (most recent call last):
+        """
+      And the command output should contain:
+        """
+          File "features/steps/steps.py", line 19, in step_chained_exception_causes_failure
+            raise e2
+        RuntimeError: OOPS-2
+        """

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

@@ -0,0 +1,51 @@
+@issue
+@junit
+@wip
+Feature: Issue #510 -- JUnit XML output is not well-formed (in some cases)
+
+  . Special control characters in JUnit stdout/stderr sections
+  . are directly written to CDATA XML sections.
+  .
+  . According to the XML charset specification only the following unicode
+  . codepoints (characters) are allowed in a CDATA section:
+  .
+  .   Char ::=  #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
+  .   /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
+  .
+  . [XML-charsets] "The normative reference is XML 1.0 (Fifth Edition),
+  .     section 2.2, https://www.w3.org/TR/REC-xml/#charsets
+
+
+  @use.with_xmllint=yes
+  @xfail
+  Scenario:
+    Given a new working directory
+    And a file named "features/steps/special_char_steps.py" with:
+      """
+      # -*- coding: UTF-8 -*-
+      from __future__ import print_function
+      from behave import step
+
+      @step(u'we print ^D')
+      def step_print_special_char_control_d(context):
+          print(u"\004")
+      """
+    And a file named "features/special_char.feature" with:
+      """
+      Feature: An illegal char
+        Scenario: Control-D
+          When we print ^D
+      """
+    When I run "behave --junit features/special_char.feature"
+    Then it should pass with:
+      """
+      1 scenario passed, 0 failed, 0 skipped
+      """
+    When I run "xmllint reports/TESTS-special_char.xml"
+    Then it should pass
+    And the command output should not contain "parser error"
+    And the command output should not contain:
+      """
+      reports/TESTS-special_char.xml:12: parser error : PCDATA invalid Char value 4
+      """
+    And note that "xmllint reports additional correlated errors"