Published Release Notes

Improvements for test cases and assertions

The process of modifying test cases and assertions has been improved. Adjusting test cases to application changes is now much easier.

You now can:

• Select a page on which to run a tested rule.
• Change the class and rule of unit test cases.
• Create assertions that validate specific error messages on pages, properties, and activities.
• Automatically update decision result assertions with property changes made to a rule.
• Modify a rule's properties directly from decision result assertions.

For more information, see:

• Updating scenario tests
• Setting up your test environment
• Configuring page assertions
• Configuring property assertions
• Configuring decision result assertions

Identify Pega unit test cases associated with inactive or deleted rules

From the Application: Unit testing landing page, you can view a list of all Pega unit test cases that are associated with inactive or deleted rules in the currently included applications. You cannot use these test cases because they will always fail.

Either remove such test cases, or reactivate the rules that they are associated with.

For more information, see Application: Unit testing landing page.

Merged test-coverage report improves overview of application quality

You can now merge multiple application-level test coverage reports from built-on apps into a single report. This single test-coverage report provides an overview of your application's quality, and eliminates the need to manually collate data from multiple reports.

For more information, see Generating a merged coverage report.

Updates to creating and cleaning the test data for automated tests

Creating test data for automated tests is now easier and more customizable. During test case or suite creation, you can now create objects, load work and data objects, and add user pages from the clipboard. These objects and pages can be further configured and will be available in the clipboard when you run the test.

For test cases, you can now define a separate set of actions to perform after the tested rule is run, such as applying a data transform, loading a data page or object, or running an activity,

You can also prevent test data from being removed from the clipboard after a test is run so that subsequent tests can use the same test data.

For more information, see Setting up your test environment and Cleaning up your test environment.

Simulation of data pages and third-party connections

When configuring your unit test case environment, you can now set up simulated data for connector and data page rules, instead of connecting to external sources.

By simulating such data calls, you are not dependent on any third-party server when running your tests.

This feature supports the following rules:

• Data page
• Connect-Cassandra
• Connect-CMIS
• Connect-dotNet
• Connect-EJB
• Connect-HBase
• Connect-HTTP
• Connect-Java
• Connect-JMS
• Connect-MQ
• Connect-REST
• Connect-SAP
• Connect-SAPJCo
• Connect-SOAP

For more information about simulating third-party connections, see Simulating data pages and third-party connections.

New branch quality dashboard

Pega Platform™ 8.4 introduces a new branch quality dashboard that shows the following metrics:

• The branch’s guardrail compliance score and the number of guardrail violations
• The percentage and number of unit tests that passed for the branch
• The percentage and number of rules that the tests cover
• Potential merge conflicts that can be addressed directly from the branch quality dashboard

For more information about the new branch quality dashboard, see Viewing branch quality and branch contents.

Enhanced reliability and stability of scenario tests

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

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

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

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.