The above exception is caused by the test DefaultExceptionThrowerTests.Should_throw_correct_exception_when_resolved_constructors_are_used.
If you comment out that test, no problem arises. Discovery shows 982 test cases and the IDE displays them all.
Editing the expected message for the second and third cases so that the test name does not get truncated also eliminates the problem. Discovery then shows all 985 cases. Of course the edited cases then fail.
My hypothesis is that the truncated test cases are causing some failure in Visual Studio, but I have no way to verify that. I'm told that the truncation is by design. We have a bug for NUnit to try to shorten long names in a more useful way before they go to Visual Studio.
By the way, your tests run fine in the NUnit Gui.
I don't see any more that we can do about this problem, but I'll wait for you to comment before closing the bug. Your best recourse is to either shorten the names of the tests yourself or provide an alternate name using TestCaseData or in your own code that emulates it. I spent a bit of time on this because I thought there might be some way that NUnit could highlight the source of the problem, but it appears to be out of our hands.
The above exception is caused by the test DefaultExceptio nThrowerTests. Should_ throw_correct_ exception_ when_resolved_ constructors_ are_used.
If you comment out that test, no problem arises. Discovery shows 982 test cases and the IDE displays them all.
Editing the expected message for the second and third cases so that the test name does not get truncated also eliminates the problem. Discovery then shows all 985 cases. Of course the edited cases then fail.
My hypothesis is that the truncated test cases are causing some failure in Visual Studio, but I have no way to verify that. I'm told that the truncation is by design. We have a bug for NUnit to try to shorten long names in a more useful way before they go to Visual Studio.
By the way, your tests run fine in the NUnit Gui.
I don't see any more that we can do about this problem, but I'll wait for you to comment before closing the bug. Your best recourse is to either shorten the names of the tests yourself or provide an alternate name using TestCaseData or in your own code that emulates it. I spent a bit of time on this because I thought there might be some way that NUnit could highlight the source of the problem, but it appears to be out of our hands.
Charlie