The new v2.9 release of the FuseIT SFDC Explorer has some new features.
Run anonymous apex in a testing context
For some time I've been promoting the idea of being able to run anonymous apex in a testing context. This offered a few benefits.
- The anonymous apex could then call existing apex test methods. They could then be run in isolation.
- Helper methods defined in a test class could be accessed.
- You would be 100% safe from accidentally updating real data in the org. No callouts could occur.
The first point has largely been addressed in The Holy Grail of Apex Testing in Salesforce
To address the other points I've applied the same technique to run anonymous apex in a testing context. This can be access with the "Use Testing Context" check button. With it active, you can do things like access
Improved support for running selected test methods
Individual test methods can now be checked in the asynchronous test results viewer. Pressing the "Run Selected Tests" button will run those tests in isolation.
Fixed the "Open Log" button on the Apex Tests Queued tab. It will now correctly open the log or prompt to create the TraceFlag to capture it for the next run.
Several users reported problems with the 2.7 and 2.8 release with the login process. It would fail with the message:
java.lang.NullPointerException Error Id: 1655897833-5655 (293693299)
This was a Salesforce GACK response from a call to the Metadata API describeMetadata() web method. I'm not sure what causes it for some orgs and not others, but I believe I've isolated it from the login process in our code.