Published Release Notes

Unit testing support for more rule types

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

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

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

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.

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

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

Condition builder enhancements

To enhance the precision of condition builder in both App Studio and Dev Studio, the new instances include comparator helps you specify the number of field group and field group list instances to which a when rule applies. In addition, a search option that returns results on keypress helps you easily look for existing values.

For more information, see Create conditions in an enhanced condition builder (8.5), Defining conditions in the condition builder.

Support for nested Declare Trigger rules

Pega Platform™ now supports nested Declare Trigger rules so that you can conveniently create correlations between actions in your case types. Declare Triggers rules invoke an action when a specified event takes place in a case type. You can now design more complex scenarios faster by nesting more Declare Trigger rules that work in the context of running another Declare Trigger rule. For example, when a case participant changes a postal code in their personal details, a Declare Trigger rule runs and a respective customer service representative (CSR) receives an email. After the CSR receives the email, a nested Declare Trigger rule runs and your application creates a document with the updated personal details and attaches it to the case.

For more information, see Develop applications faster with nested Declare Trigger rules (8.5), Declare Trigger rules.