Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hook up code coverage reporting to CI #814

Open
MonsieurNicolas opened this issue May 19, 2023 · 0 comments
Open

Hook up code coverage reporting to CI #814

MonsieurNicolas opened this issue May 19, 2023 · 0 comments
Assignees

Comments

@MonsieurNicolas
Copy link
Contributor

What problem does your feature solve?

Rust added better support for code coverage last year.

We should take advantage of this.

What would you like to see?

At a minimum, reports per build on code coverage stats to help reviewers & to help prioritize code cleanup/testing.

Better:

  • in the context of a PR, provide "diffs" on the coverage point of view, to easily spot when there might be gaps in coverage

What alternatives are there?

It may be possible to have some sort of report on a schedule that updates a static page on the project (either as a GH action, or from Jenkins).

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

No branches or pull requests

3 participants
@graydon @MonsieurNicolas and others