Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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

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. 

 

 

 

Merge application-level test reports by using the Pega API service

Valid from Pega Version 8.5

A new REST API is now available so that you can merge test coverage reports at the application level without having to perform this task manually. This service accepts the application IDs for the test coverage reports that you want to merge and generates a consolidated report in the target application provided.

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.

Improvements to scenario testing for increased efficiency

Valid from Pega Version 8.5

Several enhancements have been made to scenario tests for increased test efficiency. See below for a list of these improvements.

  • Scenario testing now supports multiple actions per run, and all events that are configured as part of a scenario test are now triggered sequentially. Previously, only the first event was triggered, and the system ignored the rest. 
  • If a scenario test encounters a JavaScript error at any point during the run, the system immediately stops the tests. Refer to the logs for a detailed description of the error. 
  • Actions can now be configured and recorded on custom components in the scenario testing tool. 

For more information, see Creating UI-based tests with scenario testing

Chrome support for editing specification descriptions in Word

Valid from Pega Version 7.2

If you use Google Chrome 42 and later, you can now create, save, and update specification descriptions even if you are not using the Microsoft Silverlight NPAPI plug-in.

The new Upload Word document as description option provides you with the functionality to upload a Word document that contains the specification description. In addition, you can use the Export to Word option to export the description that you entered in the rich text editor to a Word document.

Redesigned tool for documenting your applications

Valid from Pega Version 7.2

Use the newly designed Document Application tool to generate application profile documents, application documents, and specification documents. The Document Application tool provides a streamlined landing page for all document types, including custom templates, and replaces the Application Document wizard.

For more information, see Document Application tool and Enhancements to the Direct Capture of Objectives.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us