Automated code reviews via mutation testing - semantic code coverage (fork of the latest free version)
Find a file
2012-12-07 19:06:56 +01:00
bin Publish exit status of CLI runner in executable 2012-11-24 17:36:47 +01:00
config Cleanup node body mutation 2012-12-06 22:30:57 +01:00
lib Expand foo= to foo_writer_spec.rb in dm-2 strategy 2012-12-07 19:06:56 +01:00
spec Make sure mutation is inserted after fork 2012-12-07 18:53:03 +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 Allow failures on 1.8 and rbx 2012-12-07 11:57:57 +01:00
Changelog.md Add changelog 2012-12-07 12:10:11 +01:00
Gemfile Remove git source of inflector 2012-12-07 12:55:14 +01:00
Gemfile.devtools Add devtools 2012-12-06 21:35:17 +01:00
Guardfile Add return statement mutations 2012-12-06 19:53:44 +01:00
locator.rb Add strategy objects 2012-11-22 00:10:50 +01:00
mutant.gemspec Bump version to 0.2.0 2012-12-07 18:17:20 +01:00
Rakefile Add devtools 2012-12-06 21:35:17 +01:00
README.md spelling 2012-12-07 11:55:04 +01:00
TODO Add todo not about equivalent subtrees 2012-12-07 18:41:25 +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 don't notice, either that code isn't being covered or it doesn't do anything.

Mutant does currently only support 1.9 mode under rubinius or mri.

Installation

Install the gem mutant via your preferred method.

Examples

cd your_lib
# Run mutant on virtus (that uses the dm-2 style spec layout)
mutant -I lib -r virtus --rspec-dm2 ::Virtus

Credits

  • A gist from dkubb showing ideas.
  • Older abandoned mutant. For motivating me doing this one.
  • heckle. For getting me into mutation testing.

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

Copyright (c) 2012 Markus Schirp

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.