zingtouch VS Stryker.NET

Hey all! Back in university I needed to incorporate a gesture library into my honours project, in order to support multi-device gestures (e.g. a "pinch" where one input is coming from one phone, and the other is coming from a tablet adjacent to it). I wound up forking zingtouch since it had an approachable architecture, then took it in my own direction as the project rapidly evolved- it's now quite a different library under the hood. I don't currently work in javascript so the library sat around waiting for a v1.0.0 release for ages without being touched, while I focused on other things. I've occasionally been chipping away at it though, and challenged myself to hit full 100% test coverage before releasing v1.0.0, which I finally did yesterday! (And a good thing too- I found a fair amount of bugs and silly decisions on my part along the way). So, v1.0.0 is out on npm, and I just wanted to share my excitement at finally crossing that threshold. The name is a mash-up of "wams" and "gestures". "Wams" was the name of my honours project.

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/