@TestSetup method not handled properly when running unit tests against org with namespace

[Scott Wells]

A user has reported an issue with 2.3.2.0 where an Apex unit test class with a @TestSetup method is not running using the async endpoint and therefore its @TestSetup method is not being properly reported as it is via the sync endpoint. This occurs only in an org with a namespace. I’ve reproduced this locally and it’s due to a map lookup via a qualified test class name missing when the unqualified name would resolve properly.

I’m attaching a test build here so that the user can help confirm the fix before including it in an official build.

[Scott Wells]

This is a test build that is 2.3.2.0 with a prospective fix for this issue. Please download (but don't extract) the attached archive and install it using Settings | Plugins | Install plugin from disk (under the gear drop-down menu), the restart the IDE, disable the Always run test async option, and see whether the problem is resolved or not.

[Hagai Shatz]

Thanks - I can confirm that the fix solved the issue.

[Scott Wells]

Thank you, both for confirming and for reporting the issue. Apologies for the testing oversight in the first delivered version of these changes.

[Scott Wells]

Delivered in 2.3.2.1.