Like I said, this is a real error, so you need to talk to your devs to figure
out why you're getting this.
--
--
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.
Basically the script gets a focus on "Place Order" button and clicks it. At
this point the alert occurs
2018-12-07 10:33:21 INFO Selenium>>>
http://127.0.0.1:9515/session/5ee6d653d161aabc0a8fe64ac2c8391f/execute |
{"script":"return (function(){\nreturn
Hi Titus
Just before the error what I get is
2018-12-07 10:33:24 INFO Selenium <- {"sessionId":
"5ee6d653d161aabc0a8fe64ac2c8391f","status":0,"value":null}
Time after is 2018-12-07 10:33:24 +1100
2018-12-07 10:33:24 INFO Selenium -> POST session/
5ee6d653d161aabc0a8fe64ac2c8391f/element
Put that line of code in your before hook. When an unexpected alert pops
up, it'll tell you what exactly was just sent to the browser that caused
it. It spits out a lot of text to console, so hopefully the issue is
happening frequently enough that you can turn it on for a short time and
Thanks Titus, Yes I know the issue with, "Watir::Wait.until {element}" this
is all over our automation code , the previous automation tester did this
practise. In on my list to clean this up
But sorry I didnt quite understand the statement "Also log the wire calls
getting sent to the driver
The issue is that sometimes an alert has popped up. Whenever an alert is
present, the driver will not accept any commands that do not deal with that
alert. Just like a user can't do anything on a site without dismissing it.
That includes screenshots. Rescuing the error won't help if you just
