One inbox per test
Create separate email addresses for test users and parallel runs. Match each message to the inbox your test created.
A Mailcatcher alternative that tests the delivered email.
Bring your email checks into real, controlled inboxes. MailSlurp gives your team hosted message inspection and repeatable end-to-end tests.
Trusted by teams at
Follow the message all the way to the inbox.
Trigger a signup, password reset or order confirmation in your app. Receive the actual email in MailSlurp and inspect its subject, sender, body, headers and attachments. A successful API response is only the start of the journey.
Explore end-to-end email testing
Wait for the right message
Use wait APIs and message filters to retrieve the expected email within a defined timeout.
Finish the customer journey
Extract the verification code or reset link, return to your app and check the next screen.
Email and SMS. One complete test.
A customer can sign up by email and verify a phone number in the same session. Give your test an inbox and a phone number, receive both messages and check the code before continuing.
Use MailSlurp with Playwright, Cypress, Selenium or your existing test runner. Keep the received message available when a failed run needs investigation.
Explore SMS testing
Make sure the email works for the person opening it.
An automated assertion can confirm the link exists. Device previews show how the delivered email looks, and Email Audit checks for broken links, missing images and content issues before a release.
See real-client previews
How to run your first end-to-end check
Create a test identity
Create an inbox for the test user, then enter its address in your application's signup or password-reset form. Use a separate inbox for each parallel run.
Receive and inspect the message
Wait for the expected email. Check the recipient, subject and content, then extract the code or URL your customer needs. The email testing guide covers the workflow.
Complete the action and repeat
Submit the code or open the link in your test session. Assert the application outcome, retain useful failure evidence and add the check to your normal test suite. Start with our Playwright email testing guide.
Take the check from local development into shared QA.
Start with the received message
Start with a test address that your application can deliver to through its normal sending path. Receive the email in MailSlurp and inspect the final headers, body and attachments.
Check local SMTP settings and CI recipients
When moving a Mailcatcher workflow, review your development SMTP configuration and test-recipient handling. Try the same signup message in local development and CI, then complete its verification link in the application.
Questions before you switch?
How do I move a local MailCatcher check into a shared test?
Give the scenario a controlled MailSlurp inbox and configure your test application to use the intended sending path. Trigger the email, wait for it in that inbox and verify the body, attachment or link. Use test recipient addresses throughout the evaluation, then run the same scenario in CI with its own inbox and timeout. Build an automated email check.
Can I use my existing test runner?
Yes. Use MailSlurp APIs or SDKs to create inboxes, wait for messages and retrieve codes or links from Playwright, Cypress, Selenium or another test runner. Complete the action in your application and assert the final state.
Can I test SMS and the appearance of an email too?
Yes. Add phone numbers and SMS checks for verification flows, and use device previews to inspect the delivered email on supported clients. Current plans show the allowances for each capability.
Make the next release a checked one.
Create a test inbox and complete your first email journey.