busser-behave 0.1.3

data/vendor/behave/features/capture_stderr.feature

@@ -0,0 +1,172 @@
+@sequential
+Feature: Capture stderr output and show it in case of failures/errors
+
+    As a tester
+    To simplify failure diagnostics
+    I want that:
+      - captured output is displayed only when failures/errors occur
+      - all output is displayed when capture is disabled
+        (but may clutter up formatter output)
+
+    @setup
+    Scenario: Test Setup
+        Given a new working directory
+        And   a file named "features/steps/stderr_steps.py" with:
+            """
+            from behave import step
+            import sys
+
+            @step('a step writes "{text}" to stderr and passes')
+            def step_writes_to_stderr_and_passes(context, text):
+                sys.stderr.write("stderr:%s;\n" % text)
+
+            @step('a step writes "{text}" to stderr and fails')
+            def step_writes_to_stderr_and_fails(context, text):
+                sys.stderr.write("stderr:%s;\n" % text)
+                assert False, "XFAIL, step with: %s;" % text
+            """
+        And a file named "features/capture_stderr.example1.feature" with:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes
+                    When a step writes "Bob" to stderr and passes
+                    Then a step writes "Charly" to stderr and passes
+            """
+        And a file named "features/capture_stderr.example2.feature" with:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes
+                    When a step writes "Bob" to stderr and fails
+                    Then a step writes "Charly" to stderr and fails
+            """
+
+
+    @capture
+    Scenario: Captured output is suppressed if scenario passes (CASE 1: --capture)
+        When I run "behave -f plain -T --capture features/capture_stderr.example1.feature"
+        Then it should pass
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and passes ... passed
+                    Then a step writes "Charly" to stderr and passes ... passed
+            """
+        But the command output should not contain:
+            """
+            stderr:Alice;
+            """
+
+    @capture
+    Scenario: Captured output is suppressed if scenario passes (CASE 2: --capture-stderr)
+        When I run "behave -f plain -T --capture-stderr features/capture_stderr.example1.feature"
+        Then it should pass
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and passes ... passed
+                    Then a step writes "Charly" to stderr and passes ... passed
+            """
+        But the command output should not contain:
+            """
+            stderr:Alice;
+            """
+
+    @capture
+    Scenario: Captured output is shown up to first failure if scenario fails (CASE 1: --capture)
+        When I run "behave -f plain -T --capture features/capture_stderr.example2.feature"
+        Then it should fail with:
+            """
+            0 scenarios passed, 1 failed, 0 skipped
+            1 step passed, 1 failed, 1 skipped, 0 undefined
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and fails ... failed
+            Assertion Failed: XFAIL, step with: Bob;
+            Captured stderr:
+            stderr:Alice;
+            stderr:Bob;
+            """
+        But the command output should not contain:
+            """
+            stderr:Charly;
+            """
+
+    @capture
+    Scenario: Captured output is shown if scenario fails up to first failure (CASE 2: --capture-stderr)
+        When I run "behave -f plain -T --capture-stderr features/capture_stderr.example2.feature"
+        Then it should fail with:
+            """
+            0 scenarios passed, 1 failed, 0 skipped
+            1 step passed, 1 failed, 1 skipped, 0 undefined
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and fails ... failed
+            Assertion Failed: XFAIL, step with: Bob;
+            Captured stderr:
+            stderr:Alice;
+            stderr:Bob;
+            """
+        But the command output should not contain:
+            """
+            stderr:Charly;
+            """
+
+    @no_capture
+    Scenario: All output is shown when --no-capture-stderr is used and all steps pass (CASE 1)
+        When I run "behave -f plain -T --no-capture-stderr features/capture_stderr.example1.feature"
+        Then it should pass
+        And the command output should contain:
+            """
+            stderr:Alice;
+            stderr:Bob;
+            stderr:Charly;
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and passes ... passed
+                    Then a step writes "Charly" to stderr and passes ... passed
+            """
+
+
+    @no_capture
+    Scenario: All output is shown up to first failing step when --no-capture-stderr is used (CASE 2)
+        When I run "behave -f plain -T --no-capture-stderr features/capture_stderr.example2.feature"
+        Then it should fail with:
+            """
+            0 scenarios passed, 1 failed, 0 skipped
+            1 step passed, 1 failed, 1 skipped, 0 undefined
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stderr and passes ... passed
+                    When a step writes "Bob" to stderr and fails ... failed
+            Assertion Failed: XFAIL, step with: Bob;
+            """
+        And the command output should contain:
+            """
+            stderr:Alice;
+            stderr:Bob;
+            """
+        But the command output should not contain:
+            """
+            stderr:Charly;
+            """

