-
Notifications
You must be signed in to change notification settings - Fork 111
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 log errors #85
Comments
@MRolandd currently jest does not differentiate between an "error" and a "failure" so currently that portion is unused. It's a feature I've wanted to add to jest for a while and eventually will do - it's a bit complex of a change in jest to make that happen. |
Ok, then it is a way to parse syntax errors from the code as failures? If I have a syntax error my log file is empty. Just with an empty testsuites |
Well syntax errors and other non-recoverable errors like this result in jest not even successfully parsing the test file. So, in this case, a reporter (any reporter) wouldn't get enough useful information to be able to generate a report. jest-junit, in particular, would need to know the describe and/or it block names otherwise we'd be reporting on failures/errors on some generated id and you might not be able to make a connection to the actual test file. |
Thank you for your reply. It really helped about this issue. |
How to display syntax errors in Junit log? Or exactly how does the
<error>
tag appear? If I fail a test it is a<failure>
.In PHP unit the
<error>
tag appears when There is a syntax errorThe text was updated successfully, but these errors were encountered: