Import and Export

CaseWriter exchanges test cases through Excel files and through a native TestRail integration.

Excel Export

Export is reachable from the repository toolbar's actions menu, the tree's right-click menu, a case's own menu, and the bulk action panel.

The export dialog offers three scopes:

Scope	Exports
All Test Cases	Everything in the repository
Selected Test Cases	Just what you selected
Current Test Set	The set you are in, with an Include Sub Test Sets switch

A summary shows how many cases the current scope covers before you confirm.

The export runs as a background job: the dialog tracks its progress, the job can be cancelled while it runs, and the finished file downloads as .xlsx.

Exporting From an AI Session

An AI session has its own Excel export, independent of the repository. Select cases in the results list and use Export Excel in the selection bar, or export the whole session.

Unlike Save to Repository, an Excel export from a session is not gated on approval.

Excel Import

Import in the repository actions menu opens the Excel import dialog.

note

Only one import can run at a time. While a job is in flight, the Import action is disabled and a progress chip appears in the toolbar.

Steps

1. Download Template if you want the expected layout.
2. Drag a file onto the dialog, or select one. Excel (.xlsx, .xls) and TestRail CSV (.csv) are accepted.
3. The file is validated and previewed: detected format, the columns found, sample rows, and any warnings.
4. Check the column mapping. Mappings are suggested automatically; adjust any that are wrong. Title must be mapped — the import will not start without it.
5. Optionally save the mapping as a named profile so the next file with the same layout maps itself.
6. Choose the Target Test Set and start the import.

Files whose layout matches an existing profile are mapped from that profile automatically.

Progress

The import runs in chunks in the background.

• The progress dialog shows the status, the current step, and rows imported so far.
• Run in Background closes the dialog and leaves a progress chip in the toolbar; selecting it reopens the detail.
• Cancel Import stops the job.
• When it finishes, a summary reports Imported, Updated, Skipped, and Failed counts, and the tree refreshes.

An import that is still running survives a page reload, and the toolbar picks it back up.

TestRail Import

CaseWriter imports from TestRail natively — you do not need to round-trip through Excel.

The wizard is in the repository's actions menu, under the TestRail submenu: Import from TestRail.... The submenu only appears when a TestRail integration is available, and importing does not require a project mapping.

Wizard Steps

Step	What you do
Source	Pick the TestRail project
Preview	Review and configure what will be imported
Confirm	Check the summary and start
Progress	Watch it run and finish

Source

Choose the TestRail Project. A multi-suite project also asks for the Suite to import.

Then choose where the data lands:

Mode	Result
Auto	Creates a new RabbitQA project and run from the TestRail project
Bind to existing Run	Attaches the imported cases to a RabbitQA run you already have

Scope

A scope bar controls what is pulled across.

Option	Notes
Test Cases	The default, and the conservative choice
Test Runs	Unavailable when binding to an existing run
Run Results	Requires Test Runs, or binding to an existing run

Full Import selects all three at once. It is unavailable when binding to an existing run.

At least one scope must be selected.

Preview

The preview shows the section tree, sample cases, and the counts behind them, and is where you set the structure options.

Folder structure:

Mode	Result
Mirror	Recreates the TestRail section hierarchy inside RabbitQA
Flat	Puts every case in a single folder
Hybrid	Lets you pick which sections to bring over

Conflict strategy decides what happens to cases that already exist:

Mode	Result
Update	Overwrite the existing case with the TestRail version
Skip	Leave the conflicting case untouched
Create new	Create a separate copy for each conflict

Changing the scope after a preview invalidates it; Re-preview rebuilds it.

Confirm and Progress

The confirm step summarizes the folder structure, the conflict strategy, and the new cases to be created.

Starting the import moves to the progress step, which reports counts for cases, runs, and results as they land, and ends in Import complete, Import failed, or Cancelled.

Pushing Cases to TestRail

The TestRail submenu also pushes the other way, once TestRail project mappings are configured.

Action	What it does
Sync All Cases	Creates every unmapped case from the selected project in TestRail, in a section named "RabbitQA Cases". Already-mapped cases are skipped
View Sync History	Opens the sync log drawer for the selected project
Manage TestRail Integration	Opens the integrations settings

The confirmation names the RabbitQA project and the TestRail project before anything is written. When the sync finishes, the result reports how many cases were synced, skipped, and failed.

Cases that are linked to TestRail carry a badge, and a link dialog attaches an existing TestRail case to a RabbitQA one.

Related

• Test Repository — where import and export are launched from
• AI Test Sessions — session-level Excel export
• Review Workflow — why repository export is gated but Excel export is not