GromacsWrapper
GromacsWrapper copied to clipboard
testing codecov
Test different versions of codecov.yml to see if anything solves #287
Validate with
curl --data-binary @codecov.yml https://codecov.io/validate
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 51.25%. Comparing base (e7fd8c3) to head (2568d8a).
:warning: Report is 4 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #294 +/- ##
==========================================
+ Coverage 0.00% 51.25% +51.25%
==========================================
Files 22 23 +1
Lines 3954 4318 +364
Branches 0 624 +624
==========================================
+ Hits 0 2213 +2213
+ Misses 3954 1924 -2030
- Partials 0 181 +181
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
I was able to get normal coverage when running locally
pytest -v --disable-pytest-warnings --durations=20 --low-performance --cov-report=xml --cov-report=term-missing --color=yes ./tests
coverage report
I can locally reproduce the No data to report. --- I think after adding the pytest-pep8 plugin to pytest-cov (and pytest-xdist) (python 3.13).
When removing the plugin (mamba uninstall pytest-pep8) the lack of coverage remains, so maybe something else changed.
The issue was that --cov=gromacs in the presence of a ./gromacs directory expected the code to be installed with pip install -e . instead of a normal installation. Although the package is installed as gromacs, the presence of the directory seems to have confused it.
I didn't explore more specific options in the pyproject.toml where it may be possible to specify a module name (to disambiguate source = ["gromacs"]).
In short: use a developer installation for testing.