<commit_before>Feature: EmailSpec Example -- Prevent Bots from creating accounts

In order to help alleviate email testing in apps
As an email-spec contributor I want new users of the library
to easily adopt email-spec in their app by following this example

In order to prevent bots from setting up new accounts
As a site manager I want new users
to verify their email address with a confirmation link

Scenario: A new person signs up imperatively 
    Given I am a real person wanting to sign up for an account
    And I am at "/"

    When I fill in "Email" with "<EMAIL>"
    And I fill in "Name" with "<NAME>"
    And I press "Sign up"

    Then "<EMAIL>" should receive 1 email
    And "<EMAIL>" should have 1 email
    And "<EMAIL>" should not receive an email

    When "<EMAIL>" opens the email with subject "Account confirmation"

    Then I should see "confirm" in the email
    And I should see "<NAME>" in the email
    And I should see "Account confirmation" in the subject

    When I follow "confirm" in the email
    Then I should see "Confirm your new account"


Scenario: slightly more declarative, but still mostly imperative
    Given I am a real person wanting to sign up for an account
    And I'm on the signup page

    When I fill in "Email" with "<EMAIL>"
    And I fill in "Name" with "<NAME>"
    And I press "Sign up"

    Then I should receive an email

    When I open the email
    Then I should see "Account confirmation" in the subject

    When I follow "confirm" in the email
    Then I should see "Confirm your new account"


 Scenario: declarative
    Given I am a real person wanting to sign up for an account
    And I'm on the signup page

    When I submit my registration information
    Then I should receive an email with a link to a confirmation page


<commit_msg> add failing feature to show issue with link following in e-mails<commit_after>Feature: EmailSpec Example -- Prevent Bots from creating accounts

In order to help alleviate email testing in apps
As an email-spec contributor I want new users of the library
to easily adopt email-spec in their app by following this example

In order to prevent bots from setting up new accounts
As a site manager I want new users
to verify their email address with a confirmation link

Scenario: A new person signs up imperatively 
    Given I am a real person wanting to sign up for an account
    And I am at "/"

    When I fill in "Email" with "<EMAIL>"
    And I fill in "Name" with "<NAME>"
    And I press "Sign up"

    Then "<EMAIL>" should receive 1 email
    And "<EMAIL>" should have 1 email
    And "<EMAIL>" should not receive an email

    When "<EMAIL>" opens the email with subject "Account confirmation"

    Then I should see "confirm" in the email
    And I should see "<NAME>" in the email
    And I should see "Account confirmation" in the subject

    When I follow "Click here to confirm your account!" in the email
    Then I should see "Confirm your new account"


Scenario: slightly more declarative, but still mostly imperative
    Given I am a real person wanting to sign up for an account
    And I'm on the signup page

    When I fill in "Email" with "<EMAIL>"
    And I fill in "Name" with "<NAME>"
    And I press "Sign up"

    Then I should receive an email

    When I open the email
    Then I should see "Account confirmation" in the subject

    When I follow "confirm" in the email
    Then I should see "Confirm your new account"


 Scenario: declarative
    Given I am a real person wanting to sign up for an account
    And I'm on the signup page

    When I submit my registration information
    Then I should receive an email with a link to a confirmation page




{'fraction_non_alphanumeric': 0.044264507422402156, 'fraction_numerical': 0.0010796221322537112, 'mean_word_length': 3.140782122905028, 'pattern_counts': {'":': 0, '<': 21, '<?xml version=': 0, '>': 21, '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': '967616', 'n_tokens_mistral': 974, 'n_tokens_neox': 924, 'n_words': 612}