Is there any coverage trade off on setting the clover.pertest.coverage=diff ?

Hi, I followed the recommenations for CPU intensive tests mentioned in the http://confluence.atlassian.com/display/CLOVER/Clover+Performance+Tuning#CloverPerformanceTuning-RuntimePerformanceSettings. I would like to know if there's any trade off on using that setting in terms of coverage?

Thanks in advance

Pedro

1 answer

1 accepted

Accepted Answer
0 votes

Hi Pedro,

There's no trade-off in terms of functionality.

There are very subtle differences related with JVM implementations (IBM Java vs Oracle Java vs OpenJDK) regarding threads, locks, volatile variables and data race conditions. You can read "JSR 133: Java Memory Model and Thread Specification Revision" if you like such stuff.

For this reason different strategies have been implemented in Clover, especially for running multi-threaded tests (i.e. when multiple test methods are executed at once; not to be mislead with sequential tests of multi-threaded applications). For example:

  • single-threaded vs multi-threaded per-test recorders
  • using synchronized blocks vs volatile variables

Regards
Marek

Suggest an answer

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

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

287 views 0 6
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