Using third party testing tools with your Pega application
|Description||An overview of the testing tools that can be used with your Pega application|
|Version as of||8.5|
Pega provides various built-in testing tools that can be leveraged to test our Pega applications. However, Pega applications can also be tested with various third-party testing tools. Pega does not have any specific preferred tools or vendors, but below are some suggestions based on how Customers have approached their testing needs.
For functional testing of your Pega applications, consider the following approaches:
For unit testing Pega Applications, Pega Units are the best approach.
Pega provides a Test ID attribute for unique identification of UI elements that enables you to write dependable automated tests against any Pega application. To perform UI-based functional tests and end-to-end scenario tests, and to verify that end-to-end cases work as expected, Pega provides the Pega Scenario testing built-in tool. You can also use third party Selenium and Cucumber tools to automate those tests. Pega provides a Selenium-based UI test framework and sample UI tests in its Selenium Starter Kit, which you can use to build up a test automation suite for your Pega application. These test frameworks are built with maintenance and best practices in mind.
To automate mobile-specific tests for a Pega Mobile Application, you can use the Expresso Framework for Android UI. For more information, see the Mobile testing with Espresso framework Pega Collaboration Centre article.
API or Services Testing
To test your APIs or Services, you can use REST-assured, Citrus, POSTMAN or SoapUI tools. These tests can even be automated using the Karate Cucumber Framework as preferable.
Pega provides accessibility features to individual access groups. The accessibility features are available to access groups with the accessibility ruleset (PegaWAI ruleset) provisioned. Other than Pega Accessibility Inspector tool, for testing accessibility compliance, tools such as aXe-core from Deque Systems, pa11y, or tenon.io can be inserted into your build process. Testing the UI with a popular screen reader combo such as JAWS [latest] and Internet Explorer can also be done. Voiceover and iOS is by far the most common combo for testing accessibility on mobile devices.
For testing application performance, tools such as Apache JMeter, BlazeMeter, HP LoadRunner can be helpful. For monitoring the performance in a Production system, Pega Predictive Diagnostic Cloud (PDC) should help. PDC can monitor alerts, exceptions and other metrics that matter from the application perspective. If you would like to monitor other aspects of the environment, such as the app or database server and other parts of the deployment stack, there are many solutions out there such as AppDynamics, DataDog, NewRelic and so on. Depending on your particular deployment setup, for example cloud vs on-prem, as well as other variables, you should be able to decide which one to use.
- Pegaunit Testing
- Selenium Starter Kit
- Mobile Testing
- Demystifying application accessibility and testing
- Understanding accessibility
- Building an accessible UI
- Accessibility Inspector
- Security Checklist
- Security Testing Application
- Pega Rule Security Analyzer
- Performance Testing
- Pega Predictive Diagnostic Cloud