Question
Thryve Digital Health LLP
IN
Last activity: 1 Jan 2025 20:06 EST
How to add unit test rules for uncovered rules
Hi All,
Rule type supported for Test Coverage are around 27. Out of these 27 rule types, There are many for which we are not able to create AUTs in Pega (For Example, section, harness, paragraph, navigation, declare trigger etc.).
It is giving us a very low score when we calculate test coverage from Pega DM. How do we increase this test coverage score and how to create test cases for these type of rules?
Please advise.
Thanks,
Sandeep
Rulesstack Private Limited
IN
Increasing your test coverage score in Pega DM, especially for rule types that don't support Automated Unit Tests (AUTs), can be challenging. Here are some strategies to help you improve your test coverage:
Manual Testing and Conversion:
• For rules like sections, harnesses, and paragraphs, you can manually run these rules and then convert the manual runs into automated tests. This involves running the rule, verifying the results, and then using the "Convert to test" option to create a test casehttps://academy.pega.com/topic/creating-pega-unit-test-cases/v1
Use of Declarative Rules:
• For rules like Declare Triggers, you can create test cases by simulating the conditions that would trigger these rules. This might involve setting up specific data conditions and then verifying the outcomeshttps://academy.pega.com/topic/creating-pega-unit-test-cases/v1.
Scenario Testing:
• Scenario testing can help cover complex interactions between different rule types. You can create end-to-end scenarios that involve multiple rule types, ensuring broader coveragehttps://academy.pega.com/topic/test-coverage/v1.
Custom Test Cases:
Increasing your test coverage score in Pega DM, especially for rule types that don't support Automated Unit Tests (AUTs), can be challenging. Here are some strategies to help you improve your test coverage:
Manual Testing and Conversion:
• For rules like sections, harnesses, and paragraphs, you can manually run these rules and then convert the manual runs into automated tests. This involves running the rule, verifying the results, and then using the "Convert to test" option to create a test casehttps://academy.pega.com/topic/creating-pega-unit-test-cases/v1
Use of Declarative Rules:
• For rules like Declare Triggers, you can create test cases by simulating the conditions that would trigger these rules. This might involve setting up specific data conditions and then verifying the outcomeshttps://academy.pega.com/topic/creating-pega-unit-test-cases/v1.
Scenario Testing:
• Scenario testing can help cover complex interactions between different rule types. You can create end-to-end scenarios that involve multiple rule types, ensuring broader coveragehttps://academy.pega.com/topic/test-coverage/v1.
Custom Test Cases:
• For unsupported rule types, consider writing custom test cases that mimic the behavior of these rules. This might involve creating mock data and using it to test the rule's functionalityhttps://academy.pega.com/topic/creating-pega-unit-test-cases/v1.
Regular Review and Updates:
• Regularly review your test cases and update them as your application evolves.
By implementing these strategies, you should be able to improve your test coverage score and ensure that your application is thoroughly tested.
https://academy.pega.com/topic/test-coverage/v1
Regards,
Mohd Qizer Uddin
HCA Healthcare
US
@AtmaSandeepK16971429To improve test coverage for rule types not directly supported by Automated Unit Tests (AUTs) in Pega, focus on testing the functionality that uses these rules. Use Pega Scenario Testing to create end-to-end UI tests for flows involving sections, harnesses, or navigation rules. Ensure rules like Declare Triggers are indirectly tested by simulating events or scenarios that trigger them, and validate outcomes through related processes. For static content like paragraphs, test rendering using data transforms or custom scripts. Tag unsupported rules as "Not Applicable for AUT" to clarify their coverage limitations and document indirect testing methods. Leverage third-party tools like Selenium for UI validation and monitor coverage reports regularly to identify gaps. Collaborate with your team and Pega Support to improve coverage and implement additional tests for critical scenarios