yam-rs
quickcheck
| yam-rs | quickcheck | |
|---|---|---|
| 2 | 13 | |
| 2 | 2,396 | |
| - | - | |
| 9.1 | 4.0 | |
| 4 days ago | 10 months ago | |
| Rust | Rust | |
| GNU Lesser General Public License v3.0 only | The Unlicense |
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.
yam-rs
- What's everyone working on this week (35/2023)?
-
Iterating on Testing in Rust
https://github.com/Ygg01/steel_yaml/blob/master/tests/yaml_t...
Here is how I made dynamic tests for it.
But cargo nextest is a game changer. Colored output + fast fail (configurable) + timeout detection is just great.
https://nexte.st/book/custom-test-harnesses.html
quickcheck
- 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.
What are some alternatives?
mockall - A powerful mock object library for Rust
proptest - Hypothesis-like property testing for Rust
afl.rs - 🐇 Fuzzing Rust code with American Fuzzy Lop
Mockito - HTTP mocking for Rust!
shiny - a shiny test framework for rust
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rFmt
tarpaulin - A code coverage tool for Rust projects
cargo-fuzz - Command line helpers for fuzzing
Racer - Rust Code Completion utility
polish - Testing Framework for Rust