Coverage over time for Components

[katia-sentry]

Successful implementation of 'Coverage over Time for Components' feature

Problem to solve:

• We have no ability to view component data over time and no ability in the UI to get a point in time view of component coverage without filtering on the file tree.

Solution:

• Similar to the flags tab, we should display component coverage over time graphically. This should include an ability to click from the name of a component through to see a filtered view of the files like we did with the flags tab.

Flags tab for reference:

Figma: link
Notion: link
Notion technical: link

Planning

Beta Give feedback

1. [Technical Planning] Coverage Over Time for Components #1280
   investigation +1
   

Backend

Beta Give feedback

1. [API] Add Repository.componentsMeasurementsActive resolver #1358
   +0
   
2. [API] Add Repository.componentsMeasurementsBackfilled resolver #1359
   +0
   
3. [API] Add Repository.componentsCount resolver #1368
   +0
   
4. [API] Add Component type for Repository.components to retrieve measurements of each component #1360
   +0
   
5. [API] Add deleteComponentMeasurements mutation to delete measurements for a given component ID #1361
   +0
   
6. [Worker] Modify TimeseriesBackfillDatasetTask to use a batching method for components #1362
   +0
   
7. [Worker] Modify TimeseriesDeleteTask to be able to delete by component name #1432
   +0
   
8. [API] lastUploaded is not computed correctly #1601
   bug +1
   

Gazebo

Beta Give feedback

1. Create feature flag for Components tab #1383
   +0
   
2. Add ComponentsTab placeholder under RepoPage #1370
   1 of 1
   +0
   
3. Refactor useActivateFlagMeasurements to be generic that takes in measurement type #1374
   +0
   
4. Create useRepoComponents hook to be fetch component measurement booleans #1369
   3 of 3
   +0
   
5. Create hook to retrieve repo components' measurements #1373
   1 of 1
   +0
   
6. Create hook to delete component measurements #1376
   1 of 1
   +0
   
7. Create useRepoComponents hook to query Component measurements #1377
   1 of 1
   +0
   
8. Refactor constants.ts from ComponentTab and FlagsTab to a shared util #1371
   +0
   
9. Migrate to use the newly created component related hooks #1379
   6 of 6
   +0
   
10. Show last uploaded for each component in the table #1380
    +0
    
11. Add branch selector to the table #1381
    +0
    
12. Rework the Components Not Configured flow #1378
    +0
    
13. Update the CSS of the Sparkline to align with the design doc #1382
    +0
    
14. Enable the ComponentsTab in the Repo page #1375
    +0
    
15. Look for other areas of refactor to shared between the components and flags over time repo page tabs #1372
    +0
    
16. Create feedback GH issue to link to on the app #1517
    +0
17. Branch filtering not working #1602
    bug +1
    
18. Remove greyed out placeholder table in the "enable analytics" view #1603
    bug +1
    
19. Create a "Learn More" link under the configured components area #1635
    bug +1
    
20. Update the "is backfilling" to align with the design doc #1636
    bug +1
    
21. UI cleanup laundry list #1639
    10 of 10
    bug +1
    
22. When page is narrowed, the numbers disappear #1642
    +0
    
23. A few UI tweaks #1666
    3 of 3
    bug +1
    
24. Bug when clicking on a component in the table doesn't link correctly to the code tree #1702
    bug +1
    

Testing

Beta Give feedback

1. Create and execute test plan for backend and UI #1545
   +0
   
2. Manual Test components tab #1461
   0 of 6
   +0
   

[codecovdesign]

Discovery to ready for dev of brings components to the repo level

[codecovdesign]

rough notes from components audit session 2/13/24 about flags and components:

Areas worth looking at related to flags and new components section:

• Feedback issue: Feedback on the new 'Flags' tab feedback#27
  • If looking for components feedback Nikos at Unity might help
    • Feedback: would like to select specific flag/component and see the specific data around that (on repo page data + ability to share that saved view)
• Config status
  • Not configured: https://app.codecov.io/gh/codecov/gazebo/flags
  • Configured in yaml, but needs processing: https://app.codecov.io/gh/codecov/codecov-action/flags
  • Configured in yaml and UI: https://app.codecov.io/gh/codecov/codecov-cli/flags
• Information architecture
  • Where to place flags
    • Separate sections?
    • Same section?
      • What could describe both “Grouping” “Breakdown” “Filters” “Flags and Components”
• Filters
• Flags trend line
  • Color is constant pink for now, should be revisited
• Ability to delete
  • Nuance is that is only deletes from the UI
  • Not sure if this is required for the component side of things?