Get coverage data for all projects in a group to download (#215104) · Issues · GitLab.org / GitLab

Get coverage data for all projects in a group to download

Problem to solve

As a development team lead, I want a single page of code coverage data for my group's projects, so I can quickly get the test coverage data Dakota is asking for and get back to work.

Dakota is using this data to show that directionally the code coverage measure is improving for the group.

Intended users

Delaney (Development Team Lead)

Further details

Delaney needs to get the data for all projects that belong to the group they manage without implementing an API integration or doing it manually.

Proposal

At the group page: create a new Analytics -> CI/CD page.
Add to this page a download button.
- The download button will get all coverage data for each project in the group
The Provided CSV will includes:
- Date coverage was calculated (at most once per day, take last calculated number on a given day)
- Project Name
- Job name coverage came from (there may be multiple per project) from the default branch
- Coverage value

example:

Date	Project Name	Job Name	Coverage
2020-04-21	myProject	myJobRspec	89.05%
2020-04-21	myProject	myJobKarma	34.05%
2020-04-21	myOtherProject	myOtherJobRspec	89.05%
2020-04-21	myOtherProject	myOtherJobKarma	34.05%
2020-04-20	myProject	myJobRspec	85.55%
2020-04-20	myProject	myJobKarma	30.05%
2020-04-20	myOtherProject	myOtherJobRspec	89.05%
2020-04-20	myOtherProject	myOtherJobKarma	34.05%
2020-04-19	myProject	myJobRspec	81.75%
2020-04-19	myProject	myJobKarma	30.01%
2020-04-19	myOtherProject	myOtherJobRspec	89.05%
2020-04-19	myOtherProject	myOtherJobKarma	34.05%

note: % sign in last column is optional

@jj-ramirez has provided the full design for this page attached to this issue. This issue is capturing the work for the button and new page only.

Permissions and Security

Any user should be able to get to this page / download the data.

Documentation

Create documentation for this feature.

Availability & Testing

What does success look like, and how can we measure that?

See the parent epic.

What is the type of buyer?

Dakota - The Application Development Director is the buyer for this feature.

This will be built for GitLab Premium

Is this a cross-stage feature?

This iteration will not be cross-stage

Links / references

### Problem to solve

As a development team lead, I want a single page of code coverage data for my group's projects, so I can quickly get the test coverage data [Dakota](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/#dakota---the-application-development-director) is asking for and get back to work.

Dakota is using this data to show that directionally the code coverage measure is improving for the group.

### Intended users

* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)

### Further details

Delaney needs to get the data for all projects that belong to the group they manage without implementing an API integration or doing it manually.

### Proposal

* At the group page: create a new Analytics -> CI/CD page.
* Add to this page a download button.
  * The download button will get all coverage data for each project in the group
* The Provided CSV will includes:
  * Date coverage was calculated (at most once per day, take last calculated number on a given day)
  * Project Name
  * Job name coverage came from (there may be multiple per project) from the default branch
  * Coverage value

example:

| Date | Project Name | Job Name | Coverage |
| ------ | ------ | ------ | ------ |
| 2020-04-21 | myProject | myJobRspec | 89.05% |
| 2020-04-21 | myProject | myJobKarma | 34.05% |
| 2020-04-21 | myOtherProject | myOtherJobRspec | 89.05% |
| 2020-04-21 | myOtherProject | myOtherJobKarma | 34.05% |
| 2020-04-20 | myProject | myJobRspec | 85.55% |
| 2020-04-20 | myProject | myJobKarma | 30.05% |
| 2020-04-20 | myOtherProject | myOtherJobRspec | 89.05% |
| 2020-04-20 | myOtherProject | myOtherJobKarma | 34.05% |
| 2020-04-19 | myProject | myJobRspec | 81.75% |
| 2020-04-19 | myProject | myJobKarma | 30.01% |
| 2020-04-19 | myOtherProject | myOtherJobRspec | 89.05% |
| 2020-04-19 | myOtherProject | myOtherJobKarma | 34.05% |

note: % sign in last column is optional

@jj-ramirez has provided the full design for this page attached to this issue. This issue is capturing the work for the button and new page only.
### Permissions and Security

Any user should be able to get to this page / download the data.

### Documentation

* Create documentation for this feature.

### Availability & Testing

<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change

See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->

### What does success look like, and how can we measure that?

* See the [parent epic](https://gitlab.com/groups/gitlab-org/-/epics/3108).

### What is the type of buyer?

[Dakota - The Application Development Director](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/#dakota---the-application-development-director) is the buyer for this feature.

This will be built for ~"GitLab Premium"

### Is this a cross-stage feature?

This iteration will not be cross-stage
### Links / references

Edited May 20, 2020 by Ricky Wiens

Discussion
Designs