discussion of the key functionalities of TestArchitect and Quality Center integration.
that are typically developed and executed as standalone
units. Each test module is comprised of a sequence of test cases. By contrast, the standard
unit of test development and execution in Quality Center
, which more closely corresponds to a test case in TestArchitect
than a test module. Hence each uploaded TestArchitect
test case takes the form of a Quality Center
general, the following correspondences are used when moving test assets between the two
||Folder (with subfolders representing TA test
'#' test (QC test with '#' prepended to the name) may also be
created to hold essential test module metadata.
At the broadest level, the steps involved in developing Quality Center
tests for integration within TestArchitect
could be described as follows:
- Within Quality Center, you define each of your test cases as a
Quality Center test. You can specify design steps, but this is
- Organize your Quality Center tests into a folder structure to
resemble the test module structure you will create in TestArchitect.
each folder you create in Quality Center, create a test module in
TestArchitect with identical
- Import the Quality Center tests from each folder into the
corresponding TestArchitect test module, in which the Quality Center tests become test cases.
defined design steps in the Quality Center tests, each design
step is added to the corresponding test module as a comment within the corresponding
- Upload each TestArchitect test module to its
corresponding folder in Quality Center. This creates a Quality Center test with the same name as the TestArchitect test module's name, prepended with a
# symbol. This is known as a test module
- For each test case, create action lines that implement the
Note that you can now run the tests from either TestArchitect or Quality Center using the
Quality Center Test Lab.
The following topics provide details for the high-level steps outlined