Check JUnit and XUnit against the XSD schemas #3154
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seberm
added
command | tests
seberm
requested review from
psss,
lukaszachy,
happz,
thrix and
janhavlin
as code owners
seberm
force-pushed
the
feature/check-junit-against-schema
branch
from
119957c
to
4901812
Compare
seberm
force-pushed
the
feature/check-junit-against-schema
branch
from
4901812
to
da84c2f
Compare
|
I think we can close this PR because the schema check will be done directly (dynamically) by tmt junit report plugin (#3150). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds tests for checking XML schemas of JUnit and XUnit generated by
junitandpolarionreport plugins. The XSD schemas are purposely limited only to currently supported features (tags/attributes) by these report plugins.The plan is probably to check these schemas dynamically directly by TMT for every supported junit flavor in the future.
This PR is highly related to #3150 because I need better test coverage, especially for the
xunit.xml(output of the Polarion report plugin) - probably this will be obsoleted by tests in #3150 - Schema check is done directly in tmt.Pull Request Checklist