Import & Export

Import & Export

TestKase supports importing test cases from Excel (.xlsx, .xls) and CSV (.csv) files, and exporting your existing test cases to CSV. This is useful for migrating from another tool, sharing test cases with stakeholders who prefer spreadsheets, or bulk-creating test cases from a specification document.

Importing test cases

1. Navigate to the Test Cases section and click the Import button () in the toolbar.
2. Upload your file. Supported formats: .xlsx, .xls, .csv — max 5 MB and max 1,000 rows. A file over either limit is rejected before mapping, so split large migrations into batches.
3. If the file is an Excel workbook with multiple sheets, select which sheet to import from.
4. On the Column Mapping screen, map each column in your file to a TestKase field. Columns are auto-mapped where possible. At minimum, you must map a column to the Title field.
5. Review the Preview & Validate screen. TestKase performs a dry-run validation and highlights any rows with errors or warnings.
6. Click Import to create the test cases. The import runs as a background job — the dialog polls for progress and you can close it without cancelling the import. A summary shows how many were imported and how many failed.

File limits

The row count is the number of rows in the file, not the number of test cases. Because step rows share the 1,000, a file of 300 test cases with three steps each is roughly 900 rows and fits; the same 300 cases with four steps each does not. Split a large migration into batches of a few hundred test cases and import them one after another — folders are matched by path, so cases from separate batches land in the same folders.

The import runs in the background

Clicking Import hands the file to a background job and returns straight away. The dialog polls the job and shows progress as rows are processed.

• You can close the dialog — a toast confirms Import is running in the background. Your test cases will appear when complete. The import continues and the test case list refreshes as rows land.
• Closing the dialog does not cancel the import, and there is no way to cancel one once it has started. If you started the wrong file, let it finish and then delete the imported test cases.
• If the job fails outright, the failure is recorded against the job rather than being reported as per-row errors.

Importing into folders

The folder you select in the sidebar does not determine where imported test cases go. Instead, you specify the target folder per test case using a Folder column in your CSV or Excel file.

How it works

Add a column named Folder (or Folder Path / Folder Name) to your file and set the folder path for each test case:

Title,Summary,Folder
"Login test","Verify login",Authentication
"Signup test","Verify signup",Authentication / Registration
"API health check","Check API",Regression / API / Health

This creates the following folder structure automatically:

Authentication
├── Login test
└── Registration
    └── Signup test

Regression
└── API
    └── Health
        └── API health check

Rules

Common patterns

All test cases in one folder:

Title,Folder
"Test 1",Smoke Tests
"Test 2",Smoke Tests
"Test 3",Smoke Tests

Nested folders (2 levels):

Title,Folder
"Valid login",Authentication / Login
"Invalid login",Authentication / Login
"Signup flow",Authentication / Registration

Mixed — some in folders, some in root:

Title,Folder
"Login test",Authentication
"Quick check",
"API test",Regression / API

Importing test steps

You can import test cases with their test steps in a single file. The import uses a row-grouping convention:

• A row with a Title starts a new test case.
• A row with an empty Title is treated as an additional test step for the previous test case.

Map the following step columns during the column mapping step:

A test case row can also include step fields — this becomes the first step. Subsequent rows with empty Title add more steps to the same test case. Up to 50 steps per test case are supported.

Example structure:

In this example, the first test case ("Login - Valid credentials") gets 3 steps, and the second ("Login - Invalid password") gets 2 steps.

Download import template

On the Upload step, you can download a template in two formats:

• Excel (.xlsx) — recommended. Includes:
  • Sheet 1 "Test Cases" — styled header row plus a three-row worked example (one test case row followed by two step rows, demonstrating the multi-row step convention) and dropdown menus for list-type fields (Priority, Status, Platform, custom single/multi-list fields, etc.), making it easy to enter valid values.
  • Sheet 2 "Field Reference" — a reference table showing each field's name, type, whether it is mandatory, and allowed values, followed by notes on the Owner format, the UTC date format, and the 50-step cap.
• CSV — the same headers and the same three example rows, without the dropdown validation.

Both templates respect your project's field visibility settings — hidden fields are excluded automatically. Only fields marked as visible in your project configuration will appear as columns.

Column mapping

TestKase auto-maps columns based on header names using case-insensitive matching and common aliases (e.g. "Name" → Title, "Description" → Summary, "Preconditions" → Precondition, "Steps" → Step Description, "Step Result" → Step Expected Result). You can override any mapping using the dropdown selector.

Custom fields appear in a separate group in the mapping dropdown. Values are coerced per custom field type:

• TEXT → stored as-is
• NUMBER → must be a valid number
• SINGLE_LIST → must be one of the allowed values
• MULTI_LIST → comma-separated values
• CALENDAR → must be in YYYY-MM-DD format

Validation & error handling

During the preview step, TestKase validates every row:

Rows with errors are always skipped and the rest of the file still imports. Partial imports are fully supported — the results screen shows exactly which rows succeeded and which failed.

Sample CSV format

Basic import (test cases only):

Title,Summary,Priority,Status,Automated,Precondition,Labels,Folder
"Login - Valid credentials","Verify user can log in with correct email and password",Major,Approved,No,"User account exists","login,authentication",Authentication
"Login - Invalid password","Verify error message when wrong password is entered",Minor,Approved,No,"User account exists","login,negative",Authentication

Import with test steps:

Title,Summary,Priority,Status,Precondition,Step Description,Step Test Data,Step Expected Result
"Login - Valid credentials","Verify login flow",Major,Approved,"User account exists","Navigate to login page","/login","Login page displays"
"","","","","","Enter valid email and password","[email protected] / Pass123","Fields accepted"
"","","","","","Click Sign In button","","Dashboard appears"
"Login - Invalid password","Verify error on wrong password",Minor,Approved,"User account exists","Navigate to login page","/login","Login page displays"
"","","","","","Enter wrong password","wrong123","Error message shown"

In the steps example, rows with an empty Title are treated as additional steps for the previous test case.

Exporting test cases

1. Navigate to the Test Cases section.
2. Optionally apply filters to narrow the export to specific test cases (e.g., only Approved, Blocker-priority tests).
3. Click the Export CSV button () in the toolbar.
4. A CSV file is downloaded. If you have rows selected, only those rows are exported; with nothing selected, every test case matching your current filters is exported — not just the current page.

The exported CSV contains exactly the columns currently visible in the test case table — no more. Use the column configuration control to show the columns you want before exporting; hidden columns, including custom fields, are not written. Exporting from the folder sidebar adds Folder Path.

See also

• Test Cases — Overview, creation, detail tabs, and field reference
• Test Steps — Define step-by-step execution procedures
• Folders & Organization — Organize test cases with folders, search, and filters
• Bulk Operations — Clone and bulk update test cases
• History & Attachments — Execution history, change tracking, and file attachments
• Versioning — Automatic version tracking and execution version recording
• Best Practices — Guidelines and FAQ

Questions