Test Case Structure in Jira

TestGenie represents all testing assets as standard Jira issues. This page explains how each issue type is structured and how they connect to each other.

Test Case Issue

A Test Case is a Jira issue representing a single testing scenario. It includes:

• Summary — e.g., "Verify user login with valid credentials"

• Description — detailed explanation of what is being tested and why

• Links:

  • To Test Step child issues (one per step)

  • To Precondition issues (linked via configured link type)

  • To a Requirement issue (the story or feature being validated)

  • To one or more Test Plan issues (the plans this test case belongs to)

Test cases are created by the Rovo agent during AI generation, or can be created manually as standard Jira issues using the configured Test Case issue type.

Test Step Issue

A Test Step is a child Jira issue representing one discrete action in a test case, such as:

• "Navigate to the login page"

• "Enter a valid username and password"

• "Click Login and verify the dashboard appears"

Each Test Step issue contains:

• Step description — the action to perform

• Expected result — what should happen

Test steps are created as child issues of the parent Test Case issue, using the issue type configured in the Requirement & Test Linkage section of Issue Mapping.

Precondition Issue

Preconditions are Jira issues defining system or data states that must be true before a test can run:

• "User account exists with active subscription"

• "Application is deployed to staging environment"

• "User is logged out"

TestGenie:

• Links Test Cases to Precondition issues using the configured link type

• Uses Precondition summaries and descriptions during AI generation to produce realistic test cases

• Allows Preconditions to be added or removed during the planning stage

Test Plan Issue

A Test Plan is a Jira issue that groups a set of Test Cases for a specific sprint, release, or feature area. It includes:

• Summary — the plan name (e.g., "Sprint 12 Regression", "Release Plan")

• Assignee — the team member responsible for the plan

• Priority — the plan's priority

Test cases are linked to the plan using the Plan ↔ Test Case link type configured in Issue Mapping. A Test Plan issue is created using the issue type configured in the Execution Planning section.

Test Execution Issue

A Test Execution issue represents a single execution run of a test plan. It is created when Execute Plan is clicked in the Test Plans screen.

• Linked to the Test Plan via the Plan ↔ Execution link type

• Linked to each Test Case in the run via the Execution ↔ Test Case link type

• Stores execution status tracked in the Execution Dashboard (Passed / Failed / Not Executed)

Defect Links

When a test case is marked Failed during execution, the ACTIONS column allows linking the execution to an existing Jira defect.

Two links are created:

• Defect ↔ Execution — using the link type configured in Defect Orchestration

• Defect ↔ Test Case — using the link type configured in Defect Orchestration

These links are standard Jira issue links, visible in the defect issue view, queryable via JQL, and traceable through the full chain: defect → execution → test case → requirement.

How Issues Are Connected

Requirement Issue (Story / Bug / Feature)
  ↕ (Req ↔ Test Case link)
Test Case Issue
  ↕ (child)                    ↕ (Precondition link)          ↕ (Plan ↔ Test Case link)
Test Step Issues         Precondition Issues              Test Plan Issue
                                                              ↕ (Plan ↔ Execution link)
                                                          Test Execution Issue
                                                              ↕ (Defect ↔ Execution link)
                                                          Defect Issue
                                                              ↕ (Defect ↔ Test Case link)
                                                          Test Case Issue

All nodes in this model are standard Jira issues. All connections are standard Jira issue links. The entire structure is queryable with JQL and visible in existing Jira boards and dashboards.