<commit_before>Feature: Cucumber command line
  In order to find out what step definitions need to be implemented
  Developers should always see what step definition is missing

  @spawn
  Scenario: Get info at arbitrary levels of nesting
    Given a file named "features/call_undefined_step_from_step_def.feature" with:
      """
      Feature: Calling undefined step

        Scenario: Call from feature
          Given this directly called step does not exist

        Scenario: Call directly
          Given a step that calls an undefined step

        Scenario: Call via another
          Given a step that calls a step that calls an undefined step
      """
    And a file named "features/step_definitions/steps.rb" with:
      """
      Given /^a step that calls an undefined step$/ do
        step 'this does not exist'
      end

      Given /^a step that calls a step that calls an undefined step$/ do
        step 'a step that calls an undefined step'
      end
      """
    When I run `cucumber --strict -q features/call_undefined_step_from_step_def.feature`
    Then it should fail with exactly:
      """
      Feature: Calling undefined step

        Scenario: Call from feature
          Given this directly called step does not exist
            Undefined step: "this directly called step does not exist" (Cucumber::Undefined)
            features/call_undefined_step_from_step_def.feature:4:in `Given this directly called step does not exist'

        Scenario: Call directly
          Given a step that calls an undefined step
            Undefined step: "this does not exist" (Cucumber::Undefined)
            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
            features/call_undefined_step_from_step_def.feature:7:in `Given a step that calls an undefined step'

        Scenario: Call via another
          Given a step that calls a step that calls an undefined step
            Undefined step: "this does not exist" (Cucumber::Undefined)
            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
            ./features/step_definitions/steps.rb:6:in `/^a step that calls a step that calls an undefined step$/'
            features/call_undefined_step_from_step_def.feature:10:in `Given a step that calls a step that calls an undefined step'

      3 scenarios (3 undefined)
      3 steps (3 undefined)
      0m0.012s

      """
<commit_msg>Update how undefined nested steps are reported.<commit_after>Feature: Cucumber command line
  In order to find out what step definitions need to be implemented
  Developers should always see what step definition is missing

  @spawn
  Scenario: Get info at arbitrary levels of nesting
    Given a file named "features/call_undefined_step_from_step_def.feature" with:
      """
      Feature: Calling undefined step

        Scenario: Call from feature
          Given this directly called step does not exist

        Scenario: Call directly
          Given a step that calls an undefined step

        Scenario: Call via another
          Given a step that calls a step that calls an undefined step
      """
    And a file named "features/step_definitions/steps.rb" with:
      """
      Given /^a step that calls an undefined step$/ do
        step 'this does not exist'
      end

      Given /^a step that calls a step that calls an undefined step$/ do
        step 'a step that calls an undefined step'
      end
      """
    When I run `cucumber --strict -q features/call_undefined_step_from_step_def.feature`
    Then it should fail with exactly:
      """
      Feature: Calling undefined step

        Scenario: Call from feature
          Given this directly called step does not exist
            Undefined step: "this directly called step does not exist" (Cucumber::Undefined)
            features/call_undefined_step_from_step_def.feature:4:in `Given this directly called step does not exist'

        Scenario: Call directly
          Given a step that calls an undefined step
            Undefined nested step: "this does not exist" (Cucumber::UndefinedNestedStep)
            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
            features/call_undefined_step_from_step_def.feature:7:in `Given a step that calls an undefined step'

        Scenario: Call via another
          Given a step that calls a step that calls an undefined step
            Undefined nested step: "this does not exist" (Cucumber::UndefinedNestedStep)
            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
            ./features/step_definitions/steps.rb:6:in `/^a step that calls a step that calls an undefined step$/'
            features/call_undefined_step_from_step_def.feature:10:in `Given a step that calls a step that calls an undefined step'

      Failing Scenarios:
      cucumber features/call_undefined_step_from_step_def.feature:6
      cucumber features/call_undefined_step_from_step_def.feature:9

      3 scenarios (2 failed, 1 undefined)
      3 steps (2 failed, 1 undefined)
      0m0.012s

      """

{'fraction_non_alphanumeric': 0.05875486381322957, 'fraction_numerical': 0.007003891050583658, 'mean_word_length': 2.6747676912080056, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4734496', 'n_tokens_mistral': 1362, 'n_tokens_neox': 1320, 'n_words': 566}