This guide walks you through setting up and using TestGenie — from install on the Atlassian Marketplace to your first complete test execution run.
Step 1: Install from Atlassian Marketplace
Go to the Atlassian Marketplace and search for TestGenie.
Click Get it now and select your Jira Cloud site.
Follow the installation prompts. No credit card is required for teams up to 10 users.
Once installed, TestGenie appears in your Jira project navigation.
Step 2: Open the Get Started Screen
After installation, open TestGenie in any Jira project. The Get Started screen is the default landing page. It shows:
Click Start Configuring to proceed.
Note: If a license warning banner appears at the top of the screen, your app license is not yet active. Contact your Jira administrator or visit the Atlassian Marketplace to activate your subscription.
Issue Mapping is a one-time setup that tells TestGenie which of your existing Jira issue types and link types to use. Open it via the TestGenie navigation or the Start Configuring button on the Get Started screen.
The screen has three sections:
Requirement & Test Linkage
Field | What to select |
|---|
Requirement issue type | The Jira issue type that represents requirements (e.g., Story) |
Test Case issue type | The issue type used for test cases (e.g., Task, or a custom type) |
Req ↔ Test Case link type | The link type connecting requirements to test cases (e.g., "is tested by") |
Defect Orchestration
Field | What to select |
|---|
Defect issue type | The Jira issue type used for bugs/defects (e.g., Bug) |
Defect ↔ Execution link type | The link type between a defect and its execution record |
Defect ↔ Test Case link type | The link type between a defect and the test case that caught it |
Execution Planning
Field | What to select |
|---|
Test Plan issue type | The issue type used for test plans (e.g., Epic, or a custom "Test Plan" type) |
Test Execution issue type | The issue type used for execution records |
Enable Test Execution tracking | Checkbox — must be checked to track pass/fail results in the Execution Dashboard |
Plan ↔ Test Case link type | The link type between a test plan and its test cases |
Plan ↔ Execution link type | The link type between a test plan and its execution runs |
Execution ↔ Test Case link type | The link type between an execution and each test case it covers |
Click Save Changes when all three sections are complete.
Tip: You can reuse the same link type (e.g., "Relates to") across multiple relationships. All three sections must be filled in before Test Plans and Execution tracking will work.
Step 4: Generate Test Cases with Rovo
Open any Jira story, bug, or feature in your project.
Launch the Rovo agent from the Ask Rovo panel in the right sidebar.
Ask the agent: "Generate test cases for this issue."
The Rovo agent reads the issue summary and description, then generates a list of planned test case summaries.
Review the plan. Optionally adjust the scenario description, add preconditions, or change the coverage issue.
When satisfied with the plan, ask the agent to generate detailed drafts.
Review each draft (summary, description, test steps, expected results).
Confirm creation — test cases are created as native Jira child issues linked to the parent story.
Generated test cases immediately appear in the Test Cases screen.
Step 5: View Test Cases
Navigate to Test Cases in the TestGenie sidebar.
All test cases for the current project are listed here
Each test case shows its test steps, assignee, status, and linked test plans
Use filters to narrow by assignee, status, or priority
Step 6: Create a Test Plan
Navigate to Test Plans.
Click Create New Plan.
Fill in the plan name, assignee, and priority.
Click Link Test Cases to add test cases to the plan.
Assign individual test cases to team members as needed.
Click Execute Plan to start a test run — this opens the Execution Dashboard for that plan.
Step 7: Track Test Execution
In the Execution Dashboard:
Stat cards at the top show live counts: Tests Passed / Tests Failed / Not Executed
Select each test case row and mark its result using the TEST RESULT column dropdown
Use the Active Runs sidebar to switch between execution sets for the same plan
When a test fails, use the ACTIONS column to link the failed execution to an existing Jira defect
Step 8: Export Results
When a run is complete, click Export Report from the Execution Dashboard to download and share results with stakeholders.
The exported report includes the run summary and individual test case results.