Importing Test Cases
Tuskr provides a flexible way to import your test plan from spreadsheets and other test case management tools. You can import test cases along with their custom fields. For your convenience, Tuskr can also create test suites and sections on the fly saving you the burden of manually creating them.
Format and encodingThe file should be a CSV (comma separated values) file and in UTF-8 encoding. If you use popular spreadsheet tools like Microsoft Excel, Google Spreadsheets or Apple Numbers, this should happen automatically.
Multiline values are allowed and they should be separated with \n character. Multiple rows should be separated by \r\n. If you export the file from any of the popular spreadsheet apps mentioned earlier, this should happen automatically.
The first row
The first row in the file will be considered as column headers and will not be imported.
A maximum of 1000 test cases can be imported at a time. If you have a large file, split it into smaller ones and import each one separately.
FieldsThe following fields are supported. Custom fields are also supported and are described later. If you have marked any custom fields as required, then they too must be included while importing.
|Name||A short description of the test case|
|Suite||The test suite this test case must be added to|
|Section||The test suite section this test case must be added to|
|Type||The type of the test case|
|Field Set||The field set of the test case|
|Estimated Time||The estimated time in minutes required to execute this test case by a tester|
Custom field formats
|Text||Multiline values are allowed and they should be separated with the newline (\n) character.|
|Number||Decimal numbers with should use period (.) as the decimal separator.|
|User||Use email address or name. If name is specified it should match exactly with the user's full name|
|Date||Dates should be encoded as YYYY-MM-DD e.g. 2022-08-15 for 15th August 2022. Encoding in any other format will result in unexpected behaviour.|
|Multi-select||Multiple values should be separated with newline (\n) character.|
Example 1 - only steps - we can see three steps below:
Go to tuskr.app +++ Click on pricing Scroll down +++ Click on buy Pay by credit card
Example 2 - same three steps, but with instructions and expected results:
Go to tuskr.app >>> you should see the website +++ Click on pricing Scroll down >>> you should see the purchase options +++ Click on buy Pay by credit card >>> your credit card should be charged
Every step can start with <number><dot><space> e.g. 1. 2. 3. etc. To separate instructions and expected results use Expected Results:
Same example above but with alternate format:
1. Go to tuskr.app. Expected Results: you should see the website 2. Click on pricing Scroll down Expected Results: you should see the purchase options 3. Click on buy Pay by credit card Expected Results: your credit card should be charged
How to import
To import test cases in a project, click Main Menu ▸ Test Cases, and then click on the button in the title.