Question
Estes Express Lines
US
Last activity: 23 Feb 2023 12:39 EST
How to limit the application test coverage metrics to ruleset versions from a Product rule
As per my understanding Pega OOTB supports the test coverage metrics generated at application level or a user level. During the Pega Dev Ops deployment, "Enable test coverage" starts a new session for application level test coverage and then this can be validated using "Validate test coverage".
Would like to see if there are any approaches to limit the test coverage scope to the delta changes (i.e. to limit to the rules covered by all ruleset versions from a product rule) lined up for a deployment from Dev to QA environment.
Appreciate your responses on possible approaches.
Also reviewed below community question where a response states that this can be limited to a specific period of rule changes by specifying a start date for test coverage report generation where the report considers the rule changes from the given date till the report generated date.
https://support.pega.com/question/get-unit-test-coverage-specific-period
***Edited by Moderator Marije to add Capability tags***
Bits In Glass
CA
Yes, you are correct that Pega supports test coverage metrics at the application level or user level. However, by default, the test coverage is generated for the entire application, and there is no direct way to limit the test coverage scope to only the delta changes.
One possible approach to limit the test coverage scope to delta changes is to use a version control system like Git to track the changes made to the application over time. You can then use Git to identify the set of rules that have changed between two releases, and generate test coverage reports only for those rules. This approach requires some manual effort to track the changes and generate the reports, but it provides more fine-grained control over the test coverage scope.
Another approach is to specify a start date for test coverage report generation. You can do this by configuring the "Test Coverage Report" rule in Pega. In the rule form, you can set the "Coverage Calculation Start Date" property to a specific date, and the report will consider only the rule changes made after that date. This approach limits the test coverage scope to a specific period of rule changes, but it may not be suitable if you have multiple deployments within a short time frame, as it can be difficult to identify the exact start date for each deployment.
Yes, you are correct that Pega supports test coverage metrics at the application level or user level. However, by default, the test coverage is generated for the entire application, and there is no direct way to limit the test coverage scope to only the delta changes.
One possible approach to limit the test coverage scope to delta changes is to use a version control system like Git to track the changes made to the application over time. You can then use Git to identify the set of rules that have changed between two releases, and generate test coverage reports only for those rules. This approach requires some manual effort to track the changes and generate the reports, but it provides more fine-grained control over the test coverage scope.
Another approach is to specify a start date for test coverage report generation. You can do this by configuring the "Test Coverage Report" rule in Pega. In the rule form, you can set the "Coverage Calculation Start Date" property to a specific date, and the report will consider only the rule changes made after that date. This approach limits the test coverage scope to a specific period of rule changes, but it may not be suitable if you have multiple deployments within a short time frame, as it can be difficult to identify the exact start date for each deployment.
Overall, both approaches require some manual effort to track the changes and generate the reports, but they provide more control over the test coverage scope compared to the default behavior of generating test coverage for the entire application.