Test entity mappings between TestArchitect and Quality Center

This topic describes how TestArchitect test module and test case fields and contents are mapped to Quality Center tests, determining how information is transferred during the import and upload processes.

The following discussion of element mappings is organized by the affected TestArchitect project entities:

These sections summarize the transfer of data between TestArchitect and Quality Center during both import and upload transmissions. Further details are provided in the notes and details following these sections.

TestArchitect test folder

TA fieldDirection of flow1QC fieldQC entityNotes / Conditions
Name(folder label)folder containing subfolders5This is the label applied to a QC folder. Folders have no Details tabs, hence the related field or property name is not available.


Example:

TestArchitect test module

TA fieldDirection of flow1QC field2QC entityNotes / Conditions
Name(folder label)folder containing tests5This is the label applied to a QC folder. Folders have no Details tabs, hence the related field or property name is not available.
Name
’#’ prepended to Name
Test Name#test4 
DescriptionDescription#test4 
Source (value auto-gen’d on upload*)Test ID#test4*Values for Source are auto-generated on upload (regardless of whether a value already exists in the field – thus ensuring mappings with Quality Center remain unique).
SourceTest ID#test4Note that on import, uniqueness is enforced by clearing the Source values of any test modules in the project that conflict with the uploaded one.
Test Objectives tab: ID, Title fields*test objective6#test4*Fields are concatenated, separated with ‘:’. Multiple objectives separated by newlines.
Editor tab: line(s) in OBJECTIVES section
content parsed*
test objective6#test4*Content is parsed into ID and Title columns of the action line, with ’test objective’ in the action column, prepended with ‘//’ to form comment. Note that the actual test objective fields (on the test module’s Test Objectives tab) are not populated.
action linesingle step within Design Steps tab#test4See below for processing and distribution of action line information on upload


Figure: Handling of test module fields on import and upload


Figure: Handling of test module’s test objectives on import and upload

TestArchitect test case

TA fieldDirection of flow1QC field2QC entityNotes / Conditions
ID*Test Nametest*Upload only applies when title in comment=yes (see next entry)
ID, Title
ID + ‘, ’ + Title*
Test Nametest*Conditioned on title in comment=no (default)
Title
‘Title: ’ + Title
CommentstestConditioned on title in comment=yes
DescriptionDescriptiontest 
Source (value auto-gen’d on upload*)*Test IDtest*Values for Source are auto-generated on upload (regardless of whether a value already exists in the field – thus ensuring mappings with Quality Center remain unique).
SourceTest IDtestNote that on import, uniqueness is enforced by clearing the Source values of any test cases in the project that conflict with the uploaded one.
Test Objectives tab: ID, Title fields*test objective6test*Fields are concatenated, separated with ‘:’. Multiple objectives separated by newlines.
Test module’s Editor tab: line(s) directly under appropriate TEST CASE headercontent parsed*test objective6test*Content is parsed into ID and Title columns of the action line, with ’test objective’ in the action column, prepended with ‘//’ to form comment. Note that the actual test objective fields (on the test case’s Test Objectives tab) are not populated.
action linesingle step within Design Steps tabtestSee below for processing and distribution of action line information on upload

1 Direction of flow:

applies to import (QC to TA)
applies to upload (TA to QC)
applies bidirectionally

2 Unless otherwise specified, referenced fields belonging to Quality Center test entities may be found under the Details tab or, in the case of action line-specific fields, the Design Steps tab.

3 Note that values for Source are either autogenerated (on upload) or loaded from Quality Center on import. Note also that Source values are modified on every upload (to ensure mappings with Quality Center tests remain unique). On import, uniqueness is enforced by deleting the Source values of any test modules that conflict with the uploaded one.

4 The creation of a #test in Quality Center during an upload is contingent on the Map Test Module (#) check box being selected in the Upload Test Module dialog box.

5 There is a distinction made in TestArchitect–Quality Center integration between Quality Center folders containing tests, and ones holding other folders. A folder containing tests is the analog of the TestArchitect test module, whereas a folder containing subfolders corresponds to a TestArchitect test folder.

6 Requires that the test objective field exist in Quality Center test entities, as a subtab in Details. See Creating a custom test objective field in Quality Center.

TestArchitect items are uploaded to Quality Center as follows:


Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

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

Tel: +1 (650) 572-1400