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 typeTestArchitect field type
DateTimeDate
IntegerNumber (9 digits only)
Single Line Text
List item

DoubleSingle Line Text
List Item

HistoryMulti Line Text
HTMLMulti Line Text
PlainTextSingle Line Text
Multi Line Text
Label
Hyperlink

StringSingle Line Text
List item
Boolean

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


Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGearはLogiGear Corporationの登録商標であり、Action Based TestingおよびTestArchitectはLogiGear Corporationの商標です。ここに記載されているその他の商標は、各所有者の財産です。

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400