MbUnit and places we can improve
Some feedback from Roy's post, Chris Bilson shares his thoughts here and Roy has kindly shared his addtional thoughts here. A few things jump out here.
- Ease of use
MbUnit has no mocking framework because I would rather leave that to the folks that are writing mocking software and leave MbUnit as a pure unit test framework. MbUnit is supported by all mocking frameworks so we really have no need to complicate the framework with one, I would rather you use the tools you feel most at home with.
MbUnit's documentation are at an early stage like the project its self, it's something that needs to improve and thanks to using a wiki format anyone can jump in and make some edits. It's early days yet for books and articles, but I know of at least two forthcoming books that feature MbUnit and an article on O'Reilly that me and Jay wrote. A few folks have talked about and show-cased MbUnit at user groups and I would welcome more. Of course over time I am sure this area will fill out more.
Ease of use
MbUnit matches NUnit feature for feature (a few things are different but on a whole you have the same asserts and fixtures, if you have used NUnit then you can use MbUnit and feel right at home. MbUnit does have more features so as you dig into these you will start down a new learning curve, of course with more books, articles and documentation the curve will get flatter.