Rewrite Vs Refactor
summary
Provides concrete rules for choosing rewrite versus refactor for test automation: keep refactoring when tests are >70% coverage and most failures are isolated units, apply targeted refactors for modules with cyclomatic complexity under 15, and fix flaky tests in CI; opt to rewrite when core logic spans 3+ repositories duplicated, when pipelines take build time >10m or when >30% of tests are consistently unreliable. Gives examples of incremental refactors that cut execution time and one full rewrite where fragmentation prevented safe change.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:46Test automation focus
- 10:10Complexity in testing
- 20:10Learning from mistakes
- 30:31Automation pitfalls
- 40:12Automated test design
- 45:18Q&A and summary
