Right Tool for the Right Job - Part 2

In the previous post I talked about running test in Resharper vs. TestDriven.NET

This time I will compare Visual Studio .NET 2008 (VS) with TestDriven.NET (TD.NET) for another functionality - quick code execution for evaluation purposes.

VS was shipped with a feature called Object Test Bench. The idea was to be able to instantiate an object of a class in order to execute it's methods for quick evaluation. Great idea. The steps to have it going were multiple.

Step 1 - Open Object Test Bench

Step 2 - Class View

Right click on the class

Step 3 - Create Instance

This will create the temporary object in Object Test Bench space.

Step 4 - Invoking Method

Step 5 - Getting Result

Step 6 - Finalizing

Note: to see the result stored under string1, you have to mouse over.

Not the same thing with TD.NET

Step 1 - Point to the method to invoke

Step 2 - See the result

Don't know what about you, but for me it's an obvious difference. Multiple steps in VS vs. single* step in TD.NET. Thanks David for showing this one.

So the right tool for the right job. Do you have any samples? Show it! Heck, why just to limit ourselves with VS only. We can do more than that. How about replacing RDBS with OODBS as the right tool? Sky is the limit.

* If you set your VS to show Output window automatically, it will popup on it's own. Otherwise that will be 2 step process. Still ALT-V, O should make it a step and a half :)