We're proud to announce the next major release of StrykerJS: 5.0. With a name change, a new dimension in your report, a new way to discover files, updated mutators, quality of life improvements, and minor bug fixes.
This release marks a fundamental shift in the way Stryker works internally. It now uses "mutation switching", which improves performance and usability, similar to how Stryker.NET and Stryker4s already work. This change, unfortunately, couldn't be done without breaking changes. See the breaking changes paragraph if you're interested.
This beta is a huge milestone because it means a fundamental shift in the way Stryker works internally. It now uses "Mutation switching", a technique that can improve performance.
With version 3 of Stryker, we've been focussing on usability. We also did some smaller changes worth pointing out. For a full list of changes, please read our changelog.
If you've used Stryker before, you'll know that it produces a gorgeous report you can view in the browser. It works by generating HTML files based on the events raised by Stryker. During development of Stryker4s and Stryker.NET, we realized that producing the same report would be a lot of work.
Instead of a new HTML reporter implementation for each Stryker framework, we've decided to move the logic of presenting the report to your browser. That way, any framework can support an HTML report simply by producing a JSON file.
Stryker 0.34 is here. This new version comes with features to help you get started. It's never been this easy to mutation test your JS project!
The 0.21 release of Stryker simplifies configuration by using your git database.
Stryker now supports bundling your code using webpack before running your tests. The installation/upgrade scenario's in this blog post can be circumvented by using the Quickstart if you don't already use Stryker in your project.
Let's start this new year strong. Stryker 0.18 adds coverage analysis support for transpilers, starting with the TypeScript transpiler.
A new Stryker plugin that adds support for Babel projects has just been released!
The installation/upgrade scenario's in this blog post can be circumvented by using the Quickstart if you don't already use Stryker in your project.
The Stryker HTML Reporter version 0.10 has a lot of new features, but more importantly: a sexy new look.
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.