Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Avoid duplicating application test efforts by merging test coverage reports (8.5)

Updated on May 3, 2021

When you merge application-level test coverage reports, you gain insight into your testing hierarchy and can avoid creating duplicate tests for rules that are used across multiple applications.

Enhancements to the Pega API service allow you to select applications in your testing stack and generate test coverage reports with merged application-level test details. By specifying multiple source applications from which to merge testing results, you can generate a consolidated report in your target application that shows testing overlaps and gaps. 

Input fields for source and target application IDs
Input fields for source and target application IDs

To identify the list of coverage reports to merge, use the SourceApplicationID along with the TargetApplicationID for the output location of the consolidated report. 

The consolidated report provides a list of covered and uncovered rules, as well as a separate list of merged reports at the application level. 

List of covered rules in the merged report

For more information, see the following topics:

  • Previous topic Delay the execution of a step within a test and rerun failed scenario tests for enhanced scenario test stability (8.5)
  • Next topic Export and import simulation data automatically with Deployment Manager (8.4)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us