Skip to content
QA Workflow Assistant

Blog

AI Test Case Generator for Xray

Generate structured test cases with AI, review the coverage, and move approved tests into your Jira/Xray workflow as Test issues with steps, Test Sets, and Test Executions.

QA Workflow Assistant7 min read
  • xray
  • ai
  • test-cases
  • jira

Generate structured test cases from a user story or requirement, review the coverage, then move the approved tests into your Jira/Xray workflow. QA Workflow Assistant drafts the cases with AI; you decide what reaches Xray.

Try it with your own user story — see what a structured AI draft looks like before connecting anything. No signup required.

→ Try the free AI test case generator

From user story to Xray Test

The workflow has one AI step and one human gate before anything is created in Xray:

  1. User story or requirement — the behavior you need to test
  2. AI test generation in QA Workflow Assistant — structured cases with title, precondition, steps, expected result, and priority
  3. QA review — edit, remove, and select the cases worth keeping
  4. Jira Test issues with Xray steps — one issue per selected case
  5. Test Set (optional) — a new set containing the pushed Tests
  6. Test Execution (optional) — a new execution containing the pushed Tests, ready for a run

The review step is the point. AI speeds up the first draft; it does not know your release risk, your environments, or which cases already exist in your repository. A QA professional checks the draft before it becomes part of the test library, so Xray receives reviewed Tests instead of a bulk dump that needs cleanup later.

The generator is the same one described in the AI test case generator for Jira. This page focuses on what happens when the destination is Xray.

Example: password reset story to Xray

The following is an illustrative example, not a live generator response.

User story: As a customer, I want to reset my password so I can regain access to my account.

A Pro generation, which includes negative and edge coverage, might draft cases like these:

Test caseTypePriority
Request a reset link with a registered emailPositiveHigh
Request a reset with an unregistered emailNegativeMedium
Use an expired reset linkEdgeHigh

After review, you keep the first case and tighten its steps:

  • Precondition: An active account exists; email delivery works in the test environment
  • Steps: 1. Open the password reset page 2. Enter the registered email 3. Submit the request
  • Expected result: A confirmation appears without revealing account details; a reset email is sent to that address

When you push the selected case with Xray connected:

  • It becomes a Jira Test issue in your project
  • Its steps are added as Xray test steps, with the expected result recorded on each step
  • If you choose, the push also creates a Test Set and a Test Execution containing the Tests from that push

What QA Workflow Assistant sends to Xray

With a Pro account, a connected Jira Cloud site, and Xray Cloud API credentials:

  • Test issues — one Jira issue per selected case, using your project’s Test issue type
  • Xray test steps — the case’s steps added to each Test issue
  • Test Sets — optionally, a new Test Set issue with the pushed Tests added to it
  • Test Executions — optionally, a new Test Execution issue with the pushed Tests added to it

A few details worth knowing:

  • Only the cases you select are pushed. Cases you already pushed are skipped rather than duplicated.
  • Xray steps are added only when the issue type is a Test-type issue and Xray credentials are saved. If your project has no Test issue type, the push falls back to another issue type and shows a warning.
  • Test Sets and Test Executions require those issue types to exist in the Jira project.

What it does not do:

  • It does not create Xray Test Plans. Plans stay in Xray, managed by you. See Xray Test Plan vs Test Execution.
  • It does not add Tests to an existing Test Set or Test Execution; it creates new ones for the pushed Tests.
  • It does not link Tests to your requirement issues. Add traceability links in Jira/Xray as usual.
  • It does not generate automated or Cucumber test scripts. The Gherkin option only changes how the Jira issue description is formatted.
  • It does not record execution results. Running Tests and setting statuses happens in Xray.

QA Workflow Assistant and Xray, not versus

Xray remains your test management system: the test repository, Test Plans, executions, results, and reporting all live there.

QA Workflow Assistant works before and during delivery:

  • Before: turning a story or requirement into a structured draft
  • Review: giving QA a place to edit and select cases
  • Delivery: creating the reviewed Tests, and optionally a Test Set and Test Execution, in your Jira/Xray project

It is an addition to an Xray workflow, not a substitute for it.

Free preview vs Xray delivery

The free AI test case generator shows the drafting step: paste a story, get 1–2 structured cases, no signup. It does not connect to Jira or Xray.

Delivery into Xray is a Pro workflow. You sign in, connect Jira Cloud and add your Xray Cloud API credentials in the integration settings, generate and review the coverage, then push the cases you select. Plans and prices are on Pricing.

Who this is for

  • QA engineers already working in Jira and Xray who write Tests from stories every sprint
  • Testers manually turning stories into Xray Tests and retyping steps into the Test issue
  • Small and lean QA teams where each tester covers many stories with their own account
  • Teams that want human review before generated coverage enters test management

For safe push habits, read pushing generated tests to Jira and Xray. For how sets and executions fit together in Xray itself, see Xray Test Sets and Xray test execution.

FAQ

Can AI generate test cases for Xray?

Yes. QA Workflow Assistant generates structured test cases from a user story or requirement. After you review them, Pro users with Xray connected can push them into Xray as Test issues with steps.

Does QA Workflow Assistant replace Xray?

No. Xray stays your test management system. QA Workflow Assistant helps you draft and review coverage and deliver it into supported Jira/Xray issue types.

Can it create Xray Test issues?

Yes. Each selected case becomes a Jira issue using the project’s Test issue type.

Can it add manual steps to Xray tests?

Yes. When Xray Cloud API credentials are saved and the issue type is a Test type, the generated steps are added as Xray test steps.

Does it create Xray Test Sets?

Yes, optionally. The push can create a new Test Set containing the Tests from that push. It does not add Tests to an existing Test Set.

Does it create Xray Test Executions?

Yes, optionally. The push can create a new Test Execution containing the Tests from that push. Execution results are recorded in Xray.

Does it create Xray Test Plans?

No. QA Workflow Assistant does not create Xray Test Plans. You manage Test Plans in Xray.

Can I review AI-generated test cases before sending them to Xray?

Yes. You edit and select cases in the workspace, and only the selected cases are pushed.

Can I try the test generator without connecting Xray?

Yes. The free AI test case generator needs no account and no Jira or Xray connection.

Do I need a Pro account to push tests into Xray?

Yes. Jira and Xray push require Pro, a connected Jira Cloud site, and Xray Cloud API credentials.

Try it with your own user story

Start with the drafting step: paste a story, see structured test cases, and judge the quality before you connect Xray. No signup required.

→ Try the free AI test case generator

Stay ahead in QA

Get practical QA guides, Jira & Xray tutorials, testing checklists, AI testing insights, and occasional product updates.

No spam. Unsubscribe anytime.