busser-behave 0.1.3

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

@@ -0,0 +1,17 @@
+Feature: Local Context Parameters defined in Scenarios (Steps)
+
+    . SPECIFICATION:
+    .   * When a step adds/modifies an attribute in the Context object,
+    .     then its value is only available to other steps in this scenario.
+    .   * After a scenario is executed all Context object changes are undone.
+
+    Scenario: Add Local Context parameter in Scenario/Step
+      Given the behave context does not have a parameter "local_name"
+      When I set the context parameter "local_name" to "Alice"
+      Then the behave context should have a parameter "local_name"
+      And  the behave context should contain:
+        | Parameter  | Value   |
+        | local_name | "Alice" |
+
+    Scenario: Ensure that Local Context parameter is not available to next Scenario
+      Then the behave context should not have a parameter "local_name"

data/vendor/behave/features/directory_layout.advanced.feature

@@ -0,0 +1,147 @@
+Feature: Advanced, more complex directory layout (Variant 2)
+
+  As a story/test writer
+  I want a deeper, more structured directory structure when many feature files exist
+  So that I have the parts better under control (more managable)
+
+  . ADVANCED, MORE COMPLEX DIRECTORY LAYOUT STRUCTURE:
+  .     features/
+  .       +-- group1.features/
+  .       |      +-- *.feature
+  .       +-- group2.features/
+  .       |      +-- *.feature
+  .       +-- steps/*.py          # Step definitions or step-library imports.
+  .       +-- environment.py      # OPTIONAL: environment setup/hooks.
+  .
+  . SEE ALSO:
+  .   * http://pythonhosted.org/behave/gherkin.html#layout-variations
+  .
+  . RELATED:
+  .   * issue #99: Layout variation "a directory containing your feature files" ...
+
+    @setup
+    Scenario: Setup directory structure
+        Given a new working directory
+        And a file named "features/steps/steps.py" with:
+            """
+            from behave import step
+
+            @step('{word:w} step passes')
+            def step_passes(context, word):
+                pass
+
+            @step('{word:w} step fails')
+            def step_fails(context, word):
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/steps/environment_steps.py" with:
+            """
+            from behave import step
+
+            @step('environment setup was done')
+            def step_ensure_environment_setup(context):
+                assert context.setup_magic == 42
+            """
+        And a file named "features/environment.py" with:
+            """
+            def before_all(context):
+                context.setup_magic = 42
+            """
+        And a file named "features/group1/alice.feature" with:
+            """
+            Feature: Alice
+                Scenario: A1
+                  Given a step passes
+                  When another step passes
+                  Then a step passes
+
+                Scenario: A2
+                  Then environment setup was done
+            """
+        And a file named "features/group1/bob.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                  When a step passes
+                  Then another step passes
+            """
+        And a file named "features/group2/charly.feature" with:
+            """
+            Feature: Charly
+                Scenario: C1
+                  Given another step passes
+                  Then a step passes
+            """
+
+
+    Scenario: Run behave with feature directory
+        When I run "behave -f progress features/"
+        Then it should pass with:
+            """
+            3 features passed, 0 failed, 0 skipped
+            4 scenarios passed, 0 failed, 0 skipped
+            8 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with feature subdirectory (CASE 1)
+        When I run "behave -f progress features/group1/"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            3 scenarios passed, 0 failed, 0 skipped
+            6 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with feature subdirectory (CASE 2)
+        When I run "behave -f progress features/group2/"
+        Then it should pass with:
+            """
+            1 feature passed, 0 failed, 0 skipped
+            1 scenario passed, 0 failed, 0 skipped
+            2 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with one feature file
+        When I run "behave -f progress features/group1/alice.feature"
+        Then it should pass with:
+            """
+            1 feature passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            4 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+        When I run "behave -f progress features/group2/charly.feature"
+        Then it should pass with:
+            """
+            1 feature passed, 0 failed, 0 skipped
+            1 scenario passed, 0 failed, 0 skipped
+            2 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+
+    Scenario: Run behave with two feature files (CASE 1)
+        Given a file named "one.featureset" with:
+            """
+            features/group1/alice.feature
+            features/group2/charly.feature
+            """
+        When I run "behave -f progress @one.featureset"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            3 scenarios passed, 0 failed, 0 skipped
+            6 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with two feature files (CASE 2: different ordering)
+        Given a file named "two.featureset" with:
+            """
+            features/group2/charly.feature
+            features/group1/alice.feature
+            """
+        When I run "behave -f progress @two.featureset"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            3 scenarios passed, 0 failed, 0 skipped
+            6 steps passed, 0 failed, 0 skipped, 0 undefined
+            """

data/vendor/behave/features/directory_layout.basic.feature

@@ -0,0 +1,75 @@
+Feature: Basic directory layout (Variant 1)
+
+  As a story/test writer
+  I want a simple, non-deep directory structure
+  So that I can easily get an overview which stories/tests exist
+
+  . BASIC DIRECTORY LAYOUT STRUCTURE:
+  .     features/
+  .       +-- steps/*.py          # Step definitions or step-library imports.
+  .       +-- *.feature           # Feature files.
+  .       +-- environment.py      # OPTIONAL: environment setup/hooks.
+  .
+  . SEE ALSO:
+  .   * http://pythonhosted.org/behave/gherkin.html#layout-variations
+
+
+    @setup
+    Scenario: Setup directory structure
+        Given a new working directory
+        And a file named "features/steps/steps.py" with:
+            """
+            from behave import step
+
+            @step('{word:w} step passes')
+            def step_passes(context, word):
+                pass
+
+            @step('{word:w} step fails')
+            def step_fails(context, word):
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/alice.feature" with:
+            """
+            Feature: Alice
+                Scenario: A1
+                  Given a step passes
+                  When another step passes
+                  Then a step passes
+            """
+        And a file named "features/bob.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                  When a step passes
+                  Then another step passes
+            """
+
+
+    Scenario: Run behave with feature directory
+        When I run "behave -f progress features/"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            5 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with one feature file
+        When I run "behave -f progress 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
+            """
+
+
+    Scenario: Run behave with two feature files
+        When I run "behave -f progress features/alice.feature features/bob.feature"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            5 steps passed, 0 failed, 0 skipped, 0 undefined
+            """

data/vendor/behave/features/directory_layout.basic2.feature

@@ -0,0 +1,87 @@
+Feature: Basic directory layout (Variant 1B)
+
+  As a story/test writer
+  I want a simple, non-deep directory structure
+  So that I can easily get an overview which stories/tests exist
+
+  . BASIC DIRECTORY LAYOUT STRUCTURE:
+  .     testing/features/
+  .       +-- steps/*.py          # Step definitions or step-library imports.
+  .       +-- *.feature           # Feature files.
+  .       +-- environment.py      # OPTIONAL: environment setup/hooks.
+  .
+  . SEE ALSO:
+  .   * http://pythonhosted.org/behave/gherkin.html#layout-variations
+
+
+    @setup
+    Scenario: Setup directory structure
+        Given a new working directory
+        And a file named "testing/features/steps/steps.py" with:
+            """
+            from behave import step
+
+            @step('{word:w} step passes')
+            def step_passes(context, word):
+                pass
+
+            @step('{word:w} step fails')
+            def step_fails(context, word):
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "testing/features/alice.feature" with:
+            """
+            Feature: Alice
+                Scenario: A1
+                  Given a step passes
+                  When another step passes
+                  Then a step passes
+            """
+        And a file named "testing/features/bob.feature" with:
+            """
+            Feature: Bob
+                Scenario: B1
+                  When a step passes
+                  Then another step passes
+            """
+
+
+    Scenario: Run behave with testing directory
+        When I run "behave -f progress testing/"
+        Then it should fail with:
+            """
+            ConfigError: No steps directory in '{__WORKDIR__}/testing'
+            """
+
+    Scenario: Run behave with feature subdirectory
+        When I run "behave -f progress testing/features/"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            5 steps passed, 0 failed, 0 skipped, 0 undefined
+            """
+
+    Scenario: Run behave with one feature file
+        When I run "behave -f progress testing/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
+            """
+
+
+    Scenario: Run behave with two feature files
+        Given a file named "one.featureset" with:
+            """
+            testing/features/alice.feature
+            testing/features/bob.feature
+            """
+        When I run "behave -f progress @one.featureset"
+        Then it should pass with:
+            """
+            2 features passed, 0 failed, 0 skipped
+            2 scenarios passed, 0 failed, 0 skipped
+            5 steps passed, 0 failed, 0 skipped, 0 undefined
+            """

data/vendor/behave/features/environment.py

@@ -0,0 +1,53 @@
+# -*- coding: UTF-8 -*-
+
+from behave.tag_matcher import ActiveTagMatcher, setup_active_tag_values
+from behave4cmd0.setup_command_shell import setup_command_shell_processors4behave
+import platform
+import sys
+import six
+
+# -- 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 = {
+    "python2": str(six.PY2).lower(),
+    "python3": str(six.PY3).lower(),
+    "python.version": python_version,
+    # -- python.implementation: cpython, pypy, jython, ironpython
+    "python.implementation": platform.python_implementation().lower(),
+    "pypy":    str("__pypy__" in sys.modules).lower(),
+    "os":      sys.platform,
+}
+active_tag_matcher = ActiveTagMatcher(active_tag_value_provider)
+
+# -----------------------------------------------------------------------------
+# HOOKS:
+# -----------------------------------------------------------------------------
+def before_all(context):
+    # -- SETUP ACTIVE-TAG MATCHER (with userdata):
+    # USE: behave -D browser=safari ...
+    setup_active_tag_values(active_tag_value_provider, context.config.userdata)
+    setup_python_path()
+    setup_context_with_global_params_test(context)
+    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)
+
+# -----------------------------------------------------------------------------
+# SPECIFIC FUNCTIONALITY:
+# -----------------------------------------------------------------------------
+def setup_context_with_global_params_test(context):
+    context.global_name = "env:Alice"
+    context.global_age  = 12
+
+def setup_python_path():
+    # -- NEEDED-FOR: formatter.user_defined.feature
+    import os
+    PYTHONPATH = os.environ.get("PYTHONPATH", "")
+    os.environ["PYTHONPATH"] = "."+ os.pathsep + PYTHONPATH

data/vendor/behave/features/exploratory_testing.with_table.feature

@@ -0,0 +1,141 @@
+Feature: Exploratory Testing with Tables and Table Annotations
+
+   As a tester
+   I want sometimes to explore a problem domain
+   And see not only the expected results
+   But also the actual results in a table.
+
+    . HINT: Does not work with monochrome format in pretty formatter:
+    .   behave -f pretty --no-color ...
+    .   behave -c ...
+
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And   a file named "features/steps/explore_with_table_steps.py" with:
+      """
+      from behave import given, when, then, step
+
+      database = {
+          "Alice": { "age": 10 },
+          "Bob":   { "age": 11 },
+      }
+
+      @when('I query the database with')
+      def step_query_database_and_update_table(context):
+          assert context.table, "REQUIRE: table"
+          context.table.require_column("Name")
+          age_index = context.table.ensure_column_exists("Age")
+          for index, row in enumerate(context.table.rows):
+              name = row["Name"]
+              person = database.get(name, None)
+              if person:
+                  row.cells[age_index] = str(person["age"])
+          context.current_table = context.table
+
+      @when('I add {number:n} to column "{column}"')
+      def step_query_and_annotate_database(context, number, column):
+          assert context.current_table, "REQUIRE: current_table"
+          age_index = context.current_table.ensure_column_exists("Age")
+          for row in context.current_table.rows:
+              value = int(row.cells[age_index]) or 0
+              row.cells[age_index] = str(value + number)
+
+      @step('note that the "{name}" column was added to the table')
+      def step_note_that_column_was_added(context, name):
+          assert context.current_table.has_column(name)
+
+      @then('note that the "{name}" column was modified in the table')
+      def step_note_that_column_was_modified(context, name):
+          pass
+
+      @then('I inspect the table')
+      def step_inspect_table(context):
+          assert context.current_table
+          context.table = context.current_table
+
+      @then('the table contains')
+      def step_inspect_table(context):
+          assert context.table, "REQUIRE: table"
+          assert context.current_table, "REQUIRE: current_table"
+          assert context.table == context.current_table
+      """
+
+
+    Scenario: Add table column with new data in a step and ensure changes are shown
+      Given a file named "features/table.set_column_data.feature" with:
+        """
+        Feature:
+          Scenario:
+            When I query the database with:
+              | Name  |
+              | Alice |
+              | Bob   |
+            Then note that the "Age" column was added to the table
+        """
+      When I run "behave -f plain features/table.set_column_data.feature"
+      Then it should pass with:
+         """
+         1 scenario passed, 0 failed, 0 skipped
+         2 steps passed, 0 failed, 0 skipped, 0 undefined
+         """
+      And the command output should contain:
+         """
+         | Name  | Age |
+         | Alice | 10  |
+         | Bob   | 11  |
+         """
+      But note that "the Age table column was added by the step"
+
+
+    Scenario: Modify table cells in a column and ensure changes are shown
+      Given a file named "features/table.modify_column.feature" with:
+        """
+        Feature:
+          Scenario:
+            When I query the database with:
+               | Name  | Age  |
+               | Alice | 222  |
+               | Bob   | 333  |
+            Then note that the "Age" column was modified in the table
+            Then the table contains:
+               | Name  | Age |
+               | Alice | 10  |
+               | Bob   | 11  |
+        """
+      When I run "behave -f plain features/table.modify_column.feature"
+      Then it should pass with:
+         """
+         1 scenario passed, 0 failed, 0 skipped
+         3 steps passed, 0 failed, 0 skipped, 0 undefined
+         """
+      And the command output should contain:
+         """
+         | Name  | Age |
+         | Alice | 10  |
+         | Bob   | 11  |
+         """
+      But note that "the Age column was modified in the table"
+      And the command output should not contain:
+         """
+         | Name  | Age |
+         | Alice | 222 |
+         | Bob   | 333 |
+         """
+
+
+    Scenario: Modify table cells in a column (formatter=pretty with colors)
+      When I run "behave -f pretty features/table.modify_column.feature"
+      Then it should pass with:
+         """
+         1 scenario passed, 0 failed, 0 skipped
+         3 steps passed, 0 failed, 0 skipped, 0 undefined
+         """
+      And the command output should contain:
+         """
+         | Name  | Age |
+         | Alice | 10  |
+         | Bob   | 11  |
+         """
+      But note that "the Age column was modified in the table"