[
https://issues.apache.org/jira/browse/CASSANDRA-8953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-8953:
------------------------------------------
Component/s: Test/unit
CI
> ability to run jacoco coverage with a specific patch
> ----------------------------------------------------
>
> Key: CASSANDRA-8953
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8953
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Legacy/Testing, Test/unit
> Reporter: Russ Hatch
> Priority: Normal
>
> It would be very nice to have code coverage analysis for specific patches (or
> any other way of isolating a change, like a topic branch with a patch
> applied).
> This would ideally be a nice way for committers to see how much of a new
> patch gets exercised by unit (and possibly dtests as well).
> A first iteration of this capability might just be:
> * getting a list of files a patch alters
> * assuming what tests are affected based on source file names
> * running that set of units tests and reporting with jacoco
> * figuring out which lines touched by the diff are covered or not (if you
> alter a line you should be the person to add tests).
> the final nice to have would be support for functional tests as part of
> this system, but I'm unsure presently how we can do this without running the
> entire dtest suite which is a bit onerous.
> There are two github projects which might be interest for this endeavor. The
> first one converts jacoco coverage data to cobertura format, and the second
> one can take cobertura data and calculate diff coverage:
> https://github.com/rix0rrr/cover2cover
> https://github.com/Bachmann1234/diff-cover
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
