Overview
With TFJ's customizable export/import it is possible to copy an entire T4J provides a way to export a test plan structure into another project.
Test cases including their test steps and parameters can be duplicated into another project's test plan or definition.
from one project and import it as new folders and issues in another project.
This feature is currently only
available to administrators.
On this page:
| Table of Contents |
|---|
Exporting a test plan
Go to Plan List View
Follow the instructions to export a test plan
A .json file will be downloaded which contains the data structure of the test plan.
Important – Proceed with caution when modifying file content manuallyin JSON format in Test Plans - How-to Guide.
Any user can export a test plan, but import is only allowed to administrators.
Importing a test plan
This can be done via the Definition View or the Plan List View.
| Note |
|---|
Before importing, make sure to modify the value of the prjKey parameter from the previously exported file. Change the value to the destination project's project key. Otherwise, it will be imported into the same project you exported it from. See snippet below for reference. In here, the name of the test plan can also be changed if the same plan name already exists in the destination project. |
| Code Block | ||
|---|---|---|
| ||
{
"trees" : {
"prjKey" : "DESTINATION_PRJKEY",
"tree" : [ {
"folders" : [ {
"name" : "TEST_PLAN_NAME", |
Go to Definition View or Plan List View
Click on the Import button in the TFJ navigation
Modify the file that has been previously exported, as described in the section How to modify an exported plan file for import.
Select the Plan entry in the main T4J menu.
Select the Import dropdown menu entry in the set of R4J menus.
Select the file in the dialog Import Test Plan.
Select Browse to open the file explorer and choose the .json file to be imported
Click Import
Additional Notes:
In definition view, test cases that already exist in context will not be imported
When importing from plan list view, the plan structure will automatically be imported to the definition as wella previously exported JSON file.
Select Import.
The results of a successful import are the following:
A new test plan exists in the destination project.
The issues in the test plan have been duplicated in the destination project. (Issues that already existed in the destination project are not duplicated. This can occur if the test plan in the source project used issues in the destination project by reference.)
The project tree contains a new folder and subfolders corresponding to the test plan folder and its subfolders.
Errors in file content structure or data
result in
Limitations
Overwrite/update not fully supported
the failure of the import.
How to modify an exported test plan file for import
The plan export produces a file that sets the following attributes to values for the plan that is being exported:
prjKey: the key of the plan’s projectname: the name of the plan
The project key must be changed to the key of the destination project. If that project already contains a plan with the same name, the name must also be changed.
Limitations of Import
Import is restricted to projects that have the same issue type scheme Support for test case issue links in import is limited to relationships as that of the source project.
Only issue links between issues in the same test plan – else, the links are ignored and not importedplan are imported.
Attachments are not yet supportedVersion and Component fields not yet supportedimported.
The values of Versions and Components fields are not imported.