On Feb 1, 8:06 am, "Johan Appelgren" <[EMAIL PROTECTED]>
wrote:
> On Jan 31, 3:01 pm, "Jason Smith" <[EMAIL PROTECTED]> wrote:
>
> > I'd like to control the sequence of my tests so I'm using the
> > ProcessTestFixture attribute on the class and the TestSequence
> > attribute on the tests. However when I do this MbUnit "finds" one too
> > many tests and executes the last test twice ( not just reporting it
> > twice the code gets executed twice ). The same behaviour occurrs even
> > when I remove the TestSequence attribute. Only when I revert to
> > TestFixture do I get the desired number of tests. Can anybody point
> > me in the right direction to prevent the last test from executing
> > twice?
>
> Can you provide an example class that shows this problem?
>
> I tested with the following class and it was reported as one test when
> I executed it using MbUnit.Cons.exe.
>
> [ProcessTestFixture]
> public class Class1
> {
> [Test]
> [TestSequence(0)]
> public void T1() { }
>
> [Test]
> [TestSequence(1)]
> public void T2() { }
> }
>
> /Johan
Tried with the Zanebug beta and it looks like it does the wrong thing
with ProcessTestFixture. Is that the testrunner you are using?
/Johan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
