Test With... Runtime

I thought I'd take a souvaneir snapshot before I repave.  The final straw was installing .NET v2.0.31112.  This is the runtime you get with the beta of Monad over at BetaPlace.  Installing it in a virtual machine would have been sensible, but I was impatient.

Below you can see the 'Test With... Runtime' menu.  This menu is auto-populated when you install the add-in.  At the moment it looks for installed versions of .NET and Mono.  With some manual configuration it will work with Rotor/SSCLI as well (if anyone is interested I'll write this up as well).

The test runner used by 'Test With... Runtime' is much simpler than the one used by 'Run Test(s)'.  Whereas 'Run Test(s)' will detect the test framework being used and execute a suite of tests, 'Test With... Runtime' will simply execute a single method using the specified runtime. This makes sense when you can't count on your test execution engine working on the target runtime (a serious issue when working with Rotor/SSCLI and early versions of Mono).

3 Comments

  • I ended up installing this latest version when I downloaded mbUnit, and now my Debug doesn't work.

  • You have by any chance uninstalled csUnit recently? This seems to break Visual Studio's add 'New Project' wizards and this add-in's debugging support.



    Could you see if 'New Project' wizards are working and report back?



    Thanks, Jamie.

  • I uninstalled csUnit some time ago, but have done unit testing using nunitaddin in the meantime before installing mbunit. The behaviour I'm seeing is that a right click on a [Test] compiles the first time but does not run the test, and subsequent just doesn't run the test. I'm hunting down all installed nunit* to remove, and then will reinstall.

Comments have been disabled for this content.