Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Test automation

An effective automation test suite for your Pega Platform™ application ensures that the features and changes you deliver to your customers are high quality and do not introduce regressions.

At a high level, this is the recommended test automation strategy for testing your Pega Platform applications:

  • Create your automation test suite based on industry best practices for test automation.
  • Build up your automation test suite by using Pega Platform features.
  • Run the right set of tests at different stages.
  • Test early and test often.

LSA should focus on minimal three level of testing Pega applications, they are  

  1. Unit Testing
  2. Functional Testing
  3. UI Testing
 

Unit tests

Use unit tests for most of your testing. Unit testing looks at the smallest functionality units and is the least expensive to run. In an application, the smallest unit is the rule. You can run unit tests on rules as you develop them by using the PegaUnit test framework. For more information, see PegaUnit testing.

UI-based functional and scenario tests

Use UI-based functional tests and end-to-end scenario tests to verify that end-to-end cases work as expected. These tests are the most expensive to run. Pega Platform supports automated testing for these types of tests through the TestID property in user interface rules. For more information, see Tools for testing the UI.

You can use the TestID property to identify a user interface element uniquely, you can write dependable automated UI-based tests for any Pega Platform application.

API-based functional tests

Perform API-based testing to verify that the integration of underlying components works as expected without going through the user interface. These tests are helpful when the UI changes frequently. You can validate case management workflows through the service API layer using the Pega API in your Pega Platform application. Similarly, you can perform API-based testing on any functionality that is exposed through REST and SOAP APIs. For more information on the Pega API, see Integrating with APIs and services.

Automation test suite

Use Pega Platform features and industry test solutions, such as JUnit, RSpec, and SoapUI, to build your test automation suite. When you create your automation test suite, run it on your pipeline. During your continuous integration stage, the best practice is to run your unit tests, guardrail compliance, and critical integration tests. These tests ensure that you receive sufficient coverage, quick feedback, and fewer disruptions from test failures that you cannot reproduce. A best practice is to run all your remaining automation tests during the continuous delivery stage to guarantee that your application is ready to be released. Such tests include acceptance tests, full regression tests, and non-functional tests such as performance and security tests.

You receive the following benefits by running the appropriate tests at each stage of development:

  • Timely feedback
  • Effective use of test resources
  • Reinforcement of testing best practices

Check your knowledge with the following interaction: 


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice