Why it matters
Regression testing reruns suites after changes to catch new failures. Policy edits, embedding upgrades, and prompt changes all break previously working answers.
How it works
Maintain versioned test suites in CI. Run on knowledge releases, model upgrades, and config changes. Compare diffs and block on failures.
Example
Nintendo regression reruns fifty refund tests after every Help Center deploy, catching a broken citation link before production promotion.
Common mistakes
- 1Tests run manually when someone remembers
- 2Suites never updated after bug fixes
- 3Flaky tests disabled permanently
Test the answer before your customer does.
Run answer tests and evaluations against your governed knowledge before you ship.
See answer evaluations