Timeline for Package test coverage way lower than actual
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:54 | history | edited | CommunityBot |
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
|
|
| Jan 26, 2015 at 10:29 | history | tweeted | twitter.com/#!/StackSalesforce/status/559659275740798976 | ||
| Dec 22, 2014 at 15:32 | vote | accept | Novarg | ||
| Dec 22, 2014 at 15:32 | answer | added | Novarg | timeline score: 3 | |
| Dec 20, 2014 at 8:44 | comment | added | Daniel Ballinger | You can see details about parallel testing in UNABLE_TO_LOCK_ROW error while running all apex test classes. It would need to be combined with exception handling in the test methods to cause an issue. If your false assertions are being hit at the end of the test methods then they are running to completion as expected. Are you able to add a sample of one of your test methods to the question? | |
| Dec 19, 2014 at 13:19 | comment | added | Novarg |
@DanielBallinger normally not. And System.assert(false, 'Boom'); does make upload to fail. Message is One or more Apex tests failed. Resolve the test failures, then upload again., so pretty much as expected I guess. Could you please explain a bit more the running in parallel part please?
|
|
| Dec 19, 2014 at 9:21 | comment | added | Daniel Ballinger |
OK, that is one thing ruled out. Is there anything interesting about your test cases? E.g. Do they have a depandancy on a particular user or custom setting. Could running them in parallel cause issues due to the use of for update? If you put a System.assert(false, 'Boom'); at the end of a test case does it fail as expected in the package uploader. Or put the assertions in the code that should be covered but doesn't appear to be.
|
|
| Dec 19, 2014 at 6:35 | comment | added | Novarg | @DanielBallinger thanks for your comment, but that was pretty much the very first thing I did | |
| Dec 18, 2014 at 19:10 | comment | added | Daniel Ballinger | Try clearing the Test history and then running all the test cases again. You can do this under App Setup > Develop > Apex Test Execution > View Test History and then Clear Test Data. There might be older test run data that is pushing the figure up. The packaging process runs all the included tests from scratch to calculate the coverage. | |
| Dec 18, 2014 at 14:27 | history | asked | Novarg | CC BY-SA 3.0 |