-
Notifications
You must be signed in to change notification settings - Fork 370
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
Fix build log parser failed test list #2077
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hakonsbm Thanks for this! A few questions:
- Should we add a version requirement to junitparser in the right places?
- Have you tested this by breaking a few tests?
- Are we sure we will only ever need element [0] from the list?
Done!
Yes, to find out what caused this I had to break a few
Right now it seems like each testcase always give at most one result and skipped tests give exactly one result. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one suggestion for an additional protection against additional result elements.
Minimal but important fix to test reporting, therefore merging based on single review. |
Resolves #1945 by updating the
summarize_tests.py
script forjunitparser
version 2.0. With version 2.0 ofjunitparser
case.result
is changed to a list. This caused skipped tests to not be detected as skipped, and therefore added to the list of failing tests which is printed if any other tests fail.