busser-behave 0.1.3

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

@@ -0,0 +1,74 @@
+@issue
+Feature: Issue #159: output stream is wrapped twice in the codecs.StreamWriter
+
+  @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
+
+      @step('firstname is "{name}"')
+      def step_impl(context, name):
+          pass
+
+      @step(u'full name is Loïc "{name}"')
+      def step_impl(context, name):
+          pass
+      """
+
+  Scenario: Single feature, pass (a)
+    Given a file named "features/issue159_stream_writer.feature" with:
+      """
+      Feature:
+        Scenario:
+          When firstname is "Loïc"
+      """
+    When I run "behave -f plain features/"
+    Then it should pass
+
+
+  Scenario: Single feature, pass (b)
+    Given a file named "features/issue159_stream_writer.feature" with:
+      """
+      Feature:
+        Scenario:
+          When full name is Loïc "Dupont"
+      """
+    When I run "behave -f plain features/"
+    Then it should pass
+
+
+  Scenario: Two features, FAIL (a)
+    Given a file named "features/issue159_stream_writer.feature" with:
+      """
+      Feature:
+        Scenario:
+          When full name is Loïc "Dupont"
+      """
+    And   a file named "features/issue159_stream_writer_again.feature" with:
+      """
+      Feature:
+        Scenario:
+          When full name is Loïc "Dupond"
+      """
+    When I run "behave -f plain features/"
+    Then it should pass
+
+
+  Scenario: Two features, FAIL (b)
+    Given a file named "features/issue159_stream_writer.feature" with:
+      """
+      Feature:
+        Scenario:
+          When firstname is "Loïc"
+      """
+    And   a file named "features/issue159_stream_writer_again.feature" with:
+      """
+      Feature:
+        Scenario:
+          When firstname is "Loïc"
+      """
+    When I run "behave -f plain features/"
+    Then it should pass

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

@@ -0,0 +1,86 @@
+@issue
+Feature: Issue #162 Unnecessary ContextMaskWarnings when assert fails or exception is raised
+
+  . Behave shows unnecessary ContextMaskWarnings related to:
+  .
+  .   * tags
+  .   * capture_stdout
+  .   * capture_stderr
+  .   * log_capture
+  .
+  . if:
+  .
+  .   * an assertion fails in a step-definition/step-function
+  .   * an exception is raised by a step-definition/step-function
+  .
+  . and an additional scenario follows.
+  . REASON: Context "behave" mode is not restored when an exception is raised.
+
+
+  @setup
+  Scenario: Feature 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
+
+      @step('a step assert fails')
+      def step_assert_fails(context):
+          assert False, "XFAIL-STEP"
+
+      @step('an exception is raised')
+      def step_raises_exception(context):
+          raise RuntimeError("XFAIL-STEP")
+      """
+
+
+  Scenario: Assertion fails in a step
+    Given a file named "features/example0162_assert_fails.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step passes
+          When a step assert fails
+          Then a step passes
+
+        Scenario:
+          Given a step passes
+      """
+    When I run "behave -f plain features/example0162_assert_fails.feature"
+    Then it should fail with:
+      """
+      1 scenario passed, 1 failed, 0 skipped
+      2 steps passed, 1 failed, 1 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      ContextMaskWarning: user code is masking context attribute
+      """
+
+
+  Scenario: Exception is raised in a step
+    Given a file named "features/example0162_exception_raised.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step passes
+          When an exception is raised
+          Then a step passes
+
+        Scenario:
+          Given a step passes
+      """
+    When I run "behave -f plain features/example0162_exception_raised.feature"
+    Then it should fail with:
+      """
+      1 scenario passed, 1 failed, 0 skipped
+      2 steps passed, 1 failed, 1 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      ContextMaskWarning: user code is masking context attribute
+      """

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

@@ -0,0 +1,16 @@
+@issue
+Feature: Issue #171: Importing step from other step file fails with AmbiguousStep Error
+
+  . When a step module imports another step module
+  . this should not cause AmbiguousStep errors
+  . due to duplicated registration of the same step functions.
+  .
+  . NOTES:
+  .   * In general you should avoid this case (provided as example here).
+
+
+  @reuse.colocated_test
+  Scenario: Step module imports other step module
+    Given I use the current directory as working directory
+    When I run "behave -f plain features/step.import_other_step_module.feature"
+    Then it should pass

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

