busser-behave 0.1.3

data/vendor/behave/examples/async_step/README.txt

@@ -0,0 +1,8 @@
+EXAMPLE: Async-steps and async-dispatch/async-collect
+================================================================================
+
+BASED-ON: features/step.async_step.feature
+REQUIRES: Python 3.5 (or Python 3.4)
+
+Examples for testing asyncio frameworks with async-steps, etc.
+

data/vendor/behave/examples/async_step/behave.ini

@@ -0,0 +1,14 @@
+# =============================================================================
+# BEHAVE CONFIGURATION
+# =============================================================================
+# FILE: .behaverc, behave.ini
+#
+# SEE ALSO:
+#  * http://packages.python.org/behave/behave.html#configuration-files
+#  * https://github.com/behave/behave
+#  * http://pypi.python.org/pypi/behave/
+# =============================================================================
+
+[behave]
+show_timings  = true
+

data/vendor/behave/examples/async_step/features/async_dispatch.feature

@@ -0,0 +1,8 @@
+@use.with_python.version=3.4
+@use.with_python.version=3.5
+@use.with_python.version=3.6
+Feature:
+  Scenario:
+    Given I dispatch an async-call with param "Alice"
+    And   I dispatch an async-call with param "Bob"
+    Then the collected result of the async-calls is "ALICE, BOB"

data/vendor/behave/examples/async_step/features/async_run.feature

@@ -0,0 +1,6 @@
+@use.with_python.version=3.4
+@use.with_python.version=3.5
+@use.with_python.version=3.6
+Feature:
+  Scenario:
+    Given an async-step waits 0.3 seconds

data/vendor/behave/examples/async_step/features/environment.py

@@ -0,0 +1,28 @@
+# -*- coding: UTF-8 -*-
+
+from behave.tag_matcher import ActiveTagMatcher, setup_active_tag_values
+import sys
+
+# -- MATCHES ANY TAGS: @use.with_{category}={value}
+# NOTE: active_tag_value_provider provides category values for active tags.
+python_version = "%s.%s" % sys.version_info[:2]
+active_tag_value_provider = {
+    "python.version": python_version,
+}
+active_tag_matcher = ActiveTagMatcher(active_tag_value_provider)
+
+# -----------------------------------------------------------------------------
+# HOOKS:
+# -----------------------------------------------------------------------------
+def before_all(context):
+    # -- SETUP ACTIVE-TAG MATCHER (with userdata):
+    setup_active_tag_values(active_tag_value_provider, context.config.userdata)
+
+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/examples/async_step/features/steps/async_dispatch_steps.py

@@ -0,0 +1,26 @@
+from behave import given, then, step
+from behave.api.async_step import use_or_create_async_context, AsyncContext
+from hamcrest import assert_that, equal_to, empty
+import asyncio
+
+@asyncio.coroutine
+def async_func(param):
+    yield from asyncio.sleep(0.2)
+    return str(param).upper()
+
+@given('I dispatch an async-call with param "{param}"')
+def step_dispatch_async_call(context, param):
+    async_context = use_or_create_async_context(context, "async_context1")
+    task = async_context.loop.create_task(async_func(param))
+    async_context.tasks.append(task)
+
+@then('the collected result of the async-calls is "{expected}"')
+def step_collected_async_call_result_is(context, expected):
+    async_context = context.async_context1
+    done, pending = async_context.loop.run_until_complete(
+        asyncio.wait(async_context.tasks, loop=async_context.loop))
+
+    parts = [task.result() for task in done]
+    joined_result = ", ".join(sorted(parts))
+    assert_that(joined_result, equal_to(expected))
+    assert_that(pending, empty())

data/vendor/behave/examples/async_step/features/steps/async_steps34.py

@@ -0,0 +1,10 @@
+# -- REQUIRES: Python >= 3.4
+from behave import step
+from behave.api.async_step import async_run_until_complete
+import asyncio
+
+@step('an async-step waits {duration:f} seconds')
+@async_run_until_complete
+@asyncio.coroutine
+def step_async_step_waits_seconds_py34(context, duration):
+    yield from asyncio.sleep(duration)

data/vendor/behave/examples/async_step/features/steps/async_steps35.py

@@ -0,0 +1,10 @@
+# -- REQUIRES: Python >= 3.5
+from behave import step
+from behave.api.async_step import async_run_until_complete
+import asyncio
+
+@step('an async-step waits {duration:f} seconds')
+@async_run_until_complete
+async def step_async_step_waits_seconds_py35(context, duration):
+    """Simple example of a coroutine as async-step (in Python 3.5)"""
+    await asyncio.sleep(duration)

