Excel/CSV
AIO Tests allows you to import existing manual test cases from Excel or CSV file with the click of a button. Once you import the test case files, all data from the uploaded file will get copied over to AIO fields, including traceability (requirements) mapping. By importing your existing cases, you can start working on AIO Tests readily without having to manually re-create your current cases.
The uploaded file size should not be more than 100 MB.
In this documentation, you’ll understand:
Steps to Import Excel/CSV
Step 1: To import a Excel/CSV file, simply click on the Cases option in the top bar menu.
Step 2: On the Cases tab, click on the Import Cases button.
Step 3: On the import cases page, you will get 3 tabs on the Import Cases view- File, Other Projects, and Jobs. On the File page, click on the “Browse to upload file” button under the Classic & BDD box to import a .csv/Excel file.
Sample .csv
Blank sample .csv
Single line cases sample .csv
Multi-line cases sample .csv
Sample .xlsx
The first row in the user’s .csv or Excel file is considered as a header row by the system.
The Existing Case ID and Title are mandatory fields that need to be mapped. Along with existing case ID and Title, users also need to map other mandatory fields if they marked required from field configuration settings.
The sample .csv and Excel files provided are for ease of use and not a mandatory format. User can map their own fields to AIO Tests fields.
Step 4: Once you upload a file, the Field Mapping section will appear on the screen. Users can map the fields in the input file to the fields available in AIO Tests.
The Field Mapping section takes the headers from the uploaded file and maps it to the AIO Tests fields automatically, if similar field names are found.
Users have the option to update the mappings as per their requirements.
Users can map the field manually by clicking on the “Reset Mapping” option located at the bottom of the page.
If users changed a few mappings and would like to see what AIO Tests auto-mapped, they can click on “Re-Initialize Mapping”.
Mapping folder hierarchy
AIO Tests require a special delimiter to identify a folder hierarchy, which is ->
As an example, a folder mapping of Login->2FA will result in a parent folder named Login and a child folder under Login, named 2FA.
While importing cases, if a default folder is selected i.e. anything other than “Not Assigned”, then the above hierarchy would be created under the selected default folder.
Mapping Data-driven cases/Example-based cases
To import cases based on parameters, users need to add a column in Excel and map it with the Datasets field in the above field mapping. Users are expected to define the datasets with pipe-separated values as below:
To use a parameter in a step, it needs to be enclosed within angular brackets as shown below:
Step 5: Click on the Select Data Mapping button to see the Data Mapping screen. It maps data provided in the file to values available in AIO Tests and Jira.
The Source Field Values in data mapping are unique values available in the source file, and the AIO Tests Target Field values are the values for the respective fields available in AIO Tests. E.g. The source file can have priorities defined as Highest, High, Medium and Low. AIO Tests, however, offers Critical, High, Medium, Low and Lowest. Users have the option to map their source field values with AIO Tests field values.
If a value (for status, types, priorities and custom fields) isn’t mapped, but the same name value is found in the project being imported to, in AIO Tests, it will automatically be assigned once the import process finishes.
Folder: This acts as the destination folder where the user wants to import their cases. Select the folder from the already created folders drop-down.
By default, the Not Assigned folder is selected, but the user can select from the already created folders via the drop-down.
Default Status: Select the Default Status for newly created cases from the Status drop-down menu.
Step 6: Click on the Select User Mapping button to map users available in AIO Tests and Jira.
Step 7: Once data and user mapping is finalized, click on the Start Import button.
Once you click on the Start Import button, you will be redirected to the Jobs section and a success message will be displayed on the screen stating “Batch <batch #> created successfully”.
Job: The Job tab shows all the import requests that have either been submitted or completed. Once the batch is created, it shows the status “Queued”. The import function is a batch process that runs every 2 minutes and checks if any files have been submitted/queued for import. If new files exist, they are processed. Clicking the Refresh button below will update the status of the batch to either “Running” or “Completed”.
Upon clicking the down-carat icon next to the Created Date, the result of the batch processing will be displayed on the screen, whether the import actually succeeded or not.
How to Import Custom Fields
AIO Tests allows the users to import more fields as per their requirements other than the fields available in AIO Tests by letting them create custom fields on AIO Tests. To know the steps to create custom fields in AIO Tests, click here.
While importing, the custom fields created on AIO will be available to map to the fields from Excel/CSV.
For Single-select lists and Multi-select lists type of custom fields, users can import a maximum of 50 list options.
For importing date fields, users will need to ensure they follow the supported date formats (see below for the list).
User type fields (single-user and multi-user) will not be imported. Users will need to use the Bulk edit of case details feature to update such fields.
Supported Date Formats for Custom Fields
8-Jun-20 | 8-Jun-2020 | Jun 8, 2020 | Jun 8, 20 | Jun-8, 20 | Jun-8, 2020 | 8-Jun, 20 | 8-Jun, 2020 | 8 Jun 2020 |
8 Jun 20 | 8/Jun/2020 | 8/Jun/20 | 2020-Jun-8 | 2020 Jun 8 | 2020/Jun/8 | Jun 8 2020 | Jun 8 20 | June 8, 2020 |
June 8, 20 | 8-June-2020 | 8-June-20 | 8 June 2020 | 8 June 20 | June-8, 2020 | June-8, 20 | 8-June, 20 | 8-June, 2020 |
2020/June/8 | 2020-June-8 | 8/June/2020 | 8/June/20 | 2020 June 8 | Jun-8-2020 | Jun-8-20 | June-8-20 | June-8-2020 |
Missing Data Impact
If some data is found missing or empty while importing/mapping the file, the file will fail to import with an error. Below is a list of a few common errors.
Message | Description |
Story not found [Jira issue key] | This usually happens when the Jira story that you are trying to link doesn't exist or if it belongs to another project. |
Cannot create Test Step. Mandatory data is missing for the Test Step. Please provide the value for Step and Expected Result | While creating a Case with steps, step description and expected result are mandatory fields. If the source file doesn’t provide these values then this error will be shown |
Re-Import Error File
AIO Tests allows you to re-import files that had an error and failed to upload with the click of a button. With this feature, users will be able to fix and reupload a file that’s showing failed/success with errors status.
Steps to Re-Import Error File
Step 1: To re-import an error file, all you need to do is click on the Cases option in the top bar menu.
Step 2: Click on the Import Cases button.
Step 3: On the Import Cases page, click on the Jobs tab.
Step 4: Click on the Downloads Error File button for the desired Failed/Success with errors status import files. Fix the errors in the downloaded file.
Users can view the result of the import files by clicking the down-carat icon next to the Created Date. It will help them to know whether the import actually succeeded or not. Here, we are re-importing the error file for failed status.
Step 5: Once you have fixed the errors in the downloaded file, click on the Re-Import Error File button.
Step 6: Once you have re-imported the error file, click on the Start Re-Import button.
Once you click on the Start Re-Import button, you will be able to import the updated Excel/CSV file using the same steps as mentioned above in the Steps to Import Excel/CSV section.
For failed cases, new cases will be generated, and for scenarios where you have success with errors, existing cases that were partially created will be updated with the new information provided in the file.
For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com.