Show exception details and stacktrace if TestFixtureSetUp blows up

[hickford]

Reproduced from https://stackoverflow.com/questions/1411676/how-to-diagnose-testfixturesetup-failed

NUnit should show exception details and stacktrace if TestFixtureSetUp blows up, as it does when a test fails.

Test Name:  ExampleTest
Test FullName:  ExampleTests.ExampleTest
Test Source:    ExampleTests.cs : line 56
Test Outcome:   Failed
Test Duration:  0:00:00.0000001

Result Message: TestFixtureSetUp failed in ExampleTests

[CharliePoole]

The NUnit VS Adapter is... well, an adapter! It can only adapt NUnit to the interfaces and displays provided by the Visual Studio Test Window. That window is exclusively devoted to listing individual test cases, so it's difficult to report any other kind of error.

If you run tests under the NUnit Console runner, TestFixtureSetUp failures are listed individually. Similarly, if you use the Gui, the properties of the node representing the fixture will show the exact result and the Errors and Failures tab will also list it.

There are two ways I can imagine handling this request...

1. Display the information as a sort of log entry in the Output window at the bottom of the screen. This is already cluttered with warnings of various kinds but it may still be desirable. If the individual test indicated a setup failure, you might have to look here.
2. Create an error message from the setup failure and use it for every test in that fixture. That way, the error would be seen no matter which method you selected. Ironically, this is what NUnit used to do. We stopped doing it because the console output became crowded with repeated failures whenever a TestFixtureSetUp threw an exception. Since NUnit no longer reports the info in this way, I would have to look at the code to see how feasible it is to do it within the adapter.

[CharliePoole]

No comments for eight months!!! I'll give it another month before closing. How do folks think this situation should be handled?

[OsirisTerje]

I've been looking at doing it as your option 1 above in the NUnIt3 adapter and the same can be done here.

[unickq]

I think it might help - to store TestFixtureSetUp/TestFixtureTearDown exceptions/statuses somewhere