What is TestDriven.NET

"The Zero Friction Unit Testing Add-In for Microsoft Visual Studio .NET"

Test Driven Development is the practice of writing unit tests for your code before you actually write that code. By writing a test and then writing the code to make that test pass you have a much better idea of what the goal and purpose of your code is. Test Driven Development encourages complete code coverage, which not only increases the quality of your code, but allows you to refactor the internals of a method or class and quickly and easily test the outside interface of an object.

TestDriven.NET makes it easy to run unit tests with a single click, anywhere in your Visual Studio solutions. It supports all versions of Microsoft Visual Studio .NET meaning you don't have to worry about compatibility issues and fully integrates with all major unit testing frameworks including NUnit, MbUnit, & MS Team System.

Download TestDriven.NET 2.0

It's highlights:

1. When running under VS2005 you should find 'Test With... Debugger' a lot faster. It now uses a cached test process is a similar way to the default 'Run Test(s)' test runner. It will no longer do a full solution build or touch your project files before starting. This means is will play nicely with version control and doesn't need to create a '*.Surrogate' project when used with MSTest projects.
2. There is now a 'Repeat Test Run' option on the code context menu. This will rebuild your tests and repeat the test run using the last used test runner. If you prefer to use the keyboard you can associate shortcuts with 'RerunTests', 'RerunWithDefault', 'RerunWithDebugger', 'RerunWithCoverage' or 'RerunWithMSBee'. The 'RerunTests' command will use the last used test runner. The few people who have tried this feature seem to end up using it a lot. :)
3. You can now 'Test With... .NET 1.1' from VS2005. Your tests will be built using MSBee/.NET 1.1 and executed inside a .NET 1.1 process. Any .NET 1.1 build errors will be merged into the VS2005 'Error List'. This is particularly useful when working on class library code that must run on .NET 1.1 and .NET 2.0.
4. You will find 'Go To Reflector' menu buttons on the 'Code', 'Disassembly' and 'Call Stack' context menus. This isn't strictly speaking using testing related, but it can be very useful if you hit a problem on some system or 3rd party code. For example when an exception is thrown you can easily navigate down the call stack and see exactly what caused it.
5. Once in Reflector you can right click on any method and 'Toggle Breakpoint'. This means you can set breakpoints on assemblies you don't have the source for! If you're using this in VS2005 be sure to disable the debugging option 'Enable Just My Code'. You can find this on the VS2005 'Options...' dialog under 'Debugging\Enable Just My Code'.

Click for more information

TestDriven.NET Official Site

Tags: Testdriven.net, test driven programming, unit testing, Microsoft .net, .net framework, nunit

Can't find what you're looking for? Try Google Search!

	Web eshwar123.blogspot.com