A regression is functionality that used to work but is now broken after a change. It can affect a single unit of work or several previously working behaviors. section 1.8
Regressions are easy to miss when shared code or data changes over time. They often appear near a sprint or release deadline, when a fix for one bug accidentally introduces another. section 1.8
Use runnable tests as a safety net:
- Run tests for earlier features after making a change, rather than assuming they still work. section 1.8
- Make tests accessible so teammates can check whether a change broke code they depend on. section 1.8
- Treat reliable test results as confidence to change unfamiliar or legacy code. section 1.8




