Softwr

Testing · head to head

Cucumber vs Split

Cucumber logo

Cucumber

Testing

Behaviour-driven development testing framework that returned to community ownership after nine years under SmartBear

From
Free
Rated
-
Full reviewWebsite
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

The short version

  • Only Cucumber has a free tier, so it costs nothing to try first.
  • Each has a real cost: Cucumber gherkin's plain-language layer adds a real maintenance burden, keeping feature files, step definitions and implementation code synchronised across a large suite is a known source of drift and duplicated effort.; 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.
  • They diverge on capability: Cucumber covers Gherkin syntax, Split covers Feature flags with targeting.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Cucumber and Split actually diverge.

Attributes where Cucumber and Split differ
AttributeCucumberSplit
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, WindowsWeb, API, iOS, Android, Java, Node.js, Python, Go, .NET

Identical on both: 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 Cucumber

  • Gherkin syntax
  • Step definition binding
  • Multi-language support
  • Living documentation
  • Tagging and scenario outlines
  • Reporting plugins

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

What people use each for

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

Cucumber

  • A team practising behaviour-driven development that wants shared, readable specifications between product owners and engineersnot Split
  • An organisation wanting living documentation that stays synchronised with actual test coverage rather than a separate specification documentnot Split
  • A QA team migrating acceptance tests from a proprietary BDD tool to an open source, community-governed alternativenot Split
  • A Java, JavaScript or Ruby project needing a mature BDD framework rather than building Gherkin-style parsing from scratchnot Split

Split

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

Where each one falls short

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

Cucumber

  • Gherkin's plain-language layer adds a real maintenance burden, keeping feature files, step definitions and implementation code synchronised across a large suite is a known source of drift and duplicated effort.
  • Ownership has moved twice in under a decade, from independent to SmartBear-owned to independent community ownership again, which should temper confidence in any specific long-range roadmap claim.
  • Non-technical stakeholders who are meant to read and write Gherkin scenarios often do not engage with them in practice, leaving the readability benefit unrealised while the maintenance cost remains.
  • Step definition reuse across a large feature file set can become tangled, with ambiguous step matching causing hard-to-debug failures as a suite grows.
  • As a community-owned project without a corporate backer's support infrastructure, enterprise buyers wanting a formal support contract have no vendor to buy one from, unlike some competing BDD tools still sold commercially.

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.

Pricing, plan by plan

Cucumber

Free
  • CucumberFree
    • Full functionality across Cucumber-JVM, Cucumber-JS, Cucumber-Ruby and other implementations
    • Community support via GitHub
    • Returned to independent community ownership in December 2024 after nine years connected to SmartBear

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

Which should you pick?

Choose Cucumber if

  • You need gherkin syntax.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want step definition binding.
Cucumber review

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

Questions people ask

Is Cucumber or Split better?
Neither clearly leads. Cucumber starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cucumber or Split?
Cucumber has a free tier; the other does not. Paid plans start at Free for Cucumber and On request for Split.
Does Cucumber or Split run on more platforms?
Cucumber runs on Linux, macOS, Windows. Split runs on Web, API, iOS, Android, Java, Node.js, Python, Go, .NET.
Can I use Cucumber for free?
Yes. Cucumber has a free tier, so you can try it without paying. Split starts at On request.
What is Cucumber best used for?
Cucumber is most often used for a team practising behaviour-driven development that wants shared, readable specifications between product owners and engineers, an organisation wanting living documentation that stays synchronised with actual test coverage rather than a separate specification document, a qa team migrating acceptance tests from a proprietary bdd tool to an open source, community-governed alternative, a java, javascript or ruby project needing a mature bdd framework rather than building gherkin-style parsing from scratch. Of those, a team practising behaviour-driven development that wants shared, readable specifications between product owners and engineers and an organisation wanting living documentation that stays synchronised with actual test coverage rather than a separate specification document are not what Split is typically brought in for.
What can Cucumber do that Split cannot?
Cucumber covers Gherkin syntax, Step definition binding, Multi-language support, Living documentation. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Cucumber: Is Cucumber owned by SmartBear?

No, not currently. SmartBear acquired Cucumber Ltd in 2019 but the open source project returned to independent community ownership in December 2024.

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.

Cucumber: Is Cucumber free?

Yes, entirely open source with no licence fee across all its language implementations.

Split: Can I buy just feature flags?

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

Cucumber: Does Cucumber replace Selenium or Appium?

No, Cucumber provides the Gherkin specification layer and step definition binding; the actual browser or mobile automation still needs a driver such as Selenium or Appium underneath.

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.

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 Cucumber

More on Split

Keep looking

Other head to heads