lets_expect
Clean tests in Rust (by tomekpiotrowski)
bolero
property testing and verification front-end for Rust (by camshaft)
| lets_expect | bolero | |
|---|---|---|
| 2 | 2 | |
| 59 | 167 | |
| - | - | |
| 0.0 | 7.2 | |
| about 1 year ago | 15 days ago | |
| Rust | C | |
| MIT License | 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.
lets_expect
Posts with mentions or reviews of lets_expect.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-10.
-
Announcing lets_expect - Clean tests in Rust.
Github docs.rs
-
Testing in rust: are there any useful crates, macros etc that you use to make this easier and less verbose?
For that reason I've recently created lets_expect. It's a procedural macro that introduces its own syntax for unit tests inspired by RSpec's one-liner syntax. I think it looks very clean and concise. I consider it experimental at this point, so I haven't announced it anywhere yet, but I use it to test some of my Rust code. Basic structure is as follows:
bolero
Posts with mentions or reviews of bolero.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-11.
-
Testing in rust: are there any useful crates, macros etc that you use to make this easier and less verbose?
This one is nice too. https://github.com/camshaft/bolero
-
[release] Fazi - a drop-in replacement for libfuzzer
I wrote bolero because of the exact reasons you said here. The usage of cargo-fuzz is quite awkward, not to mention incompatible with other engines like AFL and honggfuzz.
What are some alternatives?
When comparing lets_expect and bolero you can also consider the following projects:
parse-rosetta-rs - Comparing parser APIs
rstest - Fixture-based test framework for Rust
jasmine - Simple JavaScript testing framework for browsers and node.js
libfuzzer - Rust bindings and utilities for LLVM’s libFuzzer
fazi - drop-in replacement for libfuzzer
AssertJ - AssertJ is a library providing easy to use rich typed assertions
toml - Rust TOML Parser
kani - Kani Rust Verifier