Distributed processing

Just tried this out, and so far all works great. At least it works as expected, didn't tinker too much with it, but i'm running 1 node, and NCrunch now succesfully uses that to run unit tests, so effectively it's twice as fast. I'm mostly pinning my tests, so there's just 10~50 at a time to run, but it still feels faster. Plus it offloads CPU from my dev box, which is great. Great work!

Thanks! I really appreciate you taking the time to share your experience with this feature. Most of the time I only hear about things when they break, so it's really great to get some positive feedback :)

Do post back again after you've been using it for a few weeks. I'd really like to hear about your long time thoughts on it along with any suggestions on how it could improved.

Remco wrote:Most of the time I only hear about things when they break,

Or when users have to pay again to renew their license :)

Right now the only 'not on the green happy path' is the fact that i'm using my home laptop as a node, and it has different time zone and different culture, so that exposed a number of places where tests fail. This is a good think, but was a surprise at first.

It is interesting when test bugs like this surface with the distributed testing. I also have a good chuckle when I see it - as it's sometimes easy to forget that the tests are being run on a completely different machine with different configuration. The slightly annoying thing about this is that it causes tests to fail intermittently, rather than consistently. I've often found it to be good practice to always do a full end-to-end test run on a new grid node when it is first connected, just to make sure all the existing tests work the way they should.