testmail.app

Stop wiring throwaway inboxes by hand. Spin up test mailboxes on demand, hook them into your tests, and assert on real messages the same way you verify API responses. With testmail.app, you generate unique addresses per run or per spec using namespaces and tags, send your app’s emails to those addresses, then fetch and inspect the results through simple JSON or GraphQL calls. Typical flow: create a namespace, store an API key in your secrets manager, send an email in your test step, query for the latest message with filters (subject, to, tags), and validate the subject, headers, text/HTML parts, links, and attachments. Use live queries to wait for a message instead of polling, and keep runs fast with pagination and wildcard search when processing multiple notifications.

In continuous delivery, treat inboxes like ephemeral test data. Provision a namespace per branch or pipeline and tag each test for isolation (e.g., signup, reset, invoice). Parallel jobs won’t collide because every address is unique. For flows that send OTPs, magic links, or confirmation emails, use a wait-until API query to capture the message as soon as it lands, extract the token or URL, and continue the scenario. Validate spam characteristics before you ship by running spam checks and asserting against thresholds. When your app sends files, pull attachments, verify filenames and MIME types, and compare checksum or size to ensure the right payload went out. more