A Good Flaky Test Is an Unrun Flaky Test
summary
Presentation argues that a good flaky test is one that never runs; it discusses flaky tests in automated testing and techniques to prevent, detect, and quarantine them so they don’t execute in CI. The focus is on practical test hygiene and tooling strategies to keep flaky tests out of the test run rather than trying to stabilize every flaky case.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:29About Raic and automation
- 3:17What are flaky tests
- 8:22Why flaky tests are dangerous
- 10:29Existing approaches
- 12:16Test quarantine idea
- 14:00Quarantine mechanics
- 17:50Running isolated tests
- 21:48Adding to quarantine
- 23:59Detecting flaky tests
- 27:32Quarantine criteria
- 29:21Automating test quarantine
- 32:12Quarantine results
- 35:42Summary
- 36:39Q&A
related talks
42mFlaky tests are a pain
01h 09mFlaky Tests: The Method
15mHow to (not) write a flaky test
40mFinding Flakiness: The Real Reasons Your Tests Aren't Reliable
46mFilip Hric: How to Write a Flaky Test Description: How (not) to Write a Flaky Test
22mTest Confidence: Types of Flake & How to Remediate
28mThe State of Art in Tackling Flaky Tests
31mCI and the Great Flakiness Adventure