busser-behave 0.1.3

data/vendor/behave/invoke.yaml

@@ -0,0 +1,21 @@
+# =====================================================
+# INVOKE CONFIGURATION:
+# =====================================================
+# -- ON WINDOWS:
+# run:
+#   echo: true
+#   pty:  false
+#   shell: C:\Windows\System32\cmd.exe
+# =====================================================
+
+run:
+    echo: true
+    pty:  true
+
+behave_test:
+    scopes:
+      - features
+      - tools/test-features
+      - issue.features
+    args: features tools/test-features issue.features
+

data/vendor/behave/issue.features/README.txt

@@ -0,0 +1,17 @@
+issue.features:
+===============================================================================
+
+:Status:   PREPARED (fixes are being applied).
+:Requires: Python >= 2.6 (due to step implementations)
+
+This directory contains behave self-tests to ensure that behave related
+issues are fixed.
+
+PROCEDURE:
+
+    * ONCE: Install python requirements ("requirements.txt")
+    * Run the tests with behave
+
+::
+
+    bin/behave -f progress issue.features/

data/vendor/behave/issue.features/environment.py

@@ -0,0 +1,97 @@
+# -*- coding: UTF-8 -*-
+# FILE: features/environment.py
+# pylint: disable=unused-argument
+"""
+Functionality:
+
+  * active tags
+"""
+
+from __future__ import print_function
+import sys
+import platform
+import os.path
+import six
+from behave.tag_matcher import ActiveTagMatcher
+from behave4cmd0.setup_command_shell import setup_command_shell_processors4behave
+# PREPARED:
+# from behave.tag_matcher import setup_active_tag_values
+
+
+def require_tool(tool_name):
+    """Check if a tool (an executable program) is provided on this platform.
+
+    :params tool_name:  Name of the tool to check if it is available.
+    :return: True, if tool is found.
+    :return: False, if tool is not available (or not in search path).
+    """
+    # print("CHECK-TOOL: %s" % tool_name)
+    path = os.environ.get("PATH")
+    if not path:
+        return False
+
+    for searchdir in path.split(os.pathsep):
+        executable1 = os.path.normpath(os.path.join(searchdir, tool_name))
+        executables = [executable1]
+        if sys.platform.startswith("win"):
+            executables.append(executable1 + ".exe")
+
+        for executable in executables:
+            # print("TOOL-CHECK: %s" % os.path.abspath(executable))
+            if os.path.isfile(executable):
+                # print("TOOL-FOUND: %s" % os.path.abspath(executable))
+                return True
+    # -- OTHERWISE: Tool not found
+    # print("TOOL-NOT-FOUND: %s" % tool_name)
+    return False
+
+def as_bool_string(value):
+    if bool(value):
+        return "yes"
+    else:
+        return "no"
+
+def discover_ci_server():
+    # pylint: disable=invalid-name
+    ci_server = "none"
+    CI = os.environ.get("CI", "false").lower() == "true"
+    APPVEYOR = os.environ.get("APPVEYOR", "false").lower() == "true"
+    TRAVIS = os.environ.get("TRAVIS", "false").lower() == "true"
+    if CI:
+        if APPVEYOR:
+            ci_server = "appveyor"
+        elif TRAVIS:
+            ci_server = "travis"
+        else:
+            ci_server = "unknown"
+    return ci_server
+
+
+# -- MATCHES ANY TAGS: @use.with_{category}={value}
+# NOTE: active_tag_value_provider provides category values for active tags.
+active_tag_value_provider = {
+    "python2": str(six.PY2).lower(),
+    "python3": str(six.PY3).lower(),
+    # -- python.implementation: cpython, pypy, jython, ironpython
+    "python.implementation": platform.python_implementation().lower(),
+    "pypy":    str("__pypy__" in sys.modules).lower(),
+    "os":      sys.platform,
+    "xmllint": as_bool_string(require_tool("xmllint")),
+    "ci": discover_ci_server()
+}
+active_tag_matcher = ActiveTagMatcher(active_tag_value_provider)
+
+def before_all(context):
+    # -- SETUP ACTIVE-TAG MATCHER (with userdata):
+    # USE: behave -D browser=safari ...
+    # NOT-NEEDED: setup_active_tag_values(active_tag_value_provider,
+    #                                     context.config.userdata)
+    setup_command_shell_processors4behave()
+
+def before_feature(context, feature):
+    if active_tag_matcher.should_exclude_with(feature.tags):
+        feature.skip(reason=active_tag_matcher.exclude_reason)
+
+def before_scenario(context, scenario):
+    if active_tag_matcher.should_exclude_with(scenario.effective_tags):
+        scenario.skip(reason=active_tag_matcher.exclude_reason)

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

