mutant
mutant copied to clipboard
mbj
Automated code reviews via mutation testing - semantic code coverage.
Locally `--since` usually works fine as developers have a full checkout of their git repository. But on CI things are different. Most CI systems use a fetch depth of 1...
@mbj Possibly, you've already seen the [contracts](https://github.com/egonSchiele/contracts.ruby) gem. What do you think of it? Are you planning to support it in future? (now using contracts makes method not recognizable by...
A feature request I have would be to add two flags to the mutant cli: * `--skip-subject` * `--pending-subject` The `--skip-subject` flag should perform exactly the same as `--ignore-subject`, where...
In a commit with a removal of a method, the location of the removed code was used for subject selection. The method directly below had no coverage, and was selected,...
To decrease the time until we get valuable feedback, `mutant` should print alive mutations to the console while it is still running.
Normally the pre-generation of mutant finishes in < 2seconds. So to reduce complexity it was decided (by me) we kill the streaming infrastructure. This also enables to report the amount...
Seems like mutant doesn't apply [ruby 2.1+ refinements](http://ruby-doc.org/core-2.1.1/doc/syntax/refinements_rdoc.html) and complains about undefined methods instead.