Property-Based Testing
ScalaCheck brings Haskell's QuickCheck to the JVM, leveraging Scala's type system and functional programming features. This deep dive covers advanced Gen combinators, Arbitrary instances, stateful Commands testing, and integration patterns with Scala's major test frameworks. ScalaCheck Architecture ScalaCheck is built around three core concepts:
Testing
ScalaCheck's basic API — forAll, Gen.choose, Arbitrary — covers most property-based testing needs. But real production code involves domain types, complex constraints, and stateful systems. This guide covers the advanced ScalaCheck features that handle those cases: custom generators with combinators, custom Shrink instances, and the Commands API for
Tools & Frameworks
QuickCheck is the original property-based testing library, born in Haskell and widely imitated across dozens of languages. Instead of writing individual test cases, you describe invariants your code must always satisfy, and QuickCheck generates hundreds of random inputs to try to break them. When it finds a failing case,
Property-Based Testing
QuickCheck originated in Haskell in 1999 and remains the foundational property-based testing library. Its ideas have since spread to dozens of languages, but the Haskell version—and Erlang's commercial Quviq QuickCheck—represent the most mature implementations. This post covers advanced QuickCheck patterns that go beyond the introductory
Clojure
Example-based tests verify that specific inputs produce specific outputs. They are good at documenting intended behavior and catching known regressions. What they cannot do is find the bugs you haven't thought of yet. Property-based testing flips the model: you describe invariants your code must always satisfy,
Property-Based Testing
When developers first encounter property-based testing, the most common question is: "Does this replace my existing tests?" The answer is no — but understanding why requires a clear picture of what each approach does well and where each one falls short. Example-based testing and property-based testing
Property-Based Testing
Python developers have one of the best property-based testing tools available in any language: Hypothesis. It's mature, actively maintained, deeply integrated into the Python ecosystem, and capable of finding bugs that would take years of manual testing to stumble upon. If you're writing Python and
Property-Based Testing
Property-based testing is one of those techniques that sounds academic until you actually use it — and then you wonder how you ever shipped code without it. Instead of writing individual examples ("given input X, expect output Y"), you describe the properties your code must satisfy for any
Testing
Property-based tests find bugs that example-based tests miss, but they have different CI requirements: they're statistically driven, they need reproducible failures, and they can be slow if misconfigured. This guide covers CI integration patterns for the major property-based testing frameworks across Python (Hypothesis), JavaScript (fast-
Property-Based Testing
APIs are one of the highest-leverage targets for property-based testing. A REST API has a large input space (any valid HTTP request), a defined contract (the API spec), and invariants that must hold across all inputs (status codes, response shapes, business rules). Example-based API tests verify that
Property-Based Testing
PropEr is the open-source property-based testing library for Erlang, directly inspired by Quviq's commercial QuickCheck. It brings full stateful testing, type-based generation, and targeted property-based testing (TPBT) to the Erlang/OTP ecosystem. For Elixir, PropEr integrates with ExUnit via the PropCheck library. Why PropEr
Tools & Frameworks
fast-check is the leading property-based testing library for JavaScript and TypeScript. It brings Haskell's QuickCheck model to the JS ecosystem with full TypeScript types, a rich built-in arbitrary library, model-based testing for stateful systems, and seamless integration with Jest, Vitest, and Mocha. Key Takeaways