One inbox per test
Create separate email addresses for test users and parallel runs. Match each message to the inbox your test created.
A MailHog alternative for local tests and CI runs.
Give your email tests real inboxes without maintaining a shared capture server. MailSlurp connects received messages, APIs and end-to-end checks.
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.
Keep the email check consistent across environments.
Start with the received message
Create an inbox for the test and direct the application message to that address. The same inbox API can retrieve the received email whether the test ran on a developer machine or in CI.
Verify the same notification in each environment
When evaluating a MailHog or Mailpit alternative, check your SMTP settings and test-recipient configuration first. Run a representative notification, inspect its final content and follow its link before migrating the rest of the suite.
Questions before you switch?
How do I prevent email collisions in CI?
Create a separate MailSlurp inbox for each job or test user and pass that address into the application scenario. Wait for the expected message in that inbox and keep its identifier with the test output. Parallel jobs can then complete their own reset links or verification codes without reading another run's message. See a parallel password-reset example.
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.