Skip to content

Conversation

@jhlegarreta
Copy link
Collaborator

Prepend src for the coverage path; otherwise, the coverage of the modules analysis.featuring.py, analysis.filtering.py, and cli.run.py are reported to be 0%, even if there they are covered extensively by existing tests.

@codecov
Copy link

codecov bot commented Dec 20, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.96%. Comparing base (b7f15dc) to head (ef8ea47).

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #23       +/-   ##
===========================================
+ Coverage   47.01%   95.96%   +48.94%     
===========================================
  Files          15       15               
  Lines         570      570               
  Branches       35       35               
===========================================
+ Hits          268      547      +279     
+ Misses        297       16      -281     
- Partials        5        7        +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jhlegarreta
Copy link
Collaborator Author

jhlegarreta commented Dec 20, 2025

So coverage has increased from 47%
coverage_package_name

in e.g. the recent PR #22, to 95% in this PR:

coverage_sources

without adding any new tests.

I thought that this may be related to the use of click commands, as the module that contains the commands, run.py, is not being covered. However, I have realized that there are modules such as filtering.py and featuring.py that do not depend on click for which the reported coverage was also 0% before this patch set.

Trying to gather information:
https://discuss.python.org/t/codecov-not-reporting-expected-coverage-when-using-package-name/105368, before I explore opening an issue in the coverage repository: https://github.com/coveragepy/coveragepy/issues

Prepend `src` for the coverage path; otherwise, the coverage of the
modules `analysis.featuring.py`, `analysis.filtering.py`, and
`cli.run.py` are reported to be 0%, even if there they are covered
extensively by existing tests.
@jhlegarreta jhlegarreta force-pushed the mnt/set-src-coverage-path branch from 20f0b0e to ef8ea47 Compare December 20, 2025 22:27
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.

1 participant