On Wednesday, October 4, 2017 at 5:52:46 PM UTC+2, [email protected] wrote: > >
Is there anything special about how JaCoCo treats abstract classes? > > No. No magic: executed = covered, not executed = not covered. And you can answer such and any following similar questions on your own by trying simple plain java examples. I managed to prepare an example of my case and pinpoint the issue. > https://github.com/juzer/spring-jacoco-demo > It seems to be related to the inheritance hierarchy and abstract classes. > I have an AbstractService which is tested by instantiating an anonymous > class and it's covered 100%. Then I have a concrete subclass that is also > tested (only methods in this class). When I run all the tests however, the > coverage of AbstractService is 0. Moving all tests to the ServiceTest > results in correct coverage report - 100% on both classes. > I'll have a look later. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/73b09f9c-ec76-4f29-8697-30e2403563ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
