Executing tests from Zephyr

As an alternative to executing tests from TestArchitect, TestArchitect test cases and test modules may be executed from Zephyr.

Restriction: Integration between TestArchitect and Zephyr has been deprecated since TestArchitect version 8.3 Update 2.
Note: At present, TestArchitect-Zephyr integration supports versions 4.5 and 4.6 of Zephyr.

To run automated tests from Zephyr, do the following from your TestArchitect Client machine:

  1. In Zephyr, click the Testcase Execution application on the left tool dock.
  2. In the Testcase Execution dialog box, select the test case execution assignment and phase in the tree view and select the test case that you want to execute on the test case grid.
    Note: Multiple test cases may be selected for execution.
  3. Click the button in the Automated column of the selected test case.

  4. In the Execute Automation Script(s) dialog box, select a ZBot from the drop-down list of available ZBots (or target machines) on which to run the automation script.
  5. Click Run.

    Zephyr connects to the TestArchitect engine to prompt it to launch the TestArchitect Execution dialog box, configured with the TestArchitect test module containing the test case(s) that the selected Zephyr test case(s) are mapped to. The TestArchitect Execution dialog box appears.

  6. In the dialog box, enter the requested information as described below:
    • TestArchitect Information panel:

      • Repository Server: Name or IP address of TestArchitect Repository Server holding the repository of the tests.
      • Port: Port number of the TestArchitect Repository Server host.
      • Repository Name: Name of TestArchitect repository hosting the tests.
      • User Name: TestArchitect user name whose account has permission to access and execute tests on the host.
      • Password: Password for the above user account.
    • General tab:
      • Variation Specification panel:

        • Keyword: Keyword, or comma-delimited list of keywords, specifying the test variation to be executed, if any. (See Creating keyword variations.)
        • AUT Version: Enter a value or click the Select Version button to specify a variation tailored to an AUT version or platform (See Creating linked variations.)
        • Time Traveling: To opt for time traveling execution, which selects an historical "snapshot" of the test's project items for execution during the test run, select the check box and provide an appropriate timestamp. (See Time Traveling for details.)
      • Controllers/Devices panel:

        • Select Controllers/Devices: Click this button to designate which controller and device the test will execute on.
          • Lab Manager Server: (Display only) IP and port number of the Lab Manager Server to which the test controllers and devices are registered.
          • Controllers/Devices panel: Lists all available controllers and cloud/physical mobile devices on which the test can be executed. The list consists of those controllers and devices that are either registered with the Lab Manager Server or have been manually added with the Add Controller or Add desired capabilities files button.
          • Controller Port Configuration: Use this panel to specify to TestArchitect the port number that the remote machine is using for its TestArchitectcontroller, if not using the default.
            • IP/Server Name: (Display only) IP address of remote machine currently selected in the Controllers/Devices panel.
            • Port: Port number through which TestArchitect will attempt to communicate with the controller on the host specified in the IP/Server Name field. If this is not the port on which the controller is known to be listening, change this value and then click Save .
        Restriction: Only one controller or one device may be selected to run tests at a time. In other words, multiple controller/device execution is prohibited.
      • Automatically add result(s) to repository: Select this check box if you want to add test results automatically to the repository once the test concludes.

        • Repository destination: Add test results to the repository at this specified location.
        • By result: Limit the results stored to the repository in accordance with the following check box selections:
          • Passed: Passed test results are stored.
          • Passed with Warnings/Errors: Passed test results with warnings/errors status are stored.
          • Passed with known bug: Test results which passed, but with marked known bugs whose outcomes have been ignored, are stored.
          • Failed: Failed test results are stored.
    • Startup Settings tab:

  7. Click Run to execute the tests.
    Note: On each subsequent test run, the information you provide is retained and automatically populates the TestArchitect Execution dialog box.
    Important: If you are executing tests for the first time, you are prompted to enter your TestArchitect license server information. Enter the required information in the dialog box. If the specified license server is reached successfully, or the trial key is validated, the provided license information is stored. From then on, you will be able to execute tests without again being prompted for this information.

TestArchitect executes the test, and the test results are uploaded to Zephyr as ZIP files for the associated Zephyr test cases.
  • When running an automated test, the execution of every single Zephyr test case entails the execution of the INITIAL section, if any. However, the execution of the last Zephyr test case entails the execution of both the INITIAL and FINAL sections. For example, execution of test case 01 (the first in the sequence) starts off with execution of the INITIAL section; the same is true for each subsequent test case, including test case 05, the last one. Note, however, that only test case 05 concludes with execution of the FINAL section.
  • If, in the TestArchitect Execution dialog box, you specify a non-default test variation (using the Keyword and/or AUT version boxes), the results of the variation's test run are uploaded as follows:
    • if the variation has been mapped with Zephyr: the results are uploaded to the correct mapped variation.
    • if the variation has not been mapped with Zephyr: the results are uploaded to the default test.