TestFramework: Add gstest_to_junit_xml.py. #54
Conversation
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
This is currently unused in gnustep-tests, and it is not installed. The intention is to have a representation of tests run under gnustep-tests in the JUnit test report XML format. This is a format ingested and understood by many utilities, so having a way to trigger gnustep-tests to produce it would be beneficial. Ideally, the framework itself would produce much more structured output, that is easier to parse; or it would support creating the .xml natively. The next best thing would be to process tests.log; however, the simplest approach was to process tests.sum. This can then trivially be plugged into gnustep-tests, controlled by an environment variable. The prototype is done in Python 3, specifically under Python 3.11. Switching to Objective-C does not necessarily introduce a dependency loop, as it is perfectly valid to run tests only after GNUstep Base has already been installed. Issue: gnustep#53 Bug: 53
|
I detest the bloated nature of junit, but I do recognise that it's widely used/supported, and that feeding test results into external tools could be useful, so I don't see any problem with this approach. |
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 is currently unused in gnustep-tests, and it is not installed. The intention is to have a representation of tests run under gnustep-tests in the JUnit test report XML format. This is a format ingested and understood by many utilities, so having a way to trigger gnustep-tests to produce it would be beneficial.
Ideally, the framework itself would produce much more structured output, that is easier to parse; or it would support creating the .xml natively. The next best thing would be to process tests.log; however, the simplest approach was to process tests.sum. This can then trivially be plugged into gnustep-tests, controlled by an environment variable.
The prototype is done in Python 3, specifically under Python 3.11. Switching to Objective-C does not necessarily introduce a dependency loop, as it is perfectly valid to run tests only after GNUstep Base has already been installed.
Issue: #53
Bug: 53