Closed DKarap closed 10 years ago
2.The implicitWait capabilities may throw timeOutExceptions that are not handle. Thus the WebDriverException catch it and terminates the process
WHERE WE FAILED TO GET A URL AND THEN TRY TO CLICK AN ELEMENT THEN WE GTH A TIMEOUT EXCEPTION: Timeout during page loading:http://weblog.independer.nl/vacature/ Exception:{"errorMessage":"URL 'http://weblog.independer.nl/vacature/' didn't load. Error: 'timeout'","request": Command duration or timeout: 5.16 seconds
org.openqa.selenium.TimeoutException: {"errorMessage":"Click failed: timeout","request":
Exceptions:
org.openqa.selenium.StaleElementReferenceException: getLinks() getVisualInfo() org.openqa.selenium.remote.UnreachableBrowserException: get() getPageSource() FATAL org.openqa.selenium.NoSuchElementException: getTitle OK org.openqa.selenium.WebDriverException: getTitle() org.openqa.selenium.NoSuchWindowException: get(url),getPageSource(); OK org.openqa.selenium.TimeoutException: clickElement() org.openqa.selenium.remote.SessionNotFoundException: get(url) - FATAL!!!
Main exceptions happened due to malakies of ghostdriver:
This is done by catching the webdriver exceptions at the main core modules
Cases that we might need to handle for exceptions: