Why Your CI Email Tests Are Flaky (And How to Fix Them)

TL;DR : If your Playwright/Cypress/Pytest tests involving email keep failing intermittently in CI, the cause is almost always shared inbox state. The fix is per-test inbox isolation, not longer timeouts. The Symptom Your test suite has a test that looks reasonable: ✓ user can register (3.2s) ✗ user receives welcome email (timeout after 30s) ✓ user receives welcome email (2.1s) ← same test, re-run, now passes The test passes locally. It fails in CI. It passes again on retry. Your team has learned to just re-run the pipeline and move on. The underlying problem is never fixed. This is not an infrastructure problem. It's not "CI is slower than local." It's a state isolation problem. The Root Cause When email-dependent tests share an inbox, several things go wrong. Race conditions in parallel runs CI pipelines run tests concurrently. If you're using -n 4 in Pytest or --workers=4 in Playwright, four tests may be signing up simultaneously — all using the same test@yourcompany.com address. Wor