-
[@Maan2003 pointed out that it seemd CodeCov is including our tests in the coverage reports](https://discord.com/channels/990354215060795454/1075805225522311168/1075807349140369459). But tests shouldn…
-
Hi @xd009642
Thank you for `tarpaulin`.
I was trying to get into `DWARF` a little bit (not successfully :disappointed: yet)
And I was experimenting with `ddbug` a bit (also uses `gimli`).
And I…
-
It would be nice if we were able to gather test coverage information for Clippy.
We have [an old script][script] written by @mcarton that could be used to run `kcov` on Clippy. It seems like this s…
-
-
It would be nice to support uploading coverage to coveralls and other services.
-
**Describe the bug**
I have a project that uses [`wait-timeout`](https://docs.rs/wait-timeout/0.2.0/wait_timeout/) to check the timeout of some commands that are executed. By some `printf` debugging …
-
Look at the conversation here - https://github.com/uber/piranha/pull/321
We want to add tooling that tracks:
- [ ] Code coverage
- [ ] Regression for memory usage
- [ ] Regression for perf…
-
`borsh-derive-internals` is designed for testability. It'd be great to see how well the tests are doing by including code coverage (e.g. using tarpaulin + codecov/coveralls).
-
Right now we're using [`kcov`](https://github.com/SimonKagstrom/kcov) / [`cargo-kcov`](https://github.com/kennytm/cargo-kcov) (a C++ program) for collecting code coverage statistics. The advantage of …
-
kevgo updated
2 years ago