|
Allow running tests in a separate domain per assembly, using a separate con: msg#00079windows.dotnet.nunit.devel
I saw this on the roadmap, and I might be able to contribute a snippet of code to save some time. I've set up TestRunner to work this way from builds .1227 on, basically creating a multi-domain runner with a root test suite filled with sub tests each in a different TestDomain, then proxying a couple of the events to supress multiple test run finished events from firing. It's a faily simple approach. The loaded test is visibly/structurally identical to loading a Solution file based test. <<winmail.dat>> |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Ann: NUnit 2.2.5 Release: 00079, Charlie Poole |
|---|---|
| Next by Date: | RE: Allow running tests in a separate domain per assembly, using a separate config file for each assembly.: 00079, Charlie Poole |
| Previous by Thread: | Ann: NUnit 2.2.5 Releasei: 00079, Charlie Poole |
| Next by Thread: | RE: Allow running tests in a separate domain per assembly, using a separate config file for each assembly.: 00079, Charlie Poole |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |