Testing Fundamentals

What Is Property-Based Testing?

Property-based testing is an approach where the test framework automatically generates many input values to verify that a property (a general statement about correct behavior) holds true across all of them.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

In traditional example-based testing, a developer writes specific inputs and expected outputs: given input A, expect output B. This is easy to understand but limited by the tester's imagination. Property-based testing inverts this: you define a property that should always hold, and the framework generates hundreds or thousands of input combinations to try to disprove it.

For example, instead of testing that sort([3, 1, 2]) === [1, 2, 3], you define the property: "for any list, the sorted output should have the same length, all original elements present, and each element should be less than or equal to the next." The framework then generates random lists of varying sizes and types, including edge cases like empty lists, lists with duplicates, and lists with negative numbers.

Popular libraries include fast-check (JavaScript/TypeScript), Hypothesis (Python), and QuickCheck (Haskell, the original). These libraries also implement "shrinking," which automatically simplifies a failing input to the smallest example that still reproduces the failure.

Property-based testing is particularly effective for pure functions, data transformations, serialization/deserialization, and mathematical operations.

Why Interviewers Ask About This

Knowing property-based testing signals you think at a higher level of abstraction about correctness. It shows awareness of testing techniques beyond happy-path assertions and demonstrates familiarity with advanced tooling.

Example Scenario

A team uses fast-check to test a URL parsing utility. The property: "parsing a URL and then serializing it back should produce the same URL." The framework discovers that URLs with unusual Unicode characters in the path cause the round-trip to produce a different string, revealing a normalization bug not covered by any handwritten test.

Interview Tip

Name a specific tool (fast-check for JS, Hypothesis for Python) and describe a property you would test in a real scenario. The concept is most compelling when paired with a concrete example of a bug it would catch.