Capybara vs Selenium: What are the differences?
Developers describe Capybara as "Acceptance test framework for web applications". Capybara helps you test web applications by simulating how a real user would interact with your app. It is agnostic about the driver running your tests and comes with Rack::Test and Selenium support built in. WebKit is supported through an external gem. On the other hand, Selenium is detailed as "Web Browser Automation". Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
Capybara can be classified as a tool in the "Testing Frameworks" category, while Selenium is grouped under "Browser Testing".
"Best acceptance test framework for Ruby on Rails apps" is the top reason why over 7 developers like Capybara, while over 149 developers mention "Automates browsers" as the leading cause for choosing Selenium.
Capybara and Selenium are both open source tools. It seems that Selenium with 14.7K GitHub stars and 4.92K forks on GitHub has more adoption than Capybara with 8.82K GitHub stars and 1.29K GitHub forks.
MIT, PedidosYa, and HubSpot are some of the popular companies that use Selenium, whereas Capybara is used by GrowthHackers, sQuidd.io, and Indiegogo. Selenium has a broader approval, being mentioned in 770 company stacks & 425 developers stacks; compared to Capybara, which is listed in 38 company stacks and 20 developer stacks.
What is Capybara?
What is Selenium?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Selenium?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.
I chose WebdriverIO and Appium to implement a E2E tests solution on a native mobile app. WebdriverIO goes well beyond just implementing the Selenium / Appium protocol and allows to run tests in parallel out of the box. Appium has the big advantage of supporting iOS and Android platforms, so the test codebase and tools are exactly the same, which greatly reduces the learning curve and implementation time.
가장 강력한 웹 UI / UX 테스트 툴 이지만, 문제도 많다. iframe 안에 있는 건 잘 select 가 안되기도 하고, 화면이 작아 컴포넌트가 화면에 보이지 않으면 또 select 할 수 없다. 하지만 브라우저를 있는 그대로 제어 할 수 있다는 게 가장 큰 매력이다.
ps. selenide 와 같이 쓰면 코드가 많이 개선된다.
Maintaining and expanding automated regression tests is one of my primary responsibilities at CrowdTwist. We use Selenium to test the front-end parts of our platform.
Used Selenium web-driver for automated QA testing in continuous integration and continuous deployment.
- Navigating our site for tests
- Navigating other sites that discriminate against non-human visitors