SECAI Core · phase 15 of 15
Regression testing
The process of testing an application after changes are made to see if these changes have triggered problems in older areas of code.
The Explain card
- Plain English
- Regression testing re-runs existing tests after a change to confirm the change has not broken things that used to work elsewhere in the system.
- Example
- After updating a safety filter, a team re-runs their suite of previously blocked jailbreak prompts and finds three that now slip through, catching the regression before deployment.
- Why it matters
- Fixes in AI systems often have side effects: tightening one filter loosens another, a new model version forgets old refusals. Regression tests are how defenders make sure yesterday's wins stay won.
- Hook
- Make sure the new patch did not reopen an old wound.
Where it sits in the deck
Phase 15: MLOps, Continuous Delivery, and Operational Resilience
Close the loop — operational practices, drift management, and delivery discipline that keep deployed AI systems healthy, current, and continuously improving.
