There is a category of test that feels productive, passes consistently, and catches absolutely...
There is a category of test that feels productive, passes consistently, and catches absolutely nothing. It lives in most codebases. It gets written during sprints, committed without question, and reviewed without comment. Nobody talks about it because it looks fine.
It is the mocked email test.
What it looks like
jest.mock('../lib/email', () => ({
sendVerificationEmail: jest.fn().mockResolvedValue({ id: 'mock-id' })
Every QA engineer has written a test like this at some point: test('user receives verification...
Email is one of those things that's genuinely hard to test. It goes out through an SMTP server, lands...
Email is the test surface nobody wants to own. It's asynchronous, depends on external providers, has...
A PR touches your password-reset template. Every unit test passes, the snapshot tests pass, CI goes...
The single most flake-prone test in any E2E suite is "user signs up, verifies via emailed OTP,...
A backend-focused pattern for testing REST API verification emails with isolated inboxes, cleaner assertions, and less…
