QA Foundations

Test debt

Also known as: test automation debt

Test debt is the accumulated cost of neglected test suites — flaky tests, brittle selectors, poor coverage, and slow runs — that makes testing progressively harder and less trustworthy over time.

Like technical debt, test debt compounds. Flaky tests that are never fixed, end-to-end tests bolted on without structure, and assertions that no longer reflect the product all accrue interest: more maintenance, slower CI, and less trust in results. Left alone, teams spend the majority of their testing effort on upkeep rather than new coverage.

Paying it down means deleting or fixing flaky tests, rebalancing toward the test pyramid, speeding up feedback, and making failures legible — the same practices that improve reliability and velocity overall.

Accumulated cost of neglected suites: flaky tests, brittle selectors, weak coverage, slow runs.
Compounds like technical debt — more upkeep, slower CI, less trust in results.
Paid down by deleting/fixing flaky tests, rebalancing to the test pyramid, and speeding feedback.

Frequently asked

How do you pay down test debt?

Quarantine, then delete or fix, the flakiest tests; rebalance toward the test pyramid (more fast unit tests, fewer brittle end-to-end ones); speed up the slowest tests; and make failures legible. The same practices that reduce test debt also improve reliability and velocity.