Issue with Expected result when running NUnit 2.5.10 tests under 2.6

[Charlie Poole]

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.

[Victor Kropp (kropp)]

NUnit 2.6.1-rc still shows "Method has non-void return value" message if Result = null

[Charlie Poole (charlie.poole)]

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.