You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "dongeforever (JIRA)" <ji...@apache.org> on 2017/04/21 09:59:04 UTC

[jira] [Created] (ROCKETMQ-187) Measure the code coverage for Integration Tests

dongeforever created ROCKETMQ-187:
-------------------------------------

             Summary: Measure the code coverage for Integration Tests
                 Key: ROCKETMQ-187
                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-187
             Project: Apache RocketMQ
          Issue Type: Improvement
            Reporter: dongeforever
            Assignee: vongosling


Now we could browse the Unit Tests and IT Tests at 
https://builds.apache.org/analysis/component_measures/?id=org.apache.rocketmq%3Arocketmq-all

But the IT Test coverage is not correct. It should cover the original sources instead of the the classes in test module.

As for as I known, the coverage report  is generated by matching the collected data(often using java agent) against a set of classes (the module classes compiled from src/main/). you could refer to: http://olafsblog.sysbsb.de/measuring-test-coverage-of-integration-tests-for-separated-modules-with-jacoco/


So we could match the jacoco-it.exec to each module's source classes to get the correct IT coverage report.
By the way, we'd better exclude the classes in the test module.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)