Skip to main content

Generate Test Cases from Jira Requirements

Use QA Copilot to generate test cases from Jira user stories and requirements.

Updated this week

Overview

QA Copilot can generate test cases directly from your Jira requirements. It reads the summary, description, and acceptance criteria from each Jira issue and produces structured test cases with steps and expected results. Related requirements are automatically included as context for better coverage.

Prerequisites

  • Jira connected as your requirement manager under Settings > Requirements

  • Requirements synced from your Jira project (happens automatically after connecting)

Step 1: Connect Jira

Go to Settings > Requirements in your project. Select Jira as the requirement manager, authenticate with your Atlassian account, and select your Jira project and issue types (Task, Story, Bug, etc.). Once saved, TestCollab automatically syncs all matching issues.

Jira requirements and user stories synced into TestCollab

Step 2: Get the test cases generated from Jira work items by QA Copilot

Navigate to Test Cases and click Create with QA Copilot. Select the From JIRA tab. Search by keyword or issue key. Select up to 5 requirements at a time and click Generate test cases.

Select Jira user stories for AI test case generation in QA Copilot

Step 3: Review and Accept

After generation (~30-90 seconds), you see the Proposed Test Cases page. Each proposal includes a title, description, priority, and test steps with expected results.

9 proposed test cases generated from a Jira requirement

For each proposed test case, you can:

  • Accept (green checkmark) - adds it to your project

  • Reject (red X) - discards the proposal

  • Edit (pencil icon) - modify title, steps, or priority before accepting

Each accepted test case is automatically linked to the specific Jira requirement it was generated from, keeping your traceability matrix accurate.

Context-Aware Generation

QA Copilot uses TF-IDF cosine similarity to find related requirements and includes them as context. For example, selecting a story about license plate recognition will also pull in related stories about gate operations and payment flows, producing integration-aware test cases.

Tips for Better Results

  • Write clear acceptance criteria in Jira - output quality matches input quality

  • Include descriptions - stories with just a title produce shallow test cases

  • Select related stories together for interaction-aware coverage

  • Always review before accepting - AI output is a strong starting point, not a finished product

Troubleshooting

  • No search results: Verify requirements are synced under the Requirements section in the sidebar

  • Generation timeout: Try selecting fewer requirements (1-2 instead of 5)

  • Sync in progress: Wait for the initial sync to complete after first connecting Jira

Did this answer your question?