Xray review

Xray is a test management tool that runs inside Jira. Teams can create, execute, and report on manual and automated tests in a Jira-based workflow, rather than managing test cases separately from their project work. That makes it most relevant to teams already using Jira for QA, not organizations looking for a standalone test management system.

Its AI features cover several parts of test creation and planning. Xray can generate manual and BDD test cases, help identify coverage gaps, and expand test coverage. Visual test models are available with Enterprise; generating automation scripts from manual tests requires Advanced or Enterprise. The product combines test creation, execution, and reporting, but the AI capabilities are not identical across plans.

Xray offers a 30-day free trial, but no free plan is listed. Pricing is based on Jira user tiers, and the Jira user tier must match the Xray instance.

Xray’s clearest advantage is keeping test work within Jira. Teams can manage manual and automated test cases, execute them, and report on results in one workflow. If Jira is already central to your QA process, that can be a better fit than introducing a separate test management product and maintaining another place for test data.

The feature set also extends beyond a basic test repository. AI can generate manual and BDD test cases, while coverage gap detection is intended to help teams spot areas that need more testing. On higher plans, Xray adds visual test models and automation script generation from manual tests.

The listed Standard plan includes 60 API requests per minute, 100 GB of cloud storage, and 75 AI-prioritized tests per run. Advanced raises those figures to 100 API requests per minute, 250 GB, and 150 AI-prioritized tests per run. Enterprise is the plan that lists visual test models, but its API limit is 20 requests per minute. Those published caps give teams something concrete to compare against their workload before switching.

The main drawback is cost, especially if you are trying to leave a paid Jira-and-Xray setup for a free tool. The pricing page lists Standard at $10 per month, or $8.33 per month with annual billing, for up to 10 users. Advanced is $15 per month for up to 10 users; an annual price is not published. Enterprise is $27.50 monthly or $22.92 monthly with annual billing for up to 10 users. There is no free plan, though a 30-day trial is listed.

Costs above 10 users are less straightforward. Standard and Enterprise have published progressive rates for larger tiers, but Advanced higher-seat and annual prices require the Marketplace calculator. Add-on and overage costs are not published. All plans require the Jira user tier to match the instance. A Reddit thread about replacing Xray and Jira described cost as the reason the company stopped using them, a reminder that the combined bill matters.

Limits also vary in ways worth checking: Enterprise lists only 20 API requests per minute, below Standard’s 60 and Advanced’s 100. Don’t assume the top plan means the highest cap.

The pricing page lists Xray Standard at $10 per month for up to 10 users, or $8.33 per month with annual billing. Advanced is $15 per month for up to 10 users; an annual price is not published. Enterprise costs $27.50 monthly or $22.92 monthly with annual billing for up to 10 users. That puts Advanced $5 above Standard and Enterprise another $12.50 above Advanced at monthly rates.

The plan jumps do not guarantee steadily higher limits: Enterprise lists 20 API requests per minute, versus 100 for Advanced. Standard includes 60. The Jira user tier must match your instance, and prices for larger teams can require the Marketplace calculator. Standard’s listed user rates start at $7.28 per user monthly for users 1–100, then fall at higher tiers; Enterprise starts at $13.20. Advanced’s larger-seat and annual prices, plus add-on and overage costs, are not published. There is no free plan; Xray lists a 30-day trial.

Xray is built inside Jira, so it makes the most sense when Jira is already central to QA. That can reduce workflow changes for a Jira team, but it also ties the test-management setup to Jira: the pricing information says your Jira user tier must match the Xray instance. Teams trying to move away from Jira should account for replacing that workflow, not just replacing a test-case tool.

The published material does not document migration steps, data-export formats, or export limits, so we can’t say how much work a move in or out requires. Confirm those details with Xray before switching, especially if you need to retain test cases, execution history, or reporting. We also don’t have Reddit posts or comments in the published sources, so we can’t substantiate a claim about what users there say makes them leave. The clearest documented reasons to compare alternatives are Jira dependence and pricing that gets harder to predict as the team grows.