Archive for mbunit tag

My MbUnit first experience

June 2007 – March 2008 .NET () • 1,073 views • 4 responses

I needed to run some unit tests today against an open source project that has some written using the MbUnit fixtures. Having previously used csUnit and NUnit I felt confident the process would be a breeze. Oh how wrong I was… I decided to show the process I took as a screencast, but some of the highlights are covered below:

View the MbUnit first experience screen cast (Flash) (7MB)

Installer abandons you

No icons created for you, no getting started info, no indication of where it put files unless you caught the window on-screen for 1 second. It may as well be in ZIP format – at least you’d know where you unpacked it.

Web site “Overview” and “Getting Started” pages have nothing about running tests

Some information on creating them and what the product is about but nothing about how to actually use it or get started running tests. That is buried away below text fixture type information.

Silently failing tests in GUI tester

Once you finally make it to the GUI tester and load the assembly and hit run… should an exception fire then the GUI doesn’t so much as display an error message or even indicate a test failed. It simply says there are x number of tests to run, 0 success, 0 failed, 0 ignored and 0 skipped.

If you want to actually see indication of the error you have to head into Report whereupon the option to output to text throws another exception.

Thankfully HTML works.

Inconsistent GUI

Not as essential as the other points but still valid…

Major mismatch between context menu and main menu options. Some options available on one and not the other (NCover, Tree) and where they are available on both are named differently (Load Project becomes Load Config).

“Remove Assemblies…” does not prompt with dialog as “…” might suggest but removes All assemblies.

Given the amount of discussion I’ve seen on MbUnit I can’t help but imagine I’m missing something.

Update

It would appear the GUI has been neglected in favour of IDE integration with TestDriven.NET. It still silently fails however.

[)amien