Import & Export

Proba.run lets you bring test cases in from a spreadsheet or from TestRail, and take your cases and results back out again as CSV, Excel, or a PDF report. This page covers all the import and export options available from a project's settings and toolbars.

Importing test cases from CSV or XLSX

Open Import in the cases toolbar, choose a .csv or .xlsx file, and upload it. The first row must be column headers; unknown columns are ignored, and completely empty rows are skipped.

Rows with an invalid title are skipped and listed with a reason, while every valid row is still imported — one bad row does not stop the rest. A file with more than 2,000 data rows, or larger than 5 MB, is rejected before anything is imported. A downloadable template with example rows is linked from the import dialog.

Importing does not deduplicate: running the same file twice creates duplicate cases.

Importing from TestRail

Structure

Export a suite from TestRail as XML (Export → XML) and upload it from Settings → Import/Export → Import from TestRail. Proba.run shows a preview — the folder tree it will create, counts of cases and requirements, and any parsing problems — before writing anything. Confirming the preview creates the structure:

• TestRail sections become folders, matched or created by name.
• Each case keeps its title, description, preconditions, priority, and steps (structured steps import as structured, plain-text steps import as text).
• TestRail references become linked requirements.

Re-importing the same or an updated export skips cases that were already imported (matched by their original TestRail ID), so you can import incrementally without creating duplicates. Only the case structure is transferred this way — runs and results are a separate import (below).

Execution history

Once a suite's structure has been imported, you can pull over its execution history directly from the TestRail API: open Import run history, enter your TestRail URL, account email, API key, and project ID, then fetch the list of runs. Pick the runs you want (or select all) and import them.

• Each imported run keeps its original author and execution date instead of the date of import.
• TestRail statuses map to Proba.run statuses; unrecognized custom statuses import as skipped and are called out in the report.
• Results for cases that were not part of the structure import are skipped and reported separately.
• Already-imported runs are marked and cannot be imported twice.

Your TestRail credentials are used only for this request and are never stored.

Exporting test cases and runs

An Export menu is available wherever cases or runs are listed — on the cases page, the runs list, the stats page, and an individual run's page. Everyone with access to the project can export, including read-only members.

• CSV — cases export includes title, priority, status, folder, tags, and steps; runs export includes status and progress counters; a single run's case list includes each case's status, configuration, and elapsed time. Case export is designed to round-trip with CSV import.
• Excel (XLSX) — the same columns as CSV, formatted as a proper workbook: bold frozen header row, autofilter, and auto-sized columns. A run report exports as two sheets, Summary and Cases.

Exporting a run report to PDF

From a run's page, choose PDF in the Export menu to download a formatted report: a header with the project and run details, a progress summary, and the full table of cases with their status, configuration, and elapsed time. PDF export is only available for a single run's report, not for case or run lists.