chore(tests) use bats junit direct exporter to get rid of NodeJS and NPM
#344
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
Signed-off-by: Damien Duportal <damien.duportal@gmail.com>
…NPM) Signed-off-by: Damien Duportal <damien.duportal@gmail.com>
dduportal
changed the title
bats junit direct exporter to get rid of NodeJS and NPM
MarkEWaite
approved these changes
Nov 13, 2023
6 tasks
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.
Since v1.6.0, the CLI
batsis able to export the test results directly to junit format.It's a good opportunity to get rid of both NodeJS and NPM from this repository which were only used to export results from the default TAP fomrat to Junit.
Note this PR bumps
batsfrom1.7.0to1.10.0to benefit from the formatter bugfixes and ensure Junit format errors.We can close unneeded PRs around NodeJS/NPM:
Closes #342
Closes #324
Testing done
targetcontains Junit XML results