Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Clover reports vary significantly from week to week in total measured coverage

I am using Clover to gather coverage data for test cases that run on our product code that is installed as a part of WebSphere Application Server (WAS). Some of these tests are true unit tests (and call the code being tested directly), but most make EJB calls into WAS to invoke product functions that require the server to be running. In general, this seems to work well (and in fact, it was this ability to handle multiple JVMs running the same instrumented code that drew me to Clover).

In order to handle the large quantity of code, we have broken up the coverage tracking into many pieces. Some are small (100-1000 elements, as reported by Clover)), while others are very large (around 450K elements). We are running a coverage build and test cycle once per week (occasionally sooner), and we save the reports so that we can observe trend data.

The problem is that we are seeing wide fluctuations in the coverage numbers reported from week to week. For example, we had one component that went from

%age classes Elements covered Total elements

5.3% 797 2,356 44,679

to

42% 797 18,768 44,695

while a different component went from

5.2% 115 522 9,981

to

35.9% 115 3,586 9,980

in the span of 5 days. The same tests were all run in both cases (we have the evidence on our CI server that shows the tests run were the same in both cases), and as you can see from the total number of elements, there were minimal code changes between the two.

In another case, we have a component where Clover report generation says that no coverage recordings could be found, but we can clearly see coverage recordings right next to the clover.db file.

How can we get the reports to be more predictable?

1 answer

1 accepted

1 vote
Answer accepted

This is related with a bug which occurs when IBM JRE is used. Clover is unable to find all coverage snapshot files. Bug is reported in https://jira.atlassian.com/browse/CLOV-1151 and will be fixed in the Clover 3.1.8 version.

Clover 3.1.8 was released on 13 Nov 2012.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

146 views 1 8
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you