Théo FIDRY

I tried it on a couple of projects, here are the results: | repository | coverage (%s) | MSI (w/t uncovered - %s) | mutation coverage (%) | MSI (w...

It's been a few days and a few changes, so here's a recap. In the situation when we have/use code coverage, I dislike `--only-covered`: - It's a performance degradation and...

Alternative idea: see if it's possible to have this setting within PHPUnit config, which although for the regular user does not make much sense, it would fix our issue perfectly....

I think there is only two-three things that are cacheable unfortunately: - for a given source file, its corresponding AST - for a given source file: its corresponding mutations; It...

with the `filter` option; cf. https://github.com/infection/infection/blob/master/.ci/travis-functions.sh#L76

Yes maybe we could have an `incremental` option which works with the last run

@maks-rafalko IIRC we said to not through for better flexibility. I'll come back to my PRs soonish but at the moment I'm in-between two movings so I don't have much...

The idea was that if we for whatever reason want to try/continue on an older (unsupported) version or newer (not supported yet) version or if we did a mistake on...

I must say, I'm really not convinced :/ >Killing is a simple as adding ->expects($this->once()) to a mock. There is 3 things bothering me in this argument: - Not everyone...

I think it should be done the other way around: to ask to justify the existing code rather than justify the potentially added code. So with your example, let's say...