Highlighting with JaCoCo

[nkal...@gmail.com]

I've been messing around with JaCoCo and thought that it would be nice to be able to have a more visual way of seeing if my projects' coverage is up to snuff or not as I develop. So the past few months I did some tinkering and came up with an app that does this:

http://s3.amazonaws.com/nishant-tests-coverage/example_report/index.html

In the above file, I considered a field to be "passing" if it has 50% or more coverage. Each field, though, also reflects the pass/fail status of every field that the element contains, which is why there are some failing areas with >50% coverage. To clarify: For a package to be marked as "passing," EVERY class needs to be passing as well. The same applies to packages and methods.

I just figured I'd share this with the community. Is there any interest in this? I'd love to hear everybody's input!

[Henrik Horneber]

Great job! But I get the feeling sonarqube already does something very similar. What am I missing?

--
You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/0a02877c-7fca-4d37-90dc-96977f932a92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[nkal...@gmail.com]

I honestly don't know what SonarQube is capable of, but what I made essentially allows me to set coverage goals for my projects. I can specify individualized coverage criteria for every package, class, and method and then see if I met those criteria with a quick glance at the index HTML screen.

If that's what SonarQube already does then I guess that's a bummer, but it was a good learning experience.