grunt-mutation-testing
grunt-mutation-testing copied to clipboard
jimivdw
JavaScript Mutation Testing as grunt plugin. Tests your tests by mutating the code.
KarmaCodeSpecsMatcher expects to see a nesting for the coverage output, which is generally true. However, when there's no coverage, will be blank. As a result, the ".forEach" call invokes an...
Hi @jimivdw I have recently set up mutation testing in my JS framework. The thing is it dosent error out but it does not move from the below point. Running...
Has anyone tried integrating this plugin with Jenkins? There is https://github.com/jenkinsci/pitmutation-plugin for Java PIT. Maybe that one could be reused?
Hi I can't get it working with karma, I receive following output: ``` $ grunt Running "mutationTest:goals" (mutationTest) task (13:38:25.033) DEBUG [KarmaServerManager]: 29 01 2016 13:38:25.033:INFO [karma]: Karma v0.13.15 server...
I'm having trouble with this plugin when also using the karma-coverage plugin. If I don't add karma-coverage to my karma conf file, I can run my tests with karma and...
It was suggested to me that Browserify might allow for in-memory mutations, as well as code parsing and formatting. This, at the very least, calls for an investigation of the...
As was suggested in #47, an example project would greatly help in getting the configuration to work properly.
Many issues until now have been caused by a wrong configration (#47, #31, #3, and many others not filed on this GitHub). As suggested in #47, the documentation should be...
As came forward in #40, it is not easy to exclude files from the configuration options. Whereas in most Grunt plugins, one can simply do `['js/*.js', '!js/*.test.js']`, this is not...
Could not the useful functionality of this codebase be extracted into something _not_ depending upon using Grunt, and then a Grunt-runner for that extracted toolkit be written? Not every project...
