Skip to main content

Using the Vansah Rovo Agent

Use the Vansah Agent for Rovo in Jira to find test cases, generate tests, manage Test Plans, record results and review coverage using everyday language.

Use the Vansah Agent for Rovo to work with Jira requirements and Vansah testing information through a conversation. It can help you find existing tests, prepare new coverage, maintain Test Cases, manage Test Plans and review execution results.

Before you begin

You need access to Rovo and Vansah on the Jira site you want to use. The information and actions available depend on your Jira and Vansah permissions and the capabilities available in your installed app version.

Open the Vansah Agent for Rovo

  1. In Jira, open Chat from the navigation bar.

  2. Select Agents and search for Vansah Agent for Rovo.

  3. Select the agent’s name to start a conversation.

  4. Choose a conversation starter or type your request. Include the Jira work item key or Jira space key so the agent knows where to look.

The conversation starters include generating Test Cases, showing coverage and recommending tests for a Jira work item. For more about the Rovo interface, see Atlassian’s guide to chatting with an agent.

What you can ask the agent to do

Replace the example keys, names and dates below with details from your own Jira site.

Task

Example request

Find and review Test Cases

Find the Test Cases linked to VANS-1234 and summarize what they cover.

Propose or create tests

Review VANS-1234 and propose positive, negative and boundary tests. Do not create anything yet.

Maintain Test Cases

Update the expected result for step 2 in VANS-C42 to say that a confirmation message appears.

Organize testing

In space VANS, link VANS-C42 and VANS-C43 to the Regression Test Folder.

Work with Test Plans

Find the Checkout Release Test Plan in space VANS and show its requirements and iterations.

Record results

Record Passed for VANS-C42 in iteration 2 of the Checkout Regression Test Plan in space VANS.

Review coverage and results

Show coverage for VANS-1234 and identify requirements that need more tests.

Review reports

Summarize the test execution results for the Regression Test Folder in space VANS.

Example: turn a requirement into reviewed test coverage

  1. Understand the requirement. Ask: “Review VANS-1234 and summarize its acceptance criteria.”

  2. Check existing tests. Ask: “Find the Test Cases already linked to VANS-1234.”

  3. Identify gaps. Ask: “Compare the existing tests with the acceptance criteria. Propose missing functional, negative and boundary scenarios. Do not create tests yet.”

  4. Review the proposal. Check that each scenario is useful, has a clear expected result and does not duplicate existing coverage.

  5. Create the agreed tests. Ask the agent to create the reviewed scenarios in Vansah and link them to VANS-1234. Name the destination Test Folder if required.

  6. Check the saved Test Cases. Open the returned Vansah links and review the steps, expected results, requirement links and folder placement before execution.

Give clear instructions for Test Plans and results

For a new Test Plan, include its name, space, start date, end date and the Jira work item or Test Folder it should cover. For an Advanced Test Plan, identify the work items and folders to include.

For an existing plan, use its exact name and include the iteration number when it matters. Supported changes include the name, description, planned dates and assignee. The agent can also help change the requirement scope of an Advanced Test Plan.

When recording results, specify the Test Case keys, result and target: a Jira work item, Test Folder or Test Plan. For a requirement within an Advanced Test Plan, give both the plan and the requirement. Recording a result saves testing information; it does not perform the test for you.

Tips for reliable answers

  • Name the records. Use work item and Test Case keys, exact plan names and folder names.

  • Set the scope. Add the space, release, sprint, component or iteration when relevant.

  • Separate a review from a change. Say “propose only” or “do not create or update anything” when you want recommendations.

  • Review before confirming. Check the target records and proposed changes when Rovo asks for confirmation.

  • Check the evidence. A coverage summary helps identify gaps; testers should still judge whether the tests meet the requirement.

If you cannot find the agent or get the expected result

  • The agent is missing: Check that you are on the correct Jira site and can access Rovo. Ask your administrator to check the installed Vansah version and your access.

  • A record cannot be found: Provide its exact key or name and space. Check that you can open it directly in Jira or Vansah.

  • The answer is incomplete: Narrow the request or ask the agent to check the remaining results and state the scope it reviewed.

  • An action is unavailable: Check your permissions and whether Vansah needs an update.

Did this answer your question?