3 ms·
GitLab PM here. Great point on #2 about the regex. We have an open issue (https://gitlab.com/gitlab-org/gitlab/-/issues/21549 https://gitlab.com/gitlab-org/gitl
by jamesh-gl 6y ago
GitLab PM here. Great point on #2 about the regex. We have an open issue (https://gitlab.com/gitlab-org/gitlab/-/issues/21549 https://gitlab.com/gitlab-org/gitlab/-/issues/21549) to parse more data from an uploaded coverage report and coverage percentage seems like a great first step so you don't have to mess around with the regex.
-James H, GitLab Product Manager, Verify:Testing
- weitzj 6y agoIt would be fine if you could for example pick up cobertura reports or maybe some other coverage formats (Golang reports, Xcode coverage reports) I know I can do this with all my Jenkins plug-ins. And maybe GitLab does not want to do all of this and people should use Sonarqube instead. But it is hard to go to GitLab when I have seen the light with Jenkins.
- jamesh-gl 6y agoCobertura is the first target report since it's the format that's supported by the Test Coverage Visualization feature (https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html https://docs.gitlab.com/ee/user/project/merge_requests/test_...). I'll make sure the other report types are on our list of future iterations as well. Thanks! -James H, GitLab Product Manager, Verify:Testing