Import/Export the Script
Last updated
Last updated
You can enjoy seamless control over the Scripts with import and export functionalities:
Export Steps: With a simple action, You can Export the Script in json/xlsx format, enabling easy sharing. Below are the sample for respective format(xlsx,json).
Import Steps: You can effortlessly import the downloaded Test Scripts from any project by following the Steps below, saving time and ensuring accurate test building.
These versatile import and export options empower you to streamline the workflow and enhance collaboration.
Previously Created Project
Previously Created Module
Previuosly Created Script
Navigate to the script in which you want to import the steps.
Click on the "Import Test" / "Import File" Button and Select the file to import the test steps.
Navigate to the script from which you want to Export .
Click on the "Export as" Button and Select the file type to export the Test Script.
A file with the selected type[Json/Xlsx] will be downloaded.
While creating test step data from a template, the following user actions are not supported:
File Upload
Execute Test Case
However, when exporting test script data, the above-mentioned action types will be included as part of the export data.
If an exported test script with "Execute Test Case" and "File Upload" user actions is imported within the same project, the file upload data and execute test case step data will remain relevant.
If the exported test script with "Execute Test Case" and "File Upload" user actions is imported outside the organization/project, the file upload data and execute test case data will be invalid. The user must upload the file again or reselect the execute test case script after importing.
For function steps, a field called "Test_Step_Number" is added to the exported Excel/JSON, denoting which parent step the function step is attached to. New steps can be added to any existing parent step in the function steps sheet by providing the necessary details, including the correct "Test_Step_Number" that corresponds to the "Execute Function" step it is attached to.
New functions can be added directly from the Excel/JSON file. The new steps for functions can be added in the function steps sheet. After adding appropriate function steps with valid data, a parent step must be added to the 'testStep' sheet/key. This new parent step must have the User Action set as 'Execute Function'.
The only field to update is "Step_Data" for the "Execute Function" step. The step data must contain a unique UUID, which can be fetched from any public platforms. Once a unique UUID is added, it will indicate that a new function is to be added.
The new function will be created in the project setup with the name mentioned in the "Step Description" field of the parent step. The newly created function will be imported into the script once the import operation is completed.
In the Same Project:
Without adding new steps:
Existing function will be used for the imported function step.
Adding new steps in Excel/JSON:
Existing function will be used for the imported function step.
New steps, if any, will be added to the imported function as well as the main function in the project setup.
Any parent step number removed from the Excel/JSON will be updated in the project step main function but added to the execute function step.
Different Project:
Any step added to Excel/JSON will also be created in both of the following scenarios:
If a function with the same name is present:
"_import " will be added to the function name, and a new function will be created with existing steps in Excel/JSON. The same function will be imported into the execute function step.
If a function with the name is not present:
A new function will be created with the name of the function (but no timestamp added) in the source project from where the file is exported. The same function will be imported into the execute function step.
Click here for more information related to the Import/Export .
