Import

Help URL: /reference/forms/import

Purpose

Turn a document (PDF, Word, Excel, CSV, text, or Markdown) spec/test script, or a GitHub issue, into a Gherkin feature draft via a staged import pipeline.

Common Tasks

• From the New feature dialog choose Import from document (PDF, Word, Excel, CSV, text, or Markdown — or drop the file onto the feature list or a feature row).

• Choose Import from GitHub issue (requires a linked repo).

• Watch the staged pipeline run: Extract & segment → Draft feature file(s) → Enrich from screenshots → Verify against your site (only when the project has a test site URL) → Finalize the draft(s).

• Answer any questions inline, or cancel and keep the draft as-is.

Key UI Elements

• Timeline rail: Shows each stage of the import, including the live "Verify against your site" stage when it runs.

• Gherkin draft tab: A live view of the feature being drafted.

• Inline questions: Prompts you answer in place to refine the draft.

• "Cancel — use draft as-is": Stops the pipeline and keeps the current draft.

Notes

• One import can split into multiple feature files.

• Excel and CSV rows are treated as candidate test cases, one per row; other document formats are treated as prose and segmented by described behavior.

• The "Enrich from screenshots" stage only does work for PDFs with embedded page images; it's skipped for other formats or text-only PDFs.

• The "Verify against your site" stage only runs when the project has a configured test site URL — it drives a live browser to correct screen names, labels, and any invented data, but never rewrites a bug/regression import's expected (currently-failing) outcome.

• The panel is inline in the Features detail pane and reattaches across reloads and sessions.