|
|
Does the framework have the ability to run methods simultaneously on different threads to reduce the amount of time waiting for I/O operations to complete on each method?
|
|
Coordinator
Apr 24 2008 at 5:15 PM
|
No, it does not support this by default. Running tests in parallel by default would be very surprising and potentially cause synchronization issues.
|
|
|
|
I don't need it by default, I just would like to have that option. Otherwise, to write asynchronous tests, I'd believe I'd have to write everything under one test method that executes processes in a threadpool to keep from each method executing serially.
Then of course I would not be taking advantage of the test framework.
|
|
Dec 17 2008 at 6:04 PM
Edited Dec 17 2008 at 6:04 PM
|
This is a feature I really miss. In large projects running all tests can take quite a while and since most of us have dual or more core cpus its rather annoying to wait twenty minutes for your tests to run when at the same time the cpu mostly idles, due
to the synchronous nature of all testrunners I have come across so far. I wrote an msbuild task for executing commands in separate threads and used it to launch nunit on several assemblies concurrently. This helped alot if you had many test assemblies but
what I really wanted was to be able to tell the testrunner to run fixtures in batches of <n>. It would be truly great to have this option.
|
|
|
|
I'm bumping a really old thread because I came looking for just this information, but don't see any options to do this.
|
|
Coordinator
Jan 31 at 7:42 PM
|
There isn't today, but it's something we're planning on for 2.0.
|
|
|
|
That's great news! Looking forward to it.
|
|