Scott Hanselman's post on MbUnit caught my attention. I have fully embraced Team System's full stack of tools since last fall when it was in Beta. I especially like the integrated unit testing framework. Having grown up an NUnit user, it was a natural progression.
I am not familiar with MbUnit but the one feature that Scott points out in his post about being able to parameterize a single test rather than “polluting” the test project with 27 different version of different ways data might be thrown at a particular API call you are developing, is an awesome feature.
I wonder what it would take to extend the VSTS Unit Testing framework to incorporate such a feature…
Tags: unit testing, mbunit, team system