Fighting Test Flakiness with Time Machines
summary
Compares Cypress timeline, Playwright trace‑viewer and Replay recordings by showing real flakiness: a test clicks while quantity is zero and an API check hasn’t returned, causing two failed runs then one pass. Shows a recording that jumps to code, rewinds with debugger/breakpoints, prints variable values and proves the bug; Replay’s time‑travel debugger is built and used to reproduce, inspect network snapshots and fix tests without guessing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:00Learning from past tests
- 6:34Time machines in automation
- 11:09Flakiness beyond automation
- 12:52Replay.io solution
- 14:37Live Replay.io demo
- 22:45Fixing flakiness with recordings
related talks
15mHow to Fix Flakiness in Tests | Using Time Machines to Debug #FlakyTest
29mBlink and you’ll miss it: Stories from discovering most annoying bugs and test flakes
17mBe Kind Rewind with Test Replay
46mBlink and You’ll Miss It: Stories From Discovering Most Annoying Bugs and Test Flakes
32mDo Not Fight Your Testing Tools
46mFilip Hric: How to Write a Flaky Test Description: How (not) to Write a Flaky Test
51mAdvanced Playwright Techniques for Flawless Testing
15mHow to (not) write a flaky test