A short case study of a real production issue that was debugged, minimized, and fixed using property-based testing.
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.
How to leverage Scala with scala.js to write frontend as functional programmers would do.
Avoid mistakes in API design, implementation and evolution with Smithy
We will look into three less-understood, yet (arguably) extremely useful constructs introduced in Cats Effect 3: Dispatcher, Supervisor, IOLocal
How to implement fast and cost-effective backend for a multiplayer game using Scala, Akka and GraalVM