Configure and run the version verification test from msdn)

From: http://msdn2.microsoft.com/zh-cn/library/ms182465 (vs.80). aspx # createbvttestlist

Visual Studio team system

How to: Configure and run a version Verification Test (BVT)

A version Verification Test (BVT) typically consists of a broad set of tests used to verify the overall quality of a specific version. BVT is usually run automatically according to the SET Plan and often run at night. You can also run it manually, for example, after the automatic operation fails. If all tests in BVT have passed, this version is considered successful.

BVT uses different parts of Visual Studio team system: Team edition for testers, Team FoundationSource codeManagement and team Foundation build. First, use team edition for testers to create a test list that contains the tests to be included in BVT. Then, use the team Foundation SourceCodeManage to check the test list into source code management. Finally, run BVT using team Foundation build or schedule regular BVT running.

Note:

Team Foundation build and team Foundation source code management do not belong to team edition for testers. To use the features of these products, in particular, to perform most of the steps in the following process, you must install all team systems or single product team Foundation source code management and team Foundation build (probably on different computers ). In addition, the client computer must install team explorer and the Visual Studio user session must be connected to the team Foundation server computer. For more information about how to connect to the team Foundation server, see How to: connect to team Foundation server.

This topic describes all the processes required to create, store, and run a version verification test:

• Create a BVT test list. Create a test list and fill it with the tests required by BVT. For more information, see create a BVT test list. 

• Check in BVT. Add the solution and BVT to source code management. For more information, see check in BVT.

• Create a version type and specify the BVT test list to run as part of the version. Before using team Foundation build to run a version, you must first create a version type. For more information, see create version type.

• Running BVT version type. Running version; this will also automatically run BVT. For more information, see running the BVT version type.

Create BVT test list create BVT test list in test Manager

1. In the test Manager window, click View test list to display the test List Pane.

2. Right-click "test list" and click "create test list ".

   The create test List dialog box is displayed.

3. Enter the name of the test list that will contain the version verification test. For example, Type"Bvts".

4. (Optional) Type A description of the BVT test list, and select the location where you want to place the new test list in the test list hierarchy.

5. Click OK ".

   New"Bvts"The test list is created and displayed in the test list hierarchy pane.

6. Click "all loaded tests" to display all tests in solution.

7. Select the test to run as a version verification test and drag it into the new"Bvts"Test list.

   Note:
   To select a test and drag it, click the row in the test Manager window. To select multiple tests, use Shift + Click and CTRL + Click. Do not use the check box to perform this operation.

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

   This"Bvts"The test list (and all test lists in the solution) resides in the test metadata file of the solution. The metadata file extension is. vsmdi. For more information, see use test list.

Check in BVT

During this process, all files of the solution will be checked in. Includes the solution's test metadata file, which contains the test list and test. The test metadata file is automatically updated to reflect the changes as long as you add, delete, or re-organize the test list, or change the content of the test list.

Check BVT in source code management

1. Connect to the team Foundation server computer. For more information, see How to: connect to team Foundation server.

2. If the solution is not in source code management, add it to source code management. For more information, see How to: Add a project or solution to source control.

3. Click View, and then click pending check-in. The pending check-in window is displayed.

4. Check in all files of the solution. For more information, see How to: Check in pending changes.

   Note:
   If you are using Visual Studio team system, a specific group process controls the creation and management of BVT. For example, the process may require that the version be verified locally before the code is checked in and before the code is tested.

   After the check-in is completed, a lock icon appears next to each file in Solution Explorer to indicate that it is in the checked-in status. For more information, see How to: Identify source control item status in Solution Explorer.

   The checked-in test can be used by the Team Foundation build function of the team system. You can now create a version type that contains the test to be run in BVT.

Create version type create BVT version type

1. In the "Team Resource Manager" window, click the Team Project.

2. Right-click "team build" 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. For more information, see How to: create a new build type

   Key Points
   On the select generate option page in the new team build type creation wizard, click Run test ". Then, select the test metadata file that contains the BVT test list created in the create BVT test list. Finally, select the test list that contains the test (your BVT test) You want to run.

4. After entering information in the Wizard, click Finish ".

   The new version type is displayed in the "team builds" folder in the "Team Resource Manager" window.

Run BVT version type run BVT using team build

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

2. Show "generate {Team Project Name} Dialog box, and list all existing version types. Make sure that your version type is selected.

3. (Optional) change the version location and directory.

4. Click Generate ".

   For more information, see How to: Run and generate Based on the generation type. To schedule periodic generation, see How to: Configure scheduled generation (command line ).

See Task

How to: organize a test as a test list
How to: create a new build type
Other resources

Working with Team Foundation source control

Digress:
1. It will be transferred only for future convenience.

2. I have been exploring TFs recently. I have been thinking about "test-driven development" for two years, but there are always reasons for me to give up. This time I picked it up again, hoping I can do it this time.

3. I found a good tool for database unit testing, massdatahandler (on blog.joycode.com, socct saw it. I downloaded it for a while, but I never did it. I tried it today. Really Useful)

5. At last :-) in fact, there is no need to refer to this document. On msdn, it is still Chinese (when can I make a breakthrough in English), but it takes too much time to find it every time. In addition, there are many tools that were rarely used in the past and can not be found for excellent text tickets. Remember it.

6. Finally, Vista was installed last night. I did not expect that many Chinese versions of the software could not be used. There are two other games on the machine that cannot be played. The system occupies 8 GB of hard disk. Starting from the machine, the memory is larger than MB. Terrible.
Even more terrible is the blue screen (I have more than 9 K servers ).