Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I'll admit to being fairly new to mutant and mutation testing in general. I did notice, though, that the README and
bin/run_mutant
shell script didn't jive with recent(ish?) changes to that gem.As-is,
bundle install
-ing this gem's dependencies and callingbin/run_mutant
threw a number of errors. Seems there've been quite a few changes in mutant:run
is the appropriate subcommandusage
flag is now required--use
flag is now--integration
This PR refactors the existing configuration to align with that project's current version by adding a
.mutant.yml
file, removing this project's custom shell script, and updating the documentation.Testing
git switch update-mutant-configuration
bundle install
bundle exec mutant run
I don't know enough to draw conclusions from the output of the test run, though. But, this change should be okay since mutation testing isn't run as part of
ruby.yml
GitHub Action. Maybe it should be? I dunno. That's beyond the scope of this change.