nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

In spite of my intentions, if a major feature has stopped working, I'll do
a dot.one release.

However, according to NUnit's own tests, SetUpFixture is working fine. My
guess is that there is some specific factor in your case that we are not
taking into account and that it doesn't come into play when running only
one assembly.

Even though you have found a workaround, it would be helpful if you could
supply a simple repro of this bug. At a minimum, I'd like to avoid it in
NUnit 3.0!

Charlie


On Sun, Oct 20, 2013 at 7:59 PM, Max Guernsey, III <max@xxxxxxxxx> wrote:

> 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 subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/1242502
>
> Title:
>   Now SetUpFixture doesn't work at all
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1242502/+subscriptions
>

-- 
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