nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

It's not possible to specify a null result in a pre-2.6 version of the
framework. This bug was fixed in 2.6 by adding a separate property to
the attribute indicating that the expected result should be used. NUnit
2.6 running tests referencing an earlier framework continue to display
this bug because it's a bug in the framework assembly itself.

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

Title:
  Issue with Expected result when running NUnit 2.5.10 tests under 2.6

Status in NUnit V2 Test Framework:
  Fix Released

Bug description:
  The  following test

  [TestCase(1, 2, Result = 3)]
  [TestCase(3, 4, Result = 7)]
  [TestCase(5, 6, Result = 11)]
  public int Add_Test(int a, int b)
  {
      return a + b;
  }

  results in 3 non-runnable tests with the message "Method has non-void
  return value" when the test references NUnit 2.5.10 (or earlier) and
  it is run using the 2.6 gui or console runner.

  This is the result of a change in 2.6 affecting compatibility.

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