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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

How coverage report is calculated if same code executed as twice

Team,  I am executing the same package files twice. For example my package contains 10 files. I am running sanity and basic test cases against 10 java instrumented files. If I run alone sanity I am getting 25% and run alone basic test case I am getting 25%. In a single shot I am running both sanity + basic test case. Now the code  coverage percentage will be 50% or 25%(because same code is running again). I am getting only 25% code coverage. Can you please give your input why it is giving 25%? 


Thanks in Advance.

2 answers

1 accepted

1 vote
Answer accepted

Are your sanity and basic tests are not mutually exclusive? In other words do they test entirely different parts of your application classes? I'm asking because tests usually overlap each other, thus the summary coverage is usually less than sum of coverage from individual tests.

If you see no difference in coverage after running both sanity and basic tests, then there are two possibilities:

  • you ran tests incorrectly, for instance you have accidentally deleted coverage files from one of tests
  • your sanity and basic tests do not differ at all, i.e. they test exactly the same functionality.


When you ran sanity and basic tests together and generated an HTML report - do you see both sanity and basic test cases on the "Test results" tab? Do you see both sanity and basic test classes on the "Test code" tab?


1 vote

Code coverage is an metric saying that how much of your code is covered by tests. It doesn't matter how many times with how many tests you'll cover one line of you code base, it's still binary metric for that single line (covered or not). The percentage Clover is calculating is basically saying  # lines covered# lines in your instrumented code base

Suggest an answer

Log in or Sign up to answer
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...

171 views 2 9
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