busser-behave 0.1.3

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

@@ -0,0 +1,102 @@
+@issue
+Feature: Issue #63: 'ScenarioOutline' object has no attribute 'stdout'
+
+  The problem occurs when "behave --junit ..." is used
+  And a feature contains one or more ScenarioOutline(s).
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      # -- OMIT: from __future__ import print_function
+      from behave import given
+      import sys
+
+      def generate_output(step, outcome, name):
+          # -- OMIT: print("{0}0 {1}: {2};".format(step, outcome, name))
+          sys.stdout.write("{0}1 {1}: {2};\n".format(step, outcome, name))
+          sys.stderr.write("{0}2 {1}: {2};\n".format(step, outcome, name))
+
+      @given(u'a {outcome} step with "{name}"')
+      def step(context, outcome, name):
+          context.name = name
+          generate_output("Given", outcome, name)
+          assert outcome == "passing"
+
+      @when(u'a {outcome} step with "{name}" occurs')
+      def step(context, outcome, name):
+          generate_output("When", outcome, name)
+          assert outcome == "passing"
+
+      @then(u'a {outcome} step with "{name}" is reached')
+      def step(context, outcome, name):
+          generate_output("Then", outcome, name)
+          assert outcome == "passing"
+          assert context.name == name
+      """
+
+  Scenario: ScenarioOutline with Passing Steps
+    Given a file named "features/issue63_case1.feature" with:
+      """
+      Feature: ScenarioOutline with Passing Steps
+        Scenario Outline:
+          Given a passing step with "<name>"
+          When  a passing step with "<name>" occurs
+          Then  a passing step with "<name>" is reached
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c --junit features/issue63_case1.feature"
+    Then it should pass with:
+      """
+      2 scenarios passed, 0 failed, 0 skipped
+      6 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      AttributeError: 'ScenarioOutline' object has no attribute 'stdout'
+      """
+
+  Scenario: ScenarioOutline with Passing and Failing Steps
+    Given a file named "features/issue63_case2.feature" with:
+      """
+      Feature: ScenarioOutline with Passing and Failing Steps
+        Scenario Outline:
+          Given a passing step with "<name>"
+          When  a failing step with "<name>" occurs
+          Then  a passing step with "<name>" is reached
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c --junit features/issue63_case2.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 2 failed, 0 skipped
+      2 steps passed, 2 failed, 2 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      AttributeError: 'ScenarioOutline' object has no attribute 'stdout'
+      """
+    And the command output should not contain:
+      """
+      AttributeError: 'Scenario' object has no attribute 'exception'
+      """
+    And the command output should contain:
+      """
+      Captured stdout:
+      Given1 passing: Alice;
+      When1 failing: Alice;
+      """
+    And the command output should contain:
+      """
+      Captured stderr:
+      Given2 passing: Alice;
+      When2 failing: Alice;
+      """

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