data/vendor/behave/examples/async_step/testrun_example.async_dispatch.txt

@@ -0,0 +1,11 @@
+Feature: 
+
+  Scenario: 
+    Given I dispatch an async-call with param "Alice" ... passed in 0.001s
+    And I dispatch an async-call with param "Bob" ... passed in 0.000s
+    Then the collected result of the async-calls is "ALICE, BOB" ... passed in 0.206s
+
+1 feature passed, 0 failed, 0 skipped
+1 scenario passed, 0 failed, 0 skipped
+3 steps passed, 0 failed, 0 skipped, 0 undefined
+Took 0m0.208s

data/vendor/behave/examples/async_step/testrun_example.async_run.txt

@@ -0,0 +1,9 @@
+Feature: 
+
+  Scenario: 
+    Given an async-step waits 0.3 seconds ... passed in 0.307s
+
+1 feature passed, 0 failed, 0 skipped
+1 scenario passed, 0 failed, 0 skipped
+1 step passed, 0 failed, 0 skipped, 0 undefined
+Took 0m0.307s

data/vendor/behave/examples/env_vars/README.rst

@@ -0,0 +1,26 @@
+EXAMPLE: Use Environment Variables in Steps
+=============================================================================
+
+:RELATED TO: `issue #497`_
+
+This directory provides a simple example how you can use environment variables
+in step implementations.
+
+::
+
+    # -- USE: -f plain --no-capture  (via "behave.ini" defaults)
+    $ behave
+    Feature: Test Environment variable concept
+
+      Scenario: 
+    USE ENVIRONMENT-VAR: LOGNAME = xxx  (variant 1)
+        When I click on $LOGNAME ... passed
+    USE ENVIRONMENT-VAR: LOGNAME = xxx  (variant 2)
+        When I use the environment variable $LOGNAME ... passed
+
+    1 feature passed, 0 failed, 0 skipped
+    1 scenario passed, 0 failed, 0 skipped
+    2 steps passed, 0 failed, 0 skipped, 0 undefined
+    Took 0m0.000s
+
+.. _`issue #497`: https://github.com/behave/behave/issues/497

data/vendor/behave/examples/env_vars/behave.ini

@@ -0,0 +1,15 @@
+# =============================================================================
+# BEHAVE CONFIGURATION
+# =============================================================================
+# FILE: .behaverc, behave.ini
+#
+# SEE ALSO:
+#  * http://packages.python.org/behave/behave.html#configuration-files
+#  * https://github.com/behave/behave
+#  * http://pypi.python.org/pypi/behave/
+# =============================================================================
+
+[behave]
+default_format = plain
+stdout_capture = false
+show_source = true

data/vendor/behave/examples/env_vars/behave_run.output_example.txt

@@ -0,0 +1,12 @@
+Feature: Test Environment variable concept
+
+  Scenario: 
+USE ENVIRONMENT-VAR: LOGNAME = xxx  (variant 1)
+    When I click on $LOGNAME ... passed
+USE ENVIRONMENT-VAR: LOGNAME = xxx  (variant 2)
+    When I use the environment variable $LOGNAME ... passed
+
+1 feature passed, 0 failed, 0 skipped
+1 scenario passed, 0 failed, 0 skipped
+2 steps passed, 0 failed, 0 skipped, 0 undefined
+Took 0m0.000s

data/vendor/behave/examples/env_vars/features/env_var.feature

@@ -0,0 +1,6 @@
+Feature: Test Environment variable concept
+
+    Scenario:
+        When I click on $LOGNAME
+        When I use the environment variable $LOGNAME
+

data/vendor/behave/examples/env_vars/features/steps/env_var_steps.py

@@ -0,0 +1,38 @@
+# -*- coding: UTF-8 -*-
+# -- FILE: features/steps/my_steps.py
+
+from __future__ import print_function
+from behave import when
+import os
+import sys
+
+# -- VARIANT 1:
+@when(u'I click on ${environment_variable:w}')
+def step_impl(context, environment_variable):
+      env_value = os.environ.get(environment_variable, None)
+      if env_value is None:
+           raise LookupError("Environment variable '%s' is undefined" % environment_variable)
+      print("USE ENVIRONMENT-VAR: %s = %s  (variant 1)" % (environment_variable, env_value))
+
+
+# -- VARIANT 2: Use type converter
+from behave import register_type
+import parse
+
+@parse.with_pattern(r"\$\w+")  # -- ONLY FOR: $WORD
+def parse_environment_var(text):
+    assert text.startswith("$")
+    env_name = text[1:]
+    env_value = os.environ.get(env_name, None)
+    return (env_name, env_value)
+
+register_type(EnvironmentVar=parse_environment_var)
+
+@when(u'I use the environment variable {environment_variable:EnvironmentVar}')
+def step_impl(context, environment_variable):
+      env_name, env_value = environment_variable
+      if env_value is None:
+           raise LookupError("Environment variable '%s' is undefined" % env_name)
+      print("USE ENVIRONMENT-VAR: %s = %s  (variant 2)" \
+            % (env_name, env_value))
+

