<commit_before>Feature: Step definition text snippets

  As a user of Cucumber, I want to get sensible text snippets, so that
  I can write my tests more easily.

Scenario: Suggestions for undefined steps with and without arguments

  Given a standard Cucumber project directory structure
  Given the standard clucumber setup
  Given a file named "features/undefined.feature" with:
  """
  Feature: Undefined steps

    Scenario: Three undefined steps
    Given this step is undefined
    When I use a step with "one arg"
    Then the step "with two args" should "suggest two args"
  """
  When I run "cucumber -f progress"
  Then it should pass with exactly:
  """
  UUU

  1 scenario (1 undefined)
  3 steps (3 undefined)
  
  You can implement step definitions for undefined steps with these snippets:
  
  Given /^this step is undefined$/ do
    pending # express the regexp above with the code you wish you had
  end
  (Given* #?{^this step is undefined$} ()
    ;; express the regexp above with the code you wish you had
    (pending))
  
  When /^I use a step with "([^\"]*)"$/ do |arg1|
    pending # express the regexp above with the code you wish you had
  end
  (When* #?{^I use a step with "([^"]*)"$} (group-0)
    ;; express the regexp above with the code you wish you had
    (pending))
  
  Then /^the step "([^\"]*)" should "([^\"]*)"$/ do |arg1, arg2|
    pending # express the regexp above with the code you wish you had
  end
  (Then* #?{^the step "([^"]*)" should "([^"]*)"$} (group-0 group-1)
    ;; express the regexp above with the code you wish you had
    (pending))
  
  <commit_msg>Fix cucumber snippets for cuke 0.8.3.<commit_after>Feature: Step definition text snippets

  As a user of Cucumber, I want to get sensible text snippets, so that
  I can write my tests more easily.

Scenario: Suggestions for undefined steps with and without arguments

  Given a standard Cucumber project directory structure
  Given the standard clucumber setup
  Given a file named "features/undefined.feature" with:
  """
  Feature: Undefined steps

    Scenario: Three undefined steps
    Given this step is undefined
    When I use a step with "one arg"
    Then the step "with two args" should "suggest two args"
  """
  When I run "cucumber -f progress"
  Then it should pass with exactly:
  """
  UUU

  1 scenario (1 undefined)
  3 steps (3 undefined)
  
  You can implement step definitions for undefined steps with these snippets:
  
  Given /^this step is undefined$/ do
    pending # express the regexp above with the code you wish you had
  end
  (Given* #?{^this step is undefined$} ()
    ;; express the regexp above with the code you wish you had
    (pending))
  
  When /^I use a step with "([^"]*)"$/ do |arg1|
    pending # express the regexp above with the code you wish you had
  end
  (When* #?{^I use a step with "([^"]*)"$} (group-0)
    ;; express the regexp above with the code you wish you had
    (pending))
  
  Then /^the step "([^"]*)" should "([^"]*)"$/ do |arg1, arg2|
    pending # express the regexp above with the code you wish you had
  end
  (Then* #?{^the step "([^"]*)" should "([^"]*)"$} (group-0 group-1)
    ;; express the regexp above with the code you wish you had
    (pending))
  
  
{'fraction_non_alphanumeric': 0.10120333230484418, 'fraction_numerical': 0.007096575131132366, 'mean_word_length': 3.199481865284974, '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': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1338329', 'n_tokens_mistral': 1002, 'n_tokens_neox': 957, 'n_words': 463}