nunit-core team mailing list archive

[Andrew Arnott <802093@xxxxxxxxxxxxxxxxxx>]

Yes, I meant 2.5.9, thanks.  Interestingly though, this failure was when
run within TeamCity, which *may* have been running NUnit 2.5.3 now that
I've checked.  Sorry I hadn't noticed that before.  I've reconfigured
TeamCity to run NUnit 2.5.8 (the latest one they offer integration with
apparently) and am running tests again now.

There are no TimeoutAttributes on these tests.  Each failing test calls
a static method which then calls
TestContext.CurrentContext.Test.FullName.

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

Title:
  TestAdapter.get_FullName throws NullReferenceException

Status in NUnit V2 Test Framework:
  New

Bug description:
  I am seeing random test failures in NUnit 2.4.9 because of this NUnit
  bug:

  Test(s) failed. System.NullReferenceException : Object reference not set to an instance of an object.
     at NUnit.Framework.TestContext.TestAdapter.get_FullName()
     at DotNetOpenAuth.Test.TestBase.MeasurePerformance(Action action, Single maximumAllowedUnitTime, Int32 samples, Int32 iterations, String name) in c:\BuildAgent\work\35657a53ee36436f\src\DotNetOpenAuth.Test\TestBase.cs:line 78

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