@@ -0,0 +1,21 @@
+@issue
+Feature: Issue #30 "behave --version" runs features and shows no version
+
+  Scenario: Ensure environment assumptions are correct (Sanity Check)
+    Given a new working directory
+    When I run "behave"
+    Then it should fail
+    And the command output should contain:
+      """
+      No steps directory in '{__WORKDIR__}/features'
+      """
+
+  Scenario: Ensure --version option is processed correctly
+    Given a new working directory
+    When I run "behave --version"
+    Then it should pass
+    And the command output should not contain:
+      """
+      No steps directory in '{__WORKDIR__}/features'
+      """
+

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

@@ -0,0 +1,16 @@
+@issue
+Feature: Issue #31 "behave --format help" raises an error
+
+  Scenario:
+    Given a new working directory
+    When I run "behave --format=help"
+    Then it should pass
+    And the command output should contain:
+      """
+      Available formatters:
+        json           JSON dump of test run
+        json.pretty    JSON dump of test run (human readable)
+        null           Provides formatter that does not output anything.
+        plain          Very basic formatter with maximum compatibility
+        pretty         Standard colourised pretty formatter
+      """

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

@@ -0,0 +1,28 @@
+@issue
+Feature: Issue #32 "behave --junit-directory=xxx" fails if more than 1 level must be created
+
+  Scenario:
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'passing')
+      def step(context):
+          pass
+      """
+    And a file named "features/issue32_1.feature" with:
+      """
+      Feature: One
+        Scenario: One
+            Given passing
+      """
+
+    When I run "behave --junit --junit-directory=report/test_results"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 0 skipped
+      1 step passed, 0 failed, 0 skipped, 0 undefined
+      """
+    And the directory "report/test_results" should exist

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

@@ -0,0 +1,74 @@
+@issue
+Feature: Issue #35 Plain Formatter shows wrong steps when tag-selection is used
+
+  Background: Test Setup
+    Given a new working directory
+    And a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'the ninja has a third level black-belt')
+      def step(context):
+          pass
+
+      @when(u'attacked by {opponent}')
+      def step(context, opponent):
+          pass
+
+      @then(u'the ninja should {reaction}')
+      def step(context, reaction):
+          pass
+      """
+    And a file named "features/issue35_1.feature" with:
+      """
+      Feature: Using Tags with Features and Scenarios
+
+        @one
+        Scenario: Weaker opponent
+            Given the ninja has a third level black-belt
+            When attacked by a samurai
+            Then the ninja should engage the opponent
+
+        @two
+        Scenario: Stronger opponent
+            Given the ninja has a third level black-belt
+            When attacked by Chuck Norris
+            Then the ninja should run for his life
+      """
+
+  Scenario: Select First Scenario with Tag
+    When I run "behave --no-timings -f plain --tags=@one features/issue35_1.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 1 skipped
+      3 steps passed, 0 failed, 3 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Feature: Using Tags with Features and Scenarios
+         Scenario: Weaker opponent
+             Given the ninja has a third level black-belt ... passed
+              When attacked by a samurai ... passed
+              Then the ninja should engage the opponent ... passed
+         Scenario: Stronger opponent
+      """
+
+  Scenario: Select Second Scenario with Tag
+    When I run "behave --no-timings -f plain --tags=@two features/issue35_1.feature"
+    Then it should pass with:
+      """
+      1 feature passed, 0 failed, 0 skipped
+      1 scenario passed, 0 failed, 1 skipped
+      3 steps passed, 0 failed, 3 skipped, 0 undefined
+      """
+    And the command output should contain:
+      """
+      Feature: Using Tags with Features and Scenarios
+         Scenario: Weaker opponent
+         Scenario: Stronger opponent
+             Given the ninja has a third level black-belt ... passed
+              When attacked by Chuck Norris ... passed
+              Then the ninja should run for his life ... passed
+      """
+

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

@@ -0,0 +1,154 @@
+@issue
+Feature: Issue #40 Test Summary Scenario/Step Counts are incorrect for Scenario Outline
+
+  As I user
+  I want that each passed and each failed scenario is counted
+  And I want that each passed and failed step in a ScenarioOutline is counted
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'a step {outcome} with "{name}"')
+      def step(context, outcome, name):
+          context.name = name
+          assert outcome == "passes"
+
+      @when(u'a step {outcome} with "{name}"')
+      def step(context, outcome, name):
+          assert outcome == "passes"
+          assert context.name == name
+
+      @then(u'a step {outcome} with "{name}"')
+      def step(context, outcome, name):
+          assert outcome == "passes"
+          assert context.name == name
+      """
+
+  Scenario: ScenarioOutline with Passing Steps
+    Given a file named "features/issue40_1.feature" with:
+      """
+      Feature: Verify Scenario/Step Summary Pass Count with ScenarioOutline
+        Scenario Outline:
+          Given a step passes with "<name>"
+          When  a step passes with "<name>"
+          Then  a step passes with "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_1.feature"
+    Then it should pass with:
+      """
+      2 scenarios passed, 0 failed, 0 skipped
+      6 steps passed, 0 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: ScenarioOutline with Failing Given-Steps
+    Given a file named "features/issue40_2G.feature" with:
+      """
+      Feature: Scenario/Step Summary Pass/Fail Count with ScenarioOutline
+        Scenario Outline:
+          Given a step fails with "<name>"
+          When  a step passes with "<name>"
+          Then  a step passes with "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_2G.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 2 failed, 0 skipped
+      0 steps passed, 2 failed, 4 skipped, 0 undefined
+      """
+
+  Scenario: ScenarioOutline with Failing When-Steps
+    Given a file named "features/issue40_2W.feature" with:
+      """
+      Feature: Scenario/Step Summary Pass/Fail Count with ScenarioOutline
+        Scenario Outline:
+          Given a step passes with "<name>"
+          When  a step fails with "<name>"
+          Then  a step passes with "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_2W.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 2 failed, 0 skipped
+      2 steps passed, 2 failed, 2 skipped, 0 undefined
+      """
+
+  Scenario: ScenarioOutline with Failing Then-Steps
+    Given a file named "features/issue40_2T.feature" with:
+      """
+      Feature: Scenario/Step Summary Pass/Fail Count with ScenarioOutline
+        Scenario Outline:
+          Given a step passes with "<name>"
+          When  a step passes with "<name>"
+          Then  a step fails with "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_2T.feature"
+    Then it should fail with:
+      """
+      0 scenarios passed, 2 failed, 0 skipped
+      4 steps passed, 2 failed, 0 skipped, 0 undefined
+      """
+
+  Scenario: ScenarioOutline with Mismatched When-Step Example Row
+    Given a file named "features/issue40_3W.feature" with:
+      """
+      Feature: Scenario/Step Summary Pass/Fail Count with ScenarioOutline
+        Scenario Outline:
+          Given a step passes with "<name>"
+          When  a step passes with "Alice"
+          Then  a step passes with "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_3W.feature"
+    Then it should fail with:
+      """
+      1 scenario passed, 1 failed, 0 skipped
+      4 steps passed, 1 failed, 1 skipped, 0 undefined
+      """
+
+  Scenario: ScenarioOutline with Mismatched Then-Step Example Row
+    Given a file named "features/issue40_3W.feature" with:
+      """
+      Feature: Scenario/Step Summary Pass/Fail Count with ScenarioOutline
+        Scenario Outline:
+          Given a step passes with "<name>"
+          When  a step passes with "<name>"
+          Then  a step passes with "Alice"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue40_3W.feature"
+    Then it should fail with:
+      """
+      1 scenario passed, 1 failed, 0 skipped
+      5 steps passed, 1 failed, 0 skipped, 0 undefined
+      """

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

@@ -0,0 +1,135 @@
+@issue
+Feature: Issue #41 Missing Steps are duplicated in a Scenario Outline
+
+  As I user
+  I want that missing steps are reported only once.
+
+  Background: Test Setup
+    Given a new working directory
+    And   a file named "features/steps/steps.py" with:
+      """
+      from behave import given, when, then
+
+      @given(u'I enter a "{name}"')
+      def step(context, name):
+          context.name = name
+
+      @when(u'I enter a "{name}"')
+      def step(context, name):
+          context.name = name
+
+      @then(u'the name is "{name}"')
+      def step(context, name):
+          assert context.name == name
+      """
+
+  Scenario: Missing Given Step
+    Given a file named "features/issue41_missing1.feature" with:
+      """
+      Feature: Missing Given-Step in a Scenario Outline
+        Scenario Outline:
+          Given an unknown step
+          When  I enter a "<name>"
+          Then  the name is "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue41_missing1.feature"
+    Then it should fail with:
+      """
+      0 steps passed, 0 failed, 4 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+      """
+    But the command output should not contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+      @given(u'an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Given an unknown step')
+      """
+
+  Scenario: Missing When Step
+    Given a file named "features/issue41_missing2.feature" with:
+      """
+      Feature: Missing When-Step in a Scenario Outline
+        Scenario Outline:
+          Given I enter a "<name>"
+          When  I use an unknown step
+          Then  the name is "<name>"
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue41_missing2.feature"
+    Then it should fail with:
+      """
+      2 steps passed, 0 failed, 2 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @when(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When I use an unknown step')
+      """
+    But the command output should not contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @when(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When I use an unknown step')
+      @when(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: When I use an unknown step')
+      """
+
+  Scenario: Missing Then Step
+    Given a file named "features/issue41_missing3.feature" with:
+      """
+      Feature: Missing Then-Step in a Scenario Outline
+        Scenario Outline:
+          Given I enter a "<name>"
+          When  I enter a "<name>"
+          Then  I use an unknown step
+
+        Examples:
+            |name |
+            |Alice|
+            |Bob  |
+      """
+    When I run "behave -c -f plain features/issue41_missing3.feature"
+    Then it should fail with:
+      """
+      4 steps passed, 0 failed, 0 skipped, 2 undefined
+      """
+    And the command output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @then(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then I use an unknown step')
+      """
+    But the command output should not contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+      @then(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then I use an unknown step')
+      @then(u'I use an unknown step')
+      def step_impl(context):
+          raise NotImplementedError(u'STEP: Then I use an unknown step')
+      """