IIRC, MbUnit v2 actually runs each fixture in a new thread so that it can easily abort the fixture if a timeout occurs. The thread is disposed at the end of the fixture.
While we could create one AppDomain per fixture, I think it would be very inefficient. My guess is that your tests are failing because they are interacting with one another. One fixture may be setting static variable or making other global changes to the environment that cause subsequent fixtures to fail. To help diagnose the problem, you can look at the first fixture that fails when running all fixtures in the assembly. If it ordinarily runs fine standalone then you have an indication that this fixture is interacting directly or indirectly with a previous fixture. Look for places where the failing fixture uses global state. Then consider how other fixtures also manipulate that state. Good luck, Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of GingerTez Sent: Thursday, January 31, 2008 2:32 AM To: MbUnit.User Subject: MbUnit Tests fail when testing assembly but not when testing class Hi, I've got a problem that tests in different classes within the same assembly execute successfully when testing the class standalone but not when testing the assembly as a whole. The error I get is related to Threading, and I believe it's because when MbUnit tests the assembly it tests all classes using the same base thread. Is there any way to tell MbUnit to completely separate the Threads per class (create a new app domain?) when testing at the assembly level? Thanks in advance, Terry Robinson. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
