Automated code reviews via mutation testing - semantic code coverage (fork of the latest free version)
Find a file
2013-01-23 14:01:04 +01:00
bin Publish exit status of CLI runner in executable 2012-11-24 17:36:47 +01:00
config Metric driven code refactoring 2013-01-04 22:16:03 +01:00
lib Use %s to avoid embedding Strings which may contain '%' characters. 2013-01-20 22:30:49 -08:00
spec Do not mutate super to super and prep release 2013-01-10 21:09:37 +01:00
tasks Cleanup and dedup mutation generation 2012-07-31 04:00:05 +02:00
test_app Add command method to test app 2012-11-24 22:42:05 +01:00
.gitignore Add a sample application to mutate in integration tests 2012-08-09 20:04:03 +02:00
.rspec Emit vcall mutation again 2012-12-06 12:32:16 +01:00
.travis.yml Add ruby-head to travis 2013-01-02 13:04:20 +01:00
Changelog.md Fix release date for 0.2.16 2013-01-20 13:19:40 +01:00
Gemfile Use inflector from git source to overcome chicken egg 2013-01-20 14:32:20 +01:00
Gemfile.devtools Update devtools 2013-01-20 14:31:47 +01:00
Guardfile Fix constant scope mutations are emitted in 2012-12-12 22:11:35 +01:00
LICENSE Add LICENSE file 2012-12-28 18:38:39 +01:00
mutant.gemspec Bump adamantium dep to ~> 0.0.5 2013-01-20 14:38:28 +01:00
Rakefile Add devtools 2012-12-06 21:35:17 +01:00
README.md Update README.md 2013-01-23 14:01:04 +01:00
TODO Organize TODO 2013-01-05 23:00:18 +01:00

mutant

Build Status Dependency Status Code Climate

Mutant is a mutation testing tool for ruby that aims to be better than existing mutation testers.

The idea is that if code can be changed and your tests do not notice, either that code isn't being covered or it does not have a speced side effect.

Mutant does currently only support 1.9 mode under Rubinius or MRI. Support for JRuby is planned.

Also it is easy to write a mutation killer for other test/spec frameworks than rspec2. Just create your own Mutant::Killer subclass, and make sure I get a PR!

See this ASCII-Cast for mutant in action! (v0.2.1)

Using Mutant

The following projects adopted mutant.

Feel free to ping me to add your project to the list!

Installation

Install the gem mutant via your preferred method.

Examples

CLI will be simplified in the next releases, but currently stick with this:

cd virtus
# Run mutant on virtus namespace (that uses the dm-2 style spec layout)
mutant -I lib -r virtus --rspec-dm2 ::Virtus
# Run mutant on specific virtus class 
mutant -I lib -r virtus --rspec-dm2 ::Virtus::Attribute
# Run mutant on specific virtus class method
mutant -I lib -r virtus --rspec-dm2 ::Virtus::Attribute.build
# Run mutant on specific virtus instance method
mutant -I lib -r virtus --rspec-dm2 ::Virtus::Attribute#name

Strategies

Mutation testing is slow. To make it fast the selection of the correct set of tests to run is the key. Mutant currently supports the following buildin strategies for selecting tests/specs.

--rspec-dm2

This strategy is the fastest but requires discipline in spec file naming.

The following specs are executed to kill a mutation on:

Public instance  methods: spec/unit/#{namespace}/#{class_name}/#{method_name}_spec.rb
Public singleton methods: spec/unit/#{namespace}/#{class_name}/class_methods/#{method_name}_spec.rb
Private instance  methods: spec/unit/#{namespace}/#{class_name}/*_spec.rb
Private singleton methods: spec/unit/#{namespace}/#{class_name}/class_methods/*_spec.rb

Expansions:

Symbolic operator like method are expanded. So for example Foo#<< is expanded to:

spec/unit/foo/left_shift_operator_spec.rb

The full list of expansion can be found here:

https://github.com/mbj/mutant/blob/master/lib/mutant/constants.rb

--rspec-unit

This strategy executes all specs under ./spec/unit for each mutation.

--rspec-integration

This strategy executes all specs under ./spec/integration for each mutation.

--rspec-full

This strategy executes all specs under ./spec for each mutation.

It is also plannned to allow explicit selections on specs to run and to support other test frameworks. Custom project specific strategies are also on the roadmap.

Alternatives

Credits

Contributing

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with Rakefile or version (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

License

See LICENSE file.