|Zephyr integration / Features of TestArchitect-Zephyr integration|
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.
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.
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.
This topic describes how TestArchitect test case information is mapped to the corresponding Zephyr test case fields.