Deltares / Deltares/imod-python
Publish code coverage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 41
- Forks
- 12
- Avg merge
- 21h 8m
- Merged PRs (30d)
- 1
Description
On Gitlab, we used to publish our code coverage. This unfortunately broke sometime before the migration to Github, and it was therefore also not migrated. Would be useful to have this again, as we might be able to use this to verify if a PR doesn't result in a decreased code coverage.
We should be careful that no integration tests are accounted for in the coverage tests.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the former GitLab coverage configuration and the current GitHub CI entry point. Check how tests are selected so integration tests are excluded. Done means coverage is published for pull requests and can reveal decreases without counting integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100