Add support for NUnit v3 XML results files#225
Merged
jozefizso merged 7 commits intodorny:mainfrom Jun 25, 2024
Merged
Conversation
stopiccot
reviewed
May 19, 2023
Collaborator
|
I would suggest rebasing these changes onto |
Contributor
Author
|
@jozefizso I'm just updating it for my own use, since there didn't seem to be a huge amount of interest in merging it. But if that's changed I can do the rebase. |
|
Is this coming soon? |
jozefizso
requested changes
Jun 25, 2024
jozefizso
approved these changes
Jun 25, 2024
Collaborator
|
Thanks a lot for this PR @kring! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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 is important for displaying the results generated by the Unity Test Framework, among probably other uses. It builds on the work started in the https://github.com/dorny/test-reporter/tree/dotnet-nunit branch.
I struggled a little bit with how to translate the format's arbitrarily-nested suites to the test-reporter's suite, group, test structure. In the end I made the last suite before the test case the "group", and flattened any suites above that into a single suite. Except that it ignores suites of type "Theory". So basically test fixtures (classes) will be groups, and assemblies/projects will be suites. Other things are definitely possible.
Fixes #98