rocketmq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dongeforever (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ROCKETMQ-187) Measure the code coverage for Integration Tests
Date Fri, 26 May 2017 08:44:04 GMT

     [ https://issues.apache.org/jira/browse/ROCKETMQ-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

dongeforever closed ROCKETMQ-187.
---------------------------------
    Resolution: Fixed

> 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
>             Fix For: 4.1.0-incubating
>
>
> 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)

Mime
View raw message