How to Fix Flakiness in Tests | Using Time Machines to Debug #FlakyTest
summary
Shows three concrete time‑travel tools and how they fix real flakes: Cypress timeline lets you hover commands and finds a last() selector clicking the wrong card, fixed by asserting the list length equals 2; Playwright trace‑viewer reveals two clicks hitting the same button so adding assertions that navigation reached Playwright before the next click fixes it; Replay recordings captures network, DOM and component code showing addToCart sends quantity 0, fixed by disabling the button until availability loads. Tools integrate with tests and app code and the fixes work.
AI-written summary · about
chapters (9)
- 0:00Introduction to time travel debugging
- 1:52Flakiness example with Cypress
- 4:20Timing issues in modern apps
- 5:03Playwright trace viewer demo
- 7:30Browser internals and testing
- 8:34Flaky apps and flaky tests
- 9:15Replay IO time machine demo
- 13:08Fixing the root cause of flakiness
- 14:33Summary of time machine tools
related talks
24mFighting Test Flakiness with Time Machines
29mBlink and you’ll miss it: Stories from discovering most annoying bugs and test flakes
46mFilip Hric: How to Write a Flaky Test Description: How (not) to Write a Flaky Test
46mBlink and You’ll Miss It: Stories From Discovering Most Annoying Bugs and Test Flakes
15mHow to (not) write a flaky test
32mHow to write a flaky test
22mTest Confidence: Types of Flake & How to Remediate
32mDo Not Fight Your Testing Tools