Question
Application Test Coverage - Behavior & Inconsistent results
Started a new Test coverage session and I noticed that with running the unit tests manually no coverage report is generated.though per the below article , it is optional, so can someone confirm
Steps followed is started the Coverage session, waited for some time and stopped coverage report showed 0% coverage. Only time I got results was when I manually ran the unit tests
Second issue that I am running into is when the coverage is running and I do some actions in the system say create a new case etc, the coverage report percentages changes, sometimes it drops and sometimes is increases so I'm curious to understand the reason for the same
Note: We are using Pega 8.1.3
After starting the coverage, users needs to execute rules ( generally by running tests like pegaunit / rspecs automation so that application rules gets covered ). The rules that gets executed between start and stop of coverage, reflects in the coverage report.
This also answers your second query, why some rules get covered when you perform some operation.
Coverage start and end are two demarcation points. Inbetween these two events, users needs to perform desired testing operations, so that rules gets covered.