@@ -0,0 +1,97 @@
+@issue
+Feature: Issue #64 Exit status not set to 1 even there are failures in certain cases
+
+  The behave exit status not always returns 1 when failure(s) occur.
+  The problem was associated with the Feature.run() logic implementation.
+
+  This problem was first discovered while verifying issue #52 (see comments).
+  See also similar test when tags select a subset of scenarios.
+
+  RELATED ISSUES:
+    * issue #52
+
+  Background: Test Setup
+    Given a new working directory
+    Given a file named "features/steps/steps.py" with:
+      """
+      from behave import given
+
+      @given(u'passing')
+      def step(context):
+          pass
+
+      @given(u'failing')
+      def step(context):
+          assert False, "failing"
+      """
+
+  Scenario: Failing in First Scenario
+    Given a file named "features/issue64_case1.feature" with:
+      """
+      Feature: Failing in First Scenario
+        Scenario:
+          Given failing
+
+        Scenario:
+          Given passing
+      """
+    When I run "behave --format=plain features/issue64_case1.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      1 scenario passed, 1 failed, 0 skipped
+      """
+
+  Scenario: Failing in Middle Scenario
+    Given a file named "features/issue64_case2.feature" with:
+      """
+      Feature: Failing in Middle Scenario
+        Scenario:
+          Given passing
+        Scenario:
+          Given failing
+        Scenario:
+          Given passing
+      """
+    When I run "behave --format=plain features/issue64_case2.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      2 scenarios passed, 1 failed, 0 skipped
+      """
+
+  Scenario: Failing in Last Scenario
+    Given a file named "features/issue64_case3.feature" with:
+      """
+      Feature: Failing in Last Scenario
+        Scenario:
+          Given passing
+        Scenario:
+          Given passing
+        Scenario:
+          Given failing
+      """
+    When I run "behave --format=plain features/issue64_case3.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      2 scenarios passed, 1 failed, 0 skipped
+      """
+
+  Scenario: Failing in First and Last Scenario
+    Given a file named "features/issue64_case4.feature" with:
+      """
+      Feature: Failing in First and Last Scenario
+        Scenario:
+          Given failing
+        Scenario:
+          Given passing
+        Scenario:
+          Given failing
+      """
+    When I run "behave --format=plain features/issue64_case4.feature"
+    Then it should fail with:
+      """
+      0 features passed, 1 failed, 0 skipped
+      1 scenario passed, 2 failed, 0 skipped
+      """

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

@@ -0,0 +1,18 @@
+@issue
+Feature: Issue #65  Unrecognized --tag-help argument
+
+  The "behave --help" output refers to the option "--tag-help"
+  in the description of the "--tags" option.
+  The correct option for more help on tags is "--tags-help".
+
+  Scenario: Ensure environment assumptions are correct (Sanity Check)
+    Given a new working directory
+    When I run "behave --help"
+    Then the command output should contain:
+      """
+      --tags-help
+      """
+    But  the command output should not contain:
+      """
+      --tag-help
+      """

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

@@ -0,0 +1,80 @@
+@issue
+Feature: Issue #66: context.text and context.table are not cleared
+
+  I noticed that context.table and context.text survive after the step is finished.
+
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+      from hamcrest import assert_that, equal_to, is_not, is_, none
+      import six
+
+      @given(u'a step with multiline text')
+      def step(context):
+          assert context.text is not None
+          assert context.text, "Ensure non-empty"
+          assert isinstance(context.text, six.string_types)
+
+      @given(u'a step with a table')
+      def step(context):
+          assert context.table is not None
+
+      @when(u'I check the "context.{name}" attribute')
+      def step(context, name):
+          context.name  = name
+          context.value = getattr(context, name, None)
+
+      @then(u'its value is None')
+      def step(context):
+          assert_that(context.value, is_(none()))
+
+      @then(u'its value is "{value}"')
+      def step(context, value):
+          assert_that(context.value, equal_to(value))
+
+      @then(u'its value is not "{value}"')
+      def step(context, value):
+          assert_that(value, is_not(equal_to(context.value)))
+      """
+
+  Scenario: Ensure multiline text data is cleared for next step
+    Given a file named "features/issue66_case1.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step with multiline text:
+            '''
+            Alice, Bob and Charly
+            '''
+          When I check the "context.text" attribute
+          Then its value is not "Alice, Bob and Charly"
+          But  its value is None
+      """
+    When I run "behave -f plain features/issue66_case1.feature"
+    Then it should pass with:
+      """
+      1 scenario passed, 0 failed, 0 skipped
+      4 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: Ensure table data is cleared for next step
+    Given a file named "features/issue66_case2.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step with a table:
+            | name  | gender |
+            | Alice | female |
+            | Bob   | male   |
+          When I check the "context.table" attribute
+          Then its value is None
+      """
+    When I run "behave -f plain features/issue66_case2.feature"
+    Then it should pass with:
+      """
+      1 scenario passed, 0 failed, 0 skipped
+      3 steps passed, 0 failed, 0 skipped, 0 undefined
+      """

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

@@ -0,0 +1,90 @@
+@issue
+Feature: Issue #67: JSON formatter cannot serialize tables.
+
+  The JSON formatter cannot handle tables (currently):
+
+    * Table as setup/intermediate/result table in steps of scenario
+    * Examples tables in a ScenarioOutline
+
+  A JSON exception occurs when such a feature file should be processed.
+
+
+  Scenario: Scenario with Tables
+    Given a new working directory
+    And   a file named "features/steps/steps1.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'I add the following employees')
+      def step(context):
+          pass  # -- SKIP: Table processing here.
+
+      @when(u'I select department "{department}"')
+      def step(context, department):
+          context.department = department
+
+      @then(u'I get the following employees')
+      def step(context):
+          pass  # -- SKIP: Table processing here.
+      """
+    And  a file named "features/issue67_case1.feature" with:
+      """
+      Feature: Scenario with Tables
+        Scenario:
+         Given I add the following employees:
+            | name      | department  |
+            | Alice     | Wonderland  |
+            | Bob       | Moonwalk    |
+          When I select department "Wonderland"
+          Then I get the following employees:
+            | name      | department  |
+            | Alice     | Wonderland  |
+      """
+    When I run "behave -f json features/issue67_case1.feature"
+    Then it should pass with:
+      """
+      1 scenario passed, 0 failed, 0 skipped
+      3 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      TypeError: <Row [u'Alice', u'Wonderland']> is not JSON serializable
+      """
+
+  Scenario: ScenarioOutline with Examples Table
+    Given a file named "features/steps/steps2.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'a step with "{name}"')
+      def step(context, name):
+          context.name = name
+
+      @when(u'a step with "{name}" occurs')
+      def step(context, name):
+          assert context.name == name
+
+      @then(u'a step with "{name}" is reached')
+      def step(context, name):
+          assert context.name == name
+      """
+    And a file named "features/issue67_case2.feature" with:
+      """
+      Feature: ScenarioOutline with Examples Table
+        Scenario Outline:
+          Given a step with "<name>"
+          When  a step with "<name>" occurs
+          Then  a step with "<name>" is reached
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -f json features/issue67_case2.feature"
+    Then it should pass with:
+      """
+      2 scenarios passed, 0 failed, 0 skipped
+      6 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+

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

@@ -0,0 +1,64 @@
+@issue
+Feature: Issue #69: JUnitReporter: Fault when processing ScenarioOutlines with failing steps
+
+  The problem occurs when "behave --junit ..." is used
+  And a feature contains one or more ScenarioOutline(s) with failing steps.
+
+  The JUnitReport does not process ScenarioOutline correctly (logic-error).
+  Therefore, Scenarios of a ScenarioOutline are processes as Scenario steps.
+  This causes problems when the step.status is "failed".
+
+  RELATED:
+    * issue #63
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given
+
+      @given(u'a {outcome} step with "{name}"')
+      def step(context, outcome, name):
+          context.name = name
+          assert outcome == "passing"
+
+      @when(u'a {outcome} step with "{name}" occurs')
+      def step(context, outcome, name):
+          assert outcome == "passing"
+          assert context.name == name
+
+      @then(u'a {outcome} step with "{name}" is reached')
+      def step(context, outcome, name):
+          assert outcome == "passing"
+          assert context.name == name
+      """
+
+  Scenario: ScenarioOutline with Failing Steps
+    Given a file named "features/issue63_case2.feature" with:
+      """
+      Feature: ScenarioOutline with Passing and Failing Steps
+        Scenario Outline:
+          Given a passing step with "<name>"
+          When  a failing step with "<name>" occurs
+          Then  a passing step with "<name>" is reached
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c --junit features/issue63_case2.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 2 failed, 0 skipped
+      2 steps passed, 2 failed, 2 skipped, 0 undefined
+      """
+    But the command output should not contain:
+      """
+      AttributeError: 'Scenario' object has no attribute 'exception'
+      """
+    And the command output should not contain:
+      """
+      behave/reporter/junit.py
+      """
+