I'm not sure that's the correct use case for the RollBack attribute (I
presume you are using MbUnit 2.x by the syntax). Log4Net would need to
subscribe to the transaction (which I believe is managed by MSDTC, but Jeff
can confirm/deny that).
I've never had a problem with the rollback working in 2.x or 3.x, but I am
using to wrap tests that calls code that utilizes ADO.Net in one manner or
another (EntLib,NHibernate,etc).
For example,
[Test]
[RollBack]
public void Should_Delete_A_User()
{
Assert.IsTrue(MyUserRepo.Delete(12));
}
Calls my repository, deletes a user, return true if successful, which passes
the assert, and then it all gets rolled back.
The only side effect I have seen is if you have identity columns as PKs,
then it "uses" up numbers (not that it truly matters, since the number
doesn't have any meaning anyway)
Phil
Philip Japikse, MCSD.Net, MCDBA, CSM
Principal Consultant
Pinnacle Solutions, Inc
[EMAIL PROTECTED]
www.japikse.blogspot.com
twitter/skimedic
(513) 312-5664
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of suedeuno
Sent: Thursday, December 04, 2008 11:30 AM
To: MbUnit.User
Subject: MbUnit Rollback usage and expectation
I have a simple test that uses log4net to log a message to sql
server.
[Test]
[RollBack]
public void LoggerIsSuccessful()
{
log.Error("Test error");
}
Maybe I'm not using this properly but the rollback never occurs. Am I
missing some requirement?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
