-
Notifications
You must be signed in to change notification settings - Fork 15
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
Handle --log-junit
option
#207
Comments
It seems that JUnit logs can be uploaded with glob patterns to GitLab! 🎉 This would simplify a lot the feature, because I could accept a directory name as the value of the option, and generate the filename automatically, without having to merge the result. |
following |
👋 Hi @Jean85 I added a MR with my implementation of this for the version 1.x.
My MR does this exactly creates generated filenames based on the file provided as a parameter. 😄 |
Seemed interesting, thank you. I'm not sure I'll be implementing the merge of the XML files though, at least at first. That's because for my use case (GitLab) multiple files are fine too. For which use case do you need one single file? |
Not a specific use case, I just did not knew that Gitlab had the artifacts_reports option 😄 but anyway problem solved. |
The
--log-junit
would be pretty useful to report tests to various systems, including the GitLab CI Unit Test Report: https://docs.gitlab.com/ee/ci/testing/unit_test_reports.htmlThis option is not feasible as a pass-through one, because it would produce multiple files, and also because there's no way to produce different files with different names for each executed test class.
This feature would mirror the coverage one, with the hijacking of the native PHPUnit option, and the merging of the resulting files. The merge would have to be written as a feature, but would be pretty straightforward, see https://github.com/drazisil/junit-merge/blob/master/lib/index.js
The text was updated successfully, but these errors were encountered: