Generating Test Cases

Learn how to generate and refine test cases directly from Jira issues using Reqase Lite's AI-powered capabilities.

Reqase Lite allows you to generate and refine test cases directly from Jira issues. Once enabled on an issue, you can configure the integration, select rules and formats, add context, and then review/edit test cases before importing or exporting.

1. Accessing Reqase Lite on an Issue

To start generating test cases from a Jira issue:

  1. Open a Jira issue (Story, Task, Bug, etc.)
  2. Click the View App Actions button (underneath the issue summary)
  3. Select Reqase Lite

๐Ÿ’ก Tip: This enables the Reqase Lite App on the issue view, allowing you to generate test cases without leaving Jira.

2. Configuring Test Case Generation

In the Reqase Lite panel, configure the following settings:

AI Integration Details

Preconfigured in Reqase Lite App Settings. This determines which AI provider and model will be used for test case generation.

Test Case Rules

Defined in Project Settings to ensure consistency across your team. These rules guide the AI in generating test cases that match your organization's standards.

Test Format

Choose between Manual, Cucumber, or Generic format (see detailed descriptions below).

Additional Context

Add case-specific details to help the AI understand unique requirements. This is recommended to capture edge cases or nuances specific to this issue.

Once configured, click Generate AI Test Cases to create draft scenarios.

3. Test Formats

Reqase Lite supports three output formats for test cases, each designed for different testing workflows:

A. Manual Test Format

Structure: Action โ†’ Data โ†’ Expected Result

Each step is broken into three parts for clarity and precision

Includes a rich text editor for formatting (bold, lists, links)

Formatting is preserved when imported into your test management tool

Best for:

Detailed validation testing, manual QA workflows, and scenarios requiring precise step-by-step instructions.

B. Cucumber (BDD) Format

Preformatted using Given / When / Then syntax

Suitable for teams practicing BDD or exporting to Cucumber-compatible tools

Each acceptance criterion maps to one scenario

Best for:

BDD workflows, automated testing frameworks, and teams using Gherkin syntax for test specifications.

C. Generic Test Format

Outputs all data and scenarios in a single block

Useful for flexible export/import into tools without strict step structure

Helpful for exploratory or lightweight testing

Best for:

Exploratory testing, flexible documentation, and teams that need adaptable test case formats.

4. Reviewing & Editing Test Cases

โš ๏ธ Important

AI-generated test cases should always be validated by a human. While AI can accelerate test case creation, human review ensures accuracy, completeness, and alignment with business requirements.

In the Reqase Lite panel, you can:

โœ๏ธ

Edit Steps

Refine text for clarity and correctness, ensuring each step is precise and actionable.

โž•

Add Steps

Include missing actions or validations that the AI may have overlooked.

๐Ÿ—‘

Delete Steps

Remove irrelevant or duplicate content to keep test cases focused and efficient.

๐Ÿ“

Add New Scenarios

Create additional test cases manually alongside AI-generated ones for comprehensive coverage.

5. Best Practices

โœ“

Always review and adjust generated cases before importing them into your test management system.

โœ“

Choose the right format: Use Manual format for detailed validation, Cucumber for BDD workflows, and Generic for exploratory/flexible needs.

โœ“

Maintain consistency: Keep project-wide consistency in Test Case Rules, while adding issue-specific context where needed.

โœ“

Validate expected results: Ensure Expected Results are observable and measurable. Avoid vague terms like "works correctly" or "functions properly."

โœ“

Provide context: The more context you provide in the "Additional Context" field, the more accurate and relevant the AI-generated test cases will be.