I found a workaround for this. It's bizarre. I switched to the "load each assembly into its own process" setting and the problem went away. The workaround is probably all anyone really needs.
-- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/1242502 Title: Now SetUpFixture doesn't work at all Status in NUnit V2 Test Framework: New Bug description: In 2.6.2, with the 2.6.2 runner, it used to be that a test suite with a SetUpFixture could not be used in flat list mode, which was no major inconvenience. Now I get that same error message no matter how I have my runner configured. This is true whether I use the 2.6.2 runner or the 2.6.3 runner. I know you aren't accepting bugs in V2. If that's really true, I'll have to go back to 2.6.2. To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/1242502/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
