-
Seeing good code coverage will give confidence to other developers to use tower. It might also help find some bugs as we strive to improve coverage.
-
The tests for tarpaulin run `cargo clean`, which nukes the target directory.
https://github.com/xd009642/tarpaulin/blob/083fec9ef018dd38516d1929b0fbedf06042fd60/src/lib.rs#L109
-
So I'm in a _definitely very unique_ situation where I have a test that requires the repos `.git` folder so I need something a bit more aggressive than the `--gitignore true` flag. I'm currently using…
-
So found an interesting thing when developing cargo-tarpaulin and confirmed it exists also with cargo-llvm-cov and using the raw llvm tools. When `#[tracing::instrument]` is added to a function the fu…
-
Hi!
I'm using the great archived test features in order to exec. my tests on a temporary CICD spawned pod in Kubernetes to test against other resources in there.
Two questions:
1) Is there a w…
lcmgh updated
2 years ago
-
-
`omar` features to be implemented are listed below
the goal of this issue is both to provide a development guideline and track implementation progress
each entry will be linked to related feature …
-
-
My workspace has about 30 packages and I am trying to report coverage per-package in the workspace but right now if I run tarpaulin on a single package, either via `cargo tarpaulin -p package1` or by …
-
When running `cbindgen::generate_with_config` in the build.rs it works fine unless the project is built via cargo-tarpaulin where the following error is returned `CargoMetadata("polyline-ffi/Cargo.tom…