I'm working on a fairly large solution with 58 projects, and love the idea of continuous testing (This is a new feature for me, having just updated to the latest R# Ultimate), however it's actually slowing me down, and quite significantly, to the point where I'm looking at disabling the R# testing features and reverting back to the native VS testing tools.
Everytime I make a small code change, and build/save, the testing runs (it's configured with the setting "On Build, run dirty tests"), and the tests are performed in a heartbeat, however this immediately triggers the code coverage analysis, which takes around 5 minutes to run, and further runs of the unit tests are blocked until the code coverage analysis has completed.
When you're practising TDD, this makes continuous testing quite painful to work with.
So, is there any way to disable code coverage automatically running in a continuous testing session? Or can the code coverage analysis be streamlined so it only analyses the dirty modules, instead of the entire project (which I assume is what's happening at the moment, given the time it takes to run)?