Use case

Temporary email for Playwright and Selenium end-to-end tests

A browser test can fill every field and click every button, but verification emails live outside the browser. A temporary inbox brings them back inside your test.

The shape of an email-aware E2E test

Create a unique address for the test.
Drive the UI to submit the signup form.
Wait for the verification email and extract the code or link.
Feed it back into the browser and assert the signed-in state.

Make the address unique per test

Emailsify addresses follow the pattern word.word123. Any address on the domain works, so tests can mint their own identifiers.

const address = `e2e.${Date.now().toString(36)}${Math.floor(Math.random()*900+100)}@emailsify.com`;

Reading the email

If your suite is driven by an AI agent (for example Claude Code running Playwright through MCP), give it the Emailsify MCP server and let it wait for the code. For plain scripts, open the inbox in a second browser context and read the message from the page.

Avoid flaky waits

Wait for the message, not a fixed sleep.
Use a generous timeout in CI: email delivery varies.
Filter by sender or subject so an older message is never picked up.

Frequently asked questions

Does it work with Cypress too?

Yes. Any tool that can type an address into a form and read a code can use it.

How do I stop one test reading another test's code?

Give every test its own address. The inbox then only ever contains that test's mail.