...
- Chrome 28+ and Selenium's chromedriver is not compatible with RHEL/!CentOS 6.x. CentOS 7.0 (64-bit) works—although there is a warning reported. This warning can be disabled from the command line with
setsebool -P unconfined_chrome_sandbox_transition 0 - Selenium WebDriver randomly fails to accept the script dialogs. This occurs when a test tries to open a dialog and the "Wait for Script Dialog" is reporting error that script dialog does not exist during the specified timeout (by default 10 seconds). The issue can be solved by increasing the wait time. See https://groups.google.com/forum/#!topic/selenium-developer-activity/It-RyMNBrpw for details.
- In Chrome, Selenium cannot interact with onBeforeUnload dialogs that open due to a Navigate, Go Back, or Go Forward action. See https://code.google.com/p/chromedriver/issues/detail?id=29 for details.
- In Chrome and Internet Explorer, Selenium cannot interact with onBeforeUnload dialogs that open when calling "Close" on the only browser window.
- Chrome: See https://code.google.com/p/chromedriver/issues/detail?id=901 for details.Internet Explorer: See https://code.google.com/p/selenium/issues/detail?id=7895 for details.
- Selenium WebDriver fails to accept an alert that is opened on a new window. See https://code.google.com/p/selenium/issues/detail?id=7807 for details.
- Modal dialogs (those opened using the JavaScript function "showModalDialog") are not supported for Chrome. Web applications that rely on this functionality should use Internet Explorer or Firefox.
- For the "click" user action, key modifiers ("Shift," "Ctrl," and "Alt") are supported only in Chrome due to an issue in Selenium WebDriver. See https://code.google.com/p/selenium/issues/detail?id=4385 for details.
- When multiple windows are opened by one user action, the Selenium WebDriver can return a wrong order of window handlers for Chrome and Internet Explorer. This can happen only in the case of unnamed windows. The workaround is to use named windows. Cannot click on area elements in Internet Explorer. See https://code.google.com/p/selenium/issues/detail?id=2354 for details.
- In Internet Explorer, if an application overrides the default "fireEvent" implementation on an element with a new implementation, Selenium will trigger the new implementation when performing actions on that element. This differs from default browser behavior, where the default "fireEvent" implementation is called even when the "fireEvent" method is changed by a web application.Selenium does not support playing back scenarios in headless mode. If headless mode is selected, the scenarios will still play back in visible mode.
Known Safari Issues
- Traffic is not recorded when playing back scenarios.
- NTLM/Digest/Basic authentication is not supported.
- Configure and Validate for Load Test are not supported.
- Attaching tools to HTTP traffic is not supported.
- The "Wait for Interval without Traffic" wait condition will always succeed after the configured interval has elapsed, regardless of whether traffic is being sent by the browser or server.
- The "Wait for Asynchronous Requests" wait condition does not work.
- Sites that use untrusted certificates are not supported.
- Users may experience test instability when switching between multiple windows or frames in Safari.
Manually Upgrading to a New Version of Selenium WebDriver
...
- Upgrade the Selenium client, which also upgrades WebDriver support for Firefox playback. This step is required, regardless of the browser(s) you want WebDriver to use for playback. For details, see Upgrading Selenium Client Libraries (Includes Updating WebDriver Support for Firefox (GeckoDriver).
- Upgrade WebDriver’s playback support for the desired browser(s)—Chrome and/or Internet Explorer. See the following sections:
| Table of Content Zone | ||||||
|---|---|---|---|---|---|---|
| ||||||
WebDriver Support for Firefox)The following is always the first step for updating Selenium WebDriver—no matter what browser you want it to use for playback. WebDriver support for Firefox will be upgraded as part of this process.
update.bat script (for Windows) or update script (GeckoDriver)To upgrade WebDriver’s support for Firefox, update GeckoDriver as follows:
Upgrading WebDriver Support for Chrome (ChromeDriver)To upgrade WebDriver’s support for Chrome, update ChromeDriver as follows: If you have not already done so, upgrade the Selenium client libraries as described in Upgrading Selenium Client Libraries (Includes Updating WebDriver Support for Firefox).
Upgrading WebDriver Support forInternet ExplorerMicrosoft Edge (InternetExplorerDriver)The Selenium WebDriver engine uses the 32-bit version of Internet Explorer. Any custom Internet Explorer Executable Path settings (e.g., from Preferences> Browser> IE Executable Path) will not be applied.
SOAtest will now use the newer version of InternetExplorerDriver for playback. Upgrading WebDriver Support for Microsoft Edge (EdgeDriver)If you have not already done so, upgrade the Selenium client libraries as described in Upgrading Selenium Client Libraries (Includes Updating WebDriver Support for Firefox).EdgeDriver)To upgrade WebDriver’s support for Microsoft Edge, update EdgeDriver as follows:
|
Running Selenium WebDriver Browser Scenarios Using soatestcli on Linux
...