Skip to content
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

Update Mutant configuration #97

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jgarber623
Copy link
Contributor

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 calling bin/run_mutant threw a number of errors. Seems there've been quite a few changes in mutant:

  • run is the appropriate subcommand
  • a usage flag is now required
  • the --use flag is now --integration
  • etc. etc. etc.

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

  1. git switch update-mutant-configuration
  2. bundle install
  3. 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.

This YML file is one of several ways to configure the Mutant CLI:

https://github.com/mbj/mutant/blob/main/docs/configuration.md

I chose this route for ease of invocation: `bundle exec mutant run`.
Following on from the previous commit (08ae0ad), this commit updates the
README with the updated Mutant invocation and removes the custom shell
script.

A future improvement _might_ introduce a binstub which would further
simplify the invocation to something like `bin/mutant run`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant