busser-behave 0.1.3

data/vendor/behave/features/formatter.steps.feature

@@ -0,0 +1,181 @@
+@sequential
+Feature: Steps Formatter (Step Definitions Formatter)
+
+    As a test writer
+    I want to get a quick overview which step definitions exist
+    To simplify the writing of feature tests.
+
+    . SOLUTION: Use StepsFormatter in dry-run mode, like:
+    .
+    .       behave --dry-run -f steps features/
+    .
+    . NOTE: This formatter is similar to the "stepdefs" formatter in cucumber.
+
+
+    @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 fails')
+            def step_fails(context):
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/steps/alice_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} lives in {city}')
+            def step_given_person_lives_in_city(context, person, city):
+                pass
+
+            @when('I visit {person}')
+            def step_when_visit_person(context, person):
+                pass
+
+            @then('I meet {person} in {city}')
+            def step_then_meet_person_in_city(context, person, city):
+                pass
+            """
+        And a file named "features/steps/bob_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} works for {company}')
+            def step_given_person_works_for_company(context, person, company):
+                pass
+
+            @when('I plan a meeting with {person}')
+            def step_when_plan_meeting_with_person(context, person):
+                pass
+
+            @then('I meet him at the {company} office')
+            def step_then_meet_him_at_company_office(context, company):
+                pass
+            """
+        And an empty file named "features/none.feature"
+
+
+    @usecase.primary
+    Scenario: Show available step definitions in dry-run mode
+        When I run "behave --dry-run -f steps features/"
+        Then it should pass with:
+          """
+          GIVEN STEP DEFINITIONS[4]:
+            Given {person} lives in {city}            # features/steps/alice_steps.py:3
+            Given {person} works for {company}        # features/steps/bob_steps.py:3
+            Given a step passes                       # features/steps/passing_steps.py:3
+            Given a step fails                        # features/steps/passing_steps.py:7
+
+          WHEN STEP DEFINITIONS[4]:
+            When I visit {person}                     # features/steps/alice_steps.py:7
+            When I plan a meeting with {person}       # features/steps/bob_steps.py:7
+            When a step passes                        # features/steps/passing_steps.py:3
+            When a step fails                         # features/steps/passing_steps.py:7
+
+          THEN STEP DEFINITIONS[4]:
+            Then I meet {person} in {city}            # features/steps/alice_steps.py:11
+            Then I meet him at the {company} office   # features/steps/bob_steps.py:11
+            Then a step passes                        # features/steps/passing_steps.py:3
+            Then a step fails                         # features/steps/passing_steps.py:7
+
+          GENERIC STEP DEFINITIONS[2]:
+            * a step passes                           # features/steps/passing_steps.py:3
+            * a step fails                            # features/steps/passing_steps.py:7
+          """
+        But note that "the GENERIC STEP DEFINITIONS can be used as given/when/then steps"
+
+
+    @usecase.secondary
+    Scenario: Show available step definitions in normal mode
+        When I run "behave -f steps features/"
+        Then it should pass with:
+          """
+          GIVEN STEP DEFINITIONS[4]:
+            Given {person} lives in {city}            # features/steps/alice_steps.py:3
+            Given {person} works for {company}        # features/steps/bob_steps.py:3
+            Given a step passes                       # features/steps/passing_steps.py:3
+            Given a step fails                        # features/steps/passing_steps.py:7
+
+          WHEN STEP DEFINITIONS[4]:
+            When I visit {person}                     # features/steps/alice_steps.py:7
+            When I plan a meeting with {person}       # features/steps/bob_steps.py:7
+            When a step passes                        # features/steps/passing_steps.py:3
+            When a step fails                         # features/steps/passing_steps.py:7
+
+          THEN STEP DEFINITIONS[4]:
+            Then I meet {person} in {city}            # features/steps/alice_steps.py:11
+            Then I meet him at the {company} office   # features/steps/bob_steps.py:11
+            Then a step passes                        # features/steps/passing_steps.py:3
+            Then a step fails                         # features/steps/passing_steps.py:7
+
+          GENERIC STEP DEFINITIONS[2]:
+            * a step passes                           # features/steps/passing_steps.py:3
+            * a step fails                            # features/steps/passing_steps.py:7
+          """
+
+
+    @language
+    Scenario: Show available step definitions for language=de (German)
+        When I run "behave --dry-run -f steps --lang=de features/"
+        Then it should pass with:
+          """
+          GIVEN STEP DEFINITIONS[4]:
+            Angenommen {person} lives in {city}       # features/steps/alice_steps.py:3
+            Angenommen {person} works for {company}   # features/steps/bob_steps.py:3
+            Angenommen a step passes                  # features/steps/passing_steps.py:3
+            Angenommen a step fails                   # features/steps/passing_steps.py:7
+
+          WHEN STEP DEFINITIONS[4]:
+            Wenn I visit {person}                     # features/steps/alice_steps.py:7
+            Wenn I plan a meeting with {person}       # features/steps/bob_steps.py:7
+            Wenn a step passes                        # features/steps/passing_steps.py:3
+            Wenn a step fails                         # features/steps/passing_steps.py:7
+
+          THEN STEP DEFINITIONS[4]:
+            Dann I meet {person} in {city}            # features/steps/alice_steps.py:11
+            Dann I meet him at the {company} office   # features/steps/bob_steps.py:11
+            Dann a step passes                        # features/steps/passing_steps.py:3
+            Dann a step fails                         # features/steps/passing_steps.py:7
+
+          GENERIC STEP DEFINITIONS[2]:
+            * a step passes                           # features/steps/passing_steps.py:3
+            * a step fails                            # features/steps/passing_steps.py:7
+          """
+        But note that "this may fail depending on the language you use with your features"
+
+
+    @language
+    Scenario: Show available step definitions for language=fr (French)
+        When I run "behave --dry-run -f steps --lang=fr features/"
+        Then it should pass with:
+          """
+          GIVEN STEP DEFINITIONS[4]:
+            Soit {person} lives in {city}             # features/steps/alice_steps.py:3
+            Soit {person} works for {company}         # features/steps/bob_steps.py:3
+            Soit a step passes                        # features/steps/passing_steps.py:3
+            Soit a step fails                         # features/steps/passing_steps.py:7
+
+          WHEN STEP DEFINITIONS[4]:
+            Quand I visit {person}                    # features/steps/alice_steps.py:7
+            Quand I plan a meeting with {person}      # features/steps/bob_steps.py:7
+            Quand a step passes                       # features/steps/passing_steps.py:3
+            Quand a step fails                        # features/steps/passing_steps.py:7
+
+          THEN STEP DEFINITIONS[4]:
+            Alors I meet {person} in {city}           # features/steps/alice_steps.py:11
+            Alors I meet him at the {company} office  # features/steps/bob_steps.py:11
+            Alors a step passes                       # features/steps/passing_steps.py:3
+            Alors a step fails                        # features/steps/passing_steps.py:7
+
+          GENERIC STEP DEFINITIONS[2]:
+            * a step passes                           # features/steps/passing_steps.py:3
+            * a step fails                            # features/steps/passing_steps.py:7
+          """
+        But note that "this may fail depending on the language you use with your features"

