-
Notifications
You must be signed in to change notification settings - Fork 53
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
Junit xml format output #130
Conversation
One note, this will not work properly if you run the application using I am coming around to writing a file (still don't want to do it, but I can't control totally how auditjs is executed), any input? |
@ajurgenson55 gave this a quick once over in Jenkins and it appears to work. Merging and then I'll handle any issues that come up in the future. |
## [4.0.1-beta.11](v4.0.1-beta.10...v4.0.1-beta.11) (2020-01-23) ### Bug Fixes * Junit xml format output ([#130](#130)) ([7e26c6c](7e26c6c))
## [4.0.1-alpha.15](v4.0.1-alpha.14...v4.0.1-alpha.15) (2020-01-23) ### Bug Fixes * add logging ([50654b7](50654b7)) * got out of whack, fixing releaserc ([58b5945](58b5945)) * Junit xml format output ([#130](#130)) ([2a10a77](2a10a77)) * muncher validation ([#133](#133)) ([0686b61](0686b61)) * note node version supported ([0f13acc](0f13acc)) * straight to alpha, address running without commands ([e1a9fc5](e1a9fc5)) * uppercase fix ([4c65ebd](4c65ebd))
🎉 This PR is included in version 4.0.1-alpha.15 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Quick lil ditty to output things in a JUnit xml format.
Format stolen from: https://stackoverflow.com/questions/4922867/what-is-the-junit-xml-format-specification-that-hudson-supports
Introduces an
xmlbuilder
library.Output looks like so when ran against
auditjs
:Right now I've created a testcase for every dependency, and version via the purl, and then added failures with the results of what failed (title and description for now). This will show as a lot of testcases (dependent on your project), and show vulnerable deps as failed test cases.
To test:
auditjs ossi --xml > file.xml
and that file.xml could be saved as testresults in Jenkinsauditjs
output to XML worked slightly differently, I think I dig this way more? Would love to hear others feedback.Fixes #115
CC @ajurgenson55 @allenhsieh @ken-duck