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

Cleaning coverage data from clover

I need to clear the information on code coverage, I know it can be done by restart server, but this solution does not really fit me, Is it possible to do it differently?

1 answer

1 accepted

0 votes
Answer accepted

Resetting hit counters at runtime is not possible right now.

Do you have any use case where such resetting of hit counters would be useful?

yep, if i would like to create new report with 0% code coverage, if i want run my tests again

I assume that you'd like to run your tests again, because you have changed something in your application, isn't it? If yes, then it means that application must be rebuilt it and new clover.db has to be copied to the application server. And because of fact that application is re-deployed it means that Clover's coverage recorders will be restarted as well.

Marek, does your answer mean that there is no ability to have clover generate historical coverage reports when the code being tested is being changed constantly? After all, whenever we rebuild our code, we generate a new set of clover.db files. Your answer indicates to me that Clover's only historical ability is when you have new/changed tests, not new/changed product code being tested. If that is true, then the historical abilities are completely useless for us (we have at least a dozen change sets going into our build every day).

@jimbabka: I think you've misunderstood my answer.

I wrote that it is not possible to nullify hit counters at runtime (i.e. when an application is running) programatically (like the inline "///CLOVER:FLUSH" directive which allows to flush data to disk).

It is of course possible to restart the application (or server) and start recording again.

Clover historical report is a different feature. It requires history snapshot file, which contains zipped XML coverage report. Historical report compares these XML files (and not clover.db files). So it is of course possible to compare builds between each other - and there's no difference whether application classes or test classes were modified.

Cheers
Marek

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Happy New Year and Welcome New Marketplace Partner Program Partners!

Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...

439 views 5 16
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