data/vendor/behave/features/formatter.steps_catalog.feature

@@ -0,0 +1,100 @@
+@sequential
+Feature: Steps Catalog Formatter
+
+    As a test writer
+    I want to get a quick overview how to use a step definition
+    By reading the step definition documentation (doc-stings).
+    However I am not interested in technical details such as
+    source location and step function names.
+    Also, I would prefer to view the step as they appear in a feature file.
+
+    . SOLUTION: Use StepsDocFormatter in dry-run mode, like:
+    .
+    .       behave --dry-run -f steps.catalog features/
+
+
+    @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):
+                '''This step always passes.'''
+                pass
+
+            @step('a step fails')
+            def step_fails(context):
+                '''This step is expected to fail.'''
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/steps/alice_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} lives in {city}')
+            def step_given_person_lives_in_city(context, person, city):
+                '''
+                Setup the data where a person lives and store in the database.
+
+                :param person:  Person's name (as string).
+                :param city:    City where the person lives (as string).
+                '''
+                database = getattr(context, "database", None)
+                if not database:
+                    context.database = {}
+                context.database[person] = { "city": city }
+
+            @when('I visit {person}')
+            def step_when_visit_person(context, person):
+                # -- NO DOC-STRING.
+                pass
+
+            @then('I meet {person} in {city}')
+            def step_then_meet_person_in_city(context, person, city):
+                '''
+                Checks if I can meet the person in the expected city.
+
+                :param person:  Person's name as key (as string).
+                :param city:    Expected city (as string).
+                '''
+                person_data = context.database.get(person, None)
+                assert person_data is not None, "Person %s not found" % person
+                assert person_data["city"] == city
+            """
+        And an empty file named "features/none.feature"
+
+
+    @usecase.primary
+    Scenario: Show documentation of available step definitions in dry-run mode
+        When I run "behave --steps-catalog features/"
+        Then it should pass with:
+          """
+          Given {person} lives in {city}
+              Setup the data where a person lives and store in the database.
+
+              :param person:  Person's name (as string).
+              :param city:    City where the person lives (as string).
+
+          When I visit {person}
+
+          Then I meet {person} in {city}
+              Checks if I can meet the person in the expected city.
+
+              :param person:  Person's name as key (as string).
+              :param city:    Expected city (as string).
+
+          Given a step passes
+          When a step passes
+          Then a step passes
+              This step always passes.
+
+          Given a step fails
+          When a step fails
+          Then a step fails
+              This step is expected to fail.
+          """
+        But note that "the step definitions are ordered by step type"
+        And note that "'When I visit {person}' has no doc-string"

data/vendor/behave/features/formatter.steps_doc.feature

@@ -0,0 +1,140 @@
+@sequential
+Feature: Steps Doc Formatter
+
+    As a test writer
+    I want to get a quick overview how to use a step definition
+    By reading the step definition documentation (doc-stings).
+
+    . SOLUTION: Use StepsDocFormatter in dry-run mode, like:
+    .
+    .       behave --dry-run -f steps.doc features/
+
+
+    @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):
+                '''This step always passes.'''
+                pass
+
+            @step('a step fails')
+            def step_fails(context):
+                '''This step is expected to fail.'''
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/steps/alice_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} lives in {city}')
+            def step_given_person_lives_in_city(context, person, city):
+                '''
+                Setup the data where a person lives and store in the database.
+
+                :param person:  Person's name (as string).
+                :param city:    City where the person lives (as string).
+                '''
+                database = getattr(context, "database", None)
+                if not database:
+                    context.database = {}
+                context.database[person] = { "city": city }
+
+            @when('I visit {person}')
+            def step_when_visit_person(context, person):
+                # -- NO DOC-STRING.
+                pass
+
+            @then('I meet {person} in {city}')
+            def step_then_meet_person_in_city(context, person, city):
+                '''
+                Checks if I can meet the person in the expected city.
+
+                :param person:  Person's name as key (as string).
+                :param city:    Expected city (as string).
+                '''
+                person_data = context.database.get(person, None)
+                assert person_data is not None, "Person %s not found" % person
+                assert person_data["city"] == city
+            """
+        And an empty file named "features/none.feature"
+
+
+    @usecase.primary
+    Scenario: Show documentation of available step definitions in dry-run mode
+        When I run "behave --dry-run -f steps.doc features/"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')
+            Function: step_given_person_lives_in_city()
+            Location: features/steps/alice_steps.py:3
+              Setup the data where a person lives and store in the database.
+
+              :param person:  Person's name (as string).
+              :param city:    City where the person lives (as string).
+
+          @when('I visit {person}')
+            Function: step_when_visit_person()
+            Location: features/steps/alice_steps.py:16
+
+          @then('I meet {person} in {city}')
+            Function: step_then_meet_person_in_city()
+            Location: features/steps/alice_steps.py:21
+              Checks if I can meet the person in the expected city.
+
+              :param person:  Person's name as key (as string).
+              :param city:    Expected city (as string).
+
+          @step('a step passes')
+            Function: step_passes()
+            Location: features/steps/passing_steps.py:3
+              This step always passes.
+
+          @step('a step fails')
+            Function: step_fails()
+            Location: features/steps/passing_steps.py:8
+              This step is expected to fail.
+          """
+        But note that "the step definitions are ordered by file location"
+        And note that "@when('I visit {person}') has no doc-string"
+
+
+    @usecase.secondary
+    Scenario: Show documentation of available step definitions in normal mode
+        When I run "behave -f steps.doc features/"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')
+            Function: step_given_person_lives_in_city()
+            Location: features/steps/alice_steps.py:3
+              Setup the data where a person lives and store in the database.
+
+              :param person:  Person's name (as string).
+              :param city:    City where the person lives (as string).
+
+          @when('I visit {person}')
+            Function: step_when_visit_person()
+            Location: features/steps/alice_steps.py:16
+
+          @then('I meet {person} in {city}')
+            Function: step_then_meet_person_in_city()
+            Location: features/steps/alice_steps.py:21
+              Checks if I can meet the person in the expected city.
+
+              :param person:  Person's name as key (as string).
+              :param city:    Expected city (as string).
+
+          @step('a step passes')
+            Function: step_passes()
+            Location: features/steps/passing_steps.py:3
+              This step always passes.
+
+          @step('a step fails')
+            Function: step_fails()
+            Location: features/steps/passing_steps.py:8
+              This step is expected to fail.
+          """

