Features of TestArchitect-Zephyr integration
A discussion of key features of TestArchitect and Zephyr integration.
At the broadest level, the steps involved in developing Zephyr test cases for integration within TestArchitect could be described as follows:
- Within Zephyr, define the System and Subsystem folders which will store test cases.
- Organize your Zephyr test cases into a folder structure that mirrors the test module structure you will create, or have created, in TestArchitect.
- For each folder you create in Zephyr, create a test module in TestArchitect with an identical name.
- Import Zephyr test cases from each test folder into the corresponding TestArchitect test module counterparts, where they will serve as test cases.
- Optionally, upload each TestArchitect test module to its corresponding folder in Zephyr. This creates a Zephyr test case with the same name as the TestArchitect test module’s name, preceded by a # symbol. This is known as a test module node.
- For each test case, create action lines that implement the test case.
With this integration with Zephyr, you will be able to do the following:
Importing Zephyr test cases into TestArchitect
Test cases residing on Zephyr can be imported into TestArchitect, which also establishes one-to-one mappings between the two sets of test cases.
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.
Mapping TestArchitect test cases to Zephyr test cases
Mappings between TestArchitect and Zephyr test cases are generated automatically when Zephyr test cases are imported to TestArchitect, and when TestArchitect test cases are uploaded to Zephyr. There may be occasions, however, when you need to create a linkage between test cases created independently on the two systems.
Mapping TestArchitect test modules to Zephyr test cases
Apart from TestArchitect test cases, you can map TestArchitect test modules to Zephyr test cases.
Uploading TestArchitect test results to Zephyr
TestArchitect test results from test projects which are mapped to Zephyr can be uploaded to Zephyr manually or automatically.
Executing tests from Zephyr
As an alternative to executing tests from TestArchitect, TestArchitect test cases and test modules may be executed from Zephyr.
Creating matching custom fields in TestArchitect and Zephyr
User-defined fields in TestArchitect are automatically mapped to Zephyr custom fields when the names and data types match.
Rules for mapping custom fields between TestArchitect and Zephyr
Custom test case fields in Zephyr can be mapped to user-defined fields in TestArchitect test modules or test cases.