This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: TestDriven.NET and Test With Debugger
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
TestDriven.NET is just amazing. Besides obsoleting the separate NUnit GUI app, with the ability to right click and select “Run Test(s), it has other great features. I'd like to give you a tip on one since it comes up with my audiences all the time. People ask, “But what if I have a problem with my unit test, how do I debug it?” Of course, you can set the NUnit GUI app to drive your debugger in VS.NET but that's a bit of a pain and friction to a lot of developers. With the “Test With...Debugger” right menu option in TestDriven.NET, you can simply out your cursor on the unit test name you want to debug (in the code) and choose this option. The debugger will automatically start up in your unit test and you can set breakpoints. Brilliant and low friction!
Previous Topic
