Regression testing means repeatedly testing existing functionality after code changes to check that it still works as expected. Changes made to fix bugs or add features can break capabilities that worked before. Running tests after changes helps catch problems before code reaches production. section 15.1
Figure 15.1 A CI tool, such as Jenkins, runs the tests every time a developer changes the app. If any of the tests fail, the CI tool notifies the developers to check which capability doesn’t work as expected and correct the problem.

A CI tool can run tests whenever developers change the app and notify them when a test fails. section 15.1


