Uploading TestArchitect test modules/test cases to Zephyr

TestArchitect test cases and test modules can be uploaded to the Zephyr server, which also establishes one-to-one mappings between the two sets of test cases.

Note: At present, TestArchitect-Zephyr integration supports versions 4.5 and 4.6 of Zephyr.

To upload TestArchitect test cases and test modules (both default and non-default variations) to Zephyr:

  1. In the TestArchitect explorer tree, right-click the Tests node, test folder node, or test module node to be uploaded, and then select External Tool > Zephyr > Upload to Zephyr.
    Note: If you are not already authenticated on the Zephyr server, TestArchitect presents a login for Zephyr.
  2. In the Upload Test Module to Zephyr dialog box, select the target folder in Zephyr to which you wish to upload the test module(s)/test case(s).

  3. Select the Map Test Module (#) and/or Map Test Folder check boxes.
    Remember: One of these two options must be selected:
    • Map Test Folder: Upload TestArchitect test cases to Zephyr.

      For each parent TestArchitecttest module, a Zephyr folder is created with the same name. Zephyr test cases with the same names as their TestArchitect counterparts are created in the appropriate folders.

    • Map Test Module (#): Upload TestArchitect test modules Zephyr as a #test case.

      In addition to creating the Zephyr folders and test cases as in the previous option, each uploaded test module generates a Zephyr test case. The test case is assigned the name of the test module, prepended with a pound sign (#), and placed in the corresponding Zephyr folder alongside its uploaded test cases. For example, a TestArchitect test module named Input Validation produces a Zephyr test case named #Input Validation, which resides in a Zephyr folder named Input Validation. This Zephyr test case contains the full content of the TestArchitect test module, including not just the test cases but the INITIAL and FINAL sections as well.

  4. In the Upload Test Module to Zephyr dialog box, click OK to upload. If the upload to Zephyr is successful, a message box to that effect is displayed.

  5. Click OK to close the dialog box.
Important:
  • If you are not using Zephyr Enterprise Edition (that is, you are using the Community Edition), and you upload TestArchitect test cases that have custom fields, an informational message appears, letting you know that the transfer could not include those fields:

    • Click OK to close the dialog box and allow the upload to proceed.
  • If you upload TestArchitect test cases that have custom fields to Zephyr, but you do not have sufficient privilege to access Zephyr custom fields, a warning message appears.

    • Choose one of the following options:
      • Yes: Continue the uploading process without TestArchitect custom fields uploaded.
      • No: Close the dialog box and abort the ongoing process.
  • It's possible for Zephyr to have custom fields which are mandatory. If you attempt to upload TestArchitect test cases that have corresponding user-defined fields with empty values, an error message appears. For example, the following message appears when an attempt is made to upload test cases with an empty Review Comments user-defined field, which Zephyr is configured to require:

    • Click OK to close the dialog box and abort the ongoing process.
The next topic describes the mapped items between TestArchitect and Zephyr.

Mapped items between TestArchitect and Zephyr

This topic describes how TestArchitect test case information is mapped to the corresponding Zephyr test case fields.

Note: At present, TestArchitect-Zephyr integration supports versions 4.5 and 4.6 of Zephyr.
TestArchitect items are uploaded to Zephyr as follows:
  • Uploading a TestArchitect test module to Zephyr also uploads that test module‚Äôs test cases.
  • Each TestArchitect test case's Title and ID fields are combined and joined by an underscore to become a Zephyr test case name.

  • Additionally, the TestArchitect test case Title field is uploaded to the Comments of a Zephyr test case, while the TestArchitect test case's ID becomes Alt. ID of the Zephyr test case.

  • TestArchitect action lines as well as test steps are mapped to Zephyr test steps.
  • For each TestArchitect action line, argument names and their values are paired and mapped to Test Data in Zephyr.
  • Expected results of TestArchitect check actions and test steps (the contents of the third column) become Expected Results in Zephyr.

  • Each TestArchitect test objective is copied to the corresponding Zephyr test case, provided that you have created a custom field in Zephyr to accept it.
    Remember: The custom field in Zephyr must be named Test Objective, and have the attribute Long Text (32000). (See Creating matching custom fields in TestArchitect and Zephyr for details.)


Note: The lower panel of a Zephyr test case, which displays the details of that TestArchitect test sequence (including #, Test Steps, Test Data, and Expected Results fields), can only be written to when the test case is initially generated (that is, on the first upload). After that, due to Zephyr limitations, the data is effectively read-only. That is, subsequent uploads of the same TestArchitect test modules and test cases have no effect on the contents of the lower panels of affected Zephyr test cases. (Note, however, that this information is strictly documentary. Whether outdated or not, it has no effect on tests that are initiated from Zephyr.)