Suggestions regarding some low-value mutations

[nene]

Hi! Thanks for an amazing tool. It's been fun to put my tests on a test.

I found that some of the mutations almost always produce false positives:

• Replacing === with == and !== with != and vice versa.
• Replacing "use strict" with "MUTATION!" or removing it altogether.

Very rarely will these mutations produce a test failure. Like in my code base all files begin with "use strict" - so as a result I almost never get 100% mutation success rate. And whether == or != produces a failure is a moot point for me, as the coding standards require to always use triple-equals.

I think both of these mutations are better detected with code style checking tools.

For the triple-equals case I found a quick hack to turn it off. But so far I haven't quite managed to get rid of the "use strict" case.

[paysdoc]

Hi Rene,

Thanks for your feedback. The triple equals were a bit of a contentious issue here too. I think we'll probably take that test out. As for the "use strict", I'll discuss with Jimi tomorrow whether and what we'll do about it. Have you tried adding ignore: [/use strict/] to the config?

[nene]

Hey, thanks. The ignore: option works perfectly for me.

[jimivdw]

Both these suggestions have been implemented in v1.1.0