You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the test run, when a function does throw {somePlainObject} (unhandled error), you don't get to see the Serialized Error inside your JUnit reporter, which is really frustrating.
Verbose reporter (works as expected):
JUnit reporter (Unknown Error: undefined):
Suggested solution
It would be beneficial to display a specific error within the JUnit reporter, rather than receiving 'Unknown Error: undefined'.
Additionally, enhancing the XML output by formatting objects and separating expected and actual results with a new line would improve readability.
Clear and concise description of the problem
During the test run, when a function does
throw {somePlainObject}
(unhandled error), you don't get to see the Serialized Error inside your JUnit reporter, which is really frustrating.Verbose reporter (works as expected):
JUnit reporter (Unknown Error: undefined):
Suggested solution
It would be beneficial to display a specific error within the JUnit reporter, rather than receiving 'Unknown Error: undefined'.
Additionally, enhancing the XML output by formatting objects and separating expected and actual results with a new line would improve readability.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: