-
Notifications
You must be signed in to change notification settings - Fork 8
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
Explore test/code coverage to identify test improvements #144
Labels
good first issue
Good for newcomers
Comments
Following is the code coverage of rust runtime as of 2/11/25:
|
20 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To automate identifying which modules and objects are missing testing, we can try some tools like tarpaulin or cargo-llvm-cov
Doesn't necessarily have to be added in automation or enforce any minimum code coverage requirements - but can at least help identify areas for test improvement short term.
Depending on how heavy it is, we can add it to rust pre merge action or a nighty job.
The text was updated successfully, but these errors were encountered: