All that without needing to handle pesky Qt version dependencies. The tests fail intermittently, forcing retries on the CI, and the browser it relies on (QtWebkit) has been deprecated.Īll things considered, with Chrome you've got a modern browser, a driver for it, and a field-tested tool to automate your tests (Selenium). Now, before all this was an option, capybara-webkit, the driver for the QtWebkit browser, was a great match for the job. It provides a standard interface to control Chrome, so it'll play nice with most tools and languages that want to use it.
They also partnered up with Selenium, a browser automation tool to release ChromeDriver. Since 2017, Google Chrome has been shipping with a headless environment, allowing us to emulate user interactions without the overhead of having a GUI. But first, let me provide some context about why it's important to make the change, and why Chrome is the perfect candidate for it. Well, you're in the right place as here I'll show exactly how you can achieve that. So, you have a Ruby on Rails project you've been testing with Capybara and capybara-webkit and you need to upgrade to Headless Chrome.
