Performing regression testing on applications
After you update to Pega Platform version 8.5.1 or later on the cloned, staging environment, rerun regression testing on your applications. Significant changes from one release to the next might cause instability in your applications. By performing regression testing, you can identify any unexpected changes to application behavior after the update and verify that all your features work as expected.
When you run regression tests, ensure that you do the
following tasks:
- Run all your automated tests.
- Run all your manual test cases and checks.
- Run your performance and other non-functional tests and checks.
- As part of regression testing, run smoke tests to verify that a wide range of
critical features still work correctly and to check if those features are
affected by any changes after the update.To reduce testing cycle times, implement an automated testing pipeline, for example, Pega Scenario Testing for smoke testing and regression testing.
- Run sanity tests. Sanity testing is focused and fast; you check that a change, for example a new feature or bug fix, does not introduce issues after the update. After you verify the change, you then test other functionality that the change might have affected. Use sanity testing to determine the effect of one specific fix or change.
- Using automated smoke test suites to reduce regression testing effort
Use Pega's built-in automated testing capabilities, which include PegaUnit and Pega scenario testing, for optimized and effective regression testing of your Pega applications. By using these testing capabilities, you reduce the time that performing regression testing takes.
Previous topic Validating the completion of update testing Next topic Using automated smoke test suites to reduce regression testing effort