Unclaimed tool
Selenium
selenium.dev
Browser automation framework for web testing.
Tools
From public taxonomy evidence
Related skills
- Unable to obtain: Capabilities -> Issue still present in 4.15
How to fix unable to obtain: Capabilities -> Issue still present in 4.15 (Selenium). The verified answer from the upstream issue, distilled into steps.
supporting match - Dotnet Error in 4.11.0 when using ChromeDriverService.CreateDefaultService()
Upgrade to Selenium 4.12 or newer. In 4.11 the .NET Service constructor treated a path without a trailing slash as a file instead of a directory, which broke ChromeDriverService.CreateDefaultService(); that was fixed for 4.12.
supporting match - Chrome team removes `--load-extension` switch on Chrome builds
How to chrome team removes --load-extension switch on Chrome builds. Verified in gh:SeleniumHQ/selenium#15788.
supporting match - org.openqa.selenium.WebDriverException: unknown error: result.webdriverValue.value list is missing or empty in...
Covers this Selenium problem: org.openqa.selenium.WebDriverException: unknown error: result.webdriverValue.value list is missing or empty in.... [titusfortner (member)]: The unknown-error driver failures come from a Chrome/ChromeDriver version mismatch caused by third-party driver managers.
supporting match - Remove CDP support for Firefox browser
A practical guide for Selenium. [pujagani (contributor)]: CDP support for Firefox was removed in Selenium 4.29.0. Upgrade to 4.29.0 or newer; the release notes cover the change.
supporting match - Chrome 111 is not compatible with default HTTP Client
If ChromeDriver fails to start after the Chrome 111 update, add --remote-allow-origins=* to your ChromeOptions as a workaround. The underlying issue (Selenium's Java HTTP client setting the Origin header) was fixed in Selenium 4.9.0, so upgrade past that and drop the workaround.
supporting match - Selenium 4 Java: random netty read TimeoutException on fast commands (fixed in 4.1.2)
This was a client-side HTTP-layer bug: the Java 4.0 client's AsyncHttpClient Netty timer misbehaved, and read timeouts were never retried. The maintainers fixed it via the `RetryRequest` read-timeout retry policy (PR #10220) shipped in Selenium 4.1.2, and the original reporter confirmed the error no longer reproduces a
supporting match
Public conversations
Recent discussions
- Selenium 4 Java: random netty read TimeoutException on fast commands (fixed in 4.1.2)
Selenium 4 (Java client) randomly throws `java.util.concurrent.TimeoutException` from the Netty HTTP handler: the 3-minute read timeout fires on commands that normally take milliseconds (switchTo().defaultContent(), click(), sendKeys(), alert.accept()), roughly <1% of test cases in large CI suites. Retrying the command