circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Published Release Notes

Find release notes for the selected Pega Version and Capability.

Browse resolved issues for Platform releases.

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.

Improvements for test cases and assertions

Valid from Pega Version 8.4

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:

Simulation of data pages and third-party connections

Valid from Pega Version 8.4

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

Valid from Pega Version 8.4

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

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:

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

All Pega product release notes can be found on their product pages.