nunit-core team mailing list archive

[Pavel Spacil <pavel.spacil@xxxxxxxxxxxxxx>]

So, I tried your nunit.core.tests and all in TestContextTests passed.
Next I've created small class to reproduce my bug, please see
attachment. It's the minimal version of your tests which we use and
where  you can reproduce the exception. Please remove SolarWinds.Logging
to get it work, it is just internal dll to log using log4net. Thanks for
your previous prompt response.

Environment: Win 7 x64 Enterprise, NUnit 2.6.0 stable, .Net 3.5 & 4 (CLR
is .Net 2.0), CPU Core 2 Duo

** Attachment added: "AssertTest.cs"
   https://bugs.launchpad.net/nunitv2/+bug/1047272/+attachment/3300337/+files/AssertTest.cs

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

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