The test coverage report in Pega Platform helps to determine the number of rules covered...

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s test coverage reports, as described in Pega Academy’sTesting Missionand thePega Certified Lead System Architect Study Guide, provide insights into rule execution during testing, available at both application and user levels. The distinction lies in the scope of the testing session.

Option A (Incorrect): The test coverage report does not differentiate based on ruleset types (application vs. branch rulesets). It tracks rule execution regardless of where rules reside, per theTest Coveragemodule.

Option B (Correct): The application-level report aggregates test coverage for all users in a session, providing a comprehensive view of rule execution across the application. The user-level report is specific to the individual user who initiated the testing session, focusing on their actions. This is explicitly stated in theTest Coverage Reportssection of Pega Community.

Option C (Incorrect): Test coverage reports do not distinguish between API-based and user-based testing. They track rule execution regardless of the testing method, as clarified in theTesting Frameworkmodule.

Option D (Incorrect): The report does not differentiate based on enterprise vs. implementation layers. Coverage is based on rule execution within the application context, not class hierarchy, per theTest Coverageguidelines.