dont-target-100-coverage VS Stryker.NET

Project sample can be found there: https://github.com/antoine-coulon/dont-target-100-coverage

Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests

This is called mutation testing btw.

Let's try it on our small example using Stryker.

There are tools that do this automatically, stryker[2] is one of them. When you run stryker, it will create many mutant versions of your production code, and run your tests for each mutant (that's how mutations are called in stryker's' documentation) version of the code. If your tests fail then the mutant is killed. If your tests passed, the mutant survived. Let's have a look at the the result of runnning stryker against reffects-store's code:

Mutation testing is pretty solid. Better than code coverage for sure. Using Stryker personally.

A mutation testing tool (like Stryker) runs your unit tests to verify they all pass then makes a small change (mutation) to your code and reruns the tests. At least one test should fail because the modified code should behave differently.

I haven't tried it yet, but last time I researched it, this is the library that looked most promising: https://stryker-mutator.io/

Website: https://stryker-mutator.io/