nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I'm not sure what bug you noticed on the changelist, but it wasn't for
this one.

In my earlier (9/24) note, I said this would be fixed in 2.6.2. The fix
has now been committed, so you can get it if you pull the latest source
and build it. Otherwise, you have to wait for 2.6.2, which will be out
sometime this month.

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1047272

Title:
  TestContext.CurrentContext.Result throws NullReferenceException

Status in NUnit V2 Test Framework:
  Fix Committed

Bug description:
  We are using stable NUnit 2.6 for testing using C# .Net code mainly due to new /runlist command line option.
  Before each test in method with TestFixtureSetUp attribute we check if the test shouldn't be skipped. If so Assert.Ignore is called.
  Later in method with TestFixtureTearDown attribute we are used to check TestContext.CurrentContext.Result for actual test result and report it. In version 2.5.8 it worked correctly and Status in Result was properly set. Since 2.6.0 it throws NullReferenceException. Is it something planned and we should call Assert.Ignore or check for the Result somewhere else? Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1047272/+subscriptions