Build and Test Integration (CMMI)
By using build and test data fields, you can perform the following actions:
Associate Bugs with the builds where they were found or fixed.
Mark Test Cases as either manual or automated and store information to support automated test cases.
For Test Cases and Shared Steps, define the action steps, the validation steps, and the data that are used to perform tests.
This topic describes data fields that are available in only specific types of work items that are provided with the following process templates:
MSF for Agile Software Development v5.0
MSF for Capability Maturity Model Integration (CMMI) Process Improvement v5.0
In this topic
Build and Test Data Fields that Appear on Work Item Forms
Additional Fields that Support Query and Reporting
Build and Test Data Fields that Appear on Work Item Forms
The following table describes the fields that you can use to track information that relates to builds and tests. For information about data types and default field attributes, see Working with Work Item Fields.
Field name |
Description |
Reference name |
Data type |
Default value of the reportable type attribute |
Default value of the index attribute |
---|---|---|---|---|---|
Automated Test Storage |
The assembly that contains the test that automates the Test Case. (Test Case only) |
Microsoft.VSTS.TCM.AutomatedTestStorage |
String |
None |
False |
Automated Test Type |
The type of test that automates the Test Case. (Test Case only) |
Microsoft.VSTS.TCM.AutomatedTestType |
String |
None |
False |
Automation Status |
The status of a Test Case. You can specify the following values:
(Test Case only) |
Microsoft.VSTS.TCM.AutomationStatus |
String |
Detail |
False |
Found In |
Product build number, also known as a revision, in which a Bug was found. |
Microsoft.VSTS.Build.FoundIn |
String |
Dimension |
False |
Integration Build |
Product build number that incorporates the code for a Requirement, a Change Request, or a Bug. |
Microsoft.VSTS.Build.IntegrationBuild |
String |
Dimension |
False |
Steps |
The action and validation steps that are required to perform the test. (Test Case and Shared Steps only) |
Microsoft.VSTS.TCM.Steps |
TestStepsControl |
None |
False |
Steps to Reproduce |
The steps that are required to reproduce unexpected behavior. (Bug only) |
Microsoft.VSTS.TCM.ReproSteps |
HTML |
None |
False |
System Info |
Information about the software and system configuration that is relevant to the Bug. (Bug only) |
Microsoft.VSTS.TCM.SystemInfo |
HTML |
None |
False |
Additional Fields that Support Query and Reporting
The following fields do not appear on work item forms, but these fields are tracked for each type of work item. You can use these fields to filter queries and create reports.
Field name |
Description |
Reference name |
Data type |
Default value of the reportable type attribute |
Default value of the index attribute |
---|---|---|---|---|---|
AutomatedTestId |
The ID of the test that automates the Test Case. (Test Case only) |
Microsoft.VSTS.TCM.AutomatedTestId |
String |
None |
False |
AutomatedTestName |
The name of the test that is used to automate the Test Case. (Test Case only) |
Microsoft.VSTS.TCM.AutomatedTestName |
String |
None |
False |
LocalDataSource |
The local data source that supports the Test Case. (Test Case only) |
Microsoft.VSTS.TCM.LocalDataSource |
HTML |
None |
False |
Parameters |
The parameters to be tested. (Shared Steps and Test Case) |
Microsoft.VSTS.TCM.Parameters |
HTML |
None |
False |
See Also
Concepts
Using System Fields and Fields Defined by the MSF Process Templates
Finding Bugs, Tasks, and Other Work Items