This page explains how TestGenie works end-to-end — from configuration through AI test case generation, test planning, execution tracking, and results export.
The TestGenie Workflow at a Glance
TestGenie covers the complete test management loop inside Jira:
Configure → Generate → Manage → Plan → Execute → Link Defects → Export
Each stage maps to a screen or action in the app:
Stage | Where it happens |
|---|
Configure issue types and link types | Issue Mapping screen |
Generate test cases from Jira stories | Rovo agent in the Ask Rovo panel |
View and manage test cases | Test Cases screen |
Organise into plans and assign | Test Plans screen |
Run tests and track results live | Execution Dashboard |
Link failed tests to defects | Execution Dashboard → ACTIONS column |
Share results with stakeholders | Export Report button |
Stage 1: Configuration (Issue Mapping)
Before any test management features work, TestGenie must know which of your existing Jira issue types and link types correspond to each role in the test lifecycle.
The Issue Mapping screen has three sections:
Requirement & Test Linkage — maps requirement and test case issue types, and the link type that connects them. Also maps test step and precondition types.
Defect Orchestration — maps the defect issue type and the link types used to connect defects to executions and test cases.
Execution Planning — maps test plan and execution issue types, enables execution tracking, and defines all plan-to-case, plan-to-execution, and execution-to-case link types.
This configuration is stored per Jira project and reused for all subsequent test generation and execution in that project.
Stage 2: AI Test Case Generation (Rovo Agent)
Test cases are generated conversationally via the Atlassian Rovo agent — accessible from the Ask Rovo panel in any Jira issue or from the Rovo interface.
The generation workflow has seven steps:
Project selection — the agent identifies the target project from the open Jira issue or from your input
Issue context detection — if launched from a Jira issue, the agent detects its type and uses it as the requirement (coverage) source
Scenario definition — you provide a scenario description, or the agent uses the issue summary as the baseline
Planned test case generation — the agent generates a list of test case summaries based on the scenario, requirement description, and any preconditions
Optional context updates — add or remove preconditions, change the requirement issue; the planned list regenerates automatically
Detailed draft generation — each planned test case is expanded into a full draft with summary, description, test steps, and expected results
Jira issue creation — you confirm; the agent creates all test case issues, test step child issues, and requirement links in Jira
Generated test cases appear immediately in the Test Cases screen.
Stage 3: Test Cases Screen
The Test Cases screen is the central view for all test cases in the project. It shows:
All test cases with their key, summary, assignee, status, and priority
Test steps and linked test plans for each case
Filtering options by assignee, status, and priority
From this screen you can navigate into individual test cases or jump to linked test plans.
Stage 4: Test Plans
The Test Plans screen is where you organise test cases into executable groups — typically by sprint, release, or feature area.
From Test Plans you can:
Create a new plan with a name, assignee, and priority
Link test cases to the plan using the Link Test Cases action
Assign individual test cases to team members
Click Execute Plan to start a test run, which opens the Execution Dashboard
Stage 5: Test Execution
The Execution Dashboard shows the live state of a test run.
Stat cards at the top show Tests Passed, Tests Failed, and Not Executed counts — updated as results are marked
The test case table shows every test case in the active run with columns for key, summary, assignee, test result, and actions
The Active Runs sidebar on the left lets you switch between multiple execution sets for the same plan
Mark each test case result as Passed, Failed, or Not Executed from the TEST RESULT column
Stage 6: Defect Linkage
When a test case is marked Failed, the ACTIONS column shows a defect link action. This connects the failed execution to an existing Jira defect using the link types configured in the Defect Orchestration section of Issue Mapping.
This creates a traceable chain: defect → execution → test case — visible in standard Jira issue views and JQL queries.
Stage 7: Export Report
When a run is complete, click Export Report from the Execution Dashboard toolbar. The report contains the full run summary and individual test case results, ready to share with stakeholders or attach to a release ticket.