Over the past few months we have been working hard to integrate Stryker.NET with azure pipelines. Learn how you can leverage our new features to include mutation testing in your continuous integration.
Over the years, we've been privileged to explain the concept of Mutation Testing to great developers, testers and others. The concept of inserting bugs into your production code in order to test your tests sparks the imagination.
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.
📊 The Stryker Dashboard can now host your mutation testing report in the cloud.
Stryker.NET 0.10 is here! This brings new features to mutation testing for .NET. Read all about these features in this blog.
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.
This is the first official release of Stryker4s! Bringing easy mutation testing to Scala sbt projects. And it comes with some great features.
It's taken a little longer than we maybe would've liked, but we are very proud of this first release. In this blog post we'll tell you about why running with the sbt plugin is a big improvement, and some of the features you can use today for Stryker4s. Although it's still possible to use the command-runner for non-sbt projects, we decided a sbt plugin was an important for the first release.
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!