Dela via

Build and test integration field reference

  • Artikel

You use Team Foundation Server (TFS) 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.

Test Manager and the test work item types (WITs) use the following fields to track test plans, progress, and results. The availability of the WITs is based on the version of TFS installed on your application-tier. To learn more about using these WITs, see Plan Manual Tests using Team Web Access.

TFS 2013.0

TFS 2013.2

TFS 2013.3

  • Bug

  • Shared Steps

  • Test Case

  • Bug

  • Shared Parameters

  • Shared Steps

  • Test Case

  • Bug

  • Shared Parameters

  • Shared Steps

  • Test Case

  • Test Plan

  • Test Suite

To learn more about upgrading an existing team project to get WITs that your team project currently doesn’t have, go here.

Build and test data fields that appear on work item forms

The following table describes the fields that are defined in one or more of the test WITs. For information about data types and field attributes, see Define and modify work item fields.

To customize a field or pick list, see Modify or add a field to support queries, reports, and workflow.

Field name

Description

Reference name

Data type

Default value of the reportable type attribute

Default value of the index attribute

Automation Status (See Note 1)

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

  • Not Automated

  • Planned

To run automated tests, see Automate a test case in Microsoft Test Manager.

Microsoft.VSTS.TCM.AutomationStatus

String

Detail

False

Found In (Note 2)

Product build number, also known as a revision, in which a bug was found.

Microsoft.VSTS.Build.FoundIn

String

Dimension

False

Integration Build (Note 2)

Product build number that incorporates the code or fixes a bug.

Microsoft.VSTS.Build.IntegrationBuild

String

Dimension

False

Issue

Indicates that the Shared Steps is associated with an expected result. Allowed values are Yes and No. (Shared Steps only)

Microsoft.VSTS.Common.Issue

String

Dimension

False

Parameters(Note 3)

Contains the parameters to use when running a manual test. (Shared Parameters, Shared Steps, and Test Case)

Microsoft.VSTS.TCM.Parameters

HTML

None

False

Steps

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

Microsoft.VSTS.TCM.Steps

TestStepsControl

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

Test Suite Type (Notes 1 and 4)

The test suite category. Allowed values are:

  • Query Based: Use to group together test cases that have a particular characteristic - for example, all the tests that have Priority=1. The suite will automatically include every test case that is returned by the query that you define.

  • Static: Use to group together test cases designed to track the test status of backlog items. Each test case that you add to a requirement-based test suite is automatically linked to the backlog item.

  • Requirement Based: Use to group together test cases with any characteristics or test suites.

For more information, see Plan Manual Tests using Team Web Access.

Microsoft.VSTS.TCM.TestSuiteType

String

Dimension

False

Notes

  1. Do not customize the pick list for these fields. The system accepts only those values listed.

  2. By adding a GLOBALLIST element to the FIELD definition, you can provide a drop-down menu of builds that users can choose from. To learn how, see Fields that support integration with test, build, and version control.

  3. Requires TFS 2013.2 or TFS 2013.3 to be installed on the application-tier server and existing team projects to be updated to support Shared Parameters. To learn more, see Configure features after a TFS upgrade.

  4. Requires TFS 2013.3 to be installed on the application-tier server and existing team projects to be updated to support Test Plan and Test Suite.

Additional fields

The following fields do not appear on work item forms, but these fields are tracked for test cases or test suites. You can use some of 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

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

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

Query Text

Field used to capture the query defined for a Query-based suite type.

Microsoft.VSTS.TCM.QueryText

PlainText

None

False

Test Suite Audit (See Note 1)

Tracks additional operations performed when modifying a test suite, for example: adding tests to a test suite or changing configurations. This field can be viewed through the History tab or through a separate query. There will be a consolidated history view, including changes performed to work items field and changes resulting from related artifacts such as test points and configurations.

Microsoft.VSTS.TCM.TestSuiteAudit

Plain Text

None

False

Test Suite Type ID (Note 1, 2)

A system assigned value that corresponds to the test suite category and only applicable to test suites. Assigned values are:

  • 1 (Static)

  • 2 (Query-based)

  • 3 (Requirement- based)

Microsoft.VSTS.TCM.TestSuiteTypeId

Integer

None

False

Notes

  1. Requires TFS 2013.3 to be installed on the application-tier server and existing team projects to be updated to support Test Plan and Test Suite.

  2. Do not customize the pick list for these fields. The system accepts only those values listed.

See Also

Concepts

Work item field reference for Visual Studio ALM