12 engineers on Hacker News describe using Capybara first-hand: 4 endorse it, 1 regret it, 1 are mixed.
“I really miss the Capybara/Rails integration of just spinning up a proper test DB”
endorse · production · hugocbp · 2020-12-11 · source ↗ · wrong label?“I've also made myself a chrome devtool to record my interactions with browser and generate capybara tests out of it, so it's quite fast”
endorse · production · oelmekki · 2017-10-31 · source ↗ · wrong label?“No more wrestling with capybara. Not having to constantly switch between the browser, test runner, IDE.”
regret · production · gingerlime · 2017-04-18 · source ↗ · wrong label?“Ruby's Capybara encapsulates Selenium and waits until elements appear on the page... I've been using it for many years”
endorse · personal · pmontra · 2015-07-22 · source ↗ · wrong label?“using RSpec and Capybara to do test-driven development... It's been an absolute joy to work this way.”
endorse · production · tspike · 2012-12-08 · source ↗ · wrong label?“Sadly, full-stack testing in Ruby still kind of sucks... I've had mixed results with env.js. While not as sexy, I've been using Capybara with the Selenium driver with more success lately.”
mixed · production · sleight42 · 2010-12-25 · source ↗ · wrong label?“our tests typically run in less than 30 seconds which include thorough Capybara (UI Interaction) testing”
neutral · production · hmeh · 2023-12-29 · source ↗ · wrong label?“We switched from cypress to capybara+selenium.”
neutral · production · jemmyw · 2023-10-11 · source ↗ · wrong label?“we run all our tests in CI with Capybara. Our CD pipeline runs the same tests but against Chrome, Firefox, Safari and Edge.”
neutral · production · petepete · 2019-12-02 · source ↗ · wrong label?“The projects made use of Rspec, Test::Unit, and Capybara.”
neutral · production · slimed · 2017-11-28 · source ↗ · wrong label?“Otherwise, we've just been using Test::Unit or straight RSpec with webrat/capybara.”
neutral · production · jeremymcanally · 2010-11-23 · source ↗ · wrong label?“Most of my code coverage is more like automated QA tests through Cucumber / Capybara / Selenium in Ruby.”
neutral · production · joshcrews · 2010-10-29 · source ↗ · wrong label?