I have found the solution to this problem, but thought it would be a good idea to post in order to help others AND make a suggestion to the overlords such as @nothingismagick
After adding @quasar/testing to a Quasar project, the jest.setup.js file prevents the stack trace of failed tests being printed to the console with the following line:
// jest speedup when errors are part of the game
Error.stackTraceLimit = 0
Whilst working with Quasar, I have come across several things which are different to stock Vue projects which have cost me a decent amount of time investigating. It seems to me that the most seamless experience for new Quasar users would be to create initial conditions that are as close as possible to those of Vue, and then provide optimisations that require “opting in” by uncommenting the relevant lines.
When you’re used to seeing the exact position of a failed test, to not have that stack trace all of a sudden is a tad disorienting.