Open your email inbox inside an automated flow
Email is a critical part of many modern user journeys. Whether your application sends registration confirmations, password reset links, order receipts, or notification messages, testing email behaviour ensures that users can complete real end-to-end tasks.
The Open Inbox step allows your test to access and open the DoesQA-provided email inbox directly within a flow. This makes email-driven interactions a first-class part of your automation rather than an external, manual afterthought.
Bring real email interactions into your automation
Many testing frameworks ignore email flows or require separate tooling just to check whether messages arrive. This can leave gaps in coverage and force teams to trust that email functionality works.
With Open Inbox, you can:
Display recent messages in the inbox
Interact with specific emails
Continue the journey from email to application
Assert on email content
Extract links, codes, or tokens
This allows automation to mirror how real users interact with email notifications.
A natural step in end-to-end testing
Email is often part of important user workflows:
Account verification
Password resets
Notification alerts
Order confirmations
Subscription notices
By opening the inbox during the test, you can confirm that:
An email was sent
It arrived in a timely manner
The contents are correct
Links and actions inside it work as expected
This turns email testing from a silent check into an active part of your test coverage.
Works with subsequent email steps
Opening the inbox is usually the first action in an email-driven sequence.
After this step you can:
Select Email — pick the message you need
Check Text — validate subject or content
Extract values — get links or codes
Continue the automation into the app
Because everything happens in one flow, you get full coverage from UI action to email result and back again.
Available for account and test-level inboxes
DoesQA provides two types of inbox contexts:
Account Email Inbox — persistent across runs
Test Case Email Inbox — unique per run
This gives you flexibility to choose the right scope for your test.
For example:
Use test-level inboxes for fresh, isolated email checks
Use account-level inboxes when debugging or building tests
Opening the inbox gives your test a clear starting point for interacting with messages.
Validate real journeys reliably
Because this step is part of the DoesQA flow model, you get consistency across runs:
No need to switch tools
No need to check external inboxes manually
No guesswork about message arrival
No fragile timing hacks
Email testing becomes deterministic and repeatable. You’re not just checking functionality — you’re validating the full user experience from action to message and back again.