-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
junitxml: incorrect tagging of import errors #575
Labels
type: bug
problem that needs to be addressed
Comments
Original comment by Oleg Sinyavskiy (BitBucket: otognan, GitHub: otognan): Also, if you ignore this assert on errors, xunitparser failes in the next assert because number of tests in the header is kind of wrong: there are 174 tests, but there are 176 elements in the xml (174 successes and failures) + 2 failures that are supposed to be errors. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: Oleg Sinyavskiy (BitBucket: otognan, GitHub: otognan)
Hello,
There are two kinds of failures you can get running py.test - "failure" and "error".
When you have import errors, it supposed to be an "error" instead of "failure.
However junit xml is inconsistent distinguishing those.
I ran py.test on my suite and I've got 2 import errors and 2 pep8 failures. Here is a junit xml header:
However import error files are still tagged as "failures" instead of "errors":
This bug shows up itself during parsing with https://pypi.python.org/pypi/xunitparser.
It has an assert:
which check if header summary is consistent with parsed tests descriptions.
The text was updated successfully, but these errors were encountered: