Published Release Notes

Pega Agile Studio integration

You can configure the new Agile Workbench tool to integrate with Pega^® Agile Studio so that bugs and user stories are synchronized between the two systems. In addition, you can improve traceability in your development environment by using the Current work feature to associate a user story or bug with development changes.

For more information, see Integrating Agile Workbench with Pega Agile Studio and Tracing development changes to work items.

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

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.

Pega unit test suites are now modular

It is now possible to include test cases and test suites inside test suites. This feature makes test suites modular and improves the management of cases while creating, modifying, and executing them for regression testing.

For more information, see Pega unit test suites.

Fetch quality metrics for Pega unit tests by using the REST API

You can use the REST API to fetch quality metrics for the Pega unit tests of your application, such as unit test compliance, unit test execution results, test coverage, and guardrail compliance.

You can use the metrics returned by the service for gating purposes in a release pipeline.

For more information about the Pega API, see Pega API for Pega Platform.

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.

Parameter page is automatically removed after each Pega unit test run

The parameter page is automatically removed after each Pega unit test run. The reliability of subsequent tests is increased because they are not influenced by leftover parameter values that were set by the previous test.

For more information, see Cleaning up your test environment.

REST API now fetches the latest version of Application Quality metrics

When you request Application Quality metrics by using the REST service, the service requests a refresh of the metrics. This means that you always get the latest version of the metrics and can decide whether your application is ready for deployment based on that information.

For more information, see Pega API.

Create connections to repositories

Pega^® Platform can communicate with common repository technologies. Whenever an action creates a RAP, Pega Platform can browse, publish, or fetch artifacts: for example, when exporting an application, product, branch, or component. Repositories are instances of the Data-Repository class which holds all necessary connection information.

Pega Platform includes tools to connect with the following repository types:

• JFrog Artifactory
• Amazon S3

For more information, see Creating a JFrog Artifactory or Amazon S3 repository connection.

Run PegaUnit tests by using an API call

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. 

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.