Test Runner - include failed assertion in error message

[jalovatt]

Is your feature request related to a problem? Please describe.

We've run into some test failures that are environment-dependent - they work fine when viewing Storybook directly or using Test Runner locally, but fail in our CI.

The failure output isn't alwayshelpful, because it doesn't actually tell us what assertion failed.

Describe the solution you'd like

Test Runner's output should include a stack trace and/or snippet of the failed lines, like we get in the live Storybook or Jest. i.e.

Unable to find an element with the text: Update

    109. await userEvent.click(someButton)
--> 110. expect(canvas.getByText('Update')).toBeVisible()
    111. expect(someApi).toHaveBeenCalled()

...HTML output...

I believe the browser has this information, as console errors reference the correct line of code:

...
at play (index.stories.tsx:188:1)
...

but Test Runner's browser logs don't actually include the thrown error.

Describe alternatives you've considered

No response

Are you able to assist to bring the feature to reality?

no

Additional context

No response