Process Test Coverage Junit5 - One Report For all classes

How to make one unique report of all test classes?

I manage to make report per test class,
every report has only one suites and that is the name of the test class.

threeReports

camunda.cfg.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
  <bean id="processEngineConfiguration" class="org.camunda.community.process_test_coverage.engine.platform7.ProcessCoverageInMemProcessEngineConfiguration">
    <property name="expressionManager">
      <bean class="org.camunda.bpm.engine.test.mock.MockExpressionManager"/>
    </property>
  </bean>
</beans>

Please have a look at Getting started - Camunda Process Test Coverage.
With the next release of the extension (Milestone 2.1.0), a maven plugin will be included that can aggregate multiple test results into one result.

2 Likes

Thanks that is exactly what I want, is there corresponding gradle plug-in or just maven is provided?

Currently we only have a maven plugin in place.
If there is some demand for a gradle plugin, this could also be provided later on.
Maybe you can open an issue for that, if you need it.

1 Like

Thanks I’ve opened the issue:

1 Like

We now implemented a gradle plugin for the aggregation of test reports:

Hopefully soon we’ll release a 2.1.0 where the gradle plugin is included.
If you want, you could of course build the plugin yourself and try it out locally.
The integration of the plugin is documented here:

Feedback would be very welcome.

1 Like

Hi Jan,

I’ve just tested your plug-in and it works perfectly fine!
I have just one more suggestion.
I cannot see overall coverage in the report,
I can see just what is coverage per test class
but the overall coverage percent is something which I need.

Maybe I did smth wrong, please check picture in attachment.

Regards,
Jovan Zoric

Hi Jovan.

Thank you for testing the plugin.

You are right. This is indeed something that is missing.
It is something, that needs to be done in the report frontend though (all information is in the report.json file).
I’ll create an issue and ask for help, as I’m not involved in the frontend development.

Best regards
Jan

1 Like