I cannot easily reproduce the problem. I'll have to wait until I have access to the code and try to pare something down for a repro. This is probably not a big deal, since it seems to work in the general case. I suppose the other alternative is that it was because I was using VS2013/.NET 4.5.1. Either way, it seems like you should just ignore this until at least one other person cares about it. It's a pretty minor inconvenience to overcome and it seems like it's not likely for many people to experience it between now and when 3.0 arrives.
As far as avoiding this in 3.0, I thought you were splitting things out so that the GUI basically had no impact on how tests would be run any more. That error is probably going away altogether in the course of that refactor, right? -- 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
