why is clover showing green on gray?

I am evaluating Clover for a purchase.

There are multiple cases where, although no specific configuration is supplied (like exclusions), some part of a code block is marked as green, whereas all the rest has gray  color marking (which should mean exclusion, see picture in attachment). image2016-6-17 13:53:51.png

In the above, how can lines 16 and 18 be grayed out ?

 

How can that be? This is obtained using Grails and the Clover grails plug-in.

 

CloverStrangeBehavior.PNG

 

This behavior seems to contract what show in the legend and to be somewhat counterintuitive.

Any help would be appreciated. thanks.

 

 

2 answers

0 votes

Hi Michele,

Indeed, Clover should show coverage for line #16 and #18 in Beatles and line #23 and #24 in ECycleStep. 

It seems to be a software bug. I noticed that in Beatles class you have the ';' at the end of the line #15 and #17, while for others not. It's looks like Clover "compacts" several statements into one. I guess that something have been changed in the AST (abstract syntax tree) in Groovy compiler, which Clover does not handle.

Could you please tell what Clover, Grails and Groovy versions do you use?

Could you please check if the same problem occurs also in Clover 4.1.1, Groovy 2.4.3 and Grails 2.5.0 (these are the highest versions of Groovy/Grails against which Clover 4.1.1 was tested before it was released).

I found that in Grails 2.5.1 the Groovy version was bumped to 2.4.4 (see https://github.com/grails/grails-core/issues/9079).

Cheers

I confirm that the same behavior/bug is exhibited with grails 2.5.0 /Groovy 2.4.3.

I reported a bug here: https://jira.atlassian.com/browse/CLOV-1953. You can add yourself as a watcher to get email notifications.

We are using grails 2.5.3. I think it exhibits the same behavior with 2.5.0, but I am not specialist.

I would greatly appreciate if your team could tests the configurations you mention. I have put the code at:

http://webnri.hq.eso.org/downloads/AtlassianClover/Beatles.tgz

It should be rather easy to reproduce.

If confirmed to be a bug, I would in particular like to know

a) the fix schedule

b) if it merely affects the display, but not the numbers.

regards,

 

Michele

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

26 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you