✳flâneur — a map of the web's best reading

The sad state of property-based testing libraries

stevana.github.io · 19,324 words · saved by 1 readers

Property-based testing is a rare example of academic research that has made it to the mainstream in less than 30 years. Under the slogan “don’t write tests, generate them” property-based testing has gained support from a diverse group of programming language communities. In fact, the Wikipedia page of the original property-basted testing Haskell library, QuickCheck, lists 57 reimplementations in other languages. In this post I’d like to survey the most popular property-based testing implementations and compare them with what used to be the state-of-the-art fifteen years ago (2009). As the title already gives away, most of the libraries do not offer their users the most advanced property-based testing features. In order to best explain what’s missing and why I think we ended up in this situation, let me start by telling the brief history of property-based testing. In Gothenburg, Sweden’s second most populated city, there’s a university called Chalmers. At the computer science department

The sad state of property-based testing libraries The sad state of property-based testing libraries Posted on Jul 2, 2024 Property-based testing is a rare example of academic research that has made it to the mainstream in less than 30 years. Under the slogan “don’t write tests, generate them” property-based testing has gained support from a diverse group of programming language communities. In fact, the Wikipedia page of the original property-basted testing Haskell library, QuickCheck , lists 57 reimplementations in other languages. In this post I’d like to survey the most popular property-bas

Explore this link on the map →

saved by

related reading