data/vendor/behave/features/capture_stdout.feature

@@ -0,0 +1,125 @@
+@sequential
+Feature: Capture stdout output and show it in case of failures/errors
+
+    As a tester
+    To simplify failure diagnostics
+    I want that:
+      - captured output is displayed only when failures/errors occur
+      - all output is displayed when capture is disabled
+        (but may clutter up formatter output)
+
+
+    @setup
+    Scenario: Test Setup
+        Given a new working directory
+        And a file named "features/steps/stdout_steps.py" with:
+            """
+            from behave import step
+            import sys
+
+            @step('a step writes "{text}" to stdout and passes')
+            def step_writes_to_stdout_and_passes(context, text):
+                sys.stdout.write("stdout:%s;\n" % text)
+
+            @step('a step writes "{text}" to stdout and fails')
+            def step_writes_to_stdout_and_fails(context, text):
+                sys.stdout.write("stdout:%s;\n" % text)
+                assert False, "XFAIL, step with: %s;" % text
+            """
+        And a file named "features/capture_stdout.example1.feature" with:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stdout and passes
+                    When a step writes "Bob" to stdout and passes
+                    Then a step writes "Charly" to stdout and passes
+            """
+        And a file named "features/capture_stdout.example2.feature" with:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stdout and passes
+                    When a step writes "Bob" to stdout and fails
+                    Then a step writes "Charly" to stdout and fails
+            """
+
+
+    @capture
+    Scenario: Captured output is suppressed if scenario passes
+        When I run "behave -f plain -T --capture features/capture_stdout.example1.feature"
+        Then it should pass
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stdout and passes ... passed
+                    When a step writes "Bob" to stdout and passes ... passed
+                    Then a step writes "Charly" to stdout and passes ... passed
+            """
+        But the command output should not contain:
+            """
+            stdout:Alice;
+            """
+
+    @capture
+    Scenario: Captured output is shown up to first failure if scenario fails
+        When I run "behave -f plain -T --capture features/capture_stdout.example2.feature"
+        Then it should fail with:
+            """
+            0 scenarios passed, 1 failed, 0 skipped
+            1 step passed, 1 failed, 1 skipped, 0 undefined
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    Given a step writes "Alice" to stdout and passes ... passed
+                    When a step writes "Bob" to stdout and fails ... failed
+            Assertion Failed: XFAIL, step with: Bob;
+            Captured stdout:
+            stdout:Alice;
+            stdout:Bob;
+            """
+        But the command output should not contain:
+            """
+            stdout:Charly;
+            """
+
+    @no_capture
+    Scenario: All output is shown when --no-capture is used and all steps pass (CASE 1)
+        When I run "behave -f plain -T --no-capture features/capture_stdout.example1.feature"
+        Then it should pass
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    stdout:Alice;
+                    Given a step writes "Alice" to stdout and passes ... passed
+                    stdout:Bob;
+                    When a step writes "Bob" to stdout and passes ... passed
+                    stdout:Charly;
+                    Then a step writes "Charly" to stdout and passes ... passed
+            """
+
+
+    @no_capture
+    Scenario: All output is shown up to first failing step when --no-capture is used (CASE 2)
+        When I run "behave -f plain -T --no-capture features/capture_stdout.example2.feature"
+        Then it should fail with:
+            """
+            0 scenarios passed, 1 failed, 0 skipped
+            1 step passed, 1 failed, 1 skipped, 0 undefined
+            """
+        And the command output should contain:
+            """
+            Feature:
+                Scenario:
+                    stdout:Alice;
+                    Given a step writes "Alice" to stdout and passes ... passed
+                    stdout:Bob;
+                    When a step writes "Bob" to stdout and fails ... failed
+            """
+        But the command output should not contain:
+            """
+            stdout:Charly;
+            """

