Feature Overview (aka. Goal Summary)

Get visibility into code coverage metrics. 

Goals (aka. expected user outcomes)

• Measure unit and e2e coverage and upload to codecov.io or sonarqube 
• Align with what is coming in CY26 in P&D, where coverage metrics will be mandated
• Propose optimal strategy on where to collect code coverage metrics
  • Is running unit test coverage (jest) in Upstream/BCP CI viable. What are the Upstream limitations, constraints?
  • Where do we run E2E Test Coverage? in Overlay for plugins? etc? 
  • etc.

Requirements (aka. Acceptance Criteria):

• Code Coverage computation will be run in CI (not locally)
• Deliver code coverage strategy for Unit Code Coverage
  • consider jest for unit codecov
• Deliver code coverage strategy for E2E Code Coverage
  • consider https://istanbul.js.org/ library for UI E2E codecov
  • consider https://go.dev/doc/build-cover for GO Lang Integration/E2E Test codecov
  • consider https://github.com/psturc/node-coverage-http for backend E2E codecov if applicable  
• Upload coverage to codecov.io (for public project) or sonarqube for internal
  • P&D Devprod team will consume from there and upload to devlake

Documentation Considerations

• RH Documentation not required

Related Links and Materials:

• CoverPort for downstream coverage: https://docs.google.com/presentation/d/1NXTEVfmAUsd-8uZxOLNzZHMvoyY1KZGAUnRsaBQWv34/edit?slide=id.g3acb18380d9_0_132#slide=id.g3acb18380d9_0_132
• https://istanbul.js.org/
• https://go.dev/doc/build-cover
• https://github.com/psturc/node-coverage-http
• DevLake: https://konflux-devlake-ui-konflux-devlake.apps.rosa.kflux-c-prd-i01.7hyu.p3.openshiftapps.com