Capybara vs Selenium

What Capybara is

Capybara is an MIT-licensed Ruby library and acceptance-testing DSL that simulates user interaction with web applications. It supplies finders, matchers, actions, sessions and automatic waiting while delegating actual execution to drivers such as the fast RackTest default or browser-capable Selenium. It is not itself a browser, test runner or assertion framework, and test fidelity, JavaScript support, isolation and concurrency behavior depend on the chosen driver and surrounding stack.

What Selenium is

Selenium is an Apache-2.0-licensed open-source browser-automation project comprising WebDriver language bindings, Selenium IDE and Selenium Grid. It controls supported browsers locally or remotely, but it does not itself provide hosted browsers, application-specific test cases, assertions or a complete test runner; teams assemble and operate those surrounding parts.

What Capybara is built to do

Navigation and actions

Visits pages, fills fields, clicks controls, attaches files and manipulates supported browser state.

Finders and matchers

Queries accessible labels, text, CSS and XPath with configurable matching behavior.

Automatic waiting

Retries eligible queries and expectations while asynchronous content settles.

Interchangeable drivers

Routes the DSL through RackTest, Selenium or compatible external drivers with different capabilities.

What Selenium is built to do

WebDriver

Controls supported browsers through native browser automation interfaces and language bindings.

Selenium Grid

Routes sessions to remote browser instances for parallel and cross-platform execution.

Selenium IDE

Records and replays browser actions through supported browser extensions.

WebDriver BiDi

Adds bidirectional browser events such as network, console and JavaScript error streams.

Choose Capybara if

• Ruby application journeys expressed through user-visible behavior
• Test suites that mix fast non-JavaScript coverage with selected real-browser scenarios
• Teams prepared to manage browser drivers, test data and asynchronous behavior

Skip Capybara if

• The test stack is not Ruby-based and gains no value from a Ruby DSL
• You expect the default RackTest driver to execute JavaScript or test a remote URL
• The suite lacks a strategy for database isolation, browser dependencies and flaky-state diagnosis

Choose Selenium if

• Cross-browser web tests that need supported language bindings and direct browser control
• Teams building their own local or distributed browser-testing infrastructure
• Projects willing to combine Selenium with an assertion library and test runner

Skip Selenium if

• You expect a hosted browser and device cloud to be included
• The team cannot maintain browser drivers, Grid capacity, selectors and synchronization logic
• The primary requirement is native mobile-app automation rather than browser or mobile-web automation

Capybara: pros & cons

• User-oriented DSL: Tests express visits, form actions, element queries and expectations close to browser behavior.
• Automatic synchronization: Finders and matchers wait up to configured limits for asynchronous page state.
• Driver portability: The same high-level API can run against RackTest, Selenium and compatible third-party drivers.
• Framework integration: Official guidance covers use with RSpec, Minitest and other Ruby test setups.
• Default driver has no JavaScript: RackTest is fast but cannot validate client-side behavior or interact with remote applications.
• Browser tests cost more: Selenium-style drivers add browser binaries, timing variability and infrastructure overhead.
• Thread and data isolation: Transactional database strategies may not share state with a separately threaded application server.
• Ambiguous selectors can fail: Capybara intentionally raises on multiple matches unless the query is made specific.

Selenium: pros & cons

• Standards-based control: WebDriver is a W3C Recommendation implemented with browser-specific drivers.
• Language options: Official downloads list bindings for Java, Python, C#, Ruby, JavaScript and Kotlin.
• Distributed execution: Grid routes WebDriver commands to remote browser instances and supports parallel, cross-platform testing.
• Record and playback: Selenium IDE records browser actions through Chrome, Firefox and Edge extensions.
• Infrastructure not included: Local browsers, remote Grid machines or a separate hosted provider must supply execution capacity.
• Test framework required: Selenium documentation states that assertions and broader test structure come from assertion libraries and test runners.
• Environment maintenance: Browser, driver, language binding and Grid compatibility must be managed across updates.
• UI-change sensitivity: Application locators, timing and workflows still require deliberate test design and maintenance.