Whether you are migrating from a different test management tool to Testlio's platform or have a number of test cases you want to add to your existing tests, creating vast quantities of tests can be time-consuming. Our test import feature does all the hard work for you.
How To Import Tests via CSV
Navigate to the Tests module
Click on "Import tests"
Select the separator character (comma, semi-colon, pipe, or tab)
Select the file you want to import and click "Import". While your file is being uploaded, you may not navigate away from this view.
After your file finishes uploading, our system runs a diagnostic on the file and will inform you of any detected issue such as missing fields, content longer than allowed by our platform, separator character issues, etc.
Once the file has been validated the platform begins to process the file and generate tests, tagging them with the name of the file, the date, and time, to allow you to easily select, review, add to plans, etc. It is now safe for you to continue using our platform or close the browser window. A progress bar showing the import progress will follow you through the system. You can use this to cancel your import, affecting only tests that have not yet been imported, or to access the test plage filtering only the imported tests.
After the import finishes, you will be able to dismiss the progress bar.
What kind of data can be imported?
Our importer uses a specific format that is optimized for you to provide all the meta-data during import. This way, you don't have to spend time editing your tests after import and can focus on what matters - testing your application.
Imported fields
The total number of tests that can be imported in 1 file cannot exceed 5,000. Mandatory fields are marked with *
Test name* - Text, maximum length 255 characters. Title for your test
Platforms - Comma-separated list of text, one of iOS/Android/Web/macOS/Windows. The platforms that this test applies to e.g. "iOS,Android,Web" NOTE: No spaces between commas and items
Labels - Comma-separated list of text, maximum length 255 characters per label. Any labels that you may want to add to this test. If the label you apply already appears in your project, we will use the existing label so that it is easy for your new test to be grouped with existing ones. NOTE: No spaces between commas and items
Features - Comma-separated list of text, maximum length 255 characters per feature. Any product features that your test describes. If the feature you apply already appears in your project, we will use the existing label so that it is easy for your new test to be grouped with existing ones. NOTE: No spaces between commas and items
Priority - String, High/Medium/Low. The importance of the test.
Automated - Text, "Yes" or "No". Whether the test has an automation script testing the exact same functionality.
Step title* - Text. Describes the actions that the tester must take to execute the step.
Step type* - Predefined text. One of the following options that define how the step is presented to the tester and what is required as input. Only one can be used per step:
| Test that can either be marked as passed or failed |
| Tester selects one of optional values |
| Tester selects a value on a numeric scale |
| Tester submits a file as an answer |
| Tester provides a lot of text as input |
| Tester provides short text as input |
Step expected result - Text. Only displayed for
passFailstep types. Describes the expected result when the tester executes the actions described in step description.Step options - Comma-separated list of text, minimum 1 character, maximum 255 characters. Only applies for
multipleChoicestep types. Lists the options presented to the tester NOTE: No spaces between commas and itemsInclude other option - Text, "Yes" or "No". Only applies for
multipleChoicestep types. Defines whether an "Other" option is presented as a last option. If selected by the tester, they need to provide text input.Step scale start - Number. 1-10 value that marks the beginning of the scale.
Step scale start label - Text, maximum 255 characters. Describes the meaning of the value at the beginning of the scale.
Step scale end - Number. 1-10 value that marks the end of the scale.
Step scale end label - Text, maximum 255 characters. Describes the meaning of the value at the end of the scale.
Execution time (minutes) - Number. Specifies the amount of time it takes to complete the test.
Existing test ID - for test update - guid. Optional value to update an existing test case. If filled and a matching test is found with this guid, the test is updated, rather than a new test created.
Test ID - for test / step update - guid. Optional value only needed to update a test case or test step. If updating a test, needs to be the same as
Existing test ID - for test update. If updating a step, needs to be the guid of the parent test or the test that is embedded (if the step that is being updated is part of an embedded test).Step ID - for step update - guid. Optional value only needed to update a test step. The guid of an existing test step that needs to be update to the content specified in the import file.
Updating tests via import
You can also use the import file to update existing tests. The “Existing test ID - for test update” column in the import file can be used to identify an existing test case and update it to match the import file. During update, a label will be added to all tests that were updated so it's easy for you to find them later.
When updating test meta-data like labels, features, or other, existing data on the Testlio platform will be overwritten to match that in the file.
The same logic applies to test steps - test steps are overwritten to match the import file if the test is identified. To update a step, you need to provide the “Test ID - for test / step update” (the parent test’s guid that the step appears in, or the test id if the step is an embedded test) and “Step ID - for step update” (the step guid of the step you want to update) columns. Based on this, the following cases can be observed:
If an existing test is in the import without steps only the content of the test is updated, the existing steps remain as they are.
If the import file has an existing test (has Existing test ID), and lists some steps with known guids (Test-Case Id and Step Id) then both test case and steps are updated. If the step listed under the existing test does not have (Test-Case Id and Step Id), a new step is created and added at the end of the test. All other steps related to that test are not deleted or modified.
For the best result for updates, please use our test export feature to get a CSV file with the correct existing test/step identifiers.
We have provided an option in test export that allows you to easily include these necessary references for tests and steps.
Note: Cross-workspace updating is not supported! Tests exported from workspace A cannot include Existing test ID, Test-Case ID, and Step ID to be imported to workspace B.