Stop the Retries in Tests & Reruns of Failing Tests
summary
Argues against automatic reruns and in-test retries as anti-patterns, showing that they hide root causes like network, timing, data, or environment issues and recommends instrumenting failures and doing proper root-cause analysis instead. Advises avoiding thread.sleep in favor of explicit waits, setting environment-specific SLAs (example: 3s production → ~7s test), reducing UI tests in favor of lower-layer checks, preferring explicit scenario tests over generic data providers, and adopting contract-driven testing with Specmatic and visual checks with Applitools rather than retry hacks.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:28Stop the Retries in Tests & Reruns of Failing Test
- 6:26Data dependencies
- 13:40Debug cause of failure
- 14:20Performance issue
- 22:00Code quality
- 22:26Quick feedback
- 23:33Proper Root Cause Analysis
- 24:50Remove external dependencies by using Intelligent Service Virtualisation! Contract
related talks
08mStop the Retries in Tests & Reruns of Failing Test
24mHow to solve intermittent issues, aka Random Failures
57mAdvanced Testing Techniques: Tips from the trenches
44mTesting the untestable - patterns and use cases analysis
45mTesting the untestable PART II – patterns, use cases and practices
42mTesting on Thin Ice: Chipping Away at Test Unpredictability
01h 19mYou Can't Test This? Hammertime!
40mUnselfish Testing