Property-Based Testing Tools

property-based-testing-tools.md

If you're coming to the Property-Based TDD As If You Meant It Workshop, you will need to bring a laptop with your favourite programming environment, a property-based testing library and, depending on the language, a test framework to run the property-based-tests.

Any other languages or suggestions? Comment below.

.NET (C#, F#, VB)

• FsCheck

Python:

• Factcheck -- requires a test framework (I like pytest), I wrote it (benefits - you can ask me about it, drawbacks - it's not very mature). Can be installed from PyPI with Pip or easy_install.
• Hypothesis -- requires a test framework, provides decorators for easy integration
• pytest-quickcheck - requires pytest, I found it hard to extend, and so wrote Factcheck

Ruby:

• Rantly

Scala:

• ScalaCheck

Clojure:

• ClojureCheck -- requires clojure.test

Java:

• JavaQuickCheck -- requires JUnit or some other testing framework

Groovy:

• Gruesome -- a quick and dirty implementation for Groovy

JavaScript:

• QC.js

For a Clojure project with the correct clojurecheck leiningen dependency feel free to clone this: https://github.com/scarytom/proptdd

JUnit theories-specific: https://github.com/pholser/junit-quickcheck

I tried qc.js before. The syntax is a little weird, but usable: https://bitbucket.org/darrint/qc.js/

(oh... it's on bitbucket!)

What about Haskell? After all, QuickCheck was first written in it, right?

Haskell - https://github.com/nick8325/quickcheck

Typescript, JavaScript - https://github.com/dubzzz/fast-check

FsCheck is on github now: https://github.com/fscheck/FsCheck

Java: https://jqwik.net

.NET (C#, F#, VB): There's also Hedgehog.

For Elixir and Erlang, there's https://github.com/pragdave/quixir

Go has https://github.com/flyingmutant/rapid (written by me), which tries to provide most of Hypothesis goodness in idiomatic Go.

Java and Scala - https://github.com/sageserpent-open/americium.

Two APIs specialised for each language, you can mix them up too.

Shrinkage is built-in, you don't write any custom shrinkage code. Shrinkage respects any invariants you set up in your generated test data.

Integrates with JUnit5, or can be used inline by tests using other test frameworks.