Multiple test builds of NUnit, each requiring a different configuration. How can I get NUnit to run them all at once?

I have 13 separate but related architecture assemblies and 13 separate NUnit assemblies, each containing all the test fixtures for assembling the corresponding architecture. I am using NUnit 2.5.2 (latest version currently).

I can run each test build separately in the NUnit GUI and all tests pass. However, when I came to merge them into one NUnit project file, NUnit insists on using one config file for the entire test run. It won't work because each test build requires a different configuration. I cannot combine them into one "uber-config" file because some of the sections are mutually exclusive. I tried to run each assembly in the project in separate AppDomains as well as separate processes, but in both cases it cannot use the DLL specific config file, so all tests crash and write.

I did a Google search, but so far I have not found any indication that NUnit supports this scenario. Am I right or am I missing something?

I tried my best to repeat the architecture of the tests so that they could use the same config file, but I had to admit defeat on that front.

+2


source to share


2 answers


I've done this in the past with a batch file that does each build through the nunit console independently. At some point I had something that combined the xml output. It could be in CruiseControl.Net code.

I haven't worked on a NUnit project for a while. I only have old code in my head. But the problem is that you get one configuration per AppDomain and NUnit loads all test assemblies into one AppDomain.



You might want to try alternative players like Resharper or TestDriven.net.

+1


source


NUnit 2.5 has a setting where you can activate each assembly in a separate AppDomain. By doing this, NUnit will load the build configuration, not the .nunit project.

For more information see here:



http://nunit.org/index.php?p=settingsDialog&r=2.5

+6


source







All Articles