By design, there is no such signal. The reason is that Gallio needs to be able to terminate a misbehaving test promptly so it wouldn't want to test to get stuck running a potentially indefinite operation in TearDown.
The best approach to these sorts of problems is to instead ensure that SetUp or some other auxiliary process takes care of cleaning up any cruft left behind from a previous iteration. Jeff. On Mon, Jul 12, 2010 at 10:20 PM, Rajeshwari Patil < [email protected]> wrote: > > Hello, > > Is there any event raised by Gallio or MBUnit when the test is stopped > manually by pressing the "Stop" button from Gallio. > > The reason is, TearDown() function not executed when the test is stopped > manually. > > Or is there any other way to do this ? > > Regards > Rajeshwari > > -- > You received this message because you are subscribed to the Google Groups > "MbUnit.User" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<mbunituser%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/mbunituser?hl=en. > -- You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en.
