Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Branch quality monitoring

Use the branch quality dashboard in Dev Studio to track quality metrics of your branch. By monitoring the condition of your branch, you can detect and address potential problems in stages early to ensure that the eventual merge process runs smoothly.

Pega Platform™ refreshes the data every time that you open the dashboard. You can also manually refresh the data at any time.

The following figure shows the Branch quality tab on which you can view guardrails, merge conflicts, and information about the unit tests that are configured on the rules in the branch:

Branch quality tab in Dev Studio.

You can use the new dashboard to track the branch guardrail compliance score and the number of guardrail violations. You can check the percentage and number of rules that the tests cover. You can also monitor the percentage and number of unit tests that passed for the selected branch.

You can analyze the quality of your branch in detail by viewing the following branch quality metrics:

  • Merge conflicts: Check the details of potential merge conflicts between your branch and the main application trunk.
  • Warnings: View, filter, and check individual guardrail warning details.
  • Uncovered rules: View, filter, and select the details of rules that are not covered by test cases.
  • Failed unit tests: Analyze the details of unit tests that have failed.
  • Rules without unit tests: See the details of rules that do not have any associated unit tests.

You use the Merge Branch RuleSet wizard to merge the changes in a branch to the base rulesets when development in the branch is complete and stable. You can use extension points to customize the standard merge branch rulesets process process.  For example, add behavior that enforces compliance with your organization's policies and procedures. For more information about adding pre-processing behavior, post-processing behavior, and customizing input validation in the UI of the wizard, see Branch merge process customization.

Actions required by an LSA to improve branch quality

A Lead System Architect (LSA) needs to review the code regularly to improve the code quality. As an LSA, perform the following actions before merging the branch:

  • Ensure that a quality check takes place to investigate and resolve the guardrail violations by the team before initiating the branch merge.
  • Investigate any potential merge conflicts to identify problems in the branch and immediately address the issues by involving the respective team members or teams.
  • Periodically review the Test Coverage report to investigate which tests do not cover executable rules in the branch; instruct the team members to prepare the unit test cases.
  • Determine the causes of individual unit test failures and ensure that the branch has a 100 percent test pass rate for unit testing.

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?

Want to help us improve this content?

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