cobertura finally came out with 1.9.1 so you don't have to build it yourself or use some alpha maven plugin. hooray!
then some guy released a patch that apparently does what you always wished cobertura would do: tell you which test method and class exercised which line and which branch. combine that with the excellent stuff in last year's gtac keynote.
instrument your application, listen in on wicket component instantiation, record coverage, cross reference the data with your test coverage report. show data about the tests or lack thereof in a hover on each component of your web page. while you're at it, why not add coverage reports of software in m2 repositories, next to the source jar. then you can see which of your dependencies are tested.
Subscribe to:
Post Comments (Atom)
0 kommenttia:
Post a Comment