PegaUnit related questions on Test Cases and Reports
PegaUnit related questions:
Is there an easy way to figure out which Test Cases are not included in one or more Test Suites?
In order to see which rules are without a Test Case (in the Automated Testing > Reports tab) the ruleset with Test Cases must be in the same application as the ruleset with the actual developed rules. However, isn't it bad practise to include test cases in this application layer (because of the risk of including them when packaging). Pega recommends creating an development application layer on top of the application which includes the test ruleset.
If it is mandatory to get coverage insight, is there a way to exclude the test ruleset from packaging?
Currently, there is no out of the box way of figuring out if Test Cases are not associated with a Test Suite
That is a good observation about the current limitation of the Reports associated with Test Cases. There are two possible solutions
From the dev application layer which is built on the production app, select the user preference to also include the built-on applications for test cases, and then when you go to the report, you will get a report against all the rules in the app stack, which will also include PegaRULES. This will obviously be a lot of rules, but if you click on any one rule category, you can filter it down to just the rulesets you care about. (Recommended approach)
Have another application rule which has all the production application rulesets along with PegaUnit, but this one is purely for reporting and test management. This app will not be packaged and migrated over. This is not convenient and can be error prone since it means having to keep two app rules in sync from the perspective of rulesets. The number of rulesets and versions may not change as often so this is might be an option, but still not recommended.
We shall take this as an enhancement request to provide better filtering capability in the testing and quality dashboards.