Verify email

This step allows to receive an email on Heal's inbox, read it and use it to verify the email. It's most frequently used in testing signup flows, where the story needs to receive a confirmation email with a code or a link, and use it to verify the email.

Each run has a unique email address

At each run (or at each run attempt if a run is retried), Heal creates a unique inbox that the story can read from. The address associated with this inbox is unique and is available in the email variable. Because that address is only ever used by a single run atempt, there's no risk of collision between emails received at the same time. This allows to run many stories using the verify email step in parallel, if needed.

Signup method

That step supports several options:

• Confirmation code - get code from email and submit: heal will read the email, parse the confirmation code, type it in the field and submit.
• Confirmation code - get code from email and save in variable: heal will read the email, parse the confirmation code, and store it in a variable. Use this option if you need more control over what the agent will do.
• Confirmation link: heal will read the email, look for a verification magic link and open it.

Example

• Type text {{email}} on the email field
• Left click on "Signup now"
• Verify email with Confirmation code - get code from email and save in variable and store code in token
• Type text {{token}} on the email verification code field
• Left click on the submit button
• AI assert Check that you see a 'Welcome to your new account' page

warning

Make sure you send only one email per story, to avoid collisions. Stories sending more than one email to {{email}} could be be unstable. You can run any amount of stories in parallel because each story has a unique email address.