Maks Rafalko

if it helps in any way, we have `-threads=int|'max'` already implemented

While the idea itself is interesting in exploring, I want to highlight that we do a lot of assertions for `$this->output->writeln()` because in some classes it's the main logic :)...

> * don't run mutations about stuff people already covered by other means (e.g. static analysis) -> mutation testing is too slow to bring up errors already covered by e.g....

> would it be possible to spread the load of killing mutants across more CPUs? just to be clear: are you talking about GH only (or better to say -...

Another idea I found in mutmut - https://mutmut.readthedocs.io/en/latest/#workflow > - Show the mutants with mutmut browse > - Find a mutant you want to work on and write a test...

So I explored one more MT lib on how they try to solve this issue. They have IDs for all the mutants. Let's say we have 10 mutants and you...

> doesn't `infection -s --filter=tests/MyExampleText.php` work like that? `--filter` runs Infection on a specific **source** file, running _all_ the tests existing in a project. To improve a feedback loop, we...

> since we likely have xdebug in the system (e.g. for coverage information) as for me and the company where I work, when collecting code coverage, we always strive **not**...

I would like to hear other opinions from @infection/core My first thought (base on your benchmarks): it's not yet clear how it affects non-timeout mutants. From the benchmarks above, we...

> do we have some timing data at hand to detect which mutations ran into timeouts previously > maybe via junit report files? not sure I got you. We use...