BPM Test coverage shows NaN

Community Community Extensions
1

I followed the instructions here using the spring-testing with starter dependency:

<dependency>
  <groupId>org.camunda.bpm.extension</groupId>
  <artifactId>camunda-bpm-process-test-coverage-starter</artifactId>
  <version>1.0.3</version>
  <scope>test</scope>
</dependency>

Test class:

@SpringBootTest(args = "--jasypt.encryptor.password=xxxx")
@RunWith(SpringRunner.class)
@Deployment(resources = {"oauth_process.bpmn"})
public class OAuthFlowTest {

    private static final String PROCESS_KEY = "oauthProcessFlow";

    @Rule
    @ClassRule
    public static ProcessEngineRule engineRule = TestCoverageProcessEngineRuleBuilder.create().build();

    @Test
    public void ProcessStartAtFindScopeApprover() {
         // bla bla bla
    }

The test runs fine, but the overall coverage shows NaN (see below). What do I miss?

2022-02-08 13:17:53.564 INFO 39000 — [ main] ocessEngineCoverageTestExecutionListener : ProcessStartAtFindScopeApprover test method coverage is 0.2222222222222222
2022-02-08 13:17:53.564 INFO 39000 — [ main] .b.e.p.j.r.TestCoverageProcessEngineRule : ProcessStartAtFindScopeApprover(OAuthFlowTest) succeeded.
2022-02-08 13:17:53.564 INFO 39000 — [ main] .b.e.p.j.r.TestCoverageProcessEngineRule : ProcessStartAtFindScopeApprover test method coverage is NaN

2

The reply is a little late, but hopefully it still helps.
When using the spring testing, you should not also define the JUnit4 rule.
Using the starter you actually don’t need any additional setup.
Also in this case, the @Deployment annotation should not be used, as the tests are running against the spring boot app, which should start the engine and deploy the processes.
Also have a look at camunda-process-test-coverage/OrderProcessTest.java at master · camunda-community-hub/camunda-process-test-coverage · GitHub.

3