Creating and Running Unit Tests for Existing Code

This section provides instructions about how to create unit tests, gives some background information about how to test methods that have restricted access, and describes the various assert classes that you can use in unit tests.

Key Tasks

Use the following topics to help you create and run unit tests:

Tasks	Associated Topics
Create and run a unit test: Describes how to create a unit test that is populated with data for the method being tested using the Visual Studio Application Lifecycle Management testing tools. You can then add Assert statements to apply testing logic to your unit tests. You can also create a blank test class and supply the details manually. Basic unit tests are ideal for test-driven development. Additionally, you can create a unit test for an .EXE or a .DLL for which you do not have access to the source code.	How to: Create and Run a Unit Test How to: Create a Basic Unit Test How to: Create a Unit Test without Source Code
Create a data-driven unit test: You can create a unit test that retrieves values from a data source instead of typing values into a test method.	How to: Create a Data-Driven Unit Test
Create unit tests that can access internal, private, and friend methods: Using Visual Studio Application Lifecycle Management you can create unit tests with the ability to access internal, private and friend methods. Note The use of Accessors has been deprecated in Visual Studio 2010 and will not be included in future versions of Visual Studio.	Unit Tests for Private, Internal, and Friend Methods Using Publicize to Create a Private Accessor
Determining whether your unit test passed or failed: You can create various kinds of assert statements, which you can use in unit tests for purposes such as comparing values or collections or checking for specific test results.	Using the Assert Classes
Running tests as a 64-bit process: You can now run tests and collect code coverage information as a 64-bit process.	How to: Run a Unit Test as a 64-bit Process
Run unit tests that target the .NET Framework 3.5 and test SharePoint applications: For Visual Studio 2010, the default target version of the .NET Framework in test projects is the .NET Framework 4. If you upgrade test projects from Visual Studio 2008, they are upgraded to target the .NET Framework 4 by default. You can edit the project properties and explicitly re-target the project to the .NET Framework 3.5. Targeting the .NET Framework 3.5 lets you test SharePoint 2010 applications. Note In the .NET Framework 3.5, multitargeting is supported for test projects that contain only unit tests. The .NET Framework 3.5 does not support any other test type, such as coded UI or load test. The re-targeting is blocked for test types other than unit tests.	How to: Configure Unit Tests to Target .NET Framework 3.5
Running tests in parallel to speed up test execution time: You can use a computer that has multiple CPUs or a single CPU with multiple cores to run your unit tests in parallel to speed up the overall test execution time.	How to: Run Unit Tests Faster Using a Computer with Multiple CPUs or Cores
Running unit tests that collect useful information about the machine on which they are running: You can create or modify a test setting and use it when you run your unit tests to collect system information and IntelliTrace data.	Create Test Settings to Run Automated Tests from Visual Studio Setting Up Machines and Collecting Diagnostic Information Using Test Settings.
Running unit tests on multiple machines: You can use a group of computers to run unit tests remotely and concurrently on several computers by using a test controller and one or more test agents that are specified in a test setting. Note Using multiple machines requires Visual Studio 2010 Ultimate.	Running Unit Tests on Multiple Machines Using a Test Controller and Test Agents
Perform stress and performance analysis by using load tests for your unit tests: You can create a load test and add your unit tests to it to help isolate performance and stress issues in your application. Note Creating and using load tests requires Visual Studio 2010 Ultimate.	Creating and Running Unit Tests for Existing Code Creating and Editing Load Tests How to: Add Web Performance, Unit and Coded UI Tests to a Load Test Scenario Using the Load Test Editor How to: Remove Web Performance Tests, Unit and Coded UI Tests from a Load Test Scenario Using the Load Test Editor
Extending unit tests using the unit testing framework: You can use the Microsoft.VisualStudio.TestTools.UnitTesting namespace to create custom unit tests.	Coding Custom Unit Tests Using the Unit Testing Framework

Related Tasks

Unit Tests and C++, Generics, and Web Services

Gain knowledge of the differences and additional information that you need about unit tests for C++, generic methods, Web Services, and smart devices.

Running Automated Tests Using Microsoft Visual Studio

You can run automated tests locally from Microsoft Visual Studio 2010. Or, you can run your automated tests remotely by using test agent controllers and test agents.

Reference

Microsoft.VisualStudio.TestTools.UnitTesting

Microsoft.VisualStudio.TestTools.UnitTesting.Web

See Also

Tasks

Walkthrough: Creating and Running Unit Tests

Walkthrough: Run Tests and View Code Coverage

Walkthrough: Using the Command-line Test Utility

Concepts

Anatomy of a Unit Test

Creating and Managing Tests

Reviewing Test Results

Verifying Code by Using Unit Tests