[wtr-general] Re: Selenium::WebDriver::Error::UnhandledAlertError: unexpected alert open: {Alert text : Bad response - parser error!}

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

[wtr-general] Re: Selenium::WebDriver::Error::UnhandledAlertError: unexpected alert open: {Alert text : Bad response - parser error!}

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

[wtr-general] Re: Selenium::WebDriver::Error::UnhandledAlertError: unexpected alert open: {Alert text : Bad response - parser error!}

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

[wtr-general] Selenium::WebDriver::Error::UnhandledAlertError: unexpected alert open: {Alert text : Bad response - parser error!}

Im having a tough time with this intermittent error I get on checkout page once all the details are filled and customer hits payment button. Sometimes Selenium::WebDriver::Error::UnhandledAlertError: unexpected alert open: { Alert text : Bad response - parser error!} (Session info: