Markus Schirp
Markus Schirp
I like that!
Yes so far mutant does a concrete syntax diff, but it should do an AST diff.
@tjchambers As you are talking about anaylsis of these reports, this is painful with the existing test reports. I'll open another enhancement ticket to finally opensource the implementation of a...
> It would be nice to have an accessible status board similar to CodeClimate's test coverage that I could use to focus on low mutation coverage. I've had such a...
> Once things are machine readable, then putting a straightforward UI on it seems like a smaller step. Depends. I wanted it to be more, referencing the (enhanced) mutant meta...
I call them: Semantically reducing operators. And Orthogonal operators. `#[]` to `#fetch` is an instance of "reduction operator". `#>` to `#
At the source code level there is no distinction being made. As I do not see a reason to do so. It _could_ be included in the report, but I...
The classes @tjchambers made up are more fine grained, but I think they all fit into `reduction` vs `orthogonal`.
@tjchambers Orthogonal operators are the ones where most equivalent mutations are coming from. But they are very helpful for example turning literals into others, example `true` to `false`.
> I think a clear set of terms to describe the different classifications would benefit mutation testing since all authors have a common vocabulary in which to share ideas. Right...