Stop mocking email in E

Short summary

Mocking email in tests creates false confidence—mocks never fail, bounce, or go to spam, but real emails do. Critical user flows like signup and verification remain untested when mocks are used, masking production incidents. While mocks are appropriate for unit tests, E2E tests should use real inboxes, and disposable email APIs like ZeroDrop now make this straightforward.

• •Mocked email tests pass when real systems fail—SMTP issues, spam filters, template breaks all go undetected
• •Signup, verification, and password reset flows are first things users do and first things that break
• •Disposable email APIs eliminate infrastructure pain that historically justified mocking in E2E tests

Generated with AI, which can make mistakes.