Write Fewer Tests! From Automation to Autogeneration
summary
Argues that exhaustive tests are auto-generated from a state-machine model so tests are created and regenerated when the model changes, not handwritten. Demonstrates a feedback app where the model yields 12 paths, a missing submit button causes a failing path reproduction, and a tic‑tac‑toe model enumerates every winning combination. Uses React Testing Library for DOM assertions and drives real browsers with Puppeteer, orchestrated by a new harness called X state test that emits concrete test cases.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:46Importance of Tests
- 6:14Model-Based Testing
- 10:30Generate Abstract Tests
- 13:15Finite State Machine
- 15:38Generate Test Plans
- 16:12Feedback App
- 19:54Time Travel Debugging
- 20:56Tic-Tac-Toe Game
related talks
45mWrite fewer tests! Model-based testing in React
31mModel-Based E2E Testing With State Machines
25mMastering UIs with Finite State Machines
29mReactive State Machines and Statecharts
26mThe missing piece of testing
27mAutomated Testing for the Modern Web
47mREACTive Automation: How to Avoid Shooting Yourself in the Foot
38mState of the Art Web User Interfaces with State Machines
