Missing stack trace when test fails since 14/01 release

[PawelWozniak]

Summary

CLI human output format has changed after 14 January release. It is definitely step in good direction as it is more readable but is missing stack trace or a least line where error occurred (most top entry from stack trace).

Steps To Reproduce:

Run test class that fails with some error.

Expected result

I can see in CLI output at which line it failed.
Example Class.testUpdateAccountID.UpdateAccountID: line 48, column 1

Actual result

It show error message but I don't know where it failed.

Additional information

SFDX CLI Version sfdx-cli/7.84.2-a2868a68d5 win32-x64 node-v12.18.3
OS and version:Windows 10

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[jamessimone]

Also suffering from this change. In addition to the stacktrace not appearing - not even the line where the failure occurred, just the message! - this issue is exacerbated by an enormous change in the behavior of the VS Code extension: previously, when tests failed, the Output panel would pop up automatically with the contents of the failure message; there was also a pop-up information status that would tell you that the tests had failed. Now, the only thing that happens when the tests finish running is a message in the status bar: "Run Apex Tests successfully ran." It's possible that the lack of feedback in VS code is directly related to the issue with the stacktrace, which is why I mention it here. The combination of both of these issues has made testing a frustrating experience over the past few days.

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[AndrewRayCode]

The previous working version of sfdx also used to show the test command being run so that you could copy it into a terminal and tweak the command line flags. That is no longer being shown either.

See also #718. I'm not sure if you can turn off auto updating for the vscode plugin's version of sfdx?

[PawelWozniak]

Closing as this is not valid anymore.