Stop the Retries in Tests & Reruns of Failing Test
summary
Asserts that automatic retries and reruns hide real failures and create brittle suites by masking network and environment flakes, timing/race conditions, data dependencies and poor locator or wait logic. Recommends shrinking UI tests toward a test pyramid, doing CI parallelization, test data strategy and root‑cause analysis, upskilling and choosing fit‑for‑purpose tools. Proposes intelligent service virtualization (mentions the open‑source Contract work) and replacing brittle checks with visual assertions to cut assertion code and surface true UX regressions.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:19TAK Environment issues Network issues Timing issues (page loading)
- 1:44ork issues ng issues (page loading) Srmance issues Intermittent issues in Product (example: race conditions) Deployment of components happening while test is running No control on downstream dependencies
- 5:12Client-side API / Server side
- 6:01Build Quality in Quality is a team responsibility Choose Practices that help
- 6:32Parallel execution Intelligent Test Data strategy
