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.

Sign up for GitHub

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

Jump to bottom

Use rust-based coverage tools rather than tarpaulin #674

Open

bfjelds opened this issue Oct 26, 2023 · 1 comment

Labels

good first issue help wanted keep-alive

Collaborator

bfjelds commented Oct 26, 2023

Migrate away from tarpaulin as code-coverage in favor or compiler-driven coverage tool built into rust.

More description here

This may lead to more accurate coverage numbers.

Collaborator Author

bfjelds commented Oct 26, 2023 •

edited

Loading

i'm not sure, but using this system might allow for coverage numbers to cover both unit tests and e2e tests:

https://stackoverflow.com/questions/3166198/with-gcov-is-it-possible-to-merge-to-gcda-files

kate-goldenring added good first issue help wanted keep-alive labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment