Apex Code Development You need to sign in to do that
Don't have an account?
mgodsey Test Coverage - 'all tests 0%' but individual methods have percentage (36% and 52%)
I'm having a lot of issues with the developer console when checking test coverage, and I don't know if it is a bug with the console or something wrong with my code.
1) I run the test in the developer console. The Test Run log is not actually showing up unless I completely close the developer console and then re-open it.
2) After running the test (it succeeds), in the overall code coverage box, the class says 100%
3) I double click on the class name in the overall code coverage box and it goes to 0%
4) When I look at the drop down of tests for that class, it shows me the following:
All Tests 0%
Test_QuoteLineITemEntryExtension.testSaveMethods 52%
Test_QuoteLineItemEntryExtension.testControllerWithParameters 36%
Why would it be showing 0% for all tests if individual methods provide coverage? Also, there is no red/blue highlighting in the class to show me what is or is not covered.
Has anyone run into this before? It's driving me crazy! Would be happy to post my test class if that helps. Thanks!
1) I run the test in the developer console. The Test Run log is not actually showing up unless I completely close the developer console and then re-open it.
2) After running the test (it succeeds), in the overall code coverage box, the class says 100%
3) I double click on the class name in the overall code coverage box and it goes to 0%
4) When I look at the drop down of tests for that class, it shows me the following:
All Tests 0%
Test_QuoteLineITemEntryExtension.testSaveMethods 52%
Test_QuoteLineItemEntryExtension.testControllerWithParameters 36%
Why would it be showing 0% for all tests if individual methods provide coverage? Also, there is no red/blue highlighting in the class to show me what is or is not covered.
Has anyone run into this before? It's driving me crazy! Would be happy to post my test class if that helps. Thanks!
This is known issue which has not been fiexed at all the instance. FOr current status and workaround refer following link:
https://success.salesforce.com/issues_view?id=a1p30000000T1m1AAC
All Answers
This is known issue which has not been fiexed at all the instance. FOr current status and workaround refer following link:
https://success.salesforce.com/issues_view?id=a1p30000000T1m1AAC