You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release 3.x had the ability to create JUnit reports, so we could replicate this in 4.0.x, the question is do we need to? We've provided the ability to export to JSON for OSS Index and that might be sufficient to pipe to another application that creates junit reports?
The text was updated successfully, but these errors were encountered:
I did some quick Googling and did not see any real clean ways to do JUnit XML format. I wrote it up fairly quickly in #130 , and if the StackOverflow answer on format can be trusted, this should be sufficient.
Someone can take the work from #130 and do auditjs ossi --xml > file.xml and save that file as their test results, I believe. We could create our own file too, but I've kept it simple for now.
Closing this for now as we saw this work in Jenkins when testing. If you have a need to have auditjs save the file for you, please open an issue specific to that!
Release 3.x had the ability to create JUnit reports, so we could replicate this in 4.0.x, the question is do we need to? We've provided the ability to export to JSON for OSS Index and that might be sufficient to pipe to another application that creates junit reports?
The text was updated successfully, but these errors were encountered: