Verify the basics
Check the sender name, sender address, subject line, preheader text, and the expected recipient. A technically delivered message can still be confusing if these basics are wrong.
Test the links
Open important links and confirm they lead to the intended destination. Avoid sending test clicks through live advertising or production tracking when a safer staging environment is available.
Check mobile readability
Read the email on a small screen. Look for oversized tables, tiny text, clipped buttons, long URLs, and layouts that require horizontal scrolling.
Test failure cases
Do not test only the happy path. Check what happens when a verification link expires, a user requests another message, or the original address is no longer available. A clear failure message can be as important as a successful email.
Useful checks for QA
A small checklist can cover address creation, form validation, successful delivery, subject rendering, plain-text fallback, HTML rendering, links, timestamps, expiry and error handling. Repeat the test on a phone because narrow screens often expose layout problems that desktop testing misses.
Record evidence without copying private mail
For bug reports, message IDs, timestamps and test-case names are usually enough. Avoid pasting complete private messages into tickets when a smaller piece of evidence will demonstrate the problem. Good QA protects both the product and the people whose data appears in the test environment.
Pre-send checks
Confirm from name, from address, reply-to, subject length, preheader and whether the template is the production version. Confirm the recipient is a test mailbox, not a real customer. Confirm the environment is staging when that is the intent.
After the message arrives
Open it on a phone and a desktop. Check images, buttons, dark-mode readability if relevant, and every primary link. Confirm the landing page matches the campaign. Confirm the link expires when it should. Confirm a second send does not create a confusing duplicate state in the product.
Evidence without leaking mail
In bug tickets, store message IDs, timestamps, environment names and screenshots of the product, not full copies of other people’s mail. Temporary email makes test identities easy; it does not make it acceptable to paste private content into a public tracker.
Related MailDroply guides
- Related guide — continue with temporary email for testing.
- Related guide — continue with email link safety.
- Related guide — continue with html email security.
Responsible use reminder
Use a temporary email address only for short-lived, low-risk tasks. Do not use MailDroply for banking, account recovery, medical records, government services, passwords or other information you cannot afford to lose. Keep the same address while you wait for a message. If the account matters, switch to a permanent mailbox you control.
Include failure copy
Write down what the product says when a link is old, when mail is delayed, and when the user asks for another send. Those sentences are part of email QA even though they appear in the app, not in the message.