@@ -0,0 +1,51 @@
+@issue
+Feature: Issue #172 Junit report file name populated incorrectly when running against a feature file
+
+  @setup
+  Scenario: Feature 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/feature_in_root_folder.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step passes
+      """
+    And a file named "features/subfolder/feature_in_subfolder.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step passes
+      """
+
+  Scenario: Running behave for one feature in root folder
+    When I run "behave --junit --junit-directory=test_results features/feature_in_root_folder.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      """
+    And a file named "test_results/TESTS-feature_in_root_folder.xml" exists
+
+  Scenario: Running behave for one feature in a subfolder
+    When I run "behave --junit --junit-directory=test_results features/subfolder/feature_in_subfolder.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      """
+    And a file named "test_results/TESTS-subfolder.feature_in_subfolder.xml" exists
+
+  Scenario: Running behave for all features
+    When I run "behave --junit --junit-directory=test_results"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      """
+    And a file named "test_results/TESTS-feature_in_root_folder.xml" exists
+    And a file named "test_results/TESTS-subfolder.feature_in_subfolder.xml" exists

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

@@ -0,0 +1,91 @@
+@issue
+Feature: Issue #175: Scenario isn't marked as 'failed' when Background step fails
+
+  Scenario has currently status "skipped" when a background step fails.
+  Expected is that scenario status should be "failed".
+  Ensure that this is the case.
+
+  RELATED: features/background.feature
+  REUSE:   Scenario from there (as copy).
+
+  . NOTE:
+  .     Cucumber has a slightly different behaviour.
+  .     When a background step fails the first scenario is marked as failed.
+  .     But the remaining scenarios are marked as skipped.
+  .
+  .     This can lead to problems when you have sporadic background step failures.
+  .     For this reason, behave retries the background steps for each scenario.
+  .
+  . SEE ALSO:
+  .   * https://github.com/cucumber/cucumber/blob/master/features/docs/gherkin/background.feature
+
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/background_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word} background step {outcome}')
+        def step_background_step_passes_or_fails(context, word, outcome):
+            if outcome == "fails":
+                assert False, "XFAIL: background step"
+            elif outcome == "passes":
+                pass
+            else:
+                message = "Unexpected outcome=%s. Use: passes, fails"
+                raise RuntimeError(message % outcome)
+        """
+    And a file named "features/steps/passing_steps.py" with:
+        """
+        from behave import step
+
+        @step('{word} step passes')
+        def step_passes(context, word):
+            pass
+
+        @step('{word} step fails')
+        def step_passes(context, word):
+            assert False, "XFAIL"
+        """
+
+
+  Scenario: Failing Background Step causes all Scenarios to fail
+    Given a file named "features/example.background_step_fails.feature" with:
+        """
+        Feature:
+
+          Background: B1
+            Given a background step passes
+            And a background step fails
+            And another background step passes
+
+          Scenario: S1
+            When a step passes
+
+          Scenario: S2
+            Then a step passes
+            And another step passes
+        """
+    When I run "behave -f plain -T features/example.background_step_fails.feature"
+    Then it should fail with:
+        """
+        0 scenarios passed, 2 failed, 0 skipped
+        2 steps passed, 2 failed, 5 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+          Background: B1
+
+          Scenario: S1
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario: S2
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+        """

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

@@ -0,0 +1,40 @@
+@issue
+Feature: Issue #177: Cannot setup logging_format
+  
+  . DESCPRIPTION:
+  .   When the logging_format is set in the behave configuration file
+  .   or on command-line, an exception is thrown, because
+  .   the ConfigParser tries to replace the placeholders in the format string
+  .   with option values in the configuration file (which do not exist).
+  .
+  . SOLUTION:
+  .   The format string must be processed as raw value (by the ConfigParser).
+  .
+  . RELATED:
+  .   * features/logging.setup_format.feature
+  .   * features/logging.setup_level.feature
+
+
+  @reuse.colocated_test
+  Scenario: Setup logging_format
+    Given I use the current directory as working directory
+    When I run "behave -f plain features/logging.setup_format.feature"
+    Then it should pass
+    And the command output should not contain:
+      """
+      Traceback (most recent call last):
+      """
+    And the command output should not contain:
+      """
+      ConfigParser.InterpolationMissingOptionError: Bad value
+      """
+
+  @reuse.colocated_test
+  Scenario: Setup logging_level
+
+    Ensure that the problem that was also mentioned, works as expected.
+    Note that this "problem" never existed (hint: missing user knowledge).
+
+    Given I use the current directory as working directory
+    When I run "behave -f plain features/logging.setup_level.feature"
+    Then it should pass

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

