-
Notifications
You must be signed in to change notification settings - Fork 9
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
Inconsistency in root level element in JUnit format #46
Comments
bryanbcook
added a commit
to bryanbcook/test-results-parser
that referenced
this issue
Feb 13, 2024
bryanbcook
added a commit
to bryanbcook/test-results-parser
that referenced
this issue
Feb 13, 2024
@ASaiAnudeep - can you accept this PR (#47) and publish a new release, please? |
ASaiAnudeep
pushed a commit
that referenced
this issue
Feb 14, 2024
* Added failing test * implementation for junit top-level suite #46
@ASaiAnudeep Thanks for merging the PR. How do we create a release for 0.1.7? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that there are several different implementations of the JUnit xml format. The root element is either a
<testsuites>
that contains a collection of<testsuite>
elements, or a single<testsuite>
.As per bryanbcook/azdevops-testplan-extension#16, there appears to be two conflicting schemas:
<testsuites>
as a root node. This is the format used by the testparser project<testsuites>
or<testsuite>
as the root node.There is also an issue in this repo for #40 which doesn't have any details.
The text was updated successfully, but these errors were encountered: