This is now fixed (in the source) in a way that will work for you. However, I suggest you avoid using the Settings to control options for your use of NUnit. That approach will cause NUnit itself, both the Gui and Console runners, to use the settings you leave behind. A better approach for programmatic control is to place the options in the TestPackage you create. TestPackage settings will override anything in the general NUnit settings.
-- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/896615 Title: Tests can't be run in existing AppDomain Status in NUnit V2 Test Framework: Fix Committed Bug description: If I set Options.TestLoader.DomainUsage as DomainUsage.None and set Options.TestLoader.ProcessModel = ProcessModel.Single, test-doman-* AppDomain created otherwise, because these parameters set to Default. It seems that problem is inside method TestLoader::MakeTestPackage in this code: if (processModel != ProcessModel.Multiple && domainUsage == DomainUsage.Multiple && !package.Settings.Contains("DomainUsage")) package.Settings["DomainUsage"] = domainUsage; Does the code needs to be changed to the following code? if (processModel != ProcessModel.Multiple && domainUsage != DomainUsage.Multiple && !package.Settings.Contains("DomainUsage")) package.Settings["DomainUsage"] = domainUsage; To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/896615/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
