I did the following:
I do not see coverage. I can confirm that no file is created in the .clover directory.
In order to get coverage, I have to change the Flush Policy. It doesn't matter what I change it to -- I just have to change it, then rebuild when prompted. When I do that, coverage shows up.
Then once I have coverage that shows up, when I click (disable) the "Toggle build with Clover" button, it is still compiling with instrumented code. So I get this compilation error in every instrumented class:
Error:(121, 2835) java: package com_atlassian_clover does not exist
The only way to get rid of this error is to change the Flush Policy (doesn't matter to what, I just have to change it). Incidentally, when I do this, I still see red/green/gray code highlights and gutter marks, even though the code is not instrumented.
FWIW, my settings are:
Preferences -> Clover (project settings)
Check "Enable Clover"
InitString --> Automatic
Flush Policy --> (doesn't matter)
Check "Instrument test source folders..."
Instrument lambda functions --> none
Rebuild Policy --> Ask
Refresh policy --> Manual
General --> Check "Show source highllights"
Per-test Coverage Data --> Check "Load per-test coverage data..."
Preferences -> Build, Execution, Deployment -> Compiler
Uncheck "Compile independent modules in parallel"
Atlassian community, Today is a major day not only for Statuspage, but also for the Atlassian community. Statuspage continues to be the industry leader for incident communication by constantly look...
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