-
Notifications
You must be signed in to change notification settings - Fork 0
coverage report for tests聽#8
Copy link
Copy link
Open
Labels
ci/cdAffects the CI/CD pipelineAffects the CI/CD pipelineenhancementSomething has been improvedSomething has been improvedgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Description
Activity
Metadata
Metadata
Assignees
Labels
ci/cdAffects the CI/CD pipelineAffects the CI/CD pipelineenhancementSomething has been improvedSomething has been improvedgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
goal
having coverage reports available on pull-requests
more information
coverage is a good identifier for code quality. it's not the online one, can be faked, is not reliable, etc. still, it's good to see contributors writing tests 馃槈
there are multiple types of coverage available for rust, but we should go for source-based coverage. the repository of
grcovhas a good setup description: https://github.com/mozilla/grcov?tab=readme-ov-file#example-how-to-generate-source-based-coverage-for-a-rust-project.