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

Let's figure when/where to put it in and I can scrub out the TestRunner specifics. Looking at the 2.2.5 organization, it seems parallel to TestDomain in Util. I'm currently thinking of it as (quite the mouthful) MultipleDomainSolutionTestRunner.

 

Is there a generalized base set of unit tests that it passed a VS solution loaded Suite that I can pass this multi-domain suite and validate that it has the same base behavior -- then vary the test based on configuration file? Actually, a more general question, is there a well know test-target-dll that serves as a standard validation artifact?

---

From: Charlie Poole [mailto:cpoole@xxxxxxxxxxxxxxxxxxx]
Sent: Sat 12/31/2005 5:35 PM
To: Will Ballard; nunit-developer@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [nunit-developer] 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.