MbUnit Mystery
time to read 3 min | 547 words

Consider the following code:

using System;

using MbUnit.Core;

using MbUnit.Core.Framework;

using MbUnit.Framework;

 

namespace ConsoleApplication1

{

      [TestFixture]

      public class Class1

      {

            [STAThread]

            static void Main(string[] args)

            {

                  using(AutoRunner auto = new AutoRunner())

                  {

                        auto.Run();

                  }

 

            }

 

            [Test]

            public void TestOne()

            {

                  Assert.AreEqual(200,100+100);

            }

 

      }

}

 

What would be the result of running this code?
Well, one result is that my floppy drive lights up and Filemon register the following activity:

15:13:34.562 ConsoleApplicat:3784 IRP_MJ_CREATE  A: SUCCESS Options: Open  Access: All 
15:13:35.562 ConsoleApplicat:3784 FASTIO_DEVICE_CONTROL A: FAILURE IOCTL: 0x560000 
15:13:35.562 ConsoleApplicat:3784 IRP_MJ_DEVICE_CONTROL A: INVALID DEVICE REQUEST IOCTL: 0x560000 
15:13:35.562 ConsoleApplicat:3784 IRP_MJ_CLEANUP A: SUCCESS  
15:13:35.562 ConsoleApplicat:3784 IRP_MJ_CLOSE  A: SUCCESS  

MbUnit version 2.22.0.0;

If someone can find out what is going on here I would be more than happy.

I tried to debug it, but I can't lie my hands on a fresh pile of MbUnit code {which moved from MbUnit homepage to TestDriven.Net and for which I can find not a sign of in the TestDriven.Net site}.

Solutions are welcome.

Tweet Share Share 0 comments
Tags: