quickcheck
Automated property based testing for Rust (with shrinking). (by BurntSushi)
cargo-llvm-cov
Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage). (by taiki-e)
Our great sponsors
| quickcheck | cargo-llvm-cov | |
|---|---|---|
| 13 | 9 | |
| 2,264 | 817 | |
| - | - | |
| 4.0 | 9.3 | |
| 5 months ago | 7 days ago | |
| Rust | Rust | |
| The Unlicense | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
quickcheck
Posts with mentions or reviews of quickcheck.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-05.
- Declarative Rust macros explanation
-
Iterating on Testing in Rust
Maybe https://github.com/BurntSushi/quickcheck too?
-
Switching from C++ to Rust
Yeah as other have mentioned, I was using Rust before 1.0.
This is my first public commit: https://github.com/BurntSushi/quickcheck/commit/c9eb2884d6a6...
I didn't write any substantive Rust before that point. So I'm at over 9 years.
-
Hey Rustaceans! Got a question? Ask here (11/2023)!
The book, Zero To Production In Rust, uses quickcheck:
-
Reltester: automatically verify the invariants of PartialOrd/PartialEq/Ord/Eq handwritten implementations
Hi all! I'm looking for some feedback on my latest crate, reltester. It's a small utility crate that, when paired with property-based testing with e.g. quickcheck makes it very easy to check that your handwritten comparison trait implementations satisfy the necessary constraints (transitivity, reflexivity, and all that stuff). I wrote it our of frustration after finding many subtle bugs in our PartialEq and PartialOrd implementations at $JOB, and hopefully someone else will find it useful.
-
Code coverage beyond lines?
For what it's worth this would also be a good candidate for property based testing, like with: https://github.com/BurntSushi/quickcheck
-
Property-Based Testing in Rust with Arbitrary
I'm aware of Hypothesis and its approach, but the connection between Hypothesis and arbitrary is indeed non-obvious. Even looking over the API docs again, the most I could pick up was this on the docs of Unstructured:
- Automated property based testing for Rust
-
Rust is more portable than C for pngquant/libimagequant
Quickcheck https://github.com/BurntSushi/quickcheck
-
How can I reproduce this quickcheck error (and why is it happening)?
I'm running into a strange issue while using [quickcheck](https://github.com/BurntSushi/quickcheck) to implement tests and I'm hoping someone here might have an idea. Long story short, I have tests which fail in weird ways when using quickcheck that I can't reproduce otherwise, so I'm not even sure if it's a legitimate issue or not.
cargo-llvm-cov
Posts with mentions or reviews of cargo-llvm-cov.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-25.
-
TIL about `cargo llvm-cov` and `cargo nextest`
I'll let them speak for themselves: https://github.com/taiki-e/cargo-llvm-cov https://nexte.st/index.html
- Code coverage beyond lines?
-
What do you expect from Rust in 2023?
Meanwhile I wholeheartedly recommend https://github.com/taiki-e/cargo-llvm-cov which makes it almost as simple.
- Kudos to cargo-llvm-cov - really useful coverage reporting
-
Code Coverage Tooling
And the options to fail on insufficient coverage are rather lacking supporting only line coverage. I have suggested improvement and might do it if there is interest from the author.
-
Measuring the coverage of a Rust program in Github Actions
Another alternative is https://github.com/taiki-e/cargo-llvm-cov which is easy to use. Don't forget to also try the --html flag with it.
-
Website similar to cppinsights.io for Rust visualization
I'd take a look at either https://github.com/taiki-e/cargo-llvm-cov and/or https://github.com/dtolnay/cargo-expand for this kinda of behavior.
- cargo-llvm-cov: Cargo subcommand to easily use LLVM source-based code coverage
What are some alternatives?
When comparing quickcheck and cargo-llvm-cov you can also consider the following projects:
proptest - Hypothesis-like property testing for Rust
grcov - Rust tool to collect and aggregate code coverage data for multiple source files
afl.rs - 🐇 Fuzzing Rust code with American Fuzzy Lop
tarpaulin - A code coverage tool for Rust projects
Mockito - HTTP mocking for Rust!
rustfix - Automatically apply the suggestions made by rustc
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
shiny - a shiny test framework for rust
cargo-expand - Subcommand to show result of macro expansion
rFmt
cargo-temp - A CLI tool that allow you to create a temporary new Rust project using cargo with already installed dependencies