Skip to main content

Application quality reports

Deployment Manager uses best practices to prevent known issues from leaking to production.

For example, by analyzing recent deployments, the Application Quality report gives you clarity about how well release guards are being used as part of an application's release process. By providing a clear data-driven view, this report underlines the role of governance and testing in certifying an application as production-ready.

Drive Quality and Security governance

The Application Quality report covers two streams of information:

  • The effectiveness of best practice task implementation for the latest deployment
  • The quality and unit test implementation trend across recent deployments, made in a selected date range.

The following example of an Application Quality report shows the Best practices and Quality metrics dashboards:

The image of the Application Quality report shows the Best practices and quality metrics dashboards.

Release Managers can govern an application's quality using some of the critical insights that they gain through Application Quality report:

Metric Description Governance Impact

Guardrail score
and 
Application compliance

Overall compliance based on adherence to best practices and guidelines ensuring optimal performance, reusability, and maintainability for high-quality Pega applications.
  • Benchmark and enforce a minimum compliance score of 90 for all applications and set incremental goals for newer applications to improve over time.
  • Detect risky design practices early through declining score due to increased rule warnings or anti-patterns that can impact performance or maintainability.
  • Drive proactive remediation with detailed review of guardrail warnings and fix high-severity issues before packaging a release.
  • Use guardrail trends to coach developers on reusable, performant, and upgrade-friendly application design.

Development Standards 

Verified adherence to Pega-recommended guardrails or custom guardrails enclosed into a policy to flag deviations.
  • Monitor adherence to guardrails by regularly reviewing violations flagged by Pega-recommended or custom guardrails, to ensure that teams follow established design standards.
  • Prevent tech debt buildup by prioritizing performance, naming, and design violations before generating deployment artifacts, to maintain application health.
  • Institutionalize feedback loops by sharing recurring guardrail or policy violations with developers during sprint retrospectives to reinforce best practices.
  • Measure the development maturity by tracking trends in violations over time as an indicator of improved developer quality and code maintainability.

Security Checklist Status

Verifies compliance towards Pega recommended security configurations and checks.
  • Ensure that every application has its security checklist configured and reviewed before deployment.
  • Detect and fix gaps early – Non-compliant items (such as unsecured authentication, missing encryption, or open access roles) must trigger remediation before promotion.
  • Standardize security baselines – Align all applications to Pega’s recommended security configurations to maintain consistent enterprise security posture.
  • Integrate into pipeline quality gates – Block deployments if key security checks (such as access control, SSL, and data encryption) fail or remain incomplete.
  • Track security maturity trends – Use checklist compliance history to monitor improvements, identify recurring vulnerabilities, and plan targeted security reviews or audits.

Test coverage and Unit testing

Trends depicting

  • Code coverage against recommended or configured thresholds.
  • Total versus run unit tests
  • Success rate of unit test runs.
  • Spot untested areas through low-coverage analysis against thresholds and drops in tests that have been run compared to the total number of tests, which indicates skipped suites that signal risks and unvalidated parts of the application that need new or improved test cases.
  • Detect regressions at early phases of releases with falling success rate trends that highlight instability introduced by recent changes.
  • Assess the depth of automation with high success yet low coverage that suggest shallow testing patterns, which demand improvement in negative and integration scenarios.

 For more information, refer to Reviewing application quality reports

 

Check your knowledge with the following interaction:

This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice