Aggregated test coverage report per unit test class and process definition

[berndvarga]

The generated reports is based on each test method.
I miss the overview, if all tasks and flows in an process definition is tested.

Maybe an additional report should be generated, which aggregate the test coverage based on test class and process definition?

Test1:
Process Definition Name: Xxx
Coverage: 81,8%
Test Class: XxxTest
Test Method: xxxStraightThrough

Test2:
Process Definition Name: Xxx
Coverage: 81,8%
Test Class: XxxTest
Test Method: xxxStartWithEvent

Proposed aggregation:
Process Definition Name: Xxx
Coverage: 100%
Test Class: XxxTest
Test Methods: xxxStraightThrough xxxStartWithEvent

My expectation is, that this will be a good enhancement.

[RasPelikan]

There is a class report. If you place all tests  for a specific workflow as test-methods into one class you will get the first l desired total report. Stephan ⁣BlueMail for Android herunterladen ​ Am 24. Feb. 2021, 09:10, um 09:10, berndvarga <[email protected]> schrieb:

…

The generated reports is based on each test method. I miss the overview, if all tasks and flows in an process definition is tested. Maybe an additional report should be generated, which aggregate the test coverage based on test class and process definition? Test1: Process Definition Name: Xxx Coverage: 81,8% Test Class: XxxTest Test Method: xxxStraightThrough  Test2: Process Definition Name: Xxx Coverage: 81,8% Test Class: XxxTest Test Method: xxxStartWithEvent  Proposed aggregation: Process Definition Name: Xxx Coverage: 100% Test Class: XxxTest Test Methods: xxxStraightThrough xxxStartWithEvent  My expectation is, that this will be a good enhancement. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #84

[berndvarga]

Okay, now I see my locally issue. The report is not generated, because I have multiple process definition in tests. If I remove all other deployments and unit test classes it works.

[berndvarga]

So i have now investigate into it. The problem on my side, is that I use an extended test class, which contains the initialization of the unit test and this share the processengine and the test coverage staff.
Additional I have two test classes, where the one class is just testing the BPMN (anything else is mocked) and an additional test class which also include a framework around the processengine and provided bean implementation.
This is the reason, why I get error during the compilation.

Class coverage can only be calculated if all tests deploy the same BPMN resources. expected:<[ProcessDefinitionEntity[usertaskevent:1:2903]]> but was:<[ProcessDefinitionEntity[XxxNavigationEventMain:1:4905], ProcessDefinitionEntity[XxxNavigationEventSub:1:4904]]>

For me it would be helpful, if I can reset the TestCoverageProcessEngineRule in the AfterClass method for the next unit test class.

Maybe such feature already exist, but I have not located it?