Austin Bingham

I'd be happier with a more extrinsic solution that didn't involve new APIs inside CR, something closer to what hammet sounds like. So instead of telling CR to invoke pytest...

You're going to get a subprocess for every test run as it is; that's how CR runs tests. If this new test runner runs pytest in-process (which is entirely possible,...

> mutmut I could run the tests Not to be rude, but could you move the mutmut support issues to mutmut?

I think [this is what you need](https://docs.pytest.org/en/stable/reference.html#pytest-main). CR used to run tests in-process, and I'm 99% sure this is how we did it for pytest.

> Could be done, but I would prefer a more generic way? I'm completely fine with a totally generic solution, but I don't know what that solution is, and I...

> hint as to where to add the call to "tufnel" You would specify that in the test command in your configuration, i.e. the file you pass to the `init`...

> In process is pretty dangerous though. In-process is a non-starter if you expect to be able to run more than one test run. But in this case we'll be...

It may not be covered. It's definitely stuff I haven't spent a lot of testing time on.

One problem with this change is that the `survival_rate()` method needs to be updated. It needs to consider "incompetent" mutants as killed, or at least as "not survivors". I guess...

Unfortunately is from a client project that we can't (as far as I know) share, but it has to do with introspecting the type annotation at runtime in order to...