capybara-webkit depends on a WebKit implementation from Qt, a cross-platform development toolkit. You'll need to download the Qt libraries to build and install the gem. You can find instructions for downloading and installing QT on the capybara-webkit wiki
Without access to your application code we can't easily debug most crashes or generic failures, so we've included a debug version of the driver that prints a log of what happened during each test. Before filing a crash bug, please see Reporting Crashes. You're much more likely to get a fix if you follow those instructions.
If you are having compiling issues please post to the mailing list.
If you're like us, you'll be using capybara-webkit on CI.
On Linux platforms, capybara-webkit requires an X server to run, although it doesn't create any visible windows. Xvfb works fine for this. You can setup Xvfb yourself and set a DISPLAY variable, or try out the headless gem.
Add the capybara-webkit gem to your Gemfile:
In RSpec, use the :js => true flag.
Take note of the transactional fixtures section of the capybara README.
Setting Webkit options
The capybara-webkit driver allows access to some of the underlying QtWebKit's configuration options. You can use
# to set a flag: driver.browser.set_attribute(:flag_name, true) # to unset a flag explicitly: driver.browser.set_attribute(:flag_name, false) # to reset a flag to default: driver.browser.reset_attribute(:flag_name)
Supported are the flag names listed below:
Please consult the Qt documentation for more information about those options. If you need more flags to be supported, please contact us.
See the CONTRIBUTING document.
Code for rendering the current webpage to a PNG is borrowed from Phantom.js' implementation.
The names and logos for thoughtbot are trademarks of thoughtbot, inc.
capybara-webkit is Copyright (c) 2011 thoughtbot, inc. It is free software, and may be redistributed under the terms specified in the LICENSE file.