Calabash
Cross-platform mobile BDD framework using Cucumber for iOS and Android.
Pricing
Free / Open source
Type
Automation
Languages
Ruby
// VERDICT
Calabash brought Cucumber/Gherkin BDD to mobile testing, but active development stopped after Microsoft/Xamarin ceased contributing (around 2017) and it now lacks a maintainer. For new work, choose a maintained tool - Appium for cross-platform, Detox for React Native; treat this entry as historical reference.
Best for
Historically, Cucumber-based BDD mobile testing in Ruby for iOS and Android - written in plain Gherkin. It is now effectively unmaintained, so this entry is mostly for reference.
Avoid when
You're choosing a tool today - Calabash is no longer actively maintained; use Appium or Detox for new mobile automation.
CI/CD fit
Largely unmaintained - prefer Appium/Detox for new work
Languages
Ruby
Team fit
Teams maintaining legacy Calabash suites · Historical reference
Setup
Maintenance
Learning
Licence
// BEST FOR
- Historically: Cucumber/Gherkin BDD test authoring for mobile
- Plain-language scenarios for iOS and Android in Ruby
- Reference for teams maintaining a legacy Calabash suite
- Understanding an early BDD-for-mobile approach
- Planning a migration off Calabash to a maintained tool
- Context for why Appium/Detox became the standards
// AVOID WHEN
- You're choosing a tool today - it's unmaintained
- You want active development, support and current OS coverage
- You need a tool that keeps pace with new iOS/Android versions
- Your team isn't already invested in a legacy Calabash setup
- You want the largest mobile-automation ecosystem (Appium)
- You're testing React Native (Detox fits better)
// QUICK START
Calabash is effectively unmaintained - there is no recommended fresh setup.
For new mobile automation, start with Appium (cross-platform) or Detox
(React Native); migrate legacy Calabash/Gherkin suites toward them.// ALTERNATIVES TO CONSIDER
// FEATURES
- Cucumber Gherkin syntax for test scenarios
- Cross-platform iOS and Android with shared steps
- Ruby-based step definitions
- Page Object pattern support
// PROS
- Readable BDD-style scenarios
- Cross-platform sharing of step libraries
- Historically strong tooling
// CONS
- No longer actively maintained
- Most teams have migrated to Appium or Maestro
- Ruby ecosystem dependency
- Limited support for modern iOS and Android versions
// EXAMPLE QA WORKFLOW
Recognise Calabash is unmaintained, not a choice for new work
For legacy suites, freeze scope and plan a migration
Choose a maintained target (Appium cross-platform, Detox for RN)
Port Gherkin scenarios to the new tool's model
Rebuild CI on the maintained framework
Decommission the Calabash setup once migrated