Skip to main content


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

Generating an application-level test coverage report

Updated on December 13, 2021

Generate an application-level coverage report that contains coverage results from multiple users. Use this report to identify which executable rules in your currently included applications are covered and not covered by tests. The results of this type of report are visible on the Application Quality Dashboard.

  1. In the header of Dev Studio, click ConfigureApplicationQualityTest Coverage.
  2. Click Application level.
  3. Click Start new session.
    Note: To start application-level coverage, your operator ID must have the pzStartOrStopMasterAppRuleCoverage privilege.
  4. Enter the title of the coverage report, and then click OK.
  5. Optional: To provide data for the report, run all of the tests that are available for your currently included applications, for example, Pega unit automated tests and manual tests.
  6. Inform all relevant users that they can log in to the application and start running tests.
  7. Wait until all users have completed their tests and have logged off.
    Note: If you stop an application coverage session before a user has logged off, the coverage data of this user is not included in the report.
  8. Click Stop coverage, and then click Yes.
  9. Review the results of coverage session. In the Coverage history section click Show Report.
  10. Optional: To see whether coverage reports were generated by other users, click Refresh.
  11. Optional: To see a list of user-level coverage reports, click User level.
  • Previous topic Generating a user-level test coverage report
  • Next topic Participating in an application-level test coverage session

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.

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

Close Deprecation Notice
Contact us