Repository navigation
Document the WebdriverClassic driver - #66
Merged
stof merged 2 commits intoSep 29, 2026
Merged
Conversation
PR FriendsOfBehat#26 added support for the webdriver_classic driver (wrapping mink/webdriver-classic-driver), but doc/index.md was never updated to mention it. Add a driver entry following the existing style, showing the browser, wd_host and capabilities options and noting that capabilities are merged with values Mink guesses from the environment. Closes FriendsOfBehat#30
stof
requested changes
Sep 29, 2026
| browser_stack: ~ | ||
| ``` | ||
|
|
||
| * **WebdriverClassicDriver** - javascript driver speaking the classic (JSON Wire Protocol-based) WebDriver protocol, the direct successor of Selenium2Driver. In order to use it, install [`mink/webdriver-classic-driver`](https://packagist.org/packages/mink/webdriver-classic-driver) through Composer. Then, modify your `behat.yml` profile: |
Member
There was a problem hiding this comment.
I suggest putting it before Selenium2Driver as it is meant to become the recommended driver for Webdriver over time (Selenium 4 speaks the W3C Webdriver protocol by default)
| browser_stack: ~ | ||
| ``` | ||
|
|
||
| * **WebdriverClassicDriver** - javascript driver speaking the classic (JSON Wire Protocol-based) WebDriver protocol, the direct successor of Selenium2Driver. In order to use it, install [`mink/webdriver-classic-driver`](https://packagist.org/packages/mink/webdriver-classic-driver) through Composer. Then, modify your `behat.yml` profile: |
Member
There was a problem hiding this comment.
The WebdriverClassicDriver speaks the W3C Webdriver Classic protocol, not the JSON Wire Webdriver protocol (which is the name of the legacy Selenium Webdriver protocol)
Per @stof's review on the PR: - Move the WebdriverClassicDriver entry before Selenium2Driver, since it's meant to become the recommended WebDriver driver over time (Selenium 4 speaks the W3C WebDriver protocol by default). - Correct the protocol description: it speaks the W3C WebDriver (Classic) protocol, not the JSON Wire Protocol. The JSON Wire Protocol is the legacy, non-standard protocol name used by the old Selenium WebDriver implementation (i.e. Selenium2Driver), not something WebdriverClassicDriver speaks.
stof
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #26 added support for the
webdriver_classicdriver (wrappingmink/webdriver-classic-driver), butdoc/index.mdwas never updated to explain how to configure it.This adds a driver entry to the "Drivers" section, next to
Selenium2Driverand its flavors, following the existing style. It shows thebrowser,wd_hostandcapabilitiesoptions and notes thatcapabilitiesis merged with values Mink guesses automatically from the environment (e.g. CI build/tag information on Travis or Jenkins).Closes #30