A short case study of a real production issue that was debugged, minimized, and fixed using property-based testing.
.jpg)
Property-based testing is often touted as a magical solution to testing: write one property, get hundreds of tests back in return. Although this sounds appealing, there are only so many times that we are going to property-test the "reverse" function. But can we use property-based testing for something "real"? The answer is a resounding "yes!".
In this talk, we will conduct a short case study of a real production issue that was debugged, minimized, and fixed using property-based testing. In the process we will experience first-hand the usefulness of property-based testing along with its staples of random data generation, shrinking, and well defined properties.
As WebAssembly matures and gets more and more traction from the community, you might wonder can Scala join that trend?
I will show you how you can build your own IDE for scala based on my nvim setup
How to make Scala more approachable and productive?
A blueprint and approach for building end-to-end, full-stack applications in Scala 3