Softwr

Testing · head to head

Split vs Xray Test Management

Split logo

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Rated
-
Full reviewWebsite
Xray Test Management logo

Xray Test Management

Testing

Native test management for Jira, licensed per Jira user rather than per tester

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Split split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract.; Xray Test Management pricing follows total Jira user count, not Xray user count, so a large company with a small QA team pays for hundreds of seats it does not use for testing.
  • They diverge on capability: Split covers Feature flags with targeting, Xray Test Management covers Native Jira issue types.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Split and Xray Test Management actually diverge.

Attributes where Split and Xray Test Management differ
AttributeSplitXray Test Management
Pricing modelquotePer Jira user per month, tiered to total instance size
PlatformsWeb, API, iOS, Android, Java, Node.js, Python, Go, .NETWeb

Identical on both: starting price (On request), free tier (No), user rating (Not yet rated), category (Testing).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Split

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

Only in Xray Test Management

  • Native Jira issue types
  • Requirement traceability
  • BDD support
  • CI integration
  • Test repository and reuse
  • Data Center edition

What people use each for

The jobs each tool is most often brought in to do.

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Xray Test Management
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Xray Test Management
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Xray Test Management
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Xray Test Management

Xray Test Management

  • A QA team already standardised on Jira that wants traceability from requirement to test to defect without a second toolnot Split
  • An organisation running Jira Data Center for compliance reasons that needs test management to matchnot Split
  • A team doing BDD that wants Gherkin scenarios linked to Jira issues rather than kept in a separate repositorynot Split
  • A company importing automated CI results into the same tracker developers already use for triagenot Split

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract.
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle.
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from.
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch.
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product.

Xray Test Management

  • Pricing follows total Jira user count, not Xray user count, so a large company with a small QA team pays for hundreds of seats it does not use for testing.
  • Since October 2025 billing is based on peak users within the period, so a temporary contractor surge or acquisition-driven headcount bump can push the account into a costlier tier retroactively.
  • It only exists as a Jira add-on, so a team that is not already on Jira gains nothing by evaluating it; there is no standalone product.
  • Cloud and Data Center are separately licensed and diverge in feature timing, so a company migrating from self-hosted Jira to Cloud has to re-evaluate the Xray purchase, not just move data.
  • Heavy customisation of test workflows inside Jira increases the risk that a Jira version upgrade or a Xray version upgrade breaks configured automation rules.

Pricing, plan by plan

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness Essentials$undefined/year
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness Enterprise$undefined/year
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Xray Test Management

On request
  • Xray Cloud Standard$10/month
    • Up to 10 Jira users
    • Manual and automated test management
    • Requirement traceability
  • Xray Cloud$undefined/month
    • Priced per Jira user, tier follows total instance headcount
    • Billed on peak user count within the billing period since October 2025
    • Rate per user declines at higher tiers but total spend still rises with headcount
  • Xray Data Center$undefined/year
    • Licensed against Jira Data Center tier
    • Separate purchase and upgrade cycle from Cloud

Which should you pick?

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Java, Node.js, Python, Go, .NET.
  • You also want metrics impact engine.
Split review

Choose Xray Test Management if

  • You need native jira issue types.
  • You also want requirement traceability.
Xray Test Management review

Questions people ask

Is Split or Xray Test Management better?
Neither clearly leads. Split starts at On request and Xray Test Management at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Split or Xray Test Management?
Split starts at On request and Xray Test Management at On request.
Does Split or Xray Test Management run on more platforms?
Split runs on Web, API, iOS, Android, Java, Node.js, Python, Go, .NET. Xray Test Management runs on Web.
What is Split best used for?
Split is most often used for a product organisation that wants every release measured against conversion and latency by default, not only deliberate experiments, running a/b tests with real statistical significance rather than comparing two dashboard lines, catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyone, a team already committed to harness for ci and cd that wants flags in the same platform and contract. Of those, a product organisation that wants every release measured against conversion and latency by default, not only deliberate experiments and running a/b tests with real statistical significance rather than comparing two dashboard lines are not what Xray Test Management is typically brought in for.
What can Split do that Xray Test Management cannot?
Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing. Xray Test Management covers Native Jira issue types, Requirement traceability, BDD support, CI integration.

Answered from the vendors’ own pages

Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

Xray Test Management: Is Xray priced per tester?

No. It is priced per user on the Jira instance it is installed into, regardless of how many of those users actually work in Xray.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

Xray Test Management: Who owns Xray?

Xblend, the company that grew out of the original XpandIT project, which Idera, Inc. acquired in 2021 along with the Xporter reporting tool.

Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

Xray Test Management: Is there a free tier?

No published free tier exists for either Cloud or Data Center editions.

Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

Share

Related pages

More on Split

More on Xray Test Management

Keep looking

Other head to heads