Coverage report generation doesn't include Apex classes when the project/module has a namespace

[Scott Wells]

Yesterday a user pointed out that his exported coverage report only included triggers, and upon a bit of investigation it's because the project/module is configured for a namespace. I've already fixed this locally and will include it in the next build, but I want to make sure there's an issue to cover it.

If anyone wants early access to the fix, let me know and I can either post it here or, if there's enough interest, just post an intermediate official release with just this fix.

[Scott Wells]

This is the same as 2.1.4.2 but with fixes for the namespace report generation issue and another issue where local covered types with the same name as system types, e.g., Field, could end up with the wrong class in the report.

You can try it by downloading (but not extracting) the archive and installing it using Settings/Preferences>Plugins>Install plugin from disk (under the gear drop-down menu). If you do, please let me know whether it resolves these issues for you properly.

[Scott Wells]

Delivered in 2.1.4.3.