All runners should yield the same result. The whole back-end is completely unified.
It might matter when the transaction gets created. If it happens in SetUp or TearDown then it won't be captured by the ambient transaction established by [Rollback] unless you add the IncludeSetUpAndTearDown = true. Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruno Wouters Sent: Tuesday, March 10, 2009 4:00 PM To: MbUnit.User Subject: MbUnit NHibernate and Rollback attribute Hi all, I'm wondering if there are any known issues with NHibernate, MS SQL, Framework 2 and MbUnit v3 using the Rollback attribute. I saw some strange behaviour. When I ran the whole test class a certain test was not rolled back but if I then would run the test individually it does rollback. Does it matter if I start a transaction somewhere in the testcode? (using ISession.BeginTransaction, isolation level is read committed) Can different runners give other test results? (resharper/ testdriven.net) 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 -~----------~----~----~----~------~----~------~--~---
