Question 1

How to handle AJAX and asynchronous JavaScript in Capybara?

Accepted Answer

Capybara automatically waits for elements to appear using its synchronization features. Adjust the wait time with Capybara.default_max_wait_time and use matchers like have_content for reliable testing without manual delays.

Question 2

Capybara vs Selenium: which one should I use?

Accepted Answer

Capybara is a testing framework that can use Selenium as a driver. Use Capybara for its high-level API and integration with Ruby test suites, while Selenium alone is better for raw browser automation outside Ruby.

Question 3

How to set up Capybara with Rails for system tests?

Accepted Answer

Require capybara/rails in your test helper, place tests in spec/system or tag with type: :system, and configure the driver. For JavaScript tests, use Capybara.javascript_driver like :selenium_chrome_headless.

Question 4

Why do my Capybara tests fail with database data not persisting?

Accepted Answer

This is due to transaction isolation with drivers like Selenium. To fix it, use tools like database_cleaner to truncate or reset the database between tests, as mentioned in the Transactions section.

Question 5

How to run Capybara tests in headless Chrome?

Accepted Answer

Use the :selenium_chrome_headless driver by setting Capybara.javascript_driver or Capybara.current_driver. Ensure chromedriver is installed and configure options in the register_driver block if needed.

Question 6

Can Capybara test file uploads and modal dialogs?

Accepted Answer

Yes, use attach_file for uploads and methods like accept_confirm or accept_prompt for modals. These are supported in drivers like Selenium, but implementation may vary based on the driver capabilities.

Capybara

What is Capybara?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions