Hypothesis-like property testing for Rust (by proptest-rs)

Proptest Alternatives

Similar projects and alternatives to proptest

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better proptest alternative or higher similarity.

proptest reviews and mentions

Posts with mentions or reviews of proptest. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-17.
  • The birth of a package manager [written in Rust :)]
    2 projects | | 17 Mar 2023
    proptest is great! It generates random input data according to some rules, and if the input fails it saves random seed into a file so that failing inputs are guaranteed to be tested on the subsequent runs (as well as new random inputs). It also doesn't immediately stop on fail but tries to find a minimal failing input first.
  • Hey Rustaceans! Got a question? Ask here (11/2023)!
    7 projects | | 13 Mar 2023
    The only other crate I could find is proptest, but it looks a lot more complicated, and I don't know if lets you skip the shrinking step as quickcheck does. I've been reading the book and going through the docs, but a quick answer would be appreciated.
  • Hey Rustaceans! Got a question? Ask here! (32/2022)!
    6 projects | | 9 Aug 2022
    Hi, I'm working on a fuzzer, that fuzzes APIs based on OpenAPI specification. I'd like to implement shrinking. It means that when an interesting input (for the API) is found, I'd like to create the smallest possible input that still causes the same behaviour of the API. I'd like to implement a payload generation via proptest, because it already has the shrinking ability. I'm having issues implementing the JSON object as a proptest strategy. Here is what I tried so far. I explained it in a detail in stackoverflow question but it did not reach many people. Thanks for your help!
  • Which Mutex to use in this case (independent tasks, partially under contention)
    3 projects | | 27 Jul 2022
    Third, if you're opting out of a compile-time safety guarantee in the name of performance, test heavily (high-coverage unit tests, property testing, fuzzing, differential fuzzing, etc.) and make use of tools like Loom and Miri's runtime data race detector for unsafe code, which can catch stuff that is beyond the scope of the compiler's guarantees.
  • Is RUST aiming to build an ecosystem on scientific computing?
    6 projects | | 10 Jul 2022
    See also property testing
  • Is there a rust way for doing TDD?
    6 projects | | 26 Jan 2022
    It is not hard to do TDD with integration tests either, just write tests that encapsulate the properties you want your library to hold then implement those properties one by one. This is also known as property driven/based testing which then couples well with fuzzers or randomized testing where you randomize the input rather than using large amounts of test assets. This also help you catch a lot more bugs that you never even thought of. proptest is a good library that can help with this.
  • Go Fuzzing
    7 projects | | 1 Jan 2022
  • In praise of property-based testing (2019)
    2 projects | | 3 Apr 2021
    I'm quite new to property testing, first introduced recently via a Rust property testing framework proptest[0]. So far i've had the feeling that property testing frameworks need to include a way to rationalize complexity, as their assumptions can easily fall short as you illustrated.

    Eg the simplest example might be an application where you input an integer, but a smaller int actually drives up the complexity. This idea gets more complex when we consider a list of ints, where a larger list and larger numbers are simpler. Etcetc.

    It would be neat if a proptest framework supported (and maybe they do, again, i'm a novice here) a way to rank complexity. Eg a simple function which gives two input failures and you can choose which is the simpler.

    Another really neat way to do that might be to actually compute the path complexity as the program runs based on the count of CPU instructions or something. This wouldn't always be a parallel, but would often be the right default i imagine.

    Either way in my limited proptest experience, i've found it a bit difficult to design the tests to test what you actually want, but very helpful once you establish that.


  • In praise of property-based testing
    6 projects | | 12 Jan 2021
    I notice that the Rust quickcheck mentions proptest which is inspired by your Hypothesis framework. Had you looked over this project when researching your recommendations?
  • A note from our sponsor - SonarLint | 25 Mar 2023
    Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today. Learn more →


Basic proptest repo stats
4 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives