Skip to content

coverage report for tests #8

Open
@bbortt

Description

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 grcov has a good setup description: https://github.com/mozilla/grcov?tab=readme-ov-file#example-how-to-generate-source-based-coverage-for-a-rust-project.

Metadata

Assignees

No one assigned

    Labels

    ci/cdAffects the CI/CD pipelineenhancementSomething has been improvedgithub_actionsPull requests that update GitHub Actions code

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions