Seems like the problem is not MbUnit related by rather TestDriven.NET
related.  When selecting 6/7 individual test fixtures instead of the
complete assembly, TD. net creates a separate app-domain for running
each of the individual fixtures.  This resulted in the code for the
AssemblyCleanUp running before and after every test fixture instead of
just before and after all the test fixtures of the assembly.  When I
run the tests for the complete assembly on project level everything
works as expected.

Carel


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to