I have looked at the documentation and found nothing that sounds like this, so I came here.
I have some unit tests that work by first populating an in-memory database, using objects I create during the `@Before` part of the unit test. The downside is that JaCoCo's reports are showing that the code in the constructor for those classes has been traversed, while actually the test itself, which happens after the database population, didn't access that code. So, is there a way to overcome this with only JaCoCo or shall I have to do something else to avoid this issue? -- 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/1b12fe19-8453-4a5e-9a43-62acef7260f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
