Walkthrough: Create And Run Unit Tests As Part of a Team Build
This topic presents the steps to create a C# project, generate unit tests to exercise a particular method in this project, bind the project's source files to a Team Foundation server, and then build the project by using Team Foundation Build. By following these steps, you can configure Team Foundation Build so that the unit tests run as part of the build.
Prerequisites
A build agent with Team Foundation Build installed. Visual Studio must be installed on the build agent.
Connection to a Team Foundation server and at least one team project. For more information, see Walkthrough: Joining a Team Project and How to: Create a Team Project.
Ability to create and queue a build definition. For more information, see How to: Create a Build Definition.
A basic understanding of the C# language.
Required Permissions
To complete this walkthrough, you must have the Administer a build and Administer workspaces permission set to Allow. You must also have the Check in and Check out permissions set to Allow. To create a team project, you must have the Create new projects permission set to Allow, and you must be a member of the SharePoint Central Admins group in Windows SharePoint Server and have Content Manager permissions in SQL Reporting Services.
You must have install permission on the computer on which you run the installer created by Team Foundation Build.
In this walkthrough, you perform the following procedures:
Creating a C# application
Adding units tests to the application
Organize unit tests in a test list
Run unit tests as part of a Team Foundation Build
Creating the C# Solution
To create the bank account application
Open Visual Studio Team System Test Edition.
On the File menu, point to New, and then click Project.
In the New Project dialog box, under Project Types, click Visual C#.
Under Templates, click Class Library.
In the Name box, type BankAccount.
Accept the default location and solution name for the solution.
Select the Add To Source Control check box, and then click OK.
The new Bank Account project is created and shown in Solution Explorer.
In Solution Explorer, double-click the file Class1.cs.
Replace the original contents of Class1.cs with the following code:
using System;
namespace BankAccountNS
{
/// <summary>
/// Bank Account demo class.
/// </summary>
public class BankAccount
{
public enum accountType
{
Gold,
Platinum,
}
public BankAccount(string customerName, double balance)
{
m_customerName = customerName;
m_balance = balance;
}
public string CustomerName
{
get { return m_customerName; }
}
public double Balance
{
get { return m_balance; }
}
public accountType GetAccountType
{
get
{
if (Balance > 15.00)
return accountType.Platinum;
else
return accountType.Gold;
}
}
private string m_customerName;
private double m_balance;
}
}
/* The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred. */
- Save Class1.cs.
Creating the Test Project and Unit Tests
To create unit tests to exercise the GetAccountType() method
In Class1.cs, find the public method name GetAccountType(), right-click it, and then click Create Unit Tests.
In the Create Unit Tests dialog box, expand the BankAccount project node to confirm that the GetAccountType check box is selected.
Click OK.
In the New Test Project dialog box, accept the default name, and click Create.
In Solution Explorer, under TestProject1, double-click BankAccountTest.cs.
Find the method GetAccountTypeTest() and change it to match the following code:
[TestMethod()]
public void GetAccountTypeTest()
{
string customerName = "Mr. Bryan Walton";
double balance = 15.01;
BankAccount target = new BankAccount(customerName, balance);
BankAccount.accountType actual;
actual = target.GetAccountType;
Assert.AreEqual(actual, BankAccount.accountType.Platinum);
}
Return to the GetAccountType() method in Class1.cs, right-click GetAccountType(), and then click Create Unit Tests.
The Create Unit Tests dialog box appears with GetAccountType selected.
Click OK.
This action creates another test method in BankAccountTest.cs called GetAccountTypeTest1().
Open BankAccountTest.cs, find GetAccountTypeTest1(), and change it to match the following code:
[TestMethod()]
public void GetAccountTypeTest1()
{
string customerName = "Mr. Bryan Walton";
double balance = 14.99;
BankAccount target = new BankAccount(customerName, balance);
BankAccount.accountType actual;
actual = target.GetAccountType;
Assert.AreEqual(actual, BankAccount.accountType.Gold);
}
- Save BankAccount.cs.
Collect your Unit Tests into a Test List
Create a test list and check it in to Team Foundation source control
On the Test menu, point to Windows, and then click Test List Editor.
Right-click the List of Tests node, and then click New Test List.
In the Create New Test List dialog box, in the Name box, type UnitTests, and then click OK.
The new test list appears in the test list hierarchy pane.
Click All Loaded Tests to show the two unit tests that you created earlier.
Note
Do not select the check boxes next to the tests.
Drag both tests into the newly-created UnitTests list.
Select the UnitTests check box.
On the Test menu, point to Run, and then click Tests in Current Context.
The Test Results pane shows the results of the tests. Both unit tests should pass. If they do not, check the source code to ensure that it matches the code that was provided earlier in this exercise.
Check in the test project along with the other C# code to Team Foundation version control by performing the following steps:
On the View menu, point to Other Windows, and then click Pending Changes.
In the Pending Changes pane, click Check In.
Run Your Unit Tests As Part Of a Team Build
To configure a build definition to run your unit tests
On the View menu, click Team Explorer.
In Team Explorer, select the team project that holds the source-controlled C# solution files and test list.
On the Build menu, click New Build Definition.
In the Build definition name box, type UnitTestsBuildDefinition.
Click the Project File tab.
Click Create.
In the MSBuild Project File CreationWizard, select the C# solution that you checked into version control: BankAccount.sln, clear the selections for any other files, and then click Next.
Click Next to accept the default configuration settings.
On the Options tab, select the Run test check box.
Under Test list to run, select UnitTests, and then click Finish.
Click the Build Defaults tab, and in the Build agent list select a working build agent.
In the Builds will be staged to the following share box, type a build staging location, and then click OK to create the build definition.
In Team Explorer, expand the Builds folder for the team project, and then click the name of the build definition that you just created.
On the Build menu, click Queue New Build.
In the Queue Build dialog box, click Queue.
The Build Explorer pane displays a list of queued build definitions. The build that you just queued will be in the list.
When the build finishes, click the Completed tab to display completed builds.
Your build definition should have a check mark in a green circle next to it, which signifies that the build succeeded.
To verify that your two unit tests passed as part of the build, right-click the build definition name, and then click Open.
Expand the Result details for Any CPU/Release node.
On the Test results line, a summary of the test results appears.
See Also
Tasks
How to: Edit a Build Definition
How to: Delete a Build Definition
How to: Queue or Start a Build Definition
Walkthrough: Creating a Build Definition in Team Foundation Build
Concepts
How to: Create and Run a Unit Test