How to make cheap e2e tests
summary
Claims that Playwright plus a local orchestration utility cuts e2e friction by running 100 dynamically generated tests in about 1.5 minutes instead of an 18 minute deploy cycle, and that unstable remote backends (15 minutes deploy plus 3 minutes of flakiness) are the real bottleneck. Describes building a PO server utility to mock GraphQL schemas, using web config to start processes, CI installs Playwright and archives reports, and recommends isolated integration tests for microfrontend setups.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:12Broken e2e tests
- 2:39Unit to e2e needs
- 3:46Scaling e2e challenges
- 4:49Isolated integration testing
- 6:18Speed comparison: e2e vs isolated integration tests
- 7:00Playwright isolated setup
- 8:27Micro frontends testing
- 9:32Reusing tests
- 9:53Testing strategy
- 10:35Testing costs
related talks
21mAt the top of the pyramid: Playwright testing at scale
29mPlaying your tests wright
48mHow We Tried to Introduce E2E Tests and Why It Failed
18mAt the top of the pyramid: Playwright testing at scale
40mMonitoring as Code: E2E Testing in Production with Playwright
43mReal World Playwright Case Studies That Will Change Your Perspective!
21mEveryone Can Easily Write Tests
49mReal World Lessons from Scaling Test Automation