Automated code reviews via mutation testing - semantic code coverage (fork of the latest free version)
Find a file
2013-06-15 17:15:37 +02:00
bin Publish exit status of CLI runner in executable 2012-11-24 17:36:47 +01:00
config Adjust unit spec timeout 2013-05-15 10:46:47 +02:00
lib Remove unused in-mutator mutation filter 2013-06-15 17:15:37 +02:00
spec Fix object cycle 2013-06-15 16:32:40 +02:00
test_app Fix whitespace 2013-04-17 20:31:21 -07:00
.gitignore Adjust gitignore 2013-03-01 18:11:41 +01:00
.rspec Emit vcall mutation again 2012-12-06 12:32:16 +01:00
.travis.yml Adjust IRC notifications [ci skip] 2013-06-02 22:36:06 +02:00
Changelog.md Port case mutations to parser 2013-06-14 21:12:09 +02:00
Gemfile Remove git dependency to unparser 2013-06-15 00:34:20 +02:00
Gemfile.devtools Sync devtools 2013-05-15 10:29:39 +02:00
Guardfile Port method extraction to parser based ast 2013-06-14 21:11:54 +02:00
LICENSE Add LICENSE file 2012-12-28 18:38:39 +01:00
mutant.gemspec Use parser ~> 2.0.beta5 2013-06-14 21:12:10 +02:00
Rakefile Correctly override mutant rake task 2013-05-22 02:36:05 +02:00
README.md Fix link to GitHub Issues. 2013-06-12 22:29:23 +03:00
TODO Port binary method operator mutator to parser 2013-06-14 21:12:10 +02: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)

Projects using Mutant

The following projects adopted mutant, and aim 100% mutation coverage:

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

Support

I'm very happy to receive/answer feedback/questions and critism.

Your options:

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.