-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support mutating changed lines only #316
Comments
Mutmut already does this if you have run a complete mutmut round first. |
Is that necessary? It's definitely not practical / feasible for large projects... |
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. |
I like the idea! However, does that require generating all the mutants? I assume there would be some kind of hashing mechanism to keep track of each mutant. |
Well.. yea all the mutants are "generated" on startup in memory. Then they get IDs based on the cache db. |
Would be done in reasonable time in large projects? |
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 run. So as soon as you get the number of mutants starting to count up from zero it will have done this work. |
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 module or functions. See the new docs. |
It would be more convenient to run something like
mutmut run --diff-only
without having to manually generate the patch file and use the--use-patch
flag.Some kind of wrapper on top of the
--use-patch
implementation.Related to #43
The text was updated successfully, but these errors were encountered: