Open johnesher opened 4 months ago
The output you showed looks like the mutmut show
output. That just shows that mutmut has enumerated the mutant, not that it has tested that mutant.
Thanks that helps me to understand. I have quite a lot of items skipped at the moment and they make it hard to see the real mutants that need to be addressed in the report. Is there an option to omit skipped mutants from the report?
It also seems to me that the behaviour of --disable-mutation-types
is unclear. Adding it halved the number of mutants, but some strings still survived as in this one below
Survived mutation testing. These mutants show holes in your test suite.
Mutant 126
--- src/example_client.py
+++ src/example_client.py
@@ -30,7 +30,7 @@
def doing_something_that_sends_an_event(self):
# return for test purposes
- return self.send_event("it happened")
+ return self.send_event("XXit happenedXX")
And it's not just that that mutant was checked when you didn't have that conf? The cache will remember mutants...
This is my pre_mutation function in mutmut_config.py
I can see it is being executed from the prints but it does not stop the mutations as shown by the snippet below
There is no setup/config file and I am running mutmut like this
mutmut run --disable-mutation-types=string,number
I would expect the string in the print above not to be mutated.
Version is
mutmut version 2.5.0
and running with python 3.10 in a venv on Ubuntu 22.04