data/vendor/behave/features/README.txt

@@ -0,0 +1,12 @@
+behave features: Self-Tests
+===============================================================================
+
+This directory contains feature tests that are executed with behave.
+These self-tests are used to:
+
+  * ensure that ``behave`` reacts as expected
+  * define the common expected behaviour for behave
+  * support "Acceptance Test Driven-Design" (ATDD)
+
+RELATED:
+  * Cucumber Technology Compatibility Kit: https://github.com/cucumber/cucumber-tck

data/vendor/behave/features/background.feature

@@ -0,0 +1,392 @@
+Feature: Background
+
+  As a test writer
+  I want to run a number of steps in each scenario
+  And I want to avoid duplicating these steps for each scenario
+  So that I write these steps only once (DRY principle).
+
+  . SPECIFICATION:
+  .   * A feature can have an optional "Background" section
+  .   * The Background must be specified before any Scenario/ScenarioOutline
+  .   * The Background may occur at most once
+  .   * The Background steps are executed in each Scenario/ScenarioOutline
+  .   * The Background steps are executed before any Scenario steps
+  .   * If a Background step fails then the is marked as scenario failed
+  .   * If a Background fails in a scenario then other scenarios are still executed.
+  .
+  . RELATED:
+  .   * parser.background.sad_cases.feature
+  .
+  . NOTE:
+  .   Cucumber has a slightly different runtime 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.
+  .   But this may lead to an increased test duration if a systematic failure
+  .   occurs in the failing background step.
+  .
+  . 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 passes')
+        def step_background_step_passes(context, word):
+            pass
+
+        @step('{word} background step fails')
+        def step_background_step_fails(context, word):
+            assert False, "XFAIL: background step"
+
+        @step('{word} background step fails sometimes')
+        def step_background_step_fails_sometimes(context, word):
+            should_fail = (context.scenarios_count % 2) == 0
+            if should_fail:
+                step_background_step_fails(context, word)
+        """
+    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_fails(context, word):
+            assert False, "XFAIL"
+        """
+
+  Scenario: Feature with a Background and Scenarios
+    Given a file named "features/background_example1.feature" with:
+        """
+        Feature:
+          Background:
+            Given a background step passes
+            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/background_example1.feature"
+    Then it should pass with:
+        """
+        2 scenarios passed, 0 failed, 0 skipped
+        7 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+          Background:
+
+          Scenario: S1
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            When a step passes ... passed
+
+          Scenario: S2
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            Then a step passes ... passed
+            And another step passes ... passed
+        """
+    But note that "the Background steps are injected into each Scenario"
+    And note that "the Background steps are executed before any Scenario steps"
+
+
+  Scenario: Failing Background Step causes all Scenarios to fail
+    Given a file named "features/background_fail_example.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/background_fail_example.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
+        """
+    And note that "the failing Background step causes all Scenarios to fail"
+
+
+  Scenario: Failing Background Step does not prevent that other Scenarios are executed
+
+    If a Background step fails sometimes
+    it should be retried in the remaining Scenarios where it might pass.
+
+    Given a file named "features/background_fails_sometimes_example.feature" with:
+        """
+        Feature:
+
+          Background: B2
+            Given a background step fails sometimes
+
+          Scenario: S1
+            Given a step passes
+
+          Scenario: S2
+            When another step passes
+
+          Scenario: S3
+            Then another step passes
+        """
+    And a file named "features/environment.py" with:
+        """
+        scenarios_count = 0
+
+        def before_scenario(context, scenario):
+            global scenarios_count
+            context.scenarios_count = scenarios_count
+            scenarios_count += 1
+        """
+    When I run "behave -f plain -T features/background_fails_sometimes_example.feature"
+    Then it should fail with:
+        """
+        1 scenario passed, 2 failed, 0 skipped
+        2 steps passed, 2 failed, 2 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+            Background: B2
+
+            Scenario: S1
+              Given a background step fails sometimes ... failed
+          Assertion Failed: XFAIL: background step
+
+            Scenario: S2
+              Given a background step fails sometimes ... passed
+              When another step passes ... passed
+
+            Scenario: S3
+              Given a background step fails sometimes ... failed
+          Assertion Failed: XFAIL: background step
+        """
+
+
+  Scenario: Feature with a Background and ScenarioOutlines
+    Given a file named "features/background_outline_example.feature" with:
+        """
+        Feature:
+          Background:
+            Given a background step passes
+            And another background step passes
+
+          Scenario Outline: SO1
+            When a step <outcome1>
+            Then another step <outcome2>
+
+            Examples: Alpha
+              | outcome1 | outcome2 |
+              | passes   | passes   |
+              | passes   | passes   |
+
+          Scenario Outline: SO2
+            Given <word1> step passes
+            Then <word2> step passes
+
+            Examples:
+              | word1   | word2   |
+              | a       | a       |
+              | a       | another |
+              | another | a       |
+        """
+    When I run "behave -f plain -T features/background_outline_example.feature"
+    Then it should pass with:
+        """
+        5 scenarios passed, 0 failed, 0 skipped
+        20 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+          Background:
+
+          Scenario Outline: SO1 -- @1.1 Alpha
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            When a step passes ... passed
+            Then another step passes ... passed
+
+          Scenario Outline: SO1 -- @1.2 Alpha
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            When a step passes ... passed
+            Then another step passes ... passed
+
+          Scenario Outline: SO2 -- @1.1
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            Given a step passes ... passed
+            Then a step passes ... passed
+
+          Scenario Outline: SO2 -- @1.2
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            Given a step passes ... passed
+            Then another step passes ... passed
+
+          Scenario Outline: SO2 -- @1.3
+            Given a background step passes ... passed
+            And another background step passes ... passed
+            Given another step passes ... passed
+            Then a step passes ... passed
+        """
+    But note that "the Background steps are injected into each ScenarioOutline"
+    And note that "the Background steps are executed before any ScenarioOutline steps"
+
+
+  Scenario: Failing Background Step causes all ScenarioOutlines to fail
+    Given a file named "features/background_fail_outline_example.feature" with:
+        """
+        Feature:
+          Background:
+            Given a background step passes
+            And a background step fails
+            But another background step passes
+
+          Scenario Outline: SO1
+            When a step <outcome1>
+            Then another step <outcome2>
+
+            Examples: Alpha
+              | outcome1 | outcome2 |
+              | passes   | passes   |
+              | passes   | fails    |
+              | fails    | passes   |
+              | fails    | fails    |
+
+          Scenario Outline: SO2
+              When <word1> step passes
+
+            Examples: Beta
+              | word1   |
+              | a       |
+              | another |
+        """
+    When I run "behave -f plain -T features/background_fail_outline_example.feature"
+    Then it should fail with:
+        """
+        0 scenarios passed, 6 failed, 0 skipped
+        6 steps passed, 6 failed, 16 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Feature:
+          Background:
+
+          Scenario Outline: SO1 -- @1.1 Alpha
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario Outline: SO1 -- @1.2 Alpha
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario Outline: SO1 -- @1.3 Alpha
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario Outline: SO1 -- @1.4 Alpha
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario Outline: SO2 -- @1.1 Beta
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+
+          Scenario Outline: SO2 -- @1.2 Beta
+            Given a background step passes ... passed
+            And a background step fails ... failed
+        Assertion Failed: XFAIL: background step
+        """
+    But note that "the failing Background step causes each ScenarioOutline to be marked as skipped"
+
+
+  Scenario: Feature with Background after first Scenario should fail (SAD CASE)
+    Given a file named "features/background_sad_example1.feature" with:
+        """
+        Feature:
+          Scenario: S1
+            When a step passes
+
+          Background: B1
+            Given a background step passes
+
+          Scenario: S2
+            Then a step passes
+            And another step passes
+        """
+    When I run "behave -f plain -T features/background_sad_example1.feature"
+    Then it should fail with:
+        """
+        Parser failure in state steps, at line 5: "Background: B1"
+        REASON: Background may not occur after Scenario/ScenarioOutline.
+        """
+
+
+  Scenario: Feature with two Backgrounds should fail (SAD CASE)
+    Given a file named "features/background_sad_example2.feature" with:
+        """
+        Feature:
+          Background: B1
+            Given a background step passes
+
+          Background: B2 (XFAIL)
+            Given 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/background_sad_example2.feature"
+    Then it should fail with:
+        """
+        Parser failure in state steps, at line 5: "Background: B2 (XFAIL)"
+        REASON: Background should not be used here.
+        """