[
https://issues.apache.org/jira/browse/CASSANDRA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635747#comment-13635747
]
Ryan McGuire edited comment on CASSANDRA-5462 at 4/18/13 10:02 PM:
-------------------------------------------------------------------
I did not intend to change any behaviour regarding -Dwithout.rat nor
-Dwithout.maven. This is meant as a refactoring removing the <antcall>
directives, which for some reason (IIRC it had to do with the fact that antcall
spawns a new ant process) were incompatible with cobertura. If this
substantially changed something, it was unintentional.
was (Author: enigmacurry):
I did not intend to change any behaviour regarding -Dwithout.rat. This is
meant as a refactoring removing the <antcall> directives, which for some reason
(IIRC it had to do with the fact that antcall spawns a new ant process) were
incompatible with cobertura. If this substantially changed something, it was
unintentional.
> Ant code coverage with unit and dtests
> --------------------------------------
>
> Key: CASSANDRA-5462
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5462
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Ryan McGuire
> Assignee: Brandon Williams
> Attachments: trunk.5462.cobertura-reports.patch
>
>
> This is a patch to our build.xml to integrate a cobertura code coverage
> report across both the unit tests and the dtests. I've had this working for
> awhile, but it's rather unwieldy: it takes over 7 hours for it to run on my
> i5 based laptop. This is because it runs through the entire dtest suite
> twice, once without vnodes turned on, and once with. It does work repeatably
> though so although it's a monster, it's probably worth including.
> See http://static.enigmacurry.com/tmp/cobertura-report-4-with-vnodes/ for
> sample output, run against trunk today.
> Once applied, you just need to run '*ant codecoverage*'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
