emanuelvarga;8162 wrote:Ok, the coverage part would not be possible, ok, for that there is sonar that provides a lot of customizations.
The nice thing about using NCrunch in your CI is that you get build, test and coverage results all in one step. If you use a different product for code coverage, you'll need to run all the tests twice :)
emanuelvarga;8162 wrote:
The biggest advantage to ncrunch for a build machine would be the parallel test execution (and maybe even grid running of tests?). This feature is currently not available in any test runner currently (correct me if i'm wrong).
Parallel test execution is becoming more common now in other products. Most of them still perform this multi-threaded within the same process, which is quite limiting .. but I'm not yet aware of any runners that can scale horizontally across a grid in the same way that NCrunch can.
It's worth remembering that it is an advantage to have your CI behaving the same way as your local dev machines. If you employ a range of different systems and products to perform your CI steps, you run the risk of having a problem in your CI that doesn't appear on your dev machine. CI problems can be time consuming to troubleshoot and can have a significant impact on team productivity.