Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUnit reporter: ‘Unknown Error: undefined’ #5603

Closed
4 tasks done
andrii-nastenko opened this issue Apr 23, 2024 · 0 comments · Fixed by #5629
Closed
4 tasks done

JUnit reporter: ‘Unknown Error: undefined’ #5603

andrii-nastenko opened this issue Apr 23, 2024 · 0 comments · Fixed by #5629
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)

Comments

@andrii-nastenko
Copy link

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):
Screenshot 2024-04-23 at 18 22 22

JUnit reporter (Unknown Error: undefined):
Screenshot 2024-04-23 at 18 23 32

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

@sheremet-va sheremet-va added p3-minor-bug An edge case that only affects very specific usage (priority) and removed enhancement: pending triage labels Apr 24, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)
Projects
None yet
2 participants