Something about parallelizing unit tests and running them as a distributed task strikes me as somewhat overkill. I'm sure that for some massive projects this would be a great gain.
Maybe I can use that for the background compiler in VB.Net. It seems to choke on large projects. Maybe I just need to be running it on the server farm.
This actually seems like an awesome tool, if not particularly clever or innovative. On a multi-core/SMP machine this improves your productivity instantly (how long do you spend running the test suite every day) and in a more development-centric shop there could very well be a cluster built from developers machines... (this is how we'll be building our network when I get rich and start a dev company.) While you are in a think cycle or just banging out code your machine is vastly underutilized - 30 dev machines x 4 cores available to everyone could run that 20 minute integration suite so fast you'd have no excuse to go for coffee anymore. Oh wait, maybe it's not such a great idea. :)
Maybe I can use that for the background compiler in VB.Net. It seems to choke on large projects. Maybe I just need to be running it on the server farm.
ReplyDeleteThis actually seems like an awesome tool, if not particularly clever or innovative.
ReplyDeleteOn a multi-core/SMP machine this improves your productivity instantly (how long do you spend running the test suite every day) and in a more development-centric shop there could very well be a cluster built from developers machines... (this is how we'll be building our network when I get rich and start a dev company.)
While you are in a think cycle or just banging out code your machine is vastly underutilized - 30 dev machines x 4 cores available to everyone could run that 20 minute integration suite so fast you'd have no excuse to go for coffee anymore.
Oh wait, maybe it's not such a great idea. :)