Skip to main content
OneTest supports importing and exporting test cases in multiple formats, making it easy to migrate from other tools or share test suites across teams. Import format selection dialog

​
Importing Test Cases

1

Open Import Dialog

Click the Import button (upload icon) in the Test Cases toolbar, or go to Pipelines > Import Test Cases for bulk imports.
2

Select Format

Choose your import format:
  • ZIP Archive — Full restore with folders, tags, and markdown files
  • Excel (XLSX) — Spreadsheet with test cases, steps, folders, and tags
3

Upload File

Click Choose File or drag and drop your file into the upload area.
4

Configure Collision Handling

Choose how to handle duplicate test cases:
5

Start Import

Click Import to begin. You’ll see a summary of imported test cases when complete.
Import upload step with collision handling
For large or complex imports with hundreds of test cases, use Pipelines instead. Pipelines provide AI-powered field mapping, decision gates, and multi-phase progress tracking.
Pipeline import flow

​
Exporting Test Cases

Click the Export button (download icon) in the Test Cases toolbar.

​
Export Formats

​
Export Scopes

  • All test cases — Export everything in the current product
  • OQL-filtered results — Export only test cases matching your current query (e.g., priority = p1 AND status = ready)
  • Selected tests — Export only test cases you’ve checked in the table
  • Unassigned tests — Export test cases not assigned to any folder

​
Preparing Import Files

Your Excel file should contain these sheets:
  • Test Cases — One row per test case with columns: Title, Description, Priority, Type, Status, Category, Tags
  • Steps (optional) — Test steps with columns: Test Case Title, Step Number, Action, Expected Result
  • Folders (optional) — Folder hierarchy with columns: Name, Parent Folder
  • Tags (optional) — Tag definitions with columns: Name, Color
Export an existing test suite first to see the expected format, then use it as a template for your import file.
ZIP archives should contain:
  • Markdown (.md) files for each test case
  • A folders.json file defining the folder structure
  • A tags.json file defining tags
This format is ideal for full backup/restore scenarios.

​
What’s Next?

Pipelines

Use AI-powered pipelines for complex bulk imports

Test Management

Organize and manage your imported test cases