Not sure if this helps but here is my spec_helper file. Nothing in looks
like it would cancel out the timeouts script setting but I could be missing
something.
require 'rspec'
require 'page-object'
require 'watir'
require 'require_all'
require 'webdrivers'
require 'watir_angular'
require 'pry-b
Here is more of the error I am seeing.
Selenium::WebDriver::Error::ScriptTimeOutError:
script timeout: result was not received in 30 seconds
(Session info: chrome=72.0.3626.119)
(Driver info: chromedriver=2.42.591059
(a3d9684d10d61aa0c45f6723b327283be1ebaad8),platform=Mac
I don't have time to test it right now, but it might be a bug. Try
Selenium::Webdriver.logger.level = :info
See if the timeout information is showing up when you initialize the browser.
It's possible that watir isn't seeing both right now. I'm working on fixing it.
--
--
Before posting, plea
Hi Titus,
Here is the output you're looking for. It looks like it is setting it but
I am not see it reflected when the spec is run.
2019-02-26 14:13:22 INFO Selenium>>>
http://127.0.0.1:9556/session |
{"desiredCapabilities":{"browserName":"chrome","version":"","platform":"ANY","javascriptEna
Try setting w3c: true in Chrome options, maybe I'm using the wrong signature
for legacy Chrome.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
watir-general@googlegro
Sorry still learning but can that be added to my current setup?
On Tue, Feb 26, 2019 at 3:07 PM Titus Fortner
wrote:
> Try setting w3c: true in Chrome options, maybe I'm using the wrong
> signature for legacy Chrome.
>
> --
> --
> Before posting, please read
> https://github.com/watir/watir_met
Hi Titus,
Never mind. I believe I figured out where it went. If not please let me
know.
I used the 'Selenium::WebDriver.logger.level = :info' and the output is
listed below. It looks as though it was added correctly.
I ran the spec test and it failed for the same reason above. ( script
timeou
