Playing your tests wright
summary
Argues that end-to-end testing is now the practical default, shows Playwright tooling that actually reduces pain: playright with auto-waiting and retrying assertions, a codegen recorder that generates interactions (but not asserts), a locator picker and UI mode with watch and trace debugging. Gives numbers: ~200–292 tests taking ~18 minutes, cut by sharding across 4 workers and merging reports. Builds working demos and debugs a failing locator live so the workflow proves out.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:16Who writes end-to-end tests
- 3:02Playwright key features
- 6:33Playwright integrations and CI/CD
- 6:55Best practices for tests
- 8:21Updating Playwright and locators
- 11:33Demo: Playwright Codegen
- 14:45Exploring Playwright UI mode
- 17:55Debugging with DOM snapshots
- 21:10Scaling tests with sharding
- 23:19Playwright community and resources
- 25:23Call to action
- 28:15Q&A
related talks
27mPlaying your tests wright
14mAdvanced Playwright Techniques for flawless testing
24mPlaying your tests wright
21mEveryone Can Easily Write Tests
12mPlay It Right With Playwright
35mState of end-to-end testing for modern web applications
51mAdvanced Playwright Techniques for Flawless Testing
18mAt the top of the pyramid: Playwright testing at scale