@@ -0,0 +1,36 @@
+@issue
+Feature: Issue #181: Escape apostrophes in undefined steps snippets
+
+  . I have noticed that, for the following line in my features file:
+  .
+  .   Then I'm redirected to http://www.example.com
+  .
+  . Behave outputs the following:
+  .
+  .   @then(u'I'm redirected to http://www.example.com')
+  .   def step_impl(context):
+  .       assert False
+
+
+  Scenario:
+    Given a new working directory
+    And an empty file named "features/steps/steps.py"
+    And a file named "features/issue181_example.feature" with
+        """
+        Feature:
+          Scenario:
+            Given I'm using an "undefined step"
+        """
+    When I run "behave -f plain features/issue181_example.feature"
+    Then it should fail with:
+        """
+        0 steps passed, 0 failed, 0 skipped, 1 undefined
+        """
+    And the command output should contain:
+        """
+        You can implement step definitions for undefined steps with these snippets:
+
+        @given(u'I\'m using an "undefined step"')
+        def step_impl(context):
+            raise NotImplementedError(u'STEP: Given I\'m using an "undefined step"')
+        """

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

@@ -0,0 +1,144 @@
+@issue
+Feature: Issue #184: TypeError when running behave with --include option
+
+  . Running behave with option '--include' causes fail with following error:
+  .
+  .  Traceback (most recent call last):
+  .   File "/.../bin/behave", line 8, in
+  .     load_entry_point('behave==1.2.3', 'console_scripts', 'behave')()
+  .   File "/.../lib/python2.7/site-packages/behave/__main__.py", line 111, in main
+  .   ...
+  .   File "/.../lib/python2.7/site-packages/behave/runner.py", line 490, in run_with_paths
+  .     if not self.config.exclude(filename) ]
+  .   File "/.../lib/python2.7/site-packages/behave/configuration.py", line 488, in exclude
+  .     if self.include_re and self.include_re.search(filename) is None:
+  .   TypeError: expected string or buffer
+  .
+  . RELATED:
+  .  * features/runner.select_files_by_regexp.feature
+  .  * features/runner.select_files_by_regexp2.feature
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/passing_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:
+      """
+      Feature: Alice
+        Scenario: A1
+          Given a step passes
+      """
+    And a file named "features/bob.feature" with:
+      """
+      Feature: Bob
+        Scenario: B1
+          When another step passes
+
+        Scenario: B2
+          Then another step passes
+      """
+
+  Scenario: Use --include command-line option to select some features
+    When I run "behave -f plain --include='features/a.*\.feature'"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Alice
+      """
+    But the command output should not contain:
+      """
+      Feature: Bob
+      """
+
+
+  Scenario: Use --include command-line option to select all features
+    When I run "behave -f plain --include='.*\.feature'"
+    Then it should pass with:
+      """
+      2 features passed, 0 failed, 0 skipped
+      3 scenarios passed, 0 failed, 0 skipped
+      """
+
+
+  Scenario: Use --exclude command-line option
+    When I run "behave -f plain --exclude='features/a.*\.feature'"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Bob
+      """
+    But the command output should not contain:
+      """
+      Feature: Alice
+      """
+
+
+  Scenario: Use --include and --exclude command-line options
+    When I run "behave -f plain --include='.*\.feature' --exclude='features/a.*\.feature'"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      2 scenarios passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Bob
+      """
+    But the command output should not contain:
+      """
+      Feature: Alice
+      """
+
+  Scenario: Use --include command-line option with file location
+    When I run "behave -f plain --include='features/a.*\.feature' features/alice.feature:3"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Alice
+      """
+    But the command output should not contain:
+      """
+      Feature: Bob
+      """
+
+  Scenario: Use --exclude command-line option with feature list file
+    Given a file named "selected.txt" with:
+      """
+      # -- FEATURE-LIST FILE:
+      features/alice.feature:3
+      features/bob.feature:7
+      """
+    When I run "behave -f plain --no-skipped --exclude='.*/a.*\.feature' @selected.txt"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 1 skipped
+      """
+    And the command output should contain:
+      """
+      Feature: Bob
+        Scenario: B2
+      """
+    But the command output should not contain:
+      """
+      Feature: Alice
+      """