Import

A wizard for migrating existing test cases out of a hosted TMS and into a Kensa project - one of the main reasons teams adopt Kensa.

#Sources

• TestRail - CSV full-project export, and REST API.
• Qase.io - JSON export.
• Allure - REST API.
• Universal CSV - for any tool that can produce a CSV, with a template.

The importer is adapter-based: each source is an isolated adapter that produces a normalized case model, so new sources can be added without touching the rest of the pipeline.

#Flow (wizard)

1. Pick a source.
2. Upload the export file (CSV/JSON) or connect to the source's REST API.
3. Preview the discovered cases, with a per-case checkbox to choose exactly what to import.
4. Confirm and watch a progress log as cases are written to disk.

#What transfers

• Title, preconditions, steps, expected results, tags, priority map directly.
• Suite hierarchy is preserved; when the source structure is incompatible it is flattened.
• Custom fields auto-map into the project schema as text (you can retype them afterward in the schema designer).
• Attachments are downloaded when the source API exposes them; otherwise the wizard warns and points at how to do a full export.

#Provenance

Each imported case records where it came from in frontmatter.source_id:

testrail:C12345
qase:1
csv:row-42

…so traceability back to the original tool survives the migration. Imported cases always get fresh Kensa ids to avoid collisions.

#Round-trip

Every importer has a matching exporter. Carried fields survive an import → export → re-import round-trip (subject to each format's inherent lossiness, which is disclosed up front).