The document provides a guide on setting up and using Capybara with RSpec for testing web applications. It details installation steps, configuration settings, and describes various drivers like RackTest, Selenium, and Capybara-Webkit. Additionally, it includes actions, matchers, and debugging information for effective testing practices.

1. Capybara
by:- Omnia Gamal El-Deen
email :- omnia.gamal1988@gmail.com
twitter @Omnia_G

2. Capybara
Go away
I'm busy
NOW

4. Why Capybara

5. Setup
Install :
sudo gem install capybara
Or Gemfile
gem "capybara", :group => :test

6. Using Capybara with RSpec
● spec/spec_helper.rb
require 'capybara/rails'
require 'capybara/rspec'
● create test directory /spec/requests
● add capybara dsl to RSpec.configure in
spec_helper.rb
RSpec.configure do |config|
config.include Capybara::DSL, :type => :request

7. Test
test_file.rb
require 'spec_helper'
describe "home page" do
before :each do
# ......
end
it "displays greeting" do
# .........
end
end

8. The DSL
● navigating (visit)
● matcher (page.should)
● clicks (click_link - click_button)
● action (fill_in)
● finders (find)
● scope (within)
● Scripting (page.execute_script)
● debugger (page.htm - save_and_open_page)
○ NOTE : You'll need to install launchy (gem 'launchy', :
group => :test)and make sure it's available to open
pages with save_and_open_page

9. Example

10. Drivers
● Driver agnostic
● Support :
○ RackTest
○ Selenium
○ Capybara-webkit
● Default:
rack_test driver

11. RackTest
● It's pure Ruby, So it interacts directly with Rack
interfaces
● It does not require a server to be started
But
● Not used to test a remote application, or to access
remote URLs (e.g., redirects to external sites, external
APIs, or OAuth services)
● Dumb
● It's not have any support for executing JavaScript

12. Selenium
● Runs tests in a real browser
● Supports any Javascript your browser supports, just like
real users
● Easy to set up with capybara
But
● Slow
● GUI browser adds a lot of cruft you don’t want
● Unfriendly
○ No console.log output
○ invisible javascript errors

13. CAPYBARA-WEBKIT
● Fast
● No browser UI
● Using webkit engine
● console.log output
● Errors in standard output

14. Setup capybara-webkit:
Gemfile
gem "capybara-webkit", :group => :test
○ You didn't need capybara itself anymore
○ You will need database_cleaner because database transactions aren’
t compatible with rspec drivers besides Rack::Test
gem 'database_cleaner', :group => :test

15. Spec_helper.rb
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'capybara/rspec'
require 'capybara-webkit'
Capybara.javascript_driver = :webkit
#...

16. DatabaseCleaner configuration
RSpec.configure do |config|
#...
config.use_transactional_fixtures = false
config.before(:suite) do
DatabaseCleaner.strategy = :truncation
end
config.before(:each) do
DatabaseCleaner.start
end
config.after(:each) do
DatabaseCleaner.clean
end
end

17. Reference :
● Example@github OmniaGM/learn-capybara
● Browser testing
● Capybara
● Capybara Cheat Sheet