This document explains how the Jira Test Case Generation feature works in GoTestPro and defines the required Jira Story Template for high-quality AI-generated test cases.

1. Overview

The Jira Test Case Generation feature allows users to automatically generate functional test cases directly from a Jira User Story using AI.

It intelligently extracts acceptance criteria, business rules, linked issues, and comments to produce detailed, executable test steps.

2. Feature Flow (End-to-End)

Below is the complete flow from selecting a Jira story to saving test cases into GoTestPro and Xray.

➊ Step 1 — Select Jira Story

Navigate to Tests → Listing
Click Create Test Cases From Jira
Select:
- Jira Project
- Jira Story (from dropdown)

The system loads basic story metadata:

Story Key
Summary
Description
Issue Type, Priority, Status

➋ Step 2 — System Fetches Enriched Jira Data

The system automatically retrieves deeper context using Jira APIs:

Acceptance Criteria
Linked Issues (Epic, Related, Depends On, Blocks)
Recent Comments (Last 10)
Labels & Components
Business Rules / Additional fields

The richer the Jira story = the better the generated test cases.

➌ Step 3 — AI Prompt Construction

The system compiles all gathered details into a structured AI prompt:

Summary + Description
Acceptance Criteria
Linked Issue context
Clarifying Comments
Labels (domain hints)
Components (system area hints)
Application Metadata (name, type, URL if configured)

Users can view, edit, or extend the AI prompt.

➍ Step 4 — AI Generates Test Cases

Upon clicking Generate Test Cases, the system sends the prompt to the AI engine.

The AI produces 5 default scenarios:

Happy Path
Alternative Flow
Negative / Error Handling
Edge Case (Boundary)
Data Validation

Each test case includes:

A meaningful title
Description
8–15 detailed test steps following real UI actions:

Examples:

navigate https://app.url
type "email@example.com" as Email field
click "Submit"
verify success message is displayed

➎ Step 5 — User Reviews & Edits Test Cases

Within the UI, the user can:

Edit titles & descriptions
Modify steps
Add new steps
Delete steps
Insert steps between others
AI-Regenerate an individual step

Users select which test cases to keep.

➏ Step 6 — Select Test Plan

User chooses:

Auto-generated test plan
Existing test plan
Custom test plan name

Test cases will be assigned to the selected plan.

➐ Step 7 — Optional: Xray Test Creation

If the checkbox Create test cases in Xray is enabled:

Each generated test case becomes an independent Xray Test Issue.
Steps are converted into Xray’s format (Action / Data / Expected Result).
Each Xray test is linked to the original story, enabling full requirement traceability.

➑ Step 8 — Save Test Cases to GoTestPro

On clicking Save Test Cases:

Test Scripts are created
Test Plan is updated/created
Xray test issues created (if enabled)
A summary is displayed with:
- Test count
- Test plan name
- Xray issue keys

➒ Step 9 — View & Execute Tests

User is redirected to:

Tests → Listing

Where the newly generated test cases are available for:

Viewing
Execution
Reporting

3. Required Jira Story Template

A clean, structured Jira story is critical for generating accurate and complete test cases.

Below is the recommended template.

3.1 Jira Story Template (Copy/Paste into Jira Story Description)

**Story Title:** [Action-oriented, clear title]

**Description:**
As a <user type>, I want <goal>, so that <business value>.

Provide background/context about the feature:
- What it does
- Why it is needed
- Business rules / workflow overview

---

**Acceptance Criteria:**
- [ ] Criterion 1: Specific, testable outcome
- [ ] Criterion 2: Expected flow behavior
- [ ] Criterion 3: Error / negative handling
- [ ] Criterion 4: Edge case / boundary condition
- [ ] Criterion 5: Data validation rule

---

**Business Rules:**
- Rule 1: [Validation rule or data constraint]
- Rule 2: [Functional requirement]
- Rule 3: [Workflow rule]
- Rule 4: [System restriction or threshold]

---

**Test Data Requirements:**
- Valid Accounts:
  - [...]
- Invalid Accounts:
  - [...]
- Required Sample Data:
  - [...]

---

**Preconditions:**
- User exists with correct permissions  
- Environment URL available  
- Feature flag enabled (if applicable)  

---

**Related Issues:**
- Epic: [EPIC-123]
- Related: [STORY-456]
- Depends on: [STORY-789]

---

**Labels:** [module-name], [feature-type], [priority-high]  
**Components:** [Backend], [Frontend], [API]

**Additional Notes:**
- Screenshots  
- Design mockups  
- Technical links

3.2 Example Story (For Reference)

**Story Title:** Implement User Login with Two-Factor Authentication

**Description:**
As a user, I want to log in using username, password, and a 6-digit 2FA code so my account remains secure.

**Acceptance Criteria:**
- [ ] User logs in with valid credentials + valid 2FA code
- [ ] Incorrect 2FA code shows an error
- [ ] User can resend 2FA code
- [ ] Maximum 3 invalid attempts before lock
- [ ] 2FA expires after 5 minutes

**Business Rules:**
- 2FA code = 6 digits
- Lockout duration = 30 minutes
- Resend cooldown = 30 seconds

**Test Data Requirements:**
- Valid user: test@example.com / Password123
- Valid 2FA: 123456
- Invalid 2FA: 000000

**Preconditions:**
- User has 2FA enabled

**Related Issues:**
- Epic: EPIC-100
- Depends on: STORY-150

**Labels:** security, authentication  
**Components:** Security, Authentication

4. Summary

The Jira Test Case Generation feature automates:

Jira Story → AI Test Cases → GoTestPro Scripts → Optional Xray Test Issues

Using a well-structured story template ensures:

Higher accuracy
Better scenario coverage
Cleaner test steps
Better negative & edge-case generation

Jira Test Case Generation – Feature Flow & Required Jira Template

Table of Contents