logo       

RE: Allow running tests in a separate domain per assembly, using a separate: msg#00080

windows.dotnet.nunit.devel

Subject: RE: Allow running tests in a separate domain per assembly, using a separate config file for each assembly.

Hi Will,



Sounds like it might be what we need. If there are licensing or copyright
issues, we can discuss offline.



Charlie



_____

From: nunit-developer-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:nunit-developer-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Will
Ballard
Sent: Saturday, December 31, 2005 2:39 PM
To: nunit-developer@xxxxxxxxxxxxxxxxxxxxx
Subject: [nunit-developer] Allow running tests in a separate domain per
assembly, using a separate config file for each assembly.



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.

<<attachment: winmail.dat>>

<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise