Unit tests give developers and testers a quick way to check for logic errors in the methods of classes in C#, Visual Basic .NET, and C++ projects. A unit test can be created one time and run every time that source code is changed to make sure that no bugs are introduced.
Note:
Visual Studio 2008 Team Edition for Developers offers two test-related capabilities that were not available in Visual Studio 2005 Team Edition for Developers. First, you can now manage test lists. For more information, see Managing Large Numbers of Tests. Also, you can now obtain code coverage data when you run tests. For more information, see How to: Obtain Code Coverage Data.
Describes the parts of a unit test and the files that are added to your solution when you create a unit test with the Visual Studio Team System testing tools.
Provides links to topics about how to create unit tests, including data-driven unit tests and unit tests for DLLs and EXEs for which you do not have the source code.
Special Considerations for Unit Tests and C++, Generics, Web Services, and Smart Devices
Provides links to topics that describe differences and additional information about unit tests and C++, Generic methods, Web Services, and Smart Devices.
Describes aspects of working with tests, including how to customize and filter test views, how to work with test lists, and how to associate tests with work items.
Describes many aspects of running tests, including how to configure test runs, how to run tests in the Visual Studio IDE and on a command line, and how to debug while you are running a test.
Describes how to create and run generic tests. Generic tests wrap external programs and tests that were not originally developed for use in the Team System testing tools.
Provides links to the walkthroughs that step you through the use of the built-in test types and other topics, such as the collection of code-coverage data.