Stryker 0.10 marks the biggest change in Stryker history yet, as we now support running mutation testing on TypeScript code.
Stryker 0.8 just released with better CI integration and configurable thresholds.
Stryker is about two years old. During this time we achieved a lot. But it's far from finished. So, what's next? Let's take a glimpse in the future.
This release of Stryker brings a number of new features and improvements. Including a new quickstart and a number of reporter improvements.
During the last weekend of January we spent a weekend with ten students from the HAN University and University of Twente developing valuable features for Stryker!
Writing unit tests can be hard. Even for an easy example such as a calculator app. There are unlimited combinations of inputs for a calculator and you're not going to test every single one. So when are you done testing?
Up until now, when you were writing unit tests, you were actually investing in code quality. Catching bugs early by continuously exercising your code with unit tests and keeping your stakeholders happy by presenting them with a code coverage number of 85% or higher. But does code coverage tell the entire story? Are your tests actually able to detect bugs? How do you test your tests? That's the problem mutation testing sets out to solve.
The full changelog can be found on GitHub. In this post we'll dive into a couple of new features.