Short answer: check out: http://www.codeplex.com/testlistgenerator.
Long answer: I previously discussed Automating Code Coverage from the Command Line. Another way to buff up your unit tests is to add categories to them. For example, suppose you had several long-wrong tests (perhaps unit testing database procedures), and you wanted the ability to run them separately, using categories, from the command line.
The free, 6-year old, open-source NUnit has category attributes, for which you can filter tests easily by. For a variety of reasons, MSTest - the core testing component of Microsoft's flagship development product, after 2 releases (2005 and 2008) still does not have these. I've had the chance to ask to ask people at MSDN events about these, and I've heard a lot of "reasons":
|Proposal for why MSTest does not need categories:||Problem with that:|
|Just put all those tests in a separate DLL|
|Just add the description tag to them and then sort by description in the VS GUI|
|Just filter by any of MSTest's advanced filter GUI features - like class or namespace.|
|Just use MSTest test lists|
|Well, you shouldn't really need categories, just run all your unit tests every time.|
So, if you want to easily get the equivalent of NUnit categories for your MSTest suite, check out http://www.codeplex.com/testlistgenerator.