function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

improper order of stack trace in test failures

I am seeing the following table below in the test result web page of our sandbox.  The interesting thing to note is that the stack trace that is given is incorrect. The second line of the stack trace should be the third line, if the trace is moving from newest to oldest.

This is consistently wrong whenever I get a stack trace in the test result page.  I would post a case on this, but I am getting an error that the self-service portal is down for my account.

Is anyone else seeing this?

TypeNameMethod NameTotal time (ms)MessageStack Trace
 ClassAccountUtiltest_updateAcvsFor_from_forDate535System.NullPointerException: Attempt to de-reference a null objectClass.AccountUtil.totalAcv: line 56, column 20
Class.AccountUtil.test_updateAcvsFor_from_forDate: line 95, column 38
Class.AccountUtil.updateAcvsFor_from_forDate: line 6, column 29