The timeout is intended to abort tests that might misbehave and never finish. For example, you might be writing some concurrency-related code that hits a deadlock.
I think we should add a [Duration] attribute to capture the second meaning: expect that the test will complete within a given time interval. I've created an issue to track this feature request: http://code.google.com/p/mb-unit/issues/detail?id=404 Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruno Wouters Sent: Thursday, March 12, 2009 2:50 PM To: MbUnit.User Subject: MbUnit Timeout attribute aborting thread Hi all, I have a timeout attribute set on all my tests. When the timeout occurs gallio seems to abort the test thread. I suspect this to render the application in an invalid state for other tests. I'm getting some strange errors about ms dtc canceling transactions. Can't the test just complete and then indicate that it has failed due to a timeout? I always thought that aborting a thread should be the last resort... Maybe two timeouts are needed? One would be the expected duration of the test and another to abort the test if it is hanging. Thanks! Greets Bruno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
