How to Automate BVTs in TFS

Following Post gives you an idea about configuring BVTs in TFS. Please follow the steps below.

A build verification test (BVT) typically consists of a broad suite of tests that are used to verify the overall quality of a particular build. BVTs are usually automated and run on a set schedule, frequently at night. They can also be run manually, such as after an automated run has failed. A build is considered a success if all the tests in the BVT have passed.

BVTs use different areas of Visual Studio Team System: Visual Studio Team System Test Edition, Team Foundation version control, and Team Foundation Build. First you use Test Edition to create a test list that contains the tests you want included in your BVT. Then you check in that test list to source control, using Team Foundation version control. Finally you use Team Foundation Build to run the BVT, or to schedule regular runs of the BVT.

This topic describes all the procedures that are required to create, store, and run build verification tests:

1.         Create a BVT Test List.

To create a BVT test list in the Test List Editor do the following.

1. In the Test List Editor, click By Test List to display the test list pane.

2. Right-click Lists of Tests and then click New Test List.

              This displays the Create New Test List dialog box.

3. Type the name of the test list that will contain your build verification tests; for example, type BVTs.

4. (Optional) Type a description of your BVT test list, and select a location in the test list hierarchy to put the new test list.

5. Click OK.

              Your new BVTs test list is created and appears in the test list hierarchy pane.

6. Click All Loaded Tests to display all the tests in your solution.

7. Select the tests that you want to run as your build verification tests and drag them into the new BVTs test list.

8. (Optional) To verify the contents of the test list, click it in the test list hierarchy pane.

                       This BVTs test list, together with all the test lists in your solution, resides in your solution's test metadata file. Test metadata files have the extension .vsmdi.

 

2.         Check in the BVT

In this procedure, you check in all the files of your solution. This includes the test metadata file of your solution, which contains your test lists and tests. Whenever you add, delete, or reorganize test lists, or change the contents of test lists, your test metadata file is automatically updated to reflect those changes.

To check in the BVT to source control

1. Connect to a Team Foundation Server computer.

2. If your solution is not already in source control, add it to source control.

3. Click View and then click Pending Checkins to display the Pending Checkin window.

4. After the check-in operation is finished, a padlock icon is displayed next to each file in Solution Explorer to indicate its Checked In status.

5. Your checked-in tests are available to the Team Foundation Build feature of Team System. You can now create a build type that contains the tests you want to run in your BVT.

 

3.         Create a Build Type

To create the BVT build type

1. In the Team Explorer window, click your team project.

2. Right-click Team Builds and then click New Team Build Type.

              The New Team Build Type Creation Wizard appears.

3. Follow the steps in the New Team Build Type Creation Wizard.

4. When you have finished entering information in the wizard, click Finish.

              Your new build type appears in the Team Explorer window under the Team Builds folder.

 

4.         Run the BVT Build Type

To run the BVT using Team Build

1. On the Build menu, click Build {Team Project Name}.

2. The Build {Team Project Name} dialog box is displayed with a list of all existing build types. Make sure your build type is selected.

3. (Optional) Change the build location and directory.

4. Click Build.