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

Code coverage is no longer accurate due to the introduction of Rust #607

Open
fpgmaas opened this issue Mar 16, 2024 · 0 comments
Open

Code coverage is no longer accurate due to the introduction of Rust #607

fpgmaas opened this issue Mar 16, 2024 · 0 comments
Labels
bug Something isn't working internal

Comments

@fpgmaas
Copy link
Owner

fpgmaas commented Mar 16, 2024

Now that we have added Rust to our projects, out code coverage is no longer accurately measured. Code coverage is only measured based on the python/deptry directory, but we should also include coverage on our .rs files in the src directory.

Currently, all our unit tests are in Python. We might also want to consider writing unit tests in Rust later, so we can test functions that are not exposed to Python. However, for this issue I propose we leave that out of scope.

Maybe we can take a look at rust-python-coverage, which uses cargo-llvm-cov

@fpgmaas fpgmaas added bug Something isn't working internal labels Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal
Projects
None yet
Development

No branches or pull requests

1 participant