Create Test Cases Skill

The Create test cases in bulk skill lets users create one or more test cases in Zephyr from a work item or a user prompt entered in Rovo chat. Users can choose whether the created test cases include only a name or also include additional details, such as the objective, preconditions, a step-by-step test script, or a BDD test script.

Users can also ask Rovo to preview proposed test cases before creating them. This allows you to review the proposed test cases, provide feedback, and refine them before they are created in Zephyr. All test cases created with Rovo are automatically labeled AI_generated.

How This Skill Works

You can use this skill to do the following:

  • Create one or more test cases from a work item

  • Create one or more test cases from a user prompt in chat

  • Create multiple test cases at once

  • Preview proposed test cases before creation

  • Review and refine proposed test cases before they are created

  • Create test cases with only a name, or with additional details such as objective, precondition, step-by-step test script, or a BDD test script

  • Turn work item content or user instructions into structured test cases

What This Skill Cannot Do

This skill cannot do the following:

  • Create test cases without a valid space key

  • Create test cases in a specific folder

  • Add unsupported fields

  • Merge separate test cases into one

  • Create test cases if the space requires custom fields

When to Use the Skill

You can use this skill when you need to do the following:

  • Create test cases from a work item

  • Create test cases from a prompt in chat

  • Create multiple test cases at once

  • Preview test cases before creating them

  • Quickly add test coverage for a new feature or release

Required Input

To create a test case or test cases in bulk, the request must include:

  • A space key where the test cases should be created

If a work item key is included in the request, the skill creates the test cases in the same space as that work item by default, unless the user explicitly specifies a different target space.

The request can be based on:

  • A work item

  • A user prompt entered in chat

You do not need to provide the test case name yourself. If you want a specific name, you can include it in the prompt.

You can also guide how much detail should be included. For example, you can ask for:

  • Name only

  • Objective

  • Precondition

  • Step-by-step test script

  • BDD script

If objective, precondition, test steps, or BDD test script are not included, explicitly ask for them in your prompt.

Note

BDD test scripts support only the following keywords: Given, When, Then, And, and But.

Example Prompts

Here are some example prompts you can use in Rovo:

  • Create test cases in space ZEP from work item ZEP-123

  • Create test cases in space XYZ from work item ZEP-123

  • Create test cases in space ZEP based on work item ZEP-123. Include objective, precondition, and steps

  • Create test cases based on work item ZEP-123

  • Create happy and unhappy path test cases based on ZEP-123

  • Preview test cases based on work item MD-14 before creating them

  • Generate a test case for a card payment flow in the MD space

  • Create test cases with BDD test scripts from work item ZEP-123 in space ZEP

  • Create test cases with an objective, precondition, and steps for login functionality in space ZEP

AI-generated Label

All test cases created with Rovo are automatically labeled AI_generated. You can use this label in the Test Case Library to filter and quickly see how many test cases were created with Rovo.

If a test case is edited after creation, or if the label is no longer needed, the AI_generated label can be removed.

Note

If the label is removed, the test case will no longer appear as AI-generated when filtering by label.

Publication date: