Pass the full thrown exception to the reporter reportTestDone api

[AriAy-Ded]

What is your Scenario?

I want to see the full stacktrace within my code when a error happens in testcafe.

Given:

• A test fails
• The test uses nested Typescript utility functions/classes

When:

• The exception is printed

Then:

• The exception contains only the stacktrace within the utility class, but the stacktrace does not show the place or function of the calling test
• The exceptions do not contain the full stacktrace,
• investigating is extremely hard.

What are you suggesting?

Pass the full exception(s) to the reporter reportTestDone api.
The passed stacktrace in this API contains testcafe internals, but it is still missing parts that lead to the test that calls utility functions.

What alternatives have you considered?

I tried writing a custom reporter, the error object does not contain the full path.
Videos help in figuring out at what point the test fails, but they are not sufficient.
Additionally i often need to write console.log statements to help figuring out the full stack trace.

none of this is straight forward and requires a lot of extra work every time something fails

Additional context

No response

[Bayheck]

Unfortunately, the priority of this enhancement is quite low, and we won’t be addressing it this time. I’ll be closing this issue.

[AriAy-Ded]

This is not a small issue, it is not possible to see the origin of errors when using utility functions, which is a basic typescript feature

[aleks-pro]

Hello @AriAy-Ded,

Could you please create a simple project that demonstrates the problematic behavior? It will help us better understand your use case.

[AriAy-Ded]

Hi @aleks-pro i created an issue here: #8450, as this is a feature request to be able to create a workaround myself