55 / 66 · 20 Agile & Scrum · Managing Test Technical Debt← prev⊞ allnext →☰ Read as one page
8.6Paying Down Test Debt: Strategies
The Boy Scout Rule
"Leave the code better than you found it." Every time you touch a test file, make one small improvement:
- Fix a test name to be more descriptive
- Replace a hardcoded value with a constant
- Remove a commented-out test
- Add a missing assertion
Dedicated Debt Sprints
Every 4-6 sprints, dedicate a full sprint to test infrastructure improvement:
- Refactor page objects
- Upgrade test framework dependencies
- Rewrite the slowest tests
- Document the test architecture for new team members
Debt Prevention
The cheapest debt is the debt you never take on:
- Code review test PRs: Catch copy-paste, hardcoded values, and missing cleanup before they merge
- Enforce standards: Lint rules for test code, required assertions, naming conventions
- Monitor trends: If flake rate is rising, investigate immediately, not next month
- Kill dead tests: If a test has been
test.skipfor 3 months, delete it