busser-behave 0.1.3

data/vendor/behave/features/logging.setup_level.feature

@@ -0,0 +1,168 @@
+Feature: Setup logging_level
+
+  As a tester
+  I want to configure the logging_level for --logcapture mode
+  So that I see only the important log-records when a scenario fails.
+
+  As a tester
+  I want to configure the logging_level for --nologcapture mode
+  So that I see only the important log-records up to this level.
+
+  . SPECIFICATION:
+  .  * logging_level can be defined on command-line
+  .  * logging_level can be defined in behave configuration file
+  .  * logging_level should be applied in before_all() hook in --nologcapture mode
+
+
+  @setup
+  Scenario: Feature Setup
+    Given a new working directory
+    And a file named "features/steps/use_behave4cmd_steps.py" with:
+        """
+        import behave4cmd0.log.steps
+        import behave4cmd0.failing_steps
+        import behave4cmd0.passing_steps
+        """
+    And a file named "features/environment.py" with:
+        """
+        def before_all(context):
+            context.config.setup_logging()
+        """
+    And  a file named "features/example.log_with_failure.feature" with:
+        """
+        Feature:
+          Scenario: S1
+            Given I create log records with:
+                | category | level   | message |
+                | root     |  ERROR  | Hello1 log-error-record |
+                | root     |  WARN   | Hello1 log-warn-record  |
+                | root     |  INFO   | Hello1 log-info-record  |
+                | root     |  DEBUG  | Hello1 log-debug-record |
+            When a step fails
+        """
+    And  a file named "features/example.log_with_pass.feature" with:
+        """
+        Feature:
+          Scenario: S2
+            Given I create log records with:
+                | category | level   | message |
+                | root     |  ERROR  | Hello2 log-error-record |
+                | root     |  WARN   | Hello2 log-warn-record  |
+                | root     |  INFO   | Hello2 log-info-record  |
+                | root     |  DEBUG  | Hello2 log-debug-record |
+            When a step passes
+        """
+
+  @capture
+  Scenario: Logcapture mode: Use logging_level on command-line
+
+    Also ensure that command-line option can override configuration file info.
+
+    Given a file named "behave.ini" with:
+        """
+        [behave]
+        logging_level = INFO
+        """
+    When I run "behave -f plain -T --logging-level=WARN features/"
+    Then it should fail with:
+        """
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Captured logging:
+        ERROR:root:Hello1 log-error-record
+        WARNING:root:Hello1 log-warn-record
+        """
+    But the command output should not contain the following log records:
+        | category | level   | message                 | Comment |
+        | root     |  INFO   | Hello1 log-info-record  | Log-level too low |
+        | root     |  DEBUG  | Hello1 log-debug-record | Log-level too low |
+        | root     |  ERROR  | Hello2 log-error-record | Scenario passes, capture log is suppressed |
+        | root     |  WARN   | Hello2 log-warn-record  | Scenario passes, capture log is suppressed |
+        | root     |  INFO   | Hello2 log-info-record  | Scenario passes, capture log is suppressed |
+        | root     |  DEBUG  | Hello2 log-debug-record | Scenario passes, capture log is suppressed |
+
+
+  @capture
+  Scenario: Logcapture mode: Use logging_level in configuration file
+    Given a file named "behave.ini" with:
+        """
+        [behave]
+        logging_level = ERROR
+        """
+    When I run "behave -f plain -T features/"
+    Then it should fail with:
+        """
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain:
+        """
+        Captured logging:
+        ERROR:root:Hello1 log-error-record
+        """
+    But the command output should not contain the following log records:
+        | category | level   | message                 | Comment |
+        | root     |  WARN   | Hello1 log-warn-record  | Log-level too low |
+        | root     |  INFO   | Hello1 log-info-record  | Log-level too low |
+        | root     |  DEBUG  | Hello1 log-debug-record | Log-level too low |
+        | root     |  ERROR  | Hello2 log-error-record | Scenario passes |
+        | root     |  WARN   | Hello2 log-warn-record  | Scenario passes |
+        | root     |  INFO   | Hello2 log-info-record  | Scenario passes |
+        | root     |  DEBUG  | Hello2 log-debug-record | Scenario passes |
+
+
+  @no_capture
+  Scenario: Normal mode: Use logging_level on command-line
+    Given a file named "behave.ini" with:
+        """
+        [behave]
+        logging_level = INFO
+        """
+    When I run "behave -f plain -T --logging-level=WARN --no-logcapture features/"
+    Then it should fail with:
+        """
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain the following log records:
+        | category | level   | message |
+        | root     |  ERROR  | Hello1 log-error-record |
+        | root     |  WARN   | Hello1 log-warn-record  |
+        | root     |  ERROR  | Hello2 log-error-record |
+        | root     |  WARN   | Hello2 log-warn-record  |
+    But the command output should not contain the following log records:
+        | category | level   | message                 | Comment |
+        | root     |  INFO   | Hello1 log-info-record  | Log-level too low |
+        | root     |  DEBUG  | Hello1 log-debug-record | Same reason |
+        | root     |  INFO   | Hello2 log-info-record  | Same reason |
+        | root     |  DEBUG  | Hello2 log-debug-record | Same reason |
+
+  @no_capture
+  Scenario: Normal mode: Use logging_level in configuration file
+    Given a file named "behave.ini" with:
+        """
+        [behave]
+        log_capture = false
+        logging_level = ERROR
+        """
+      When I run "behave -f plain -T features/"
+      Then it should fail with:
+        """
+        1 scenario passed, 1 failed, 0 skipped
+        3 steps passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the command output should contain the following log records:
+        | category | level   | message |
+        | root     |  ERROR  | Hello1 log-error-record |
+        | root     |  ERROR  | Hello2 log-error-record |
+    But the command output should not contain the following log records:
+        | category | level   | message                 | Comment |
+        | root     |  WARN   | Hello1 log-warn-record  | Log-level too low |
+        | root     |  INFO   | Hello1 log-info-record  | Same reason |
+        | root     |  DEBUG  | Hello1 log-debug-record | Same reason |
+        | root     |  WARN   | Hello2 log-warn-record  | Same reason |
+        | root     |  INFO   | Hello2 log-info-record  | Same reason |
+        | root     |  DEBUG  | Hello2 log-debug-record | Same reason |

data/vendor/behave/features/logging.setup_with_configfile.feature

@@ -0,0 +1,137 @@
+Feature: Setup logging subsystem by using a logging configfile
+
+  As a tester
+  I want to setup the logging subsystem by using a configfile
+  To be more flexible even in complex situations
+
+  @setup
+  Scenario: Feature setup
+    Given a new working directory
+    And a file named "features/steps/use_behave4cmd_steps.py" with:
+        """
+        import behave4cmd0.log.steps
+        import behave4cmd0.failing_steps
+        import behave4cmd0.passing_steps
+        """
+    And a file named "features/example.log_and_pass.feature" with:
+        """
+        Feature:
+          Scenario: Passing
+            Given I create log records with:
+              | category | level | message |
+              | root     | FATAL | Hello Alice  |
+              | foo      | ERROR | Hello Bob    |
+              | foo.bar  | WARN  | Hello Charly |
+              | bar      | INFO  | Hello Dora   |
+              | baz      | DEBUG | Hello Emily  |
+            And another step passes
+        """
+    And a file named "features/example.log_and_fail.feature" with:
+        """
+        Feature:
+          Scenario: Failing
+            Given I create log records with:
+              | category | level | message |
+              | root     | FATAL | Hello Alice  |
+              | foo      | ERROR | Hello Bob    |
+              | foo.bar  | WARN  | Hello Charly |
+              | bar      | INFO  | Hello Dora   |
+              | baz      | DEBUG | Hello Emily  |
+            And another step fails
+        """
+    And a file named "behave.ini" with:
+        """
+        [behave]
+        log_capture = false
+        logging_level = DEBUG
+        logging_format = LOG.%(levelname)-8s  %(name)-10s: %(message)s
+        """
+    And a file named "behave_logging.ini" with:
+        """
+        [loggers]
+        keys=root
+
+        [handlers]
+        keys=Console,File
+
+        [formatters]
+        keys=Brief
+
+        [logger_root]
+        level = NOTSET
+        handlers = File
+        # handlers = Console,File
+
+        [handler_File]
+        class=FileHandler
+        args=("behave.log", 'w')
+        level=NOTSET
+        formatter=Brief
+
+        [handler_Console]
+        class=StreamHandler
+        args=(sys.stderr,)
+        level=NOTSET
+        formatter=Brief
+
+        [formatter_Brief]
+        format= LOG.%(levelname)-8s  %(name)-10s: %(message)s
+        datefmt=
+        """
+
+  Scenario: Setup logging subsystem via environment (case: logging mode)
+    Given a file named "features/environment.py" with:
+        """
+        def before_all(context):
+            context.config.setup_logging(configfile="behave_logging.ini")
+        """
+    And I use the log record configuration:
+        | property | value |
+        | format   | LOG.%(levelname)-8s  %(name)-10s: %(message)s |
+    When I run "behave -f plain features/example.log_and_pass.feature"
+    Then it should pass
+    And the file "behave.log" should contain the log records:
+        | category | level | message |
+        | root     | FATAL | Hello Alice  |
+        | foo      | ERROR | Hello Bob    |
+        | foo.bar  | WARN  | Hello Charly |
+        | bar      | INFO  | Hello Dora   |
+        | baz      | DEBUG | Hello Emily  |
+    And the command output should not contain the following log records:
+        | category | level | message |
+        | root     | FATAL | Hello Alice  |
+        | foo      | ERROR | Hello Bob    |
+        | foo.bar  | WARN  | Hello Charly |
+        | bar      | INFO  | Hello Dora   |
+        | baz      | DEBUG | Hello Emily  |
+
+
+  Scenario: Setup logging subsystem via environment (case: log-capture mode)
+    Given a file named "features/environment.py" with:
+        """
+        def before_all(context):
+            context.config.setup_logging(configfile="behave_logging.ini")
+        """
+    And I use the log record configuration:
+        | property | value |
+        | format   | LOG.%(levelname)-8s  %(name)-10s: %(message)s |
+    When I run "behave -f plain --logcapture features/example.log_and_fail.feature"
+    Then it should fail with:
+        """
+        0 scenarios passed, 1 failed, 0 skipped
+        1 step passed, 1 failed, 0 skipped, 0 undefined
+        """
+    And the file "behave.log" should contain the log records:
+        | category | level | message |
+        | root     | FATAL | Hello Alice  |
+        | foo      | ERROR | Hello Bob    |
+        | foo.bar  | WARN  | Hello Charly |
+        | bar      | INFO  | Hello Dora   |
+        | baz      | DEBUG | Hello Emily  |
+    And the command output should contain the following log records:
+        | category | level | message |
+        | root     | FATAL | Hello Alice  |
+        | foo      | ERROR | Hello Bob    |
+        | foo.bar  | WARN  | Hello Charly |
+        | bar      | INFO  | Hello Dora   |
+        | baz      | DEBUG | Hello Emily  |

data/vendor/behave/features/parser.background.sad_cases.feature

@@ -0,0 +1,129 @@
+Feature: Ensure that BAD/SAD Use cases of Background are detected
+
+  To improve diagnostics when parser failures occur
+  As a test writer
+  I expect reasonable explanations what went wrong.
+
+    @setup
+    Scenario: Feature Setup
+      Given a new working directory
+      And a file named "features/steps/passing_steps.py" with
+        """
+        from behave import step
+
+        @step('a step passes')
+        def step_passes(context):
+            pass
+
+        @step('a step passes with "{text}"')
+        def step_passes(context, text):
+            pass
+        """
+
+
+    Scenario: Background with tags is not supported
+      Given a file named "features/syndrome.background_with_tags.feature" with
+        """
+        Feature: Ensure this fails
+
+          @tags_are @not_supported @here
+          Background: Oops...
+            Given a step passes
+
+          Scenario: More...
+            Given a step passes
+        """
+      When I run "behave -f plain -T features/syndrome.background_with_tags.feature"
+      Then it should fail with
+        """
+        Failed to parse "{__WORKDIR__}/features/syndrome.background_with_tags.feature":
+        Parser failure in state taggable_statement, at line 4: "Background: Oops..."
+        REASON: Background does not support tags.
+        """
+
+
+    Scenario: Background should not occur after a Scenario
+      Given a file named "features/syndrome.background_after_scenario.feature" with
+        """
+        Feature: Ensure this fails1
+
+          Scenario: One...
+            Given a step passes
+
+          Background: Oops, too late (after Scenario)
+            When a step passes
+        """
+      When I run "behave -f plain -T features/syndrome.background_after_scenario.feature"
+      Then it should fail with
+        """
+        Failed to parse "{__WORKDIR__}/features/syndrome.background_after_scenario.feature":
+        Parser failure in state steps, at line 6: "Background: Oops, too late (after Scenario)"
+        REASON: Background may not occur after Scenario/ScenarioOutline.
+        """
+
+
+    Scenario: Tagged Background should not occur after a Scenario
+      Given a file named "features/syndrome.tagged_background_after_scenario.feature" with
+        """
+        Feature: Ensure this fails1
+
+          Scenario: One...
+            Given a step passes
+
+          @tags_are @not_supported @here
+          Background: Oops, too late (after Scenario)
+            When a step passes
+        """
+      When I run "behave -f plain -T features/syndrome.tagged_background_after_scenario.feature"
+      Then it should fail with
+        """
+        Parser failure in state taggable_statement, at line 7: "Background: Oops, too late (after Scenario)"
+        REASON: Background may not occur after Scenario/ScenarioOutline.
+        """
+
+
+    Scenario: Background should not occur after a Scenario Outline
+      Given a file named "features/syndrome.background_after_scenario_outline.feature" with
+        """
+        Feature: Ensure this fails3
+
+          Scenario Outline: Two...
+            Given a step passes with "<name>"
+
+            Examples:
+              | name  |
+              | Alice |
+
+          Background: Oops, too late (after Scenario Outline)
+            When a step passes
+        """
+      When I run "behave -f plain -T features/syndrome.background_after_scenario_outline.feature"
+      Then it should fail with
+        """
+        Parser failure in state steps, at line 10: "Background: Oops, too late (after Scenario Outline)"
+        REASON: Background may not occur after Scenario/ScenarioOutline.
+        """
+
+
+    Scenario: Tagged Background should not occur after a Scenario Outline
+      Given a file named "features/syndrome.background_after_scenario_outline.feature" with
+        """
+        Feature: Ensure this fails4
+
+          Scenario Outline: Two...
+            Given a step passes with "<name>"
+
+            Examples:
+              | name  |
+              | Alice |
+
+          @tags_are @not_supported @here
+          Background: Oops, too late (after Scenario Outline)
+            When a step passes
+        """
+      When I run "behave -f plain -T features/syndrome.background_after_scenario_outline.feature"
+      Then it should fail with
+        """
+        Parser failure in state taggable_statement, at line 11: "Background: Oops, too late (after Scenario Outline)"
+        REASON: Background may not occur after Scenario/ScenarioOutline.
+        """

data/vendor/behave/features/parser.feature.sad_cases.feature

@@ -0,0 +1,144 @@
+Feature: Parsing a Feature File without a Feature or with several Features
+
+
+    @setup
+    Scenario: Feature Setup
+      Given a new working directory
+      And an empty file named "features/steps/empty_steps.py"
+      And a file named "features/steps/passing_steps.py" with:
+        """
+        from behave import step
+
+        @step('a step passes')
+        def step_passes(context):
+            pass
+        """
+
+    @no_feature
+    Scenario: Empty Feature File
+      Given an empty file named "features/empty.feature"
+      When I run "behave -f plain features/empty.feature"
+      Then it should pass with:
+          """
+          0 features passed, 0 failed, 0 skipped
+          0 scenarios passed, 0 failed, 0 skipped
+          0 steps passed, 0 failed, 0 skipped, 0 undefined
+          """
+
+
+    @no_feature
+    Scenario: Feature File without Feature, only with Comments
+      Given a file named "features/only_comments.feature" with:
+        """
+        # COMMENT: Comment starts at begin of line.
+            # INDENTED-COMMENT: Comment starts after some whitespace.
+        """
+      When I run "behave -f plain features/only_comments.feature"
+      Then it should pass with:
+        """
+        0 features passed, 0 failed, 0 skipped
+        0 scenarios passed, 0 failed, 0 skipped
+        0 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+
+
+    @no_feature
+    Scenario: Feature File without Feature, only with Empty Lines
+      Given a file named "features/only_empty_lines.feature" with:
+        """
+
+        """
+      When I run "behave -f plain features/only_empty_lines.feature"
+      Then it should pass with:
+        """
+        0 features passed, 0 failed, 0 skipped
+        0 scenarios passed, 0 failed, 0 skipped
+        0 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+
+
+    @no_feature
+    Scenario: Feature File without Feature, only with Tags
+      Given a file named "features/only_tags.feature" with:
+        """
+        @weird
+        @no_feature
+        """
+      When I run "behave -f plain features/only_tags.feature"
+      Then it should pass with:
+        """
+        0 features passed, 0 failed, 0 skipped
+        0 scenarios passed, 0 failed, 0 skipped
+        0 steps passed, 0 failed, 0 skipped, 0 undefined
+        """
+
+    @no_feature
+    @parser.with_parse_error
+    Scenario: Feature File with Text
+      Given a file named "features/only_text.feature" with:
+        """
+        This File: Contains only text without keywords.
+        OOPS.
+        """
+      When I run "behave -f plain features/only_text.feature"
+      Then it should fail with:
+        """
+        Failed to parse "{__WORKDIR__}/features/only_text.feature":
+        Parser failure in state init, at line 1: "This File: Contains only text without keywords."
+        REASON: No feature found.
+        """
+
+
+    @no_feature
+    @parser.with_parse_error
+    Scenario: Feature File with Scenario, but without Feature keyword
+      Given a file named "features/naked_scenario_only.feature" with:
+        """
+          Scenario:
+            Given a step passes
+            When a step passes
+            Then a step passes
+        """
+      When I run "behave -f plain features/naked_scenario_only.feature"
+      Then it should fail with:
+        """
+        Failed to parse "{__WORKDIR__}/features/naked_scenario_only.feature":
+        Parser failure in state init, at line 1: "Scenario:"
+        REASON: Scenario may not occur before Feature.
+        """
+
+
+    @many_features
+    @parser.with_parse_error
+    Scenario: Feature file with 2 features
+
+       NOTE: Gherkin parser supports only one feature per feature file.
+
+          Given a file named "features/steps/passing_steps.py" with:
+            """
+            from behave import step
+
+            @step('a step passes')
+            def step_passes(context):
+                pass
+            """
+          And a file named "features/two_features.feature" with:
+            """
+            Feature: F1
+              Scenario: F1.1
+                Given a step passes
+                When a step passes
+                Then a step passes
+
+            Feature: F2
+              Scenario: F2.1
+                Given a step passes
+                Then a step passes
+            """
+          When I run "behave -f plain features/two_features.feature"
+          Then it should fail with:
+            """
+            Failed to parse "{__WORKDIR__}/features/two_features.feature":
+            Parser failure in state steps, at line 7: "Feature: F2"
+            REASON: Multiple features in one file are not supported.
+            """