debian-mirror-gitlab/doc/user/group/repositories_analytics/index.md

type	stage	group	info
reference	Verify	Testing	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments

Repositories Analytics (PREMIUM)

Introduced in GitLab 13.4.

Current group code coverage

Introduced in GitLab 13.7.

The Analytics > Repositories group page displays the overall test coverage of all your projects in your group. In the Overall activity section, you can see:

• The number of projects with coverage reports.
• The average percentage of coverage across all your projects.
• The total number of pipeline jobs that produce coverage reports.

Average group test coverage from the last 30 days

Introduced in GitLab 13.9.

The Analytics > Repositories group page displays the average test coverage of all your projects in your group in a graph for the last 30 days.

Latest project test coverage list

Introduced in GitLab 13.6.

To see the latest code coverage for each project in your group:

1. On the top bar, select Menu > Groups and find your group.
2. On the left sidebar, select Analytics > Repositories.
3. In the Latest test coverage results section, from the Select projects dropdown list, choose the projects you want to check.

You can download code coverage data for specific projects using code coverage history.

Download historic test coverage data

Introduced in GitLab 13.4.

You can get a CSV of the code coverage data for all of the projects in your group. This report has a maximum of 1000 records. The code coverage data is from the default branch in each project.

To get the report:

1. On the top bar, select Menu > Groups and find your group.
2. On the left sidebar, select Analytics > Repositories.
3. Select Download historic test coverage data (.csv).
4. Select the projects and date range you want to include in the report.
5. Select Download test coverage data (.csv).

The projects dropdown shows up to 100 projects from your group. If the project you want to check is not in the dropdown list, you can select All projects to download the report for all projects in your group, including any projects that are not listed. There is a plan to improve this behavior in this related issue.

For each day that a coverage report was generated by a job in a project's pipeline, a row in the CSV includes:

• The date the coverage job ran
• The name of the job that generated the coverage report
• The name of the project
• The coverage value

If the project's code coverage was calculated more than once in a day, the last value from that day is used.

NOTE: In GitLab 13.7 and later, group code coverage data is taken from the configured default branch. In earlier versions, it is taken from the master branch.