I'm also experiencing this Groovy assert issue. It would be great to have it work correctly. Thanks Ivan
On Monday, October 5, 2020 at 7:41:34 PM UTC+2 [email protected] wrote: > I'm not able to get 100% branch coverage for Groovy's "assert" statements. > After looking into the generated code (decompiled via IDEA), it seems to me > that the problem is related to the following JaCoCo issue: > https://github.com/jacoco/jacoco/pull/321 > > If so, I wonder what the status of this issue is? Are there any plans to > tackle it, maybe? From the discussion, it looks like upstream projects are > real blockers. > > From the user perspective, it is unfortunate to have this limitation, > since "asserts" are commonly used in Groovy all over the place for > precondition checking in pour-man design-by-contract style. In the report, > it is hard to distinguish those false warnings from real missed branches. > > Tnx, > Damir > -- 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/64aac1cc-293c-4f1d-9f3f-a28abd34faf5n%40googlegroups.com.
