Import and export test cases

To move test cases into Qualflare, export them from Qase, TestRail, Testmo or Allure TestOps and import the file from Browse; files up to 20 MB import in the background, and you need the Editor role or higher.

Before you begin

Editor+ · project (requires the Editor role or higher in the project)

Qualflare doesn't import generic CSV or spreadsheet files, or its own export.

Supported sources

Allure TestOps means the test management product. Allure Report, the open-source reporter, has no test case export to import.

Menu paths differ between tools and versions, so follow the source tool's own export guide.

Import test cases

1. In Browse, open Browse actions (⋮, next to Create Suite) and choose Import. In a project with no suites, you can also click Import in the empty state.
2. In Import Test Cases, choose the tool you're importing from.
3. Upload the file and click Import. Qualflare shows Import queued — we'll notify you and the project when it's done. and closes the dialog.

When the import finishes, project members get the notification Import finished: <file name>, reading <n> cases created in <m> new suites, <k> skipped., or Import failed: <file name> with the reason. Qualflare also emails project members who haven't turned off this project's emails, unless Import finished is turned off in Project Settings > Notifications (see Notifications).

What gets imported

• Suites, test cases and their steps. Qualflare adds cases to suites with the same name and creates the suites that don't exist yet.
• Expected results become steps of type Expected Result.
• Cases from Qase, Testmo and Allure TestOps keep their state when it matches a Qualflare state: Draft, Review, Active or Outdated. Qase's Actual becomes Active, and Deprecated or Obsolete becomes Outdated. TestRail cases, and states Qualflare doesn't recognize, start as Draft.
• A case whose name already exists in its suite is skipped, so importing the same file twice doesn't create duplicates.
• Tags, custom fields and attachments aren't imported.

Limits

The dialog rejects a file over 20 MB. A file over any other limit fails, and the notification names the limit. Descriptions longer than 1,024 characters and step text longer than 256 characters are shortened.

Export test suites

1. In Browse, open Browse actions (⋮) and choose Export.
2. In Export Test Cases, pick the suites to export, or none to export every suite.
3. Click Export. Qualflare prepares the file in the background.
4. When Export Complete appears, click Download. If you see Export Failed, click Try Again.

• Starting an export needs the Editor role or higher. Export also shows for Viewers, but their export fails with Failed to start export. Please try again.
• Qualflare emails a link to the export's download page to project members who haven't turned off this project's emails. The page starts the download with a link that works for 10 minutes; if it expired, click Download again.
• Export files: deleted 30 days after the export is created. See Data retention.

Export format

The export is a ZIP archive with two CSV files:

• cases.csv: one row per case, with the columns Seq, UID, Name, Description, State, Priority, TestType, Automation, SuiteName, CreatedAt and UpdatedAt
• steps.csv: one row per step, with the columns CaseSeq, CaseName, SuiteName, Position, StepType, Instruction and SharedStepName

Suites appear only in the SuiteName column. An expected result is a step with the StepType expected_result.

Verify

• After an import: the Import finished: <file name> notification shows the counts, and the suites show in Browse.
• After an export: the ZIP holds cases.csv and steps.csv.

Troubleshoot

Next steps

• Test suites and Browse
• Test cases: fields, states and steps
• Collect test results
• Run manual tests with the Test Wizard