Code Coverage - Needs to run twice
For some reason, after running any number of tests, I need to go to "Analyze > Show Coverage Data..." twice. The first time, it comes up with the selection for which coverage would I like, I select the test, then it does nothing. The second time, it comes up with the selection for which coverage, I select the test, and then it works like it used to - the line-by-line and the class-by-class coverage is displayed as expected. I'm not sure where to start on this one so I'll wait for a response asking for whatever kind of contextual info may be relevant. For starters:
IDEA 2016.3 mac OS 10.11.4 El Capitan on a MBP retina. FWIW, I've cranked up the heap size on Intellij to nearly 2GB. Doubt that's relevant but just in case it is...
Comments (9)
-
reporter -
repo owner I noticed this after updating to 2016.3 as well. I'm going to look into it very shortly. Must be some minor behavioral change in the plugin SDK. Thanks for the report!
Oh, and glad you enjoyed the presentation and the plugin!
-
reporter @RoseSilverSoftware , btw, in regards to the code coverage tool, you know how when you click/key show coverage data, it comes up with a small dialog asking which coverage I want to show? There's only ever one option it it seems like there should be a way to default it to the only option I have instead of either using the mouse or an awkward set of arrow keys, space key, tab key, return key...it's kinda weird. I've searched around but didn't find anything. Thanks!
-
reporter oh snap just found it. Sorry and never mind! it was right in front of my face in the documentation!
https://www.jetbrains.com/help/idea/2016.3/configuring-code-coverage-measurement.html
-
repo owner Glad you found that. Yeah, coverage is pretty much an IntelliJ IDEA feature that I've extended to know about the coverage data available via the Salesforce API and how that maps to local source files.
-
repo owner I think I just figured out why it's doing this and found a fix for it. I'll need to test it across multiple versions of the IDE, but it looks promising so far.
-
repo owner -
assigned issue to
- changed version to 1.7.5.8
-
assigned issue to
-
repo owner - changed status to resolved
Delivered in 1.7.5.8.
-
repo owner - changed component to Apex Unit Testing
- Log in to comment
BTW, great presentation at DF16 a couple months back - that's what introduced me to your plugin - great stuff!