Creating matching custom fields in TestArchitect and Team Foundation Server

User-defined fields in TestArchitect are automatically mapped to TFS custom fields when the names and data types match. During uploads and downloads, the values of matched fields are kept in sync. The values of user-defined fields created in TestArchitect are loaded into their corresponding custom fields in TFS whenever test modules or test cases are uploaded to TFS. Likewise, the values of custom fields in TFS are loaded to their corresponding user-defined fields in TestArchitect, whenever TFS test cases or test suites are imported into TestArchitect.
  • To create a matching user-defined field in TestArchitect, perform the following steps:
    1. In the TestArchitect explorer tree, right-click the Administration > Fields node, and then select New Field.
    2. In the New Field dialog box, enter the following information:
      • Name: The name of the TestArchitect user-defined field must be identical to that of its corresponding custom field in TFS.
      • Apply to: Only Test module and Test case are mappable to TFS custom fields.
      • Value Type: Field data types must match between TestArchitect and TFS. (Learn more.)
      • Default value: Assign a default value to a user-defined field.
        Important: For a TestArchitect user-defined field that maps to a TFS custom field designated as Required, it is essential that a value exist in the TestArchitect field when its corresponding test module or test case is uploaded to TFS. You can ensure that such fields will have values by utilizing the Default Value field in the New Field dialog box. (For existing user-defined fields, defaults can also be set in the Edit Field dialog box.) A given user-defined field for a particular test module or test case may also be set to a specific value via the Information tab of the project item.
      For example, create a user-defined field, Scheduling Start Date.

    3. Click the Create button.
  • To add a matching TFS custom field, please refer to Microsoft's instructions:
    • Microsoft Visual Studio 2015.
    • Microsoft Visual Studio 2013.
    As an example, add the custom Scheduling Start Date field.

Rules for mapping custom fields

Custom fields in TFS may be mapped to user-defined fields in TestArchitect test modules or test cases. Mapping is driven by field names. Fields in TFS and TestArchitect are mapped automatically when their names are identical and their data types are compatible. When uploading from TestArchitect to TFS, values from TestArchitect user-defined fields are loaded into their corresponding custom fields in TFS. Likewise, values from TFS custom fields are loaded into the corresponding TestArchitect user-defined fields when importing tests from TFS to TestArchitect.
Mapped fields must have compatible data types, as specified in the following table:
TFS field type TestArchitect field type
DateTime Date
Integer

Number (9 digits only)

Single Line Text

List item

Double

Single Line Text

List Item

History Multi Line Text
HTML Multi Line Text
PlainText

Single Line Text

Multi Line Text

Label

Hyperlink

String

Single Line Text

List item

Boolean

TreePath Single Line Text

All required custom fields in the TFS test suites or test cases must have values before a TFS to TestArchitect import can take place. Similarly, uploading from TestArchitect to TFS requires that those user-defined TestArchitect fields which map to required TFS fields be populated with values. A value for a user-defined TestArchitect field may be set when the field is created, using the Default value field in the New Field dialog box, or by explicitly setting the given field for the particular project item on the item’s Information tab.