Skip to content
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

Update JUnit XSD to support additional data #83

Open
codito opened this issue Jun 24, 2024 · 0 comments
Open

Update JUnit XSD to support additional data #83

codito opened this issue Jun 24, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request logger: junit JUnit test logger issues

Comments

@codito
Copy link
Contributor

codito commented Jun 24, 2024

Current JUnit schema used by JunitXml.TestLogger is several years old. Here are the various formats used today.

  • Jenkins Junit plugin docs are here. JUnit 5 project uses the Jenkins XSD from there.
  • Gitlab JUnit parser (see attached junit example from issue) and CircleCI have added few additional elements to the schema for better reporting (reference). E.g. file in testcase element
  • Testmo provides a comparison of various possibilities in the schema here.

Proposal

Work In Progress. Kindly share your inputs.

Support a Schema logger configuration with one of junit, jenkins. Few differences:

  • jenkins allows non-empty properties node
  • jenkins allows per test case system-out/err messages
  • jenkins may be better suited for attachments support?

TODO: review if there any other differences between both?

Future

If needed, we can extend the ReportFormat=custom add the following capabilities

Related issues

@codito codito added enhancement New feature or request logger: junit JUnit test logger issues labels Jun 25, 2024
@codito codito self-assigned this Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request logger: junit JUnit test logger issues
Projects
None yet
Development

No branches or pull requests

1 participant