The information and actions available to you may depend on your Vansah permissions and the context available in Jira and Rovo.
Search your Vansah workspace
Ask the agent to find testing information across requirements, test cases, test plans, test runs, test logs, defects, and folders.
You can search using everyday language. Add details such as a Jira work item, feature, component, folder, priority, release, sprint, status, or owner to make the response more precise.
Example prompts:
Find everything related to authentication testing.
Show me all failed regression tests for Payments.
Find test assets related to the Payment Gateway.
What testing information is available for VANS-1234?
Find and review test cases
The Vansah Rovo Agent can find test cases using keywords and information such as folders, components, priorities, automation status, and linked requirements.
Use this to quickly understand what is already covered before creating more tests.
Example prompts:
Find test cases for user login.
Show regression test cases for Payments.
List the automated test cases for checkout.
Show the test cases linked to VANS-1234.
Summarize what these test cases validate.
Generate test cases from Jira requirements
The agent can generate test cases using the context available in Jira and Vansah. Generated test cases remain manageable in Vansah and can be reviewed, refined, and linked to the relevant requirement as part of your normal QA workflow.
You can ask for functional, positive, negative, boundary, or other relevant testing scenarios. Include the Jira work item key and describe the type or number of tests you need.
Example prompts:
Review VANS-1234 and create functional test cases for it.
Generate positive and negative test cases for this user story.
Create boundary test cases for the age validation requirement.
Create 10 functional test cases for VANS-1234 and link them to the requirement.
Before creating a large number of test cases, you can ask the agent to show you the proposed coverage first.
Example:
Review VANS-1234 and propose test coverage. Do not create any test cases yet.
Update and organise test cases
The Vansah Rovo Agent can help maintain existing test cases by updating their content and organizing them within Vansah.
You can ask the agent to update test steps, expected results, priority, folder, automation status, labels, and supported custom fields.
Example prompts:
Move these test cases into the Regression folder.
Update the expected results for this test case.
Mark these test cases as automated.
Change the priority of the selected test cases to High.
Add the label
paymentsto these test cases.
When requesting an update, identify the test cases clearly and describe exactly what should change.
Work with test plans
Use the Vansah Rovo Agent to search for test plans or help create and update planning information.
Test plans can be found using details such as release, sprint, status, owner, or labels. When creating a test plan, you can describe its scope, objectives, release, iterations, and assigned testers.
Example prompts:
Find the test plan for Release 4.2.
Show test plans owned by the Payments team.
Create a test plan for the checkout release.
Update this test plan to include Sprint 24.
Change the test plan status to In Progress.
Assign this test plan to the nominated testers.
Review coverage and traceability
The Vansah Rovo Agent can help you understand relationships between Jira requirements, Vansah test cases, test runs, test logs, and defects.
Use it to check whether a requirement is covered, understand execution outcomes, identify gaps, and follow testing evidence through the delivery lifecycle.
Example prompts:
Show all test cases covering VANS-1234.
Does this requirement have sufficient functional test coverage?
Find requirements without test coverage.
Which failed tests are related to this defect?
Show the execution history for the test cases linked to VANS-1234.
Identify coverage gaps or duplicated test scenarios for this requirement.
Combine tasks in one request
The agent can use multiple Vansah capabilities as part of a single conversation. For more complex work, describe the outcome you want and include the relevant Jira work item, scope, and any constraints.
Example prompts:
Review VANS-1234, find its existing test cases, identify coverage gaps, and propose additional functional tests.
Find the failed regression tests for Payments and show the defects linked to those failures.
Review the requirements in Sprint 24 and identify any that do not have test coverage.
For actions that create or change information, clearly tell the agent whether you want it to perform the action or only prepare a recommendation.
Tips for better results
Include the Jira work item key whenever possible.
Be clear about whether you want to search, review, create, or update.
State the type of testing you need, such as functional, negative, boundary, or regression.
Specify the number of test cases when quantity matters.
Add useful context such as the release, sprint, component, folder, or priority.
Ask the agent to propose changes first when you want to review them before anything is created or updated.
Review generated test cases to confirm they meet your organization's testing standards before execution.
Example end-to-end workflow
You can use the Vansah Rovo Agent to move from a Jira requirement to reviewed test coverage through a natural-language conversation:
Ask the agent to review a Jira requirement.
Ask it to find existing test cases linked to that requirement.
Ask it to identify missing, overlapping, or weak coverage.
Review the recommended test scenarios.
Ask the agent to create the approved test cases in Vansah.
Confirm that the new test cases are linked to the correct requirement and organized in the appropriate folder.
Example conversation:
Review VANS-1234 and summarize the acceptance criteria.
Find all existing test cases linked to this requirement.
Identify any functional, negative, and boundary coverage gaps. Do not create tests yet.
Create the approved test cases in Vansah and link them to VANS-1234.
Frequently asked questions
Is the Vansah Rovo Agent a general-purpose chatbot?
No. It is a purpose-built testing agent designed to work with structured Jira and Vansah testing information and established QA workflows.
Can it create test cases?
Yes. The agent can generate test cases using requirements, work items, related context, and established Vansah test-management structures. The generated tests remain available in Vansah for review, refinement, organization, and traceability.
Can it change existing test information?
Yes. Supported actions include updating and organizing test cases and managing test-plan information. Available actions depend on the capabilities enabled for the agent and the user's permissions.
Can it review test coverage?
Yes. The agent can explore the relationships between requirements, test cases, executions, test logs, and defects to help identify missing coverage, duplicated scenarios, failures, and risk areas.
Where does the agent get its information?
It uses the Jira and Vansah testing context available through Atlassian Rovo. This keeps its responses grounded in your organization's requirements and managed test assets.
Does it replace tester review?
No. The agent helps teams find information, generate tests, and analyze coverage faster. Testers and other authorized team members should still review generated content and confirm that it meets the project's requirements and quality standards.