0hjc

3 ms·

1. 1.▲
   Into the lair of the beast(medium.com)

   1 points by 0hjc 9y ago|0 comments
2. 2.▲
   by 0hjc 9y ago

   Why do you say most mutations will completely break an application? This is certainly not my experience. Mutation testing systems normal use fairly stable operators (e.g changing a > to a >=). In most locations in the code changes suc
3. 3.▲
   by 0hjc 11y ago

   The mutators are documented at http://pitest.org/quickstart/mutators/
4. 4.▲
   by 0hjc 11y ago

   This is what it known an "equivalent mutation". Along with high computational cost, it's one of the things identified in academic research as preventing the widespread use of mutation testing. There is no general method for d
5. 5.▲
   by 0hjc 11y ago

   No - pitest has no problems with the use of interfaces, reflection etc. The sentence you quoted relates to an optional feature that allows the tests that will be run against a mutated class to be limited to those within a certain "dist
6. 6.▲
   by 0hjc 11y ago

   If you're working with ruby mutant is pretty good -> https://github.com/mbj/mutant
7. 7.▲
   by 0hjc 11y ago

   Did you try using the history file option?
8. 8.▲
   by 0hjc 11y ago

   I'd recommend using one of the build tool integrations first - they're part of the core project. The IDE integrations still needed a bit of work last time I looked at them.