Richard Werkman

That mutation on numeric variables is less useful, and prone to unkillable mutants. But the first ones we could definitely add.

We currently place 2 mutations for >= (``). The `

Makes sense as safe mode was added as a temporary fix. The idea was however that we would fix all occurrences when they pop up and in time we would...

I suggest we implement this as follows: `dotnet stryker merge **/mutation-report.json another-report.json --output ./merged-mutation-report.html` For this we can use [multi-value arguments](https://natemcmaster.github.io/CommandLineUtils/docs/arguments.html?tabs=using-builder-api#variable-numbers-of-arguments). This can be built completely in the CLI project,...

You could take a look at https://stryker-mutator.io/docs/stryker-net/configuration/#mutate-glob It supports mutating just a single line in a single file like this `dotnet stryker -m "MyFolder/MyService.cs{10..11}"`

> CLI, that will load previous report, filter surviving mutants and run tests only against those This sounds interesting. @rouke-broersma would this be a nice feature for hacktoberfest?

Generated classes should be excluded from mutation by default. I'm not familiar with Mapperly so I don't know how the mapper class is generated. It could be that Stryker doesn't...

I don't see much value in this, to be honest. Why do you actually want this? What about building a notification system in the report? So that you get notified...

To be clear, I'm not only having this issue while debugging stryker but also using the actual installed tool (latest version). Just running `dotnet stryker` in the src directory.

@dupdob and you're running on windows? Maybe the OS has influence on this