Auto Coverage

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

  • Close this issue

Description

As part of Auto DevOps, we should automatically run code coverage. This may not be built into buildpacks, so we might have to augment them somehow. Ideally we'd still leverage buildpack detection so we don't have to duplicate that functionality (and potentially interpret things differently).

Proposal

  • OpenCover might be a possibility for .net coverage
  • GitLab already supports cobertura coverage reports for Test Coverage Visualization, figuring out how to autogenerate / add this to a Java or Ruby project would be a good first step.

Links / references

  • Auto DevOps: https://gitlab.com/gitlab-org/gitlab-ee/issues/2517
  • Auto CI (using Heroku CI): https://gitlab.com/gitlab-org/gitlab-ce/issues/26941

Documentation blurb

Overview

What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?

Use cases

Who is this for? Provide one or more use cases.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

  • Feature assurance
  • Documentation
  • Added to features.yml

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited Aug 28, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading