Perform Mutation Testing on the test cases to identify incorrect test cases.
Valentin Breuß commented
A very interesting Talk to this topic:
Also covers a lot of potential use cases, especially when performing it "live". I immediately thought of NCrunch as an ideal candidate for implementing them!
Kaleb Pederson commented
The work you've done with churn mode, in conjunction with mutation testing, would be a fantastic pair!
Max Guernsey commented
This could position you as chip leader in the .NET TDD space. If you make a mutation testing tool, and you make it live like your coverage currently is, you could be providing something that I think currently does not exist. Here's the funny part: You are already doing almost all the hard parts about mutation testing (coverage, deciding which tests to run, and running them). You just need to add the mutation part. If it runs in a low priority queue and is easily canceled, that won't bother me and I'm guessing it won't bother anyone else. Getting true, valuable, accurate mutation testing in two or even five minutes is a lot faster than a Java developer can reasonably expect and INFINITELY faster than a .NET developer can (presently expect).
As far as I'm aware there are currently no active mutation testing tools available for Visual Studio. Ninja Turtles and VisualMutator were previous tools, but I don't believe they work with VS2017.
Ralf Koban commented
Would be really nice, especially when used together with distributed processing.