Skip to content

feat(COVERPORT-22): add codecov integration for test coverage#676

Open
msu8 wants to merge 1 commit intokonflux-ci:mainfrom
msu8:codecov_verify
Open

feat(COVERPORT-22): add codecov integration for test coverage#676
msu8 wants to merge 1 commit intokonflux-ci:mainfrom
msu8:codecov_verify

Conversation

@msu8
Copy link

@msu8 msu8 commented Mar 10, 2026

Summary

  • Add pytest-cov to dev dependencies and configure coverage settings
  • Update GitHub Actions workflow to generate coverage and upload to Codecov with unit-tests flag
  • Add codecov.yml with flag analytics and PR comment configuration
  • Add push trigger on main branch for baseline coverage

Setup required

  • Please add [CODECOV_TOKEN](https://app.codecov.io/gh/konflux-ci/release-service-utils/config/general) as a repository secret in GitHub Settings → Secrets → Actions

@snyk-io
Copy link

snyk-io bot commented Mar 10, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@codecov-commenter
Copy link

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

Add pytest-cov, configure GitHub Actions
to upload coverage with unit-tests flag.

Signed-off-by: daturece <daturece@redhat.com>
@querti
Copy link
Contributor

querti commented Mar 10, 2026

We've had issues with codecov in our other repos, I don't know if we should enable this until we investigate https://issues.redhat.com/browse/RELEASE-2238

@msu8
Copy link
Author

msu8 commented Mar 10, 2026

We've had issues with codecov in our other repos, I don't know if we should enable this until we investigate https://issues.redhat.com/browse/RELEASE-2238

Hi, It seems that the dependency update PRs are not running e2e-tests hence why the coverage fails. Could you please share more in #wg-code-coverage Slack - perhaps more teams are having similar issues too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants