Partilhar via


Build and Test Integration

You use build and test data fields to 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 and validation steps and the data that are used to perform tests.

In this topic

  • Build and Test Data Fields that Appear on Work Item Forms

  • Additional Fields that Support Query and Reporting

The following table indicates the data fields that are valid for each type of work item that is provided with the process template for Microsoft Solutions Framework (MSF) for Agile Software Development v5.0.

Field Name

Bug

Test Case

Shared Step

Automated Test Storage

Not supported check mark Not supported

Automated Test Type

Not supported check mark Not supported

Automation Status

Not supported check mark Not supported

Found In

check mark Not supported Not supported

Integrated in Build

check mark Not supported Not supported

Steps

Not supported check mark check mark

Steps to Reproduce

check mark Not supported Not supported

System Info

check mark Not supported Not supported

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

Automation Status

The status of a test case. You can specify the following values:

  • Not Automated

  • Planned

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 or fixes a bug.

Microsoft.VSTS.Build.IntegrationBuild

String

Dimension

False

Steps

The action and validation steps that are required to perform the test.

Microsoft.VSTS.TCM.Steps

TestStepsControl

None

False

Automated Test Storage

The assembly that contains the test that automates the test case.

Microsoft.VSTS.TCM.AutomatedTestStorage

String

None

False

Automated Test Type

The type of test that automates the test case.

Microsoft.VSTS.TCM.AutomatedTestType

String

None

False

System Info

Information about the software and system configuration that is relevant to the test.

Microsoft.VSTS.TCM.SystemInfo

HTML

None

False

Steps to Reproduce

The steps that are required to reproduce unexpected behavior.

Microsoft.VSTS.TCM.ReproSteps

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. (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

Bug (Agile)

Test Case (Agile)

Shared Steps (Agile)

Using System Fields and Fields Defined by the MSF Process Templates

Finding Bugs, Tasks, and Other Work Items

Other Resources

Work Items and Workflow (Agile)

Work Item Fields (Agile)