This page describes all major capabilities of TestGenie.
AI Test Case Generation via Atlassian Rovo
TestGenie uses an Atlassian Rovo reasoning agent — not a generic AI — to generate structured test cases directly from Jira issues.
Open any Story, Bug, or Feature in Jira and ask: "Generate test cases for this issue"
The agent reads the issue summary, description, acceptance criteria, and any preconditions
Generates a list of planned test case summaries first — you review before any issue is created
Expands each into a full draft with test steps and expected results
Creates all Jira issues (test cases, test steps, requirement links) on your confirmation
This is not autocomplete. The Rovo agent reasons across your Jira project context and adapts generation to your scenario.
Issue Mapping (Configuration)
The Issue Mapping screen is a one-time configuration that maps TestGenie's test management roles to your existing Jira issue types and link types.
It has three sections:
Requirement & Test Linkage
Maps the issue types for requirements and test cases, and the link type connecting them. Also maps test step and precondition issue types and their link types.
Defect Orchestration
Maps the defect issue type and the link types used to connect defects to execution records and test cases. Once configured, linking a failed test to a defect is a single action in the Execution Dashboard.
Execution Planning
Maps test plan and execution issue types, enables execution tracking, and defines all link relationships between plans, test cases, and execution records.
No proprietary schema is created. All configured types are your existing Jira issue types — nothing in your project changes.
Test Cases Screen
The Test Cases screen provides a unified view of all test cases in the project.
Lists all test cases with key, summary, assignee, status, and priority
Shows test steps and linked test plans for each case inline
Supports filtering by assignee, status, and priority
All test cases are standard Jira issues — queryable with JQL and visible in existing Jira boards
Test Plans
The Test Plans screen lets you organise test cases into executable groups by sprint, release, or feature area.
Create a test plan with a name, assignee, and priority
Link any number of test cases to the plan
Assign individual test cases to different team members
Click Execute Plan to start a test run
Test plans are standard Jira issues created using the issue type configured in Issue Mapping.
Test Execution and Live Dashboard
The Execution Dashboard is where test runs are tracked in real time.
Stat cards at the top show live counts of Tests Passed, Tests Failed, and Not Executed — updated instantly as results are marked
The test case table shows every test case in the active run with its key, summary, assignee, current test result, and actions
The Active Runs sidebar lets you switch between multiple execution sets for the same plan
Mark each test case as Passed, Failed, or Not Executed from the TEST RESULT column
Defect Orchestration
When a test case is marked Failed, the ACTIONS column provides a one-click defect link action. This connects the failed execution to an existing Jira defect using the link types configured in Issue Mapping.
No manual discipline required — the link action is always available on a failed test
Defect → Execution → Test Case trail is created in standard Jira links
Traceable via JQL and visible in standard Jira issue views
Export Report
Click Export Report from the Execution Dashboard to generate a shareable report of the current run.
The report includes:
Export directly from the execution screen — no copy-paste, no reformatting.
Zero Schema Disruption
TestGenie creates no proprietary issue types, no hidden databases, and no external integrations.
All test data lives in Jira as standard issues
Queryable with JQL like any other Jira issue
Visible in existing boards, filters, and dashboards
Jira performance is unaffected — no issue bloat
Context-Aware Generation
The Rovo agent uses a Test Generation Context combining:
Your scenario description (or the Jira issue summary if no description is provided)
The requirement issue's summary and description (acceptance criteria, business rules)
Precondition summaries and descriptions (system state assumptions)
The richer the context, the higher quality the generated test cases.
Precondition Management
Preconditions represent states that must be true before a test can run (e.g., "User account exists with active subscription").
Preconditions are separate Jira issues linked to test cases
Added or removed during the planning stage
The planned test case list regenerates automatically when preconditions change
Precondition descriptions inform the AI about system setup assumptions
Jira-Native Issue Creation
TestGenie creates:
Test Case issues (using your configured issue type)
Test Step issues as child issues of each test case
Precondition links between test cases and precondition issues
Coverage links between test cases and requirement issues
Test Plan issues (using your configured issue type)
Execution issues (using your configured issue type)
Defect links between executions and defect issues
All are standard Jira issues created with your existing types and links.