Unit testing support for more rule types
Valid from Pega Version 8.3
You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.
- Collection
- Declare expression
- Map value
- Report definition
For more information about unit testing rules, see Pega unit test cases.
Upgrade impact
With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.
View application quality metrics by data type
Valid from Pega Version 8.3
You can now view application quality metrics by data type on the Application Quality landing page. The new Data Types tab displays metrics for data types grouped by data objects, which enables you to more quickly understand the overall coverage of the application's integrations and interfaces.
For more information about data type metrics, see Application Quality landing page.
Scenario tests are reusable
Valid from Pega Version 8.3
Existing scenario tests are now reusable in different business scenarios. Before Pega 8.3, you had to create a new test every time a user interface or process flow changed significantly. Now, scenario tests are editable to help you maintain the test stack more effectively.
For more information, see Updating scenario tests.
Improvements for automated scenario testing
Valid from Pega Version 8.3
Test automation authors can group related scenario tests into suites. The scenario test suites can be run manually from the Scenario Testing landing page as part of purpose-specific tests such as smoke tests, regression tests, and outcome-based tests. Additionally, automation authors or release managers who monitor tests for an application can disable or quarantine unstable scenario tests so that they do not run.
For more information about creating and managing test suites for scenario testing, see Creating test suites for scenario testing.
Test coverage support for more rule types
Valid from Pega Version 8.3
Test coverage has been expanded to include the following rule types. Test coverage support for these rule types enables developers to more accurately measure the effectiveness of their tests.
- Collection
- Declare trigger
- Map value
- Navigation
- Report definition
- Scorecard
For more information about test coverage, see Test coverage.
Upgrade impact
The new rule types may impact the test coverage metrics for your applications. Due to the increased number of supported rules, the reported test coverage percentage will decrease.
What steps are required to update the application to be compatible with this change?
Run your coverage reports after upgrading to see the latest metrics.
Enhanced reliability and stability of scenario tests
Valid from Pega Version 8.5
Several enhancements have been made to scenario tests to increase their stability and reliability. With enhanced improvements, you can now:
- Delay the execution of a step within a scenario test to add latency to a web browser and actions on a web page. This prevents tests from failing when a dynamic web page does not load all page element at once, but the test finds page elements that are immediately rendered.
- Automatically rerun failed scenario tests, which might fail because there are temporal stability issues on the environment or because the application UI is slowly renders.
- View the run history of scenario tests so that you can analyze the history of a test over time.
For more information, see the following:
- Delay the execution of a step within a test and rerun failed scenario tests for enhanced scenario test stability (8.5)
- Changing application quality metrics
- Automatically rerunning failed scenario tests
- Creating scenario tests
Scenario tests now honor application stack settings
Valid from Pega Version 8.5
The application stack defined on the Application Quality Settings page of Dev Studio now serves as a foundation for creating, viewing, and running scenario tests.
Dev Studio will now:
- Display scenario tests based on the application stack settings on the Dev Studio landing page.
- Store scenario tests with the configured stack settings.
- Report metrics in the application quality dashboard with respect to the configured stack settings.
For more information, see Creating UI-based tests with scenario testing.
Run an application test suite from a CI/CD pipeline
Valid from Pega Version 8.5
Deployment Manager, as well as the existing REST service used to call scenario tests, now accepts a test suite ID when running scenario tests from an application pipeline. By using test suites, you can customize a set of select scenario tests to run as a group, instead of running all the scenario tests that are applied to a particular application.
Only the tests that belong to the suite are run as part of the task.
For more information, see Creating UI-based tests with scenario testing.
Access PegaUnit compliance metrics from a centralized location
Valid from Pega Version 8.5
PegaUnit compliance metrics and execution rate have been added to the PegaUnit metrics tile of the Application Quality dashboard. This dashboard provides a centralized location for all PegaUnit data for a specific application.
The dashboard also supports granular PegaUnit test information for each case type and data type, similar to the process currently available on the branch quality dashboard.
For more information, see Analyzing application quality metrics.
Run PegaUnit tests by using an API call
Valid from Pega Version 8.5
A new REST API is now available to create and run PegaUnit tests from an external continuous improvement (CI) tool. This synchronous method allows for the processing of large quantities of tests while reducing the possibility of time-out issues. This additional method of performing PegaUnit testing does not impact users who want to continue using their current testing workflow.
For more information about setting up your environment and making API calls with Deployment Manager, see the Documentation/readme-for-swagger.md file in the DeploymentManager04_08_0x.zip file, found in the Deployment Manager download package.