For large projects, split the Cobertura XML into If your Cobertura report exceedsġ00 nodes, there can be mismatches or no matches in the merge request diff view.Ī single Cobertura XML file can be no more than 10 MiB. LimitsĪ limit of 100 nodes for Cobertura format XML files applies. Test coverage results in merge requests.Uploading a test coverage report does not enable: Hovering over the coverage bar provides further information, such as the number no coverage information: lines which are non-instrumented or not loaded.no test coverage (orange): lines which are loaded but never executed.covered (green): lines which have been checked at least once by tests.This includes reportsįrom any job in any stage in the pipeline. Other coverage analysis frameworks support the format out of the box, for example:Īfter configuration, if your merge request triggers a pipeline that collects coverage reports, the coverage information is displayed in the diff view. This format was originally developed for Java, but most coverage analysis frameworksįor other languages have plugins to add support for it, like: Coverage files are parsed in a background job so there can be a delayīetween pipeline completion and the visualization loading on the page.įor the coverage analysis to work, you have to provide a properly formatted GitLab then takes the coverage information in all the files and combines it You can specify one or more coverage reports to collect, including wildcard paths. To see which lines are covered by tests, and which lines still require coverage, before theĬollecting the coverage information is done by using the GitLab CI/CD This information inside the file diff view of your merge requests (MRs). With the help of GitLab CI/CD, you can collect the testĬoverage information of your favorite testing or coverage-analysis tool, and visualize
0 kommentar(er)
