function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
JayNicJayNic 

Test runs do not record results. New release? New broken developer console!

Hi all,

With the new release of the new developer console: they've broken something else. It appears that running tests from the developer console does not record any rest results.

The only way to get updated code coverage is by running tests from the Apex Test Execution page - which I'm sure will be taken away soon... Anyone know of any work around?

Here is the proof:
http://screencast.com/t/BB3TGw0cSK

In the video I do the following:
1) Run the test class from the developer console.
2) Examine the Overall Code Coverage section to show there is no coverage on the tested class
3) Examine the intended tested class from the developer console to see there is no coverage
4) Navigate to the apex test execution page, and run the same test
5) Navigate back to the developer console to show the test now displays correct coverage

I'm in a developer org, so I can't make a case (we're not worthy of support) so if anyone else cares to: please use my post, and video as evidence
Best Answer chosen by JayNic
Andy BoettcherAndy Boettcher
JayNic - there appears to be a Known Issue around this.  Read this and see if it helps you workaround the issue for now:  https://success.salesforce.com/issues_view?id=a1p30000000eMoyAAE

All Answers

Andy BoettcherAndy Boettcher
Well look at that.  Just running the "Run Test" from my DE as well doesn't bring back any code coverage on a class I'm 100% sure has coverage.  I ran tests through Mavensmate and yup, coverage.

Hopefully a Salesforce employee here can catch this thread....
Andy BoettcherAndy Boettcher
BTW I posted this thread out on #askforce for some additional exposure.
Andy BoettcherAndy Boettcher
JayNic - there appears to be a Known Issue around this.  Read this and see if it helps you workaround the issue for now:  https://success.salesforce.com/issues_view?id=a1p30000000eMoyAAE
This was selected as the best answer
JayNicJayNic
Thanks Andy. Looks like I can just use asychronous for now.