The Hardest Browser Tests Live Outside the Browser

Short summary

The article argues that the hardest part of end-to-end browser testing isn't the browser automation—it's orchestrating external events like email/SMS verification, file downloads, and cross-channel flows. It provides practical guidance on correlation over retrieval for verification codes, testing downloaded files beyond the click, and layering tests from API-level to full delivery. The key insight is that test stack choices should be driven by orchestration complexity, not recorder quality or selector syntax.

• •E2E test cost is driven by orchestration of external events, not browser automation
• •Use correlation (unique aliases, transaction IDs) instead of 'fetch newest email' for verification tests
• •Layer tests: API checks for token rules, a smaller set for full delivery, and always validate downloaded file content

Generated with AI, which can make mistakes.