data/vendor/behave/features/formatter.steps_usage.feature

@@ -0,0 +1,404 @@
+@sequential
+Feature: Steps Usage Formatter
+
+    As a test writer
+    I want to get an overview which step definitions are used and where
+    To simplify the refactoring of step definitions (and features).
+
+    . SOLUTION: Use StepsUsageFormatter in dry-run mode, like:
+    .
+    .       behave --dry-run -f steps.usage features/
+    .
+    . NOTE: This formatter corresponds to the "usage" formatter in cucumber.
+
+
+    @setup
+    Scenario: Feature Setup
+        Given a new working directory
+        And a file named "features/steps/passing_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_passes(context, word):
+                assert False, "XFAIL-STEP"
+            """
+        And a file named "features/steps/unused_steps.py" with:
+            """
+            from behave import step
+
+            @step('an unused step')
+            def step_unused(context):
+                pass
+
+            @step('another unused step')
+            def step_another_unused(context):
+                pass
+            """
+        And a file named "features/steps/alice_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} lives in {city}')
+            def step_given_person_lives_in_city(context, person, city):
+                pass
+
+            @when('I visit {person}')
+            def step_when_visit_person(context, person):
+                pass
+
+            @then('I meet {person} in {city}')
+            def step_then_meet_person_in_city(context, person, city):
+                pass
+            """
+        And a file named "features/steps/charly_steps.py" with:
+            """
+            from behave import given, when, then
+
+            @given('{person} works for {company}')
+            def step_given_person_works_for_company(context, person, company):
+                pass
+
+            @when('I plan a meeting with {person}')
+            def step_when_plan_meeting_with_person(context, person):
+                pass
+
+            @then('I meet him at the {company} office')
+            def step_then_meet_him_at_company_office(context, company):
+                pass
+            """
+        And a file named "features/alice.feature" with:
+            """
+            Feature:
+              Scenario: Visit Alice
+                Given Alice lives in Paris
+                When I visit Alice
+                Then I meet Alice in Paris
+
+              Scenario: Visit Bob
+                Given Bob lives in Berlin
+                When I visit Bob
+                Then I meet Bob in Berlin
+            """
+        And a file named "features/bob.feature" with:
+            """
+            Feature:
+              Scenario: Visit Bob
+                Given Bob lives in Barcelona
+                When I visit Bob
+                Then I meet Bob in Barcelona
+                And a step passes
+            """
+        And a file named "features/charly.feature" with:
+            """
+            Feature:
+              Scenario: Meeting with Charly
+                Given Charly works for ACME
+                When I plan a meeting with Charly
+                Then I meet him at the ACME office
+            """
+
+
+    @usecase.primary
+    Scenario: Show step definitions usage with all features in dry-run mode
+        When I run "behave --dry-run -f steps.usage features/"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')        # features/steps/alice_steps.py:3
+            Given Alice lives in Paris              # features/alice.feature:3
+            Given Bob lives in Berlin               # features/alice.feature:8
+            Given Bob lives in Barcelona            # features/bob.feature:3
+
+          @when('I visit {person}')                 # features/steps/alice_steps.py:7
+            When I visit Alice                      # features/alice.feature:4
+            When I visit Bob                        # features/alice.feature:9
+            When I visit Bob                        # features/bob.feature:4
+
+          @then('I meet {person} in {city}')        # features/steps/alice_steps.py:11
+            Then I meet Alice in Paris              # features/alice.feature:5
+            Then I meet Bob in Berlin               # features/alice.feature:10
+            Then I meet Bob in Barcelona            # features/bob.feature:5
+
+          @given('{person} works for {company}')    # features/steps/charly_steps.py:3
+            Given Charly works for ACME             # features/charly.feature:3
+
+          @when('I plan a meeting with {person}')   # features/steps/charly_steps.py:7
+            When I plan a meeting with Charly       # features/charly.feature:4
+
+          @then('I meet him at the {company} office')  # features/steps/charly_steps.py:11
+            Then I meet him at the ACME office         # features/charly.feature:5
+
+          @step('{word:w} step passes')             # features/steps/passing_steps.py:3
+            And a step passes                       # features/bob.feature:6
+
+          UNUSED STEP DEFINITIONS[3]:
+            @step('{word:w} step fails')            # features/steps/passing_steps.py:7
+            @step('an unused step')                 # features/steps/unused_steps.py:3
+            @step('another unused step')            # features/steps/unused_steps.py:7
+          """
+        And note that "the UNUSED STEP DEFINITIONS are ordered by file location"
+        But note that "step definitions from unused_steps.py are not used by any feature"
+
+
+    @usecase.primary
+    Scenario: Show step definitions usage with one feature (dry-run mode)
+        When I run "behave --dry-run -f steps.usage features/alice.feature"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')        # features/steps/alice_steps.py:3
+            Given Alice lives in Paris              # features/alice.feature:3
+            Given Bob lives in Berlin               # features/alice.feature:8
+
+          @when('I visit {person}')                 # features/steps/alice_steps.py:7
+            When I visit Alice                      # features/alice.feature:4
+            When I visit Bob                        # features/alice.feature:9
+
+          @then('I meet {person} in {city}')        # features/steps/alice_steps.py:11
+            Then I meet Alice in Paris              # features/alice.feature:5
+            Then I meet Bob in Berlin               # features/alice.feature:10
+
+          UNUSED STEP DEFINITIONS[7]:
+            @given('{person} works for {company}')       # features/steps/charly_steps.py:3
+            @when('I plan a meeting with {person}')      # features/steps/charly_steps.py:7
+            @then('I meet him at the {company} office')  # features/steps/charly_steps.py:11
+            @step('{word:w} step passes')                # features/steps/passing_steps.py:3
+            @step('{word:w} step fails')                 # features/steps/passing_steps.py:7
+            @step('an unused step')                      # features/steps/unused_steps.py:3
+            @step('another unused step')                 # features/steps/unused_steps.py:7
+          """
+        But note that "step definitions from charly_steps.py, passing_steps.py are now no longer used"
+
+
+    @usecase.primary
+    Scenario: Show step definitions usage with two features (dry-run mode)
+        When I run "behave --dry-run -f steps.usage features/alice.feature features/charly.feature"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')        # features/steps/alice_steps.py:3
+            Given Alice lives in Paris              # features/alice.feature:3
+            Given Bob lives in Berlin               # features/alice.feature:8
+
+          @when('I visit {person}')                 # features/steps/alice_steps.py:7
+            When I visit Alice                      # features/alice.feature:4
+            When I visit Bob                        # features/alice.feature:9
+
+          @then('I meet {person} in {city}')        # features/steps/alice_steps.py:11
+            Then I meet Alice in Paris              # features/alice.feature:5
+            Then I meet Bob in Berlin               # features/alice.feature:10
+
+          @given('{person} works for {company}')    # features/steps/charly_steps.py:3
+            Given Charly works for ACME             # features/charly.feature:3
+
+          @when('I plan a meeting with {person}')   # features/steps/charly_steps.py:7
+            When I plan a meeting with Charly       # features/charly.feature:4
+
+          @then('I meet him at the {company} office')  # features/steps/charly_steps.py:11
+            Then I meet him at the ACME office         # features/charly.feature:5
+
+          UNUSED STEP DEFINITIONS[4]:
+            @step('{word:w} step passes')           # features/steps/passing_steps.py:3
+            @step('{word:w} step fails')            # features/steps/passing_steps.py:7
+            @step('an unused step')                 # features/steps/unused_steps.py:3
+            @step('another unused step')            # features/steps/unused_steps.py:7
+          """
+        But note that "step definitions from passing_steps.py, unused_steps.py are not used by any feature"
+
+
+    @usecase.secondary
+    Scenario: Show step definitions usage with all features in normal mode
+        When I run "behave -f steps.usage features/"
+        Then it should pass with:
+          """
+          @given('{person} lives in {city}')        # features/steps/alice_steps.py:3
+            Given Alice lives in Paris              # features/alice.feature:3
+            Given Bob lives in Berlin               # features/alice.feature:8
+            Given Bob lives in Barcelona            # features/bob.feature:3
+
+          @when('I visit {person}')                 # features/steps/alice_steps.py:7
+            When I visit Alice                      # features/alice.feature:4
+            When I visit Bob                        # features/alice.feature:9
+            When I visit Bob                        # features/bob.feature:4
+
+          @then('I meet {person} in {city}')        # features/steps/alice_steps.py:11
+            Then I meet Alice in Paris              # features/alice.feature:5
+            Then I meet Bob in Berlin               # features/alice.feature:10
+            Then I meet Bob in Barcelona            # features/bob.feature:5
+
+          @given('{person} works for {company}')    # features/steps/charly_steps.py:3
+            Given Charly works for ACME             # features/charly.feature:3
+
+          @when('I plan a meeting with {person}')   # features/steps/charly_steps.py:7
+            When I plan a meeting with Charly       # features/charly.feature:4
+
+          @then('I meet him at the {company} office')  # features/steps/charly_steps.py:11
+            Then I meet him at the ACME office         # features/charly.feature:5
+
+          @step('{word:w} step passes')             # features/steps/passing_steps.py:3
+            And a step passes                       # features/bob.feature:6
+
+          UNUSED STEP DEFINITIONS[3]:
+            @step('{word:w} step fails')            # features/steps/passing_steps.py:7
+            @step('an unused step')                 # features/steps/unused_steps.py:3
+            @step('another unused step')            # features/steps/unused_steps.py:7
+          """
+
+    @corner.case
+    Scenario: StepsUsageFormatter shows undefined steps
+        Given a file named "features/undefined.feature" with:
+          """
+          Feature: With undefined steps
+            Scenario:
+              Given a step is undefined
+              Then another step is undefined
+          """
+        When I run "behave --dry-run -f steps.usage features/alice.feature features/undefined.feature"
+        Then it should fail with:
+          """
+          0 features passed, 0 failed, 0 skipped, 2 untested
+          0 scenarios passed, 0 failed, 0 skipped, 3 untested
+          0 steps passed, 0 failed, 0 skipped, 2 undefined, 6 untested
+          """
+        And the command output should contain:
+          """
+          @given('{person} lives in {city}')        # features/steps/alice_steps.py:3
+            Given Alice lives in Paris              # features/alice.feature:3
+            Given Bob lives in Berlin               # features/alice.feature:8
+
+          @when('I visit {person}')                 # features/steps/alice_steps.py:7
+            When I visit Alice                      # features/alice.feature:4
+            When I visit Bob                        # features/alice.feature:9
+
+          @then('I meet {person} in {city}')        # features/steps/alice_steps.py:11
+            Then I meet Alice in Paris              # features/alice.feature:5
+            Then I meet Bob in Berlin               # features/alice.feature:10
+
+          UNUSED STEP DEFINITIONS[7]:
+            @given('{person} works for {company}')       # features/steps/charly_steps.py:3
+            @when('I plan a meeting with {person}')      # features/steps/charly_steps.py:7
+            @then('I meet him at the {company} office')  # features/steps/charly_steps.py:11
+            @step('{word:w} step passes')                # features/steps/passing_steps.py:3
+            @step('{word:w} step fails')                 # features/steps/passing_steps.py:7
+            @step('an unused step')                      # features/steps/unused_steps.py:3
+            @step('another unused step')                 # features/steps/unused_steps.py:7
+
+          UNDEFINED STEPS[2]:
+            Given a step is undefined               # features/undefined.feature:3
+            Then another step is undefined          # features/undefined.feature:4
+          """
+
+
+    @corner.case
+    Scenario: StepsUsageFormatter shows all locations of undefined step usage
+
+        Ensure that all location are shown where an undefined step is used
+
+        Given a file named "features/undefined_duplicates.feature" with:
+          """
+          Feature: With undefined steps
+
+            Scenario: Same undefined step used twice
+              Given a step is undefined
+              And a step is undefined
+              Then a step passes
+
+            Scenario: Same undefined step used again
+              Given a step passes
+              And a step is undefined
+          """
+        When I run "behave --dry-run -f steps.usage features/undefined_duplicates.feature"
+        Then it should fail with:
+          """
+          0 scenarios passed, 0 failed, 0 skipped, 2 untested
+          0 steps passed, 0 failed, 0 skipped, 3 undefined, 2 untested
+          """
+        And the command output should contain:
+          """
+          UNDEFINED STEPS[3]:
+            Given a step is undefined               # features/undefined_duplicates.feature:4
+            And a step is undefined                 # features/undefined_duplicates.feature:5
+            And a step is undefined                 # features/undefined_duplicates.feature:10
+          """
+
+    @use_outline
+    Scenario: Scenario Outlines should not cause duplicated step entries
+
+      Scenario Outlines generate Scenarios that use the same step multiple times.
+      This duplication should not be listed.
+
+        Given a file named "features/use_scenario_outline.feature" with:
+          """
+          Feature:
+            Scenario Outline:
+              Given a step <outcome1>
+              When another step <outcome2>
+
+            Examples:
+              | outcome1 | outcome2 |
+              |  passes  | passes   |
+              |  passes  | fails    |
+          """
+        When I run "behave --dry-run -f steps.usage features/use_scenario_outline.feature"
+        Then it should pass with:
+          """
+          0 scenarios passed, 0 failed, 0 skipped, 2 untested
+          0 steps passed, 0 failed, 0 skipped, 0 undefined, 4 untested
+          """
+        And the command output should contain:
+          """
+          @step('{word:w} step passes')             # features/steps/passing_steps.py:3
+            Given a step passes                     # features/use_scenario_outline.feature:3
+            When another step passes                # features/use_scenario_outline.feature:4
+
+          @step('{word:w} step fails')              # features/steps/passing_steps.py:7
+            When another step fails                 # features/use_scenario_outline.feature:4
+          """
+        But the command output should not contain:
+          """
+          @step('{word:w} step passes')             # features/steps/passing_steps.py:3
+            Given a step passes                     # features/use_scenario_outline.feature:3
+            When another step passes                # features/use_scenario_outline.feature:4
+            Given a step passes                     # features/use_scenario_outline.feature:3
+          """
+
+    @use_outline
+    Scenario: Scenario Outlines should not cause duplicated entries for undefined steps
+
+      Scenario Outlines generate Scenarios that use the same step multiple times.
+      This duplication should not be listed.
+
+        Given a file named "features/scenario_outline_with_undefined.feature" with:
+          """
+          Feature:
+            Scenario Outline:
+              Given a step is <status1>
+              When another step is <status2>
+
+            Examples:
+              | status1   | status2   |
+              | undefined | undefined |
+              | undefined | undefined |
+          """
+        When I run "behave --dry-run -f steps.usage features/scenario_outline_with_undefined.feature"
+        Then it should fail with:
+          """
+          0 scenarios passed, 0 failed, 0 skipped, 2 untested
+          0 steps passed, 0 failed, 0 skipped, 4 undefined
+           """
+        And the command output should contain:
+          """
+          UNDEFINED STEPS[2]:
+            Given a step is undefined               # features/scenario_outline_with_undefined.feature:3
+            When another step is undefined          # features/scenario_outline_with_undefined.feature:4
+          """
+        But the command output should not contain:
+          """
+          UNDEFINED STEPS[2]:
+            Given a step is undefined               # features/scenario_outline_with_undefined.feature:3
+            Given a step is undefined               # features/scenario_outline_with_undefined.feature:3
+            When another step is undefined          # features/scenario_outline_with_undefined.feature:4
+            When another step is undefined          # features/scenario_outline_with_undefined.feature:4
+          """