Sunday, July 11, 2010

C# TDD with Visual Studio

I have been working with C# in the .NET world for a while now, but I can't help being puzzled by something. There are plenty of tools around that help the developer to work with Visual Studio, but in a test driven environment, the cycle seems far too slow and painful to be of value. Trying to drive development with tests is almost not worth it - by the time the test has run, its been such a long time, I've almost forgotten my ideas or train of thought. But then again - maybe its just my age!

Are there any tricks I am missing out on? Are there language or tool constraints? Working with Java on Eclipse is quick and relatively easy - working in Ruby it's a breeze - so in these environments, its really fun. However, I do believe that without certain support from the language and toolsets, blind adoption of certain (mostly useful and powerful) techniques is actually counterproductive.

Any thoughts or ideas welcome.