data/vendor/behave/features/cmdline.lang_list.feature

@@ -0,0 +1,33 @@
+Feature: Command-line options: Use behave --lang-list
+
+  As a user
+  I want to determine which languages are supported by behave
+  So that I can use the language code in feature files or command lines
+
+  @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/features/configuration.default_paths.feature

@@ -0,0 +1,116 @@
+@sequential
+Feature: Default paths for features in behave configfile
+
+    As a tester
+    I want to specify the default paths for features in the configuration file
+    That should be used if none are provided as command-line args
+    To support pre-pared/canned test environments
+    (and to support my laziness while using behave in a shell).
+
+
+    @setup
+    Scenario: Test Setup
+        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/alice.feature" with:
+            """
+            Feature: Alice
+                Scenario: A1
+                    Given a step passes
+                    When a step passes
+                    Then a step passes
+            """
+        And a file named "features/bob.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                    When a step passes
+            """
+        And a file named "more.features/charly.feature" with:
+            """
+            Feature: Charly
+                Scenario: C1
+                    Then a step passes
+            """
+        And a file named "behave.ini" with:
+            """
+            [behave]
+            show_timings = false
+            paths = features/bob.feature
+                    more.features/charly.feature
+            """
+
+    Scenario: Used default paths from behave configfile
+        When I run "behave -f plain"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            """
+        And the command output should contain:
+            """
+            Feature: Bob
+                Scenario: B1
+                    When a step passes ... passed
+
+            Feature: Charly
+                Scenario: C1
+                    Then a step passes ... passed
+            """
+        But the command output should not contain:
+            """
+            Feature: Alice
+            """
+
+    Scenario: Command-line args can override default paths in configfile
+        When I run "behave -f plain features/alice.feature"
+        Then it should pass with:
+            """
+            1 feature passed, 0 failed, 0 skipped
+            1 scenario passed, 0 failed, 0 skipped
+            3 steps passed, 0 failed, 0 skipped, 0 undefined
+             """
+        And the command output should contain:
+            """
+            Feature: Alice
+                Scenario: A1
+            """
+        But the command output should not contain:
+            """
+            Feature: Bob
+            """
+        And the command output should not contain:
+            """
+            Feature: Charly
+            """
+
+    Scenario: Command-line args are provided (CASE 2)
+        When I run "behave -f plain features"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+             """
+        And the command output should contain:
+            """
+            Feature: Alice
+                Scenario: A1
+                    Given a step passes ... passed
+                    When a step passes ... passed
+                    Then a step passes ... passed
+
+            Feature: Bob
+                Scenario: B1
+                    When a step passes ... passed
+            """
+        But the command output should not contain:
+            """
+            Feature: Charly
+            """

data/vendor/behave/features/context.global_params.feature

@@ -0,0 +1,35 @@
+Feature: Global Context Parameters defined in environment file
+
+  . SPECIFICATION:
+  .   * When a Context parameter is defined in "environment.py",
+  .     its value is provided to all scenarios (steps).
+  .   * Each scenario has the same global parameters (and values).
+  .   * A scenario (step) may modify global parameters (values).
+  .   * After a scenario is executed all changes to Context parameters are reverted.
+
+    Scenario: Test Setup Description (Example)
+      Given a file named "features/environment.py" with:
+        """
+        def before_all(context):
+            context.global_name = "env:Alice"
+            context.global_age  = 12
+        """
+
+    Scenario: Modify global Context parameter in Scenario Step
+      Given the behave context contains:
+        | Parameter   | Value        |
+        | global_name | "env:Alice"  |
+        | global_age  | 12           |
+      When I set the context parameter "global_name" to "step:Bob"
+      Then the behave context should contain:
+        | Parameter   | Value        |
+        | global_name | "step:Bob"   |
+        | global_age  | 12           |
+
+    Scenario: Ensure that Global Context parameter is reset for next Scenario
+      Then the behave context should have a parameter "global_name"
+      And  the behave context should contain:
+        | Parameter   | Value        |
+        | global_name | "env:Alice"  |
+        | global_age  | 12           |
+