Anders Hovmöller
Anders Hovmöller
Doh! haha, yea my bad. Coding at night when you are sleep deprived because you're sick doesn't give you the best code :P
Ah. Fixed on main now. Now I can get mutmut to collect stats on your project, but running the clean tests fail on `test_persist`.
> The reason is that I write source files in temporary folders and execute them with pytest in a subprocess. And you want those subprocesses to have mutants turned on?...
You can add it to the `also_copy` config.
This issue turned into a pile of issues, many (all?) of which are solved, so I'm closing this. If there are problems still, it's better to create new issues for...
Mutmut already does this if you have run a complete mutmut round first.
I guess you could argue for a command that fills the entire mutmut cache with "skipped" for all mutants. Then after that you would get the change mode automatically.
Well.. yea all the mutants are "generated" on startup in memory. Then they get IDs based on the cache db.
I don't know what you mean by reasonable or large :) But you can try it. If you do mutmut run and suppy --test-time-base it won't run the initial test...
I just released mutmut 3, which is a big rewrite. It has code to run only relevant tests, and you can point it nicely to run just mutants in certain...