quickcheck

I've been super interested in this field since finding out about it from the `sled` simulation guide [0] (which outlines how FoundationDB does what they do). Currently bringing a similar kind of testing in to our workplace by writing our services to run on top of `madsim` [1]. This lets us continue writing async/await-style services in tokio but then (in tests) replace them with a deterministic executor that patches all sources of non-determinism (including dependencies that call out to the OS). It's pretty seamless. The author of this article isn't joking when they say that the startup cost of this effort is monumental. Dealing with every possible source of non-determinism, re-writing services to be testable/sans-IO [2], etc. takes a lot of engineering effort. Once the system is in place though, it's hard to describe just how confident y

Maybe https://github.com/BurntSushi/quickcheck too?

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.

I like using https://altsysrq.github.io/proptest-book/intro.html for those very reasons. https://github.com/BurntSushi/quickcheck came first, but I prefer proptest’s implementation more than quickcheck’s type-based one

This looks super cool! I was under the impression that burntsushi's implementation of quickcheck [0] was the most popular property-based testing library for Rust. Was I mistaken or was there a reason the authors chose another library as inspiration? [0] https://github.com/BurntSushi/quickcheck

Worth noting that there's also an implementation of QuickCheck available for Rust (by none other than burntsushi, the author of the regex library in the OP): https://github.com/BurntSushi/quickcheck

See QuickCheck for Haskell https://wiki.haskell.org/Introduction_to_QuickCheck1 Theories for junit https://github.com/junit-team/junit4/wiki/Theories (see http://junit.org/junit4/javadoc/4.12/org/junit/experimental/... ) quickcheck for rust https://github.com/BurntSushi/quickcheck etc. There are many programming-language specific libraries for this where you define semantically appropriate suppliers of random parameter values. It would be nice to use write tests like this, then run them to get a set of seed data for the fuzzer.

Also worth mentioning the Rust library 'quickcheck' that does something similar to what you're suggesting: https://github.com/BurntSushi/quickcheck#the-quickcheck-attr...

It's definitely not idiomatic error handling, but quickcheck uses a mechanism like you speak of: https://github.com/BurntSushi/quickcheck/blob/master/src/tes... (This is just implementation details---I'm not saying this is actor based!) This lets it handle failures that panic, and then shrink the witnesses to find (hopefully) minimal witnesses. :-)

This is a really good point, and it looks like QuickCheck is supported on Rust -- here's one of several implementations: https://github.com/BurntSushi/quickcheck Would be pretty cool to see someone hook it up to the standard library tests.

I've also written a fair bit of Go and have recently taken a full dive into Rust [1, 2] and it's been a ton of fun so far. I really love both languages. Their features and goals have a pretty small intersection, but I enjoy both a lot. If you want to take a dive and are willing to put up with a little instability, now wouldn't be a bad time. The 0.10 release appears to be on the horizon and they just released binary installers, which should make tracking tip much easier: https://mail.mozilla.org/pipermail/rust-dev/2014-March/00922... [1] - https://github.com/BurntSushi/quickcheck [2] - https://github.com/BurntSushi/rust-csv