CsCheck
quickcheck
| CsCheck | quickcheck | |
|---|---|---|
| 3 | 13 | |
| 121 | 2,269 | |
| - | - | |
| 9.1 | 4.0 | |
| 10 days ago | 5 months ago | |
| C# | Rust | |
| Apache License 2.0 | 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.
CsCheck
-
CsCheck 2.0.0 released!
https://github.com/AnthonyLloyd/CsCheck https://www.nuget.org/packages/CsCheck
- Show HN: CsCheck 2.0.0 – suite of random testing tools
-
In praise of property-based testing
CsCheck
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?
FsCheck - Random Testing for .NET
proptest - Hypothesis-like property testing for Rust
Fine Code Coverage - Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
afl.rs - 🐇 Fuzzing Rust code with American Fuzzy Lop
AutoFixture - AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.
Mockito - HTTP mocking for Rust!
fsharp-hedgehog - Release with confidence, state-of-the-art property testing for .NET.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
WireMock.Net - WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
shiny - a shiny test framework for rust
GennyMcGenFace
rFmt