Skip to content
GitLab
Next
Closed
Issue created by Scott Hampton@shampton💡Maintainer

Use code coverage GraphQL API in group code coverage table

Problem to solve

This a follow up issue to both #215135 (closed) and #231386 (closed). We have the frontend work done for creating a coverage data table on the group repositories analytics page, and we have the backend work done for creating the GraphQL API for the coverage data. Now we need to update the frontend to use the GraphQL API data instead of a temporary client side resolver that is creating randomly generated data.

Intended users

Further details

  • Being able to see the coverage for all projects selected in the GitLab UI saves Delaney a step of downloading the data and viewing in a spreadsheet.
  • Delaney would like to be able to click into a project to get specific data by job for that project.
    • Clicking on the GitLab.org project would go go the Analytics -> CI/CD page.

Technical Details

  • Remove the @client indicator in ee/app/assets/javascripts/analytics/repository_analytics/graphql/queries/get_projects_test_coverage.query.graphql
  • Remove the client resolver in ee/app/assets/javascripts/analytics/repository_analytics/index.js

Documentation

  • Add a new screenshot to the docs with the new interface.

Acceptance criteria

  • The table displays all the data selected with accurate information

Is this a cross-stage feature?

No.