Right, so why does the Runner GUI crash? Aren't the actual tests run in separate process?
At the very least, it should be able to tell which test it was running when it crashed, and I wouldn't expect the test runner window to die (which, indeed, it doesn't - but seems to get very, very confused that the actual runner died). -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/1083821 Title: NUnit runner crashes when test gives StackOverflowException Status in NUnit V2 Test Framework: Invalid Bug description: Made a brand new test project, and in the default TestMethod1 method: [Test] public void TestMethod1() { TestMethod1(); } The runner application gives "NUnit-Agent has stopped working", and then the main GUI crashes out when anything else is done with it. The runner reports 2.6.2.12296 as it's version. To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/1083821/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
