@Scott Hickey but can you make it work
with @CompileStatic and the Elvis operator? We are having big struggles to
get that working. (In a Grails 3.3.x application)
Best regards / Med venlig hilsen,
Søren Berg Glasius
Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
-
We are using Clover - it is open source now. We have found it works much
better for us at Mutual of Omaha than JaCoCo or Cobertura.
Scott Hickey
Mutual of Omaha
On Thu, Jun 20, 2019 at 12:02 PM Sean LeBlanc
wrote:
> What are people using currently to get accurate code coverage from
> new(ish) v
Typically, if I have something (a microservice) that is 100% covered both for
lines and branches, neither JaCoCo or Cobertura will show it properly unless I
do some things. Here are some examples of the type of things I have to do:
* Re-order methods in a class. This can make as much as 15
Groovy has done a lot of work recently to mark generated methods with an
@Generated annotation. We have other generated methods which are synthetic
methods. I know JaCoCo has been making changes to ensure that such methods
aren't included in coverage analysis. I am not sure whether Cobertura has
do
What are people using currently to get accurate code coverage from new(ish)
versions of Groovy? We are on 2.4.10 and I see similar issues as what this
thread is talking about:
https://github.com/cobertura/cobertura/issues/184
Does anyone have good experiences with getting more accurate code c
