From d536eea864a6ed7e9e0032ec9d61edaadba6a375 Mon Sep 17 00:00:00 2001 From: Jonas Nicklas Date: Thu, 16 Sep 2010 21:55:57 +0200 Subject: [PATCH] added section on configuring drivers to readme --- README.rdoc | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.rdoc b/README.rdoc index fd633f61..8c744475 100644 --- a/README.rdoc +++ b/README.rdoc @@ -422,6 +422,27 @@ The same thing goes for within: end end +== Configuring and adding drivers + +Capybara makes it convenient to switch between different drivers. It also exposes +an API to tweak those drivers with whatever settings you want, or to add your own +drivers. This is how to switch the selenium driver to use chrome: + + Capybara.register_driver :selenium do |app| + Capybara::Driver::Selenium.new(app, :browser => :chrome) + end + +However, it's also possible to give this a different name, so tests can switch +between using different browsers effortlessly: + + Capybara.register_driver :selenium_chrome do |app| + Capybara::Driver::Selenium.new(app, :browser => :chrome) + end + +Whatever is returned from the block should conform to the API described by +Capybara::Driver::Base, it does not however have to inherit from this class. +Gems can use this API to add their own drivers to Capybara. + == Gotchas: * Access to session and request is not possible from the test, Access to