brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aled Sage <aled.s...@gmail.com>
Subject Re: Code coverage with cobertura
Date Thu, 15 Jan 2015 12:17:18 GMT
Hi Duncan,

Excellent, code coverage reports will be very useful moving forwards.

---
Regarding generating a single report, here are some comments that were 
posted off-list:

    Could you accumulate the reports as you go? Rather than running one
    merge at the end do it for each project after the
    post-integration-test or package phase, perhaps. I can imagine how
    you would configure this, can't think how you'd ask for something to
    be run at the end of the build.

    Sam

And:

    Have you tried the aggregate parameter -
    http://mojo.codehaus.org/cobertura-maven-plugin/cobertura-mojo.html#aggregate?
    Here’s an example that should aggregate it’s results:
    https://svn.codehaus.org/mojo/trunk/mojo/cobertura-maven-plugin/src/it/mcobertura-65/pom.xml

    Svet.

---
For xml versus html, If it's easy to say both then might as well do 
that. Otherwise, the html report will be more useful in the short term.

---
For integration tests, sounds like they need some tender loving care 
again. I'll try to find some time to look at any failures, but it might 
not be until next week. If anyone else picks up fixing any of these, 
then please do ping me if you want help.

---
For what numbers to expect, I'm hoping for good test coverage in core, 
policies and utils. For the projects that contain mostly entities, I 
expect poor unit test coverage but reasonably good integration test 
coverage. The reason is that running the entities installs software etc, 
so in many places it is hard to unit test that beyond the 
not-particularly-useful what commands would it have wanted to execute.

Aled


On 14/01/2015 10:26, Duncan Grant wrote:
> I'm trying to get code coverage working for brooklyn.
>
> As a first task I've upgraded the version of cobertura we are using and
> fixed some issues with paths.
> This means that you can run mvn install -P Coverage and it will produce
> coverage reports for individual projects.  I'll create a PR today.
>
> I've tried swapping the ant-run approach that is currently used for just
> the maven plugin but there were some errors that I couldn't resolve and I
> don't think it's worth the effort.
>
> I'd also like to have a single report for coverage across the project.  I
> think I just need a task that runs after all the projects have been built
> but I'm not sure how to do that as the parent project seems to run first.
> I haven't much experience with maven so I'm probably missing something
> obvious.
>
> Does anyone have an opinion on whether we should be producing xml reports
> or html reports or both?  The html report is a nice human readable report.
> The xml report can be integrated (using a plugin) with jenkins to show
> trends but I'm not sure how helpful that is.
>
> I'm also a bit stuck getting the integration tests to run (due to a failed
> dependancy over night).  Also it seems to have been a while since they
> complete successfully on http://brooklyn.builds.cloudsoftcorp.com/ .  So I
> don't have any idea what coverage will look like then.
>
> Any thoughts would be appreciated
>
> Duncan
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message