It's been obsolete for a while now. If you still need it, you can copy the driver / registration into your app's test code.
Thanks juno. #64 This will likely break rack-test 1.x as it uses new methods/API to get the cookie store. To restore that, override the changed code in your test setup, or register a custom rack-test1 driver based on the old code.
chromedriver-helper -> webdrivers. Bundler -> 2.0.2. Should not affect your app.
Due to obsolescence and maintenance difficulty. Setting up capybara-webkit and qt has never been fun, but now it's getting silly: According to the capybara-webkit wiki Qt has removed the necessary webkit bindings, and homebrew has removed the old version of qt that still had them.
New / current projects should switch to headless Chrome or Firefox with webdriver, which will work with the existing adapters, but if you need the webkit driver for legacy apps stick with version 4, or copy the adapter from version 4 into your app's test support code.
Drivers are now registered matching the names used by capybara:
:selenium => Selenium driving Firefox :selenium_headless => Selenium driving Firefox in a headless configuration :selenium_chrome => Selenium driving Chrome :selenium_chrome_headless => Selenium driving Chrome in a headless configuration
Changes some cookie escaping logic & supports capybara 3.
For more information see the release commit: cc0a1106d9cb00827aeda3301f5b75d6d10e80ba