Per-test coverage of integration tests with maven-failsafe-plugin

[#1]

My first topic is marked as SPAM, so I recreated it.

Hello!

I'm struggling with setting up per-test coverage for integration tests.

I have the simple setup:

• single clover database
• single application
• Maven 3 build
• all tests and servers are run on localhost
• integration tests are run by starting WildFly with Arquillian, clover-runtime.jar is added to the deployed artifact. Integration tests are run by maven-failsafe-plugin
• I run

  mvn clean clover:setup install 

  to build the project and run the tests.
• The i run

  mvn clover:clover

  to generate the html report based on clover.db.

For unit-tests, per-test coverage works superbly: in the html-report on covered lines I see a green line, and by clicking on it it displays the tests that cover this line.

For integration tests, the green/red coverage is shown, but there is no green line and I can't see, which lines are covered by tests.

I tried to do instrumentation-level distributed coverage by adding

<distributedCoverage/>

to clover-maven-plugin configuration
and

<configuration>
    <forkMode>once</forkMode>
    <systemProperties>
        <property>
            <name>clover.server</name>
            <value>true</value>
        </property>
    </systemProperties>
</configuration>

to maven-surefire-plugin configuration, according to Using Distributed Per-test Coverage page.

But nothing changes: I still do not see test coverage on classes run on the server.
Logs about running distributed coverage are written to maven log.

Running TestSuite
Distributed coverage is enabled with: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000
Starting distributed coverage client: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000

The strange thing is that when I look to WildFly log, I see similar logs too (after server start):

2017-09-26 17:35:32,895 INFO  [stdout] Distributed coverage is enabled with: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000

2017-09-26 17:35:32,896 INFO  [stdout] Starting distributed coverage client: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000

which makes me think that the remote server behaves as Clover server, not as the client.

Questions:

1) Do I have to use distributed coverage at all, since the decision matrix says that for my simple case I just have to use "showUniqueCoverage=true"? I tried to add this to maven configuration, but this does not work as well.

2) Since integration tests are run via maven-failsafe-plugin, I suppose we have to add some configuration to this plugin too.
I've seen this page, but it looks extremely complex and obsolete with aggregate reports and huge report descriptors.
How to configure maven-failsafe-plugin correctly?

3) How do I understand that distributed coverage has started successfully both for the server and client sides?

4) How to make my WildFly server work as Clover-client, not as Clover-server?

Thanks in advance for your answers!

Regards, DP.