This page covers common end-to-end workflows for TestGenie — from AI test case generation through to execution and reporting.
Workflow 1: Generate Tests from a Jira Story and Execute Them
Use this workflow when you want to go from a Jira story to a complete test execution run.
Open the Jira story in your project.
Launch the Rovo agent from the Ask Rovo panel.
Ask the agent: "Generate test cases for this issue."
The agent detects the story as the requirement and uses its summary and description as generation context.
Review the planned test case list. Adjust the scenario, add preconditions, or update the requirement if needed.
Confirm draft generation and review each test case with its steps.
Confirm creation — test cases are created as Jira child issues linked to the story.
Navigate to Test Plans and create a new plan.
Use Link Test Cases to add the generated test cases to the plan.
Assign test cases to team members.
Click Execute Plan to start a run in the Execution Dashboard.
Mark each test case result as Passed, Failed, or Not Executed.
Click Export Report to share results.
Workflow 2: Generate Tests from a Scenario Description
Use this when you have a well-defined user flow but not necessarily a specific Jira requirement issue.
Open the Rovo agent in Jira.
Select or confirm your Jira project.
Provide a scenario description — for example: "A new user registers with a valid email, receives a confirmation email, and activates their account."
Optionally specify preconditions (e.g., "Email server is running and reachable").
Optionally link a requirement issue if you want traceability.
Review the planned test cases, then generate drafts and confirm creation.
Generated test cases appear in the Test Cases screen and can be added to any Test Plan.
Workflow 3: Sprint Test Coverage
Use this workflow to ensure all stories in a sprint have test cases before release.
At sprint start, open each story one by one.
For each story, use the Rovo agent to generate test cases (Workflow 1 above).
Once all stories have test cases, navigate to Test Plans and create a plan named after the sprint (e.g., "Sprint 14 — Full Coverage").
Link all test cases generated for the sprint to the plan.
Assign test cases to QA engineers or developers based on their story ownership.
At sprint end or before release, click Execute Plan and run through all test cases.
Mark results live as testing progresses.
Export Report at the end — attach to the release ticket.
Workflow 4: Regression Testing
Use this workflow to manage a reusable regression test suite across sprints.
Build a set of test cases covering core application flows using the Rovo agent across multiple stories and scenarios.
Create a Test Plan called "Regression Suite".
Link all regression test cases to this plan.
Each sprint or release, click Execute Plan to start a new execution run.
The Active Runs sidebar tracks each run separately — compare pass rates across releases.
When a regression test fails, link the failed execution to the defect using the ACTIONS column.
Export Report after each run to maintain a historical record.
Workflow 5: Post-Incident Test Coverage
Use this workflow after a production bug is discovered to ensure it is covered by a test case.
Open the Jira bug (defect) issue.
Launch the Rovo agent and ask it to generate test cases for this bug.
Review and create the test cases — they are linked to the defect issue as requirement-linked test cases.
Add the new test cases to your regression plan via Test Plans → Link Test Cases.
On the next execution run, these test cases will appear in the Execution Dashboard.
Adding Preconditions to Any Generation Session
At the planning stage of any generation workflow:
Tell the agent which preconditions should apply — e.g., "The user must have an active subscription" or "The application must be deployed to staging."
You can use existing Precondition issues from the project or create new ones.
The agent uses precondition summaries and descriptions to adjust the planned test cases.
If you change preconditions, the planned test list regenerates automatically before drafts are created.
Regenerating Test Cases
If the planned test cases are not quite right:
Update the scenario description or preconditions in the Rovo conversation.
The agent automatically regenerates the planned list.
Review the updated plan before moving to draft generation.
Important: Regeneration only works before drafts are generated. Once you have confirmed drafts and created Jira issues, start a new generation session if you need a different set of test cases.