Branch quality monitoring
The Branch Quality dashboard is a feature in Pega Platform™ with which users can monitor the quality of their Branch in real-time. The dashboard provides a visual representation of key quality metrics, such as the number of open issues, the number of failed tests, and the overall code coverage of the Branch.
By monitoring these metrics, users can detect potential problems early on and take corrective action to help ensure that the eventual merge process runs smoothly. The dashboard also provides detailed information about each metric, allowing users to drill down into specific issues and take action to resolve them.
The Branch Quality dashboard is accessible through Dev Studio and is updated in real-time as new data becomes available. Pega Platform™ refreshes the data every time that you open the dashboard. You can also manually refresh the data at any time.
Overall, the Branch Quality dashboard is a powerful tool for ensuring the quality of code in a Branch and can help users identify and address potential issues before they become major problems.
The following figure shows the Branch quality tab on which you can view guardrails, merge conflicts, and information about the unit tests for the Rules in the Branch:
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 test Cases do not cover.
- Failed unit tests: Analyze the details of unit tests that have failed.
- Failed scenario tests: Analyze the details of scenario tests that have failed.
- Rules without unit tests: See the details of Rules that do not have any associated unit tests.
Use the Merge Branch Ruleset wizard to merge changes in a Branch to the base Rulesets when development in the Branch is complete and stable. Use extension points to customize the standard merge Branch Rulesets process. For example, add behavior that can help enforce 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
As a Lead System Architect (LSA), you need to review the code in the Branch to help ensure that it meets the organization's coding standards and best practices. This involves reviewing the code for readability, maintainability, and performance. As an LSA, perform the following actions before merging the Branch:
- Before initiating the Branch merge, ensure that the team conducts a quality check to investigate and resolve any guardrail violations.
- Identify and investigate any potential merge conflicts to address issues in the Branch immediately by involving the respective team members or teams.
- Periodically review the Test Coverage report to identify which tests do not cover executable Rules in the Branch and instruct team members to prepare unit test Cases.
- Determine the causes of individual unit test failures and ensure that the Branch passes 100 percent of the unit tests.
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.
Want to help us improve this content?