capybara-webkit | Capybara driver for headless WebKit

Change

command 'cd /home/sotldirectory && bin/rails r import/cron_import.rb'

to

command 'cd /home/sotldirectory && bundle exec rails r import/cron_import.rb'

Also, which rake version is listed in your Gemfile.lock?

Small thing first - there is no need to load capybara-webkit if you're using the Selenium driver.

Now onto the main issue. There is no need to call methods directly on driver when executing JS, rather you should just be calling the Capybara methods execute_script, evaluate_script, or evaluate_async_script. The evaluate_xxx methods are for when you expect a return value, the execute_script method is for when you don't care about any return value. evaluate_async_script receives a callback function as the last argument which needs to be called to return a value, but your JS_GET_IMAGE doesn't appear to ever do that (nor really need to since it's not async) so it would be better to just use evaluate_script. The other requirement for evaluate_script is that the code evaluated needs to be a single statement. To meet that requirement we can use an IIFE.

Referring to the tutorial, the following steps are executed to install qt@5.5

I think my problem was with xcrun. For fix I did :

• sudo chown root:wheel /Applications/Xcode.app
• sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
• cd /Applications/Xcode.app/Contents/Developer/usr/bin/
• sudo ln -s xcodebuild xcrun

And it work (y) !

Are you storing session information in the browsers window.localStorage and/or window.sessionStorage? If so you can set those to be cleared via options passed to the driver (Note: these settings are the default for the selenium driver in Capybara 3.12+)

You need to use the text parameter of Capybaras modal handling methods (accept_confirm/accept_alert/etc) -https://www.rubydoc.info/github/jnicklas/capybara/Capybara/Session#accept_confirm-instance_method - which will check the message before it accepts/dismisses the system modal

I'm guessing that at the same time you switched from capybara-webkit to selenium with headless chrome you also switched from Capybara 2.x to 3.x. One of the breaking changes in Capybara 3.x is that it attempts to return whitespace more as the user would actually see it. That means that if you have   characters in your markup they don't get collapsed with surrounding spaces since the browser doesn't do that. You can use the normalize_ws option to get back results more like 2.x

capybara-webkit is basically equivalent to a 7 year old version of Safari (due to QtWebkit, which it is built on, not having been updated in a long time). As such it doesn't support a lot of modern JS/CSS, which happens to include flex box. Because of this display: flex will be considered invalid and ignored.

You're going to have a much easier time testing your app if you swap from using capybara-webkit to selenium with headless chrome or firefox for your headless testing.

You are using Ruby version 2.2.5 and you are also upgrading capybara to version 3.2.1. If you take a look at the line that causes the syntax error, the commit message give you a hint: Require minimum of Ruby 2.3.0

If you look at the history, capybara version 3.2.0 requires Ruby 2.3.0+.

You can either upgrade your applications Ruby version to 2.3.0 or greater, or set your capybara version to a prior version.