Import project
Last updated
Last updated
From the context menu of a project or folder, you can import items from an Excel file directly into the selected project or folder.
In the Import dialogue box, you can first download a sample file in the appropriate format for the selected project. You can then specify which items you wish to import. A worksheet is then created in Excel for each item type, into which you can insert the data you wish to import.
Note: If you select Test Scenarios only, a Test Cases worksheet will be added to the sample file because importing test scenarios always requires importing the corresponding test cases at the same time. You can then replace the sample data in all worksheets in the sample file with the data you want to import.
Attention: please replace/delete all sample data in all tabs of the Excel file before import, otherwise this data will be imported as well. The items from the sample data will always have the name "string", which allows you to filter and delete them in the navigation item browser if they have been imported by mistake.
You can then simply drag the customised sample file into the grey area of the Import dialogue box, or browse and select it by clicking on the area. Using the 'Ignore invalid rows' checkbox will specify that all valid items in your file should be imported and invalid ones ignored. If the checkbox is not selected, the import will stop without importing anything if any of the content is incorrect.
Important import notes:
All item types:
The ID column must always be present and must have a unique value for each item in the import file
Please note that the ID is not imported into aqua and is only used to uniquely identify the items in the Excel file. Each item in aqua will be given a unique aqua ID in the usual format.
The format of the ID does not necessarily have to be the same as the ID format in aqua (e.g. TC000123), it can be simply incremented across all items in the import file.
Dependencies can be entered in the Dependencies column and always refer only to the IDs of items from the import file
If there is more than one dependency, the IDs must be separated by semicolons
For multi-select fields, the following format must be used: "Value1; Value2; Value3" (Important: always insert a space before the next value after the semicolon)
For user fields, such as "Assigned to", you must use the following format: "Last name, first name" or "email-address". If there is more than one user with the same first and last name, either add the username in parentheses ("Last name, first name (username)") or use the email address.
Requirements:
In the Hierarchy column, you can specify the hierarchy between requirements and sub-requirements by specifying the IDs of the parent requirements from the import file in the following structure: "Requirement/Subrequirement/Subrequirement" (for example, RQ1/RQ2 in the Hierarchy column of the requirement with ID RQ2 and RQ1/RQ2/RQ3 in the Hierarchy column of the requirement with ID RQ3)
Defects:
Defects can contain multiple description fields, notes, solutions etc., which are called enclosures. These must each be in a separate row in the import file and are assigned to the correct defect via the ID (i.e. all enclosures for the same defect must have the same value in the ID column)
In the column "Type (enclosure)" the type of enclosure must be entered. The following can be entered here: "Description" (for a description), "Note" (for a note), "ReplicationProcedure" (for a replication procedure) and "Resolution" (for a resolution)
In the column "Create date (enclosure)" you should enter the creation date of the enclosure
In the "Editor (enclosure)" column you should enter the creator of the enclosure as follows: "Last name, first name" or "email-address". If there is more than one user with the same first and last name, either add the user's name in brackets ("Last name, first name (user name)") or use the email address.
In the "Text (enclosure)" column, enter the content of the attachment.
Test Cases:
For test cases, each test step must be in a separate row in the import file and must be assigned to the correct test case by its ID (i.e. all test steps for the same test case must have the same value in the ID column).
In the column Name "(test step)" the name of the test step can be entered
In the column "Instructions (test step)" the instruction of the test step can be entered
In the column "Expected Results (test step)" the expected result of the test step can be entered
In the column "Type (test step)" the test step type can be specified. "Condition" for a condition and "Step" for a step
Test Scenarios:
Test scenarios must always be imported together with the test cases that you want to include in the scenarios
For each test case within a test scenario, a row with the same value in the ID column must be added to the test scenario tab in order to assign them to the same test scenario. In the column "Test case ID (test case)" the ID matching the desired test case from the test case tab should be entered
In the column "Tested version (test case)" the tested version within the test scenario can optionally be entered
In the column "Tester (test case)" you can optionally enter the tester within the scenario as follows: "Last name, first name" or "Email address". If there is more than one user with the same first and last name, either the username must be entered in parentheses ("Last name, First name (username)") or the email address must be used.
All other columns which refer to the scenario, e.g. the scenario name, are only allowed in the first row for each scenario and must be empty for all other entries (i.e. the other test cases in the scenario)
Limitations:
Value sets for test cases cannot be imported
Embedded test cases cannot be imported
Discussions cannot be imported
If you also want to import attachments or formatted description texts that contain for example pictures, you can do this by importing a zip file. Please note the following when importing a Zip file: All item types:
For each item in the Excel file for which you want to import an attachment and/or formatted text, the zip file must contain a folder with the item's ID as the folder name,
The attachments must be saved in the folder for that item, and in the Excel file, all attachments must be listed in a column called "Attachments", separated by a semicolon, including the file extensions (e.g, ExampleExcelAttachment.xls;ExampleTextAttachment.txt;ExamplePictureAttachment.png"),
The formatted descriptions must be saved in rich text format in the same folder as the item,
The filename of the formatted description must have the format "ItemID.Description.rtf", where ItemID must be replaced with the ID of the item for which the description is to be imported.
Test Cases:
The formatted descriptions and expected results of the test steps must be stored in the folder for the respective test case in rich text format
The file name of the formatted text for the step description must have the format "TestCaseID.TestStep.001.Description.rtf", where TestCaseID must be replaced by the respective ID of the test case and TestCaseID must contain the correct step number
The file name of the formatted text for the expected result must have the format "TestCaseID.TestStep.001.ExpectedResult.rtf", where TestCaseID must be replaced by the respective test-case ID and TestStep.001 must contain the correct step number
For conditions only the step description is needed, i.e. "TestCaseID.TestStep.001.Description.rtf
Defects:
The formatted text of the enclosures (descriptions, notes, solutions etc.) must be saved in rich text format in the folder for the relevant defect.
The file name of the formatted text for the enclosures must have the format "DefectID.Enclosure.001.rtf", where DefectID must be replaced by the respective ID of the defect and Enclosure001 must be incremented over all enclosures
It is recommended that a sample export is made first to better understand the exact format of the zip file to be imported. Exports can also be customised, re-zipped and re-imported into the same project or into other projects or environments. However, the import process always creates new items and does not update the previous items. When importing a zip file from another project, you should ensure that all fields to be imported are also present in the new project and have the same name or contain the same selection values. It is recommended that you use the same project configuration to avoid incompatibilities.
