Select email

Select a specific email in your automated tests

When you’re testing email-driven workflows—such as account confirmation, password resets, or transactional messages—you often need to choose a specific email from a mailbox to interact with. The Select Email step lets your test pick a particular message from the DoesQA inbox so you can continue the flow with confidence.

This makes email testing far more precise than simply checking whether an email exists. You are selecting specific content to act on, enabling downstream interactions such as clicking verification links or extracting codes.

Why selecting email matters

Automated email testing is a powerful way to validate real user journeys that involve:

• Account verification

• Password resets

• Magic link login

• Order confirmations

• Support responses

• Notification emails

Every one of these flows depends not just on an email arriving, but on the correct message being chosen and used at the right moment.

The Select Email step lets your automation:

• Pick a message based on subject text

• Choose the right email chronologically

• Target an email containing specific content

• Prepare the message for further assertions or interactions

This ensures your test never clicks the wrong link or processes the wrong message.

How it works in context

In a typical email workflow you might:

1. Trigger a user action that causes an email to be sent

2. Wait for the email to arrive

3. Use Select Email to pick the right message

4. Extract information such as links, codes, or confirmation tokens

5. Continue the automated flow with that data

This removes guesswork and makes tests far more deterministic, especially in cases where multiple emails may arrive during a run.

Match emails based on content

The Select Email step is flexible in how it identifies the correct message. You can target an email by:

• Exact subject match

• Partial subject text

• Contains specific keywords

• Chronological position (first, most recent, etc.)

This allows tests to adapt to different content patterns without breaking.

For example, if your app sends both a welcome email and a separate notification, you can precisely select the one you need for the next step.

Use the selected email in subsequent steps

Once an email is selected, you can continue your test by:

• Clicking links inside the message

• Extracting codes or tokens

• Verifying content

• Combining email data with form inputs

This enables seamless end-to-end automation of flows that depend on email confirmation.

For instance, after selecting a confirmation email you can:

• Open the link to complete account setup

• Use a code inside the message to validate MFA

• Confirm the email contents match expected text

All without manual intervention.

Better coverage for real journeys

Many teams treat email testing as a separate process. But real users move from email back to the application.

By selecting the correct email as part of your test flow, you can ensure:

• The correct email was sent

• The expected content is present

• The correct links or codes are actionable

• The user experience is validated end to end

This gives you higher confidence that critical user paths work exactly how they should in production.

Selecting emails precisely is essential when email is part of your core user journey. With this step, you automate it reliably, clearly, and in context.