Nico Jansen
Nico Jansen
Awesome idea! How exactly would that work? You want people to run stryker from night-lens? Because right now, Stryker is pretty reliant on `fs` and other core node modules to...
Seems like a lot of work to maintain, no? I think this content is better suited for a blog article. As a roadmap format, how about: https://github.com/Microsoft/TypeScript/wiki/Roadmap
Hmm interesting. But I think we should not create concepts per flavor of mutation testing framework. I think it would be helpful for people of concepts are shared. For example,...
Well... making the fields required might not make sense. "NoCoverage" for example is not supported by all. But maybe we should enforce the names. My idea was to support custom...
Agreed, once we have custom fields we should do that. However, the new flat-file syntax of the mutation testing report JSON no longer allows for custom columns. Or am I...
Ok, we should document the counters in the [stryker-handbook](https://github.com/stryker-mutator/stryker-handbook) and link from it in the report. * killed * timeout * survived * noCoverage * runtimeErrors * compileErrors * totalDetected...
It is documented here: https://github.com/stryker-mutator/stryker-handbook/blob/master/mutant-states-and-metrics.md#mutant-states-and-metrics Now, all we need to do is to link to it from the mutation testing report.
Proposal: new mutation status for mutants that are covered by a test that fails even before mutation
Can we use the `ignored` status with this and reflect the reason in a (new) reason field?
Proposal: new mutation status for mutants that are covered by a test that fails even before mutation
Great, let's do that than. Btw, I would suggest to have a compiler flag to disable this feature in Stryker, since you might be fooled by the mutation score.
> For us it would be ideal if the components would display only the columns that are passed with the json. @richardwerkman no columns are passed in the json anymore...