Ability to exclude namespaces from mutation about devtools HOT 5 CLOSED

+1

This would also be helpful when gradually killing mutations on an existing codebase.

from devtools.

@lgierth good point, I hadn't thought about that. I could see this even being useful when spiking stuff. You'd mark the stuff you're spiking as being excluded from mutant, while making sure any changes you make to the already mutation tested code are still covered. This prevents you having to balance spiking against keeping metrics happy, especially when you have no idea what the final code should look like.

from devtools.

For reference, at the moment my CI script is bundle exec rake -t ci:metrics spec:integration && (bundle exec rake -t metrics:mutant || true), which is not optimal because it won't fail for killed mutations that come back to life after a code change.

HTTPkit is at 89 % now btw :)

from devtools.

@lgierth, @dkubb Released mutant can easily exclude namespaces:

mutant --rspec '::MainNamespace*' --ignore-subject '::MainNamespace::SubNamespace*' We just need to add this to the mutant devtools tasks.

I also plan to support reading of the config/mutant.yml directly from mutant. So we dont have two moving targets.

from devtools.

This is supported already. By mutant itself and in the configuration file devtools ships.

from devtools.