I can certainly get some numbers and push the report somewhere. At the moment, I was seeing it as a tool for checking where there might be gaps when I'm writing tests, rather than something I'd necessarily put on every build, but if others see value in doing that, I wouldn't be opposed to it.
Jon On Mon, Dec 31, 2018 at 5:09 PM Jean-Louis Monteiro < [email protected]> wrote: > Hey Jon, > > Yes I did see the PR. Thanks for it. > Do you have any figures? > What are we looking at with the ability to have the coverage information? > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Mon, Dec 31, 2018 at 4:21 PM Jonathan Gallimore < > [email protected]> wrote: > > > Hey folks > > > > I started to have a play with some code coverage reports. Here's a basic > > start: https://github.com/apache/tomee/pull/336, which uses jacoco on > > openejb-core if -Pcoverage is specified. > > > > There are some test issues which I'll dig into, but it may be easier to > put > > those in a different surefire execution. > > > > Any feedback is appreciated. > > > > Jon > > >
