Generate test cases

Command: /testgen-flow · ← All scenarios · User guide

Turn a ticket (plus its linked docs) into a structured requirements document and a set of manual test cases — then export those cases to your test management system. No automation code is written here.

Use this when you have a Jira ticket, epic, or story and need designed test scenarios with traceability, optionally pushed to TestRail.

Not for: writing runnable tests — use Automate UI tests or Automate API tests for that.

Running it

/testgen-flow Generate test cases for PROJ-123
/testgen-flow Create test scenarios from EPIC-789 and export to TestRail

You can also just give it the bare ticket key or a full ticket URL.

How it works

It pulls the source material together, finds the contradictions and gaps, and — importantly — stops and asks you to answer them before it writes anything. You confirm the requirements and scenarios, and you decide when to export.

flowchart TB
    Start(["/testgen-flow + ticket key"]) --> Load["Load config + parse ticket"]
    Load --> Collect["Collect ticket + wiki data"]
    Collect --> Gaps["Find gaps & contradictions"]
    Gaps --> G1{"You answer <br>the questions"}
    G1 --> Reqs["Generate requirements doc"]
    Reqs --> RC{"You confirm <br>the requirements?"}
    RC -->|changes| Reqs
    RC -->|confirm| Cases["Design manual test cases"]
    Cases --> CC{"You confirm <br>the cases?"}
    CC -->|changes| Cases
    CC -->|confirm| Exp{"Export to <br>your TMS?"}
    Exp -->|not now| Local(["Cases saved locally"])
    Exp -->|export| TMS["Push cases to your TMS"]
    TMS --> Done(["Cases in TestRail + report"])

    classDef step fill:#dae8ff,stroke:#3674b5,color:#102a43;
    classDef gate fill:#fff2cc,stroke:#b58b00,color:#493800;
    classDef done fill:#e5f7e8,stroke:#35834a,color:#153b20;
    class Load,Collect,Gaps,Reqs,Cases,TMS step;
    class G1,RC,CC,Exp gate;
    class Start,Done,Local done;

It reads the Jira ticket and its linked Confluence pages (including child pages, which often hold the real detail), and the requirements document it produces traces back to that source material and to your answers.

What you’ll be asked to do

Answer the questions it generates — you fill these in, not the agent — since skipping them bakes assumptions into the requirements. Then confirm the requirements summary and the test scenarios, and provide the TMS destination (project, suite, section) when you’re ready to export. Occasionally you’ll need to create the target container in the TMS UI yourself if the connector can’t.

What it creates

Everything lands under plans/testgen-<TICKET-KEY>/: testgen-project-config.md, initial-data.md, the collected raw-data.md, a gap analysis.md, questions.md + answers.md, requirements.md, test-scenarios.md, and an export-report.md receipt with the created TMS IDs. A testgen-state.md tracks progress.

Automate UI tests / Automate API tests to turn cases into code · Author requirements for a full requirements engineering pass.

Prerequisites: Issue Tracker; Test Management System for export.

Sources