mutant
mutant copied to clipboard
Automated code reviews via mutation testing - semantic code coverage.
Mutant now emits: > Calling `Expression::Base#quantify` or `Regexp::Expression::Quantifier.new` with 4+ arguments is deprecated. Using `regexp_parser` version `2.5.0`
I propose that the duration from initiating mutant (hitting return) until mutant begins the killing processes be measured and added to the reporting output. My reason is that for me...
I've found that there are cases where it is extremely difficult to satisfy the mutation that deletes sorounding `T.must(arg) -> arg`. This is particullary the case for overloaded methods, for...
These all independently crash the unit tests. I left 4 tests commented out since they seem to be invalid regexps, but there still may be a need to map them....
The --since behavior is great but it has a few rough edges. One of those is that trivial formatting changes (a far-reaching rubocop style change) can trigger a massive amount...
At the moment mutant looks for configuration file in predefined place. This is a good convention and a default. In a repository hosting several components, each one in need of...
It would be helpful to be able to check that all code can be round-tripped and passes existing tests across a codebase for finding integration issues or mutant bugs.
Add additional popular repositories to the corpus test, such as `rails` for better coverage of syntax and ability to catch regressions.
Assert that we are able to round-trip all corpus source files in addition to generating mutations without error. See [this discussion on discord](https://discordapp.com/channels/767914934016802818/767915301874040844/970502515680501760)