Property-based testing is great but people should approach this with equivalence class partitioning [1] first. That always seems simpler before people think abo

Property-based testing is great but people should approach this with equivalence class partitioning [1] first. That always seems simpler before people think about it. And they should be prepared to deal with combinatoric explosion [2] with pair-wise testing [3]. And it's no replacement for high-level behavioral tests. Because we care most about how the software actually works for the customer. [1] https://en.wikipedia.org/wiki/Equivalence_partitioning https://en.wikipedia.org/wiki/Equivalence_partitioning [2] https://en.wikipedia.org/wiki/Combinatorial_explosion https://en.wikipedia.org/wiki/Combinatorial_explosion [3] https://en.wikipedia.org/wiki/All-pairs_testing https://en.wikipedia.org/wiki/All-pairs_testing