A PR touches your password-reset template. Every unit test passes, the snapshot tests pass, CI goes green, and the deploy ships a reset email whose link 404s — because nothing in the pipeline ever received an actual email. If your product sends mail that users must act on, the only test that counts is one where a real message lands in a real inbox and an assertion reads it.
The blocker has always been the inbox. Shared Gmail catch-alls need OAuth on the test runner, forwarding rules, and label gymnastics to scope per-PR runs — and two CI workers reading the same inbox at the same moment is the single biggest source of flakiness in email-dependent E2E tests. Here's the setup that removes the shared inbox entirely, based on the E2E email testing recipe.
One wildcard inbox, infinite addresses
One-time setup with the CLI:
nylas inbound create e2e
