August 9, 2021 - I have a monorepo with several packages. Unit-tests and coverage are run separately for each of packages, but within one CI job. In the end I export multiple cobertura XML files from my job: artifacts: reports: cobertura: 'packages/{package1,package2}/coverage/cobertura-coverage.xml' But then ...

The .gitlab-ci.yml looks something like this: Copytest_c: stage: test coverage: '/TOTAL\s+\d+\s+\d+\s+(\d+%)/' script: - ./test_script_c.sh artifacts: reports: coverage_report: coverage_format: cobertura path: build/tests/c/CoberturaCoverageScripts.xml test_python: stage: test coverage: '/TOTAL\s+\d+\s+\d+\s+(\d+%)/' script: - ./test_script_python.sh artifacts: reports: coverage_report: coverage_format: cobertura path: build/tests/python/CoberturaCoverageScripts.xml test_java: stage: test coverage: '/TOTAL\s+\d+\s+\d+\s+(\d+%)/' script: - ./test_script_java.sh artifacts: reports: coverage_report: coverage_format: cobertura path: build/tests/java/CoberturaCoverageScripts.xml

September 24, 2021 - In the doc https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html it’s said You can specify one or more coverage reports to collect, including wildcard paths.

September 25, 2023 - Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

... Add the coverage keyword to your job with a regular expression that matches your test tool’s output: test: script: - pytest --cov coverage: '/TOTAL.*? (100(?:\.0+)?\%|[1-9]?\d(?:\.\d+)?\%)$/' To aggregate coverage from multiple jobs, add the coverage keyword to each job.

artifacts: reports: coverage_report: coverage_format: cobertura path: coverage/cobertura-coverage.xml · You can generate multiple reports and collect them using wildcards.

June 28, 2021 - Combined test coverage for a repository (not in the context of an MR) I am aware of a feature in an MR which marks combined code coverage https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html My repo does have multiple cobertura coverage reports being generated Do I have the ability to see the combined coverage for the repo outside the MR context, while I browse the repo on master branch?

March 2, 2023 - For the test coverage format, we chose cobertura because it is compatible with Gitlab CI/CD and because of the available cobertura-merge library for creating aggregated coverage reports.

July 8, 2022 - Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Sign in to GitLab · By signing in you accept the Terms of Use and acknowledge the Privacy Statement and Cookie Policy · Don't have an account yet? Register now · or sign in with · Remember me · Explore Help About GitLab GitLab community forum · English · 简体中文 · 日本語

March 10, 2019 - This instructs coverage to write its results not into one file, .coverage, but into multiple, named .coverage.<hostname>.<pid>.<randomnumber> — meaning you get separate results files for each coverage run. Subsequently, you can combine your coverage data with coverage combine, and then do whatever you like with the combined data (coverage report, coverage html, etc.). Now there’s a bit of a difficulty with GitLab CI, which is that your individual tox testenvs will all run in completely different container instances.

# Gitlab CI configuration with PHP Code Coverage HTML report · # We merge multiple suits coverage reports and save those for download · # · stages: - test · · cache: # cache per-job and per-branch · key: "$CI_BUILD_NAME/$CI_BUILD_REF_NAME" paths: - vendor/ ·

GitLab uses CI/CD's artifacts reports feature to collect the coverage information. You can specify one or more coverage report to collect, including wildcard paths. This change should be applied into the .yml file. For the coverage analysis to work, you have to provide a properly formatted ...

You can specify one or more coverage reports to collect, including wildcard paths. GitLab then takes the coverage information in all the files and combines it together.

April 28, 2020 - Following the docs, I’ve enabled the flag in the console: Feature.all.map {|f| [f.name, f.state]} => [["multiple_merge_request_assignees", :on], ["coverage_report_view", :on]] Looking at the job logs I have confirmed that the report xml is generated, and that it’s also specified in the ...

December 24, 2021 - self-hosted Omnilbus Docker 13.12.3 ... but I think I might know why…) that, per the page at how-test-coverage-visualization-works, multiple Cobertura formatted XML reports can be uploaded as is, and that Gitlab will properly aggregate them for display in the MR diffs ...

Coverage reporting extracts a percentage from your test tool’s job log output. You define a regular expression in the coverage keyword.

You can specify one or more coverage reports to collect, including wildcard paths. GitLab then takes the coverage information in all the files and combines it together.

test: script: - run tests with coverage artifacts: reports: coverage_report: coverage_format: cobertura # or jacoco path: coverage/coverage.xml ... To collect multiple reports, use a wildcard in the artifact path.