Add optional junit report generation
What does this MR do and why?
I think it would be helpful for gitlab test report adoption to add the ability to generate and upload junit test reports to ci and project templates.
Here is a minimal iteration using a third party library. It's not ideal because it uses a library with many dependencies and a single maintainer and the dependencies should be specified elsewhere in the dependencies section of the cargo.toml file which is the equivlent of a gemfile with some added functionality. It also depends on the test directory.
Anyways, I've made it optional here for these reasons, and I wanted to gather thoughts on outputing junit reports in project and in CI/CD templates.
Example project with ci file: https://gitlab.com/allison.browne/rust-junit/-/blob/master/.gitlab-ci.yml
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.