You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/09 13:29:04 UTC
[jira] [Commented] (ROCKETMQ-187) Measure the code coverage for
Integration Tests
[ https://issues.apache.org/jira/browse/ROCKETMQ-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002670#comment-16002670 ]
ASF GitHub Bot commented on ROCKETMQ-187:
-----------------------------------------
Github user dongeforever commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/96
The PR is better not to be merged by the original author.
@lizhanhui @zhouxinyu @shroman please help merge this PR.
> 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: dongeforever
>
> 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)