busser-behave 0.1.3

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

@@ -0,0 +1,95 @@
+@issue
+Feature: Issue #288 -- Use print function instead print statement in environment/steps files
+
+  . Loaded files have future flags of importing module "behave.runner".
+  . This should be removed.
+  .
+  . AFFECTED FILES:
+  .   * features/environment.py
+  .   * features/steps/*.py
+  .
+  . AFFECTED FUTURE FLAGS:
+  .   * print_function
+  .   * absolute_import
+  .   * ...
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/reuse_steps.py" with:
+        """
+        from behave4cmd0 import passing_steps
+        """
+    And a file named "features/passing.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given a step passes
+        """
+
+  @preferred
+  Scenario: Use print function with future-statement in steps/environment (PY2, PY3)
+    Given a file named "features/steps/my_steps.py" with:
+        """
+        from __future__ import print_function
+        print("Hello step")
+        """
+    And a file named "features/environment.py" with:
+        """
+        from __future__ import print_function
+        print("Hello environment")
+        """
+    When I run "behave -f plain features/passing.feature"
+    Then it should pass with:
+        """
+        1 scenario passed, 0 failed, 0 skipped
+        1 step passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should not contain:
+        """
+        Traceback (most recent call last):
+        """
+
+  @use.with_python2=true
+  Scenario: Use python2 print keyword in steps/environment
+    Given a file named "features/steps/my_steps.py" with:
+        """
+        print "Hello step"
+        """
+    And a file named "features/environment.py" with:
+        """
+        print "Hello step"
+        """
+    When I run "behave -f plain features/passing.feature"
+    Then it should pass with:
+        """
+        1 scenario passed, 0 failed, 0 skipped
+        1 step passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should not contain "SyntaxError"
+    And the command output should not contain:
+        """
+        Traceback (most recent call last):
+        """
+
+  @use.with_python3=true
+  Scenario: Use print function without future-statement in steps/environment (PY3)
+    Given a file named "features/steps/my_steps.py" with:
+        """
+        print("Hello step")
+        """
+    And a file named "features/environment.py" with:
+        """
+        print("Hello environment")
+        """
+    When I run "behave -f plain features/passing.feature"
+    Then it should pass with:
+        """
+        1 scenario passed, 0 failed, 0 skipped
+        1 step passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should not contain:
+        """
+        Traceback (most recent call last):
+        """
+

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

@@ -0,0 +1,49 @@
+@issue
+Feature: Issue #300 -- UnicodeDecodeError when read steps.py
+
+  . My system is running on Chinese GBK character set.
+  . But you know we make our files as utf-8 format generally, and so do I.
+  . I set my step file api1_steps.py as utf-8, and entered some Chinese characters in.
+  . I run "behave", but I got UnicodeDecodeError, just like this:
+  .
+  .   File "D:\workspace\env_110\lib\site-packages\behave\runner.py", line 304, in exec_file
+  .     code = compile(f.read(), filename2, 'exec')
+  .   UnicodeDecodeError: 'gbk' codec can't decode byte 0xad in position 510: illegal multibyte sequence
+
+  | OPEN ISSUES:
+  |   * Acceptable/supported Python source file encodings
+  |   * config: Add encoding option for feature files, step files or both.
+
+    Scenario: Cause BAD-ASCII Syndrome in steps file
+        Given a new working directory
+        And a file named "features/steps/bad_ascii_steps.py" with:
+            """
+            '''
+            BAD ASCII CASES (requires UTF-8/latin1 support):
+             * Café
+             * Ärgernis ist überall
+            '''
+            # COMMENT: Ärgernis ist überall
+            """
+        And a file named "features/steps/steps.py" with:
+            """
+            from __future__ import unicode_literals
+            from behave import step
+
+            @step('{word:w} step passes')
+            def step_passes(context, word):
+                pass
+            """
+        And a file named "features/e1.feature" with:
+            """
+            Feature:
+              Scenario: Alice
+                Given a step passes
+                Then another step passes
+            """
+        When I run "behave -f plain features/e1.feature"
+        Then it should pass with:
+            """
+            1 scenario passed, 0 failed, 0 skipped
+            2 steps passed, 0 failed, 0 skipped, 0 undefined
+            """

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

@@ -0,0 +1,91 @@
+@issue
+Feature: Issue #302: Cannot escape pipe in table field value
+
+  Support escaped-pipe characters in cells of a table.
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+        """
+        from behave import then, step
+        from hamcrest import assert_that, equal_to
+
+        @step(u'I use table data with')
+        def step_use_table_data_with_table(context):
+            assert context.table, "REQUIRE: context.table is provided"
+            context.table.require_columns(["name", "value"])
+
+            context.table_data = {}
+            for row in context.table.rows:
+                name = row["name"]
+                value = row["value"]
+                context.table_data[name] = value
+
+        @then(u'table data "{name}" is "{value}"')
+        def step_table_data_name_is_value(context, name, value):
+            table_data = context.table_data
+            actual_value = table_data[name]
+            assert_that(actual_value, equal_to(value))
+        """
+
+  Scenario: Escaped-pipes in table cell
+    Given a file named "features/issue0302_example.feature" with:
+        """
+        Feature:
+            Scenario: Use a table
+             Given I use table data with:
+                 | name  | value |
+                 | alice | one\|two\|three\|four  |
+             Then table data "alice" is "one|two|three|four"
+        """
+    When I run "behave -f plain features/issue0302_example.feature"
+    Then it should pass
+    And the command output should not contain:
+        """
+        Traceback (most recent call last):
+        """
+
+
+  Scenario: Leading escaped-pipe in table cell
+    Given a file named "features/issue0302_example2.feature" with:
+        """
+        Feature:
+            Scenario: Use a table
+             Given I use table data with:
+                 | name  | value |
+                 | bob   |\|one  |
+             Then table data "bob" is "|one"
+        """
+    When I run "behave -f plain features/issue0302_example2.feature"
+    Then it should pass
+
+
+  Scenario: Trailing escaped-pipe in table cell
+    Given a file named "features/issue0302_example3.feature" with:
+        """
+        Feature:
+            Scenario: Use a table
+             Given I use table data with:
+                 | name   | value |
+                 | charly | one\||
+             Then table data "charly" is "one|"
+        """
+    When I run "behave -f plain features/issue0302_example3.feature"
+    Then it should pass
+
+
+  Scenario: Double escaped-pipe in table cell
+    Given a file named "features/issue0302_example4.feature" with:
+        """
+        Feature:
+            Scenario: Use a table
+             Given I use table data with:
+                 | name   | value |
+                 | doro   | one\\|two |
+             Then table data "doro" is "one\|two"
+        """
+    When I run "behave -f plain features/issue0302_example4.feature"
+    Then it should pass
+
+

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

@@ -0,0 +1,52 @@
+@issue
+Feature: Issue #309 -- behave --lang-list fails on Python3
+
+  . When I type "behave --lang-list", the following error occurs on Python 3.4:
+  .
+  .   Traceback (most recent call last):
+  .     File "/usr/local/bin/behave", line 11, in <module>
+  .       sys.exit(main())
+  .     File "/usr/local/lib/python3.4/dist-packages/behave/__main__.py", line 65, in main
+  .       iso_codes.sort()
+  .   AttributeError: 'dict_keys' object has no attribute 'sort'
+  .
+  . ADDITIONAL PROBLEM: On Python2 you may get an UnicodeDecodeError
+  .   Traceback (most recent call last):
+  .     ...
+  .   Languages available:
+  .     File "/Users/jens/se/behave_main.fix/behave/__main__.py", line 70, in main
+  .       print(u'%s: %s / %s' % (iso_code, native, name))
+  .   UnicodeEncodeError: 'ascii' codec can't encode characters in position 4-10: ordinal not in range(128)
+  .
+  . RELATED FEATURES:
+  .  * features/cmdline.lang_list.feature
+  .
+
+
+  @problematic
+  @not.with_os=win32
+  Scenario: Use behave --lang-list
+    When I run "behave --lang-list"
+    Then it should pass with:
+        """
+        Languages available:
+         ar: العربية / Arabic
+         bg: български / Bulgarian
+         ca: català / Catalan
+         cs: Česky / Czech
+         cy-GB: Cymraeg / Welsh
+         da: dansk / Danish
+         de: Deutsch / German
+         en: English / English
+        """
+    And the command output should contain:
+        """
+        sv: Svenska / Swedish
+        tr: Türkçe / Turkish
+        uk: Українська / Ukrainian
+        uz: Узбекча / Uzbek
+        vi: Tiếng Việt / Vietnamese
+        zh-CN: 简体中文 / Chinese simplified
+        zh-TW: 繁體中文 / Chinese traditional
+        """
+    But the command output should not contain "Traceback"

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

@@ -0,0 +1,124 @@
+@issue
+Feature: Issue #330: Skipped scenarios are included in junit reports when --no-skipped is used
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+      """
+      from behave import step
+
+      @step('{word:w} step passes')
+      def step_passes(context, word):
+          pass
+      """
+    And a file named "features/alice.feature" with:
+      """
+      @tag1
+      Feature: Alice
+        Scenario: Alice1
+          Given a step passes
+      """
+    And a file named "features/bob.feature" with:
+      """
+      Feature: Bob
+        Scenario: Bob1
+          Given another step passes
+      """
+    And a file named "features/charly.feature" with:
+      """
+      Feature: Charly
+
+        @tag1
+        Scenario: Charly1
+          Given some step passes
+
+        Scenario: Charly2
+          When another step passes
+      """
+    And a file named "alice_and_bob.featureset" with:
+      """
+      features/alice.feature
+      features/bob.feature
+      """
+    And a file named "behave.ini" with:
+      """
+      [behave]
+      default_format  = plain
+      junit_directory = test_results
+
+      [behave.userdata]
+      behave.reporter.junit.show_timestamp = false
+      behave.reporter.junit.show_hostname = false
+      """
+
+  Scenario: Junit report for skipped feature is not created with --no-skipped
+    When I run "behave --junit -t @tag1 --no-skipped @alice_and_bob.featureset"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 1 skipped
+      """
+    And a file named "test_results/TESTS-alice.xml" exists
+    And a file named "test_results/TESTS-bob.xml" does not exist
+    And the command output should contain:
+      """
+      Feature: Alice
+        Scenario: Alice1
+          Given a step passes ... passed
+      """
+    But the command output should not contain "Feature: Bob"
+    And note that "bob.feature is skipped"
+
+
+  Scenario: Junit report for skipped feature is created with --show-skipped
+    When I run "behave --junit -t @tag1 --show-skipped @alice_and_bob.featureset"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 1 skipped
+      """
+    And a file named "test_results/TESTS-alice.xml" exists
+    And a file named "test_results/TESTS-bob.xml" exists
+    And the file "test_results/TESTS-bob.xml" should contain:
+      """
+      <testsuite errors="0" failures="0" name="bob.Bob" skipped="1" tests="1" time="0.0">
+      """
+
+  Scenario: Junit report for skipped scenario is neither shown nor counted with --no-skipped
+    When I run "behave --junit -t @tag1 --no-skipped"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 1 skipped
+      2 scenarios passed, 0 failed, 2 skipped
+      """
+    And a file named "test_results/TESTS-alice.xml" exists
+    And a file named "test_results/TESTS-charly.xml" exists
+    And the file "test_results/TESTS-charly.xml" should contain:
+      """
+      <testsuite errors="0" failures="0" name="charly.Charly" skipped="0" tests="1"
+      """
+    And the file "test_results/TESTS-charly.xml" should not contain:
+      """
+      <testcase classname="charly.Charly" name="Charly2"
+      """
+    And note that "Charly2 is the skipped scenarion in charly.feature"
+
+
+  Scenario: Junit report for skipped scenario is shown and counted with --show-skipped
+    When I run "behave --junit -t @tag1 --show-skipped"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 1 skipped
+      2 scenarios passed, 0 failed, 2 skipped
+      """
+    And a file named "test_results/TESTS-alice.xml" exists
+    And a file named "test_results/TESTS-charly.xml" exists
+    And the file "test_results/TESTS-charly.xml" should contain:
+      """
+      <testsuite errors="0" failures="0" name="charly.Charly" skipped="1" tests="2"
+      """
+    And the file "test_results/TESTS-charly.xml" should contain:
+      """
+      <testcase classname="charly.Charly" name="Charly2" status="skipped"
+      """
+    And note that "Charly2 is the skipped scenarion in charly.feature"
+

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

@@ -0,0 +1,9 @@
+@issue
+@todo
+Feature: Issue #349 -- ScenarioOutline skipped with --format=json
+
+  . Scenario Outline feature selected and processed when called with --format=pretty 
+  . but skipped when called with --format=json.
+  .
+  . TODO: 
+  . Write feature test for problem (note: problem should be fixed by now).

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

@@ -0,0 +1,79 @@
+@issue
+Feature: Issue #361 -- UTF-8 File with BOM
+
+  . Using step files with "Byte-Order Mark" (BOM) prefix
+  . causes weird problems.
+  .
+  . FIXES ALSO: #300
+  . AFFECTED FILES:
+  .   * features/environment.py
+  .   * features/steps/*.py
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/reuse_steps.py" with:
+        """
+        from behave4cmd0 import passing_steps
+        """
+    And a file named "features/passing.feature" with:
+        """
+        Feature:
+          Scenario:
+            Given a step passes
+            Then a special step
+        """
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        show_timings = false
+        """
+
+
+  @encoding.<encoding>
+  @not.with_python.implementation=<exclude_pyimpl>
+  Scenario Outline: Use step file with <case>
+    Given a file named "features/steps/my_steps.py" and encoding="<encoding>" with:
+        """
+        # -*- coding: <encoding> -*-
+        '''
+        <text>.
+        '''
+        from behave import step
+
+        @step(u'a special step')
+        def step_impl(context):
+            pass
+        """
+    When I run "behave -f plain features/passing.feature"
+    Then it should pass with:
+        """
+        1 scenario passed, 0 failed, 0 skipped
+        2 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+          Scenario:
+            Given a step passes ... passed
+            Then a special step ... passed
+        """
+    And the command output should not contain:
+        """
+        SyntaxError: invalid character in identifier
+        """
+
+    Examples:
+      | encoding   | text                 | case                    | exclude_pyimpl | Comment |
+      | UTF-8-sig  | Ärgernis ist überall | UTF-8 encoding and BOM  | pypy  | pypy SyntaxError: UTF-8 with BOM |
+      | latin1     | Café                 | Latin1 encoding         | none  |                  |
+      | iso-8859-1 | Ärgernis ist überall | iso-8859-1 encoding     | none  | Alias for latin1 |
+      | cp1252     | Ärgernis ist überall | cp1252 encoding         | none  | Windows: Western Europe |
+      | cp1251     | Привет! (=hello)     | cp1251 encoding (Russia)| none  | Windows: Russia  |
+      | cp866      | Привет! (=hello)     | cp688 encoding (Russia) | none  | IBM866:  Russia  |
+      | euc_jp     | こんにちは (=hello)  | euc_jp encoding (Japan) | none  | Japanese         |
+      | gbk        | 您好 (=hello)        | gbk encoding (China)    | none  | Unified Chinese  |
+      | gb2312     | 您好 (=hello)        | gb2312 encoding (China) | none  | Simplified Chinese |
+
+    # -- DISABLE EXAMPLE ROW: Pypy 4.x has SyntaxError with UTF-8 BOM
+    # | UTF-8-sig  | Ärgernis ist überall | UTF-8 encoding and BOM  |  |