quickcheck
Automated property based testing for Rust (with shrinking). (by BurntSushi)
Racer
Rust Code Completion utility (by racer-rust)
| quickcheck | Racer | |
|---|---|---|
| 13 | 2 | |
| 2,264 | 3,362 | |
| - | 0.0% | |
| 4.0 | 0.0 | |
| 5 months ago | 5 months ago | |
| Rust | Rust | |
| The Unlicense | MIT License |
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.
Racer
Posts with mentions or reviews of Racer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-17.
-
Disable Racer and eldoc?
I recently have decided to switch to it full time, and I've encountered some annoyances while developing in Rust in it. The default rust setup uses eldoc combined with racer, which has been deprecated for a while now, for auto completion and stuff like that.
-
rust-analyzer changelog #113
On the server side, things are better, but RLS is still using racer for completions, which was never quite precise for me, and has a big disclaimer of "use rust-analyzer instead" in the README.
What are some alternatives?
When comparing quickcheck and Racer you can also consider the following projects:
proptest - Hypothesis-like property testing for Rust
Rust Language Server - Repository for the Rust Language Server (aka RLS)
afl.rs - 🐇 Fuzzing Rust code with American Fuzzy Lop
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
Mockito - HTTP mocking for Rust!
rust-analyzer - A Rust compiler front-end for IDEs
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
vscode-rust
shiny - a shiny test framework for rust
neon - Rust bindings for writing safe and fast native Node.js modules.
rFmt
YouCompleteMe - A code-completion engine for Vim