Mink driver for controlling chrome without selenium


Mink driver for controlling Chrome without the overhead of Selenium.

It communicates directly with Google Chrome over HTTP and WebSockets, which allows it to work at least twice as fast as Chrome with Selenium. For Chrome 59+ it supports headless mode, eliminating the need to install a display server, and the overhead that comes with it. This driver is tested and benchmarked against a behat suite of 1800 scenarios and 19000 steps. It can successfully run it in less than 18 minutes with Chrome 60 headless. The same suite running against Chrome 58 with xvfb and Selenium takes ~60 minutes.

Gitlab CI pipeline OpenSSF Best Practices


composer require dmore/chrome-mink-driver


  • Google Chrome or Chromium running with remote debugging.


google-chrome-stable --remote-debugging-address= --remote-debugging-port=9222

or headless (v59+):

google-chrome-unstable --disable-gpu --headless --remote-debugging-address= --remote-debugging-port=9222

It is recommended to start Chrome with the --disable-extensions flag.

See for a fully working example.


Contributions are welcome! Use the issue queue and merge requests to propose changes. Please refer to Gitlab documentation for how to use the Gitlab interface.

  • To report an issue (bug, feature request etc) use the issue queue.
  • If you are reporting a potential security issue, please check "This issue is confidential" when reporting the issue to the project.
  • To propose code changes or a solution for an issue, use merge requests.
  • Test coverage is executed on merge requests. Contributions should extend test coverage where possible and ensure all tests pass.
  • Coding standards checks are executed on merge requests. Contributions should maintain coding standards.


The project has test coverage, which you can execute using the commands below.

Test execution requires a webserver configured to serve fixtures from minkphp/driver-testsuite, which is provided by a docker image from the related behat-chrome/docker-chrome-headless project. Tests executed are both tests specific to this driver and the more comprehensive test suite from mink/driver-testsuite, which is the common testsuite to ensure consistency across Mink driver implementations.

Using make

make installInstall dependencies with composer
make testRun tests with phpunit
make phpcbfTidy code using phpcbf
make phpcsCheck coding standards with phpcs

Without make

To perform these tasks without make, you can execute the same commands as above in a container. To run the tests using phpunit:

docker run --rm -it -v .:/code -e DOCROOT=/code/vendor/mink/driver-testsuite/web-fixtures bash

then, in the container shell:

composer install

Versioning & releases


use Behat\Mink\Mink;
use Behat\Mink\Session;
use DMore\ChromeDriver\ChromeDriver;

$mink = new Mink([
  'browser' => new Session(new ChromeDriver('http://localhost:9222', null, ''))


socketTimeoutint, default: 10Connection timeout (seconds)
domWaitTimeoutint, default: 3000DOM ready waiting timeout (milliseconds)
downloadBehaviorallow, default, denyChrome switch to permit downloads. (v62+)
downloadPathe.g. /tmp/ (the default)Where to download files to, if permitted.

Pass configuration values as the third parameter to new ChromeDriver().

Rendering PDF and Screenshots

Despite the Mink functionality the driver supports printing PDF pages or capturing a screenshot.

use Behat\Mink\Mink;
use Behat\Mink\Session;
use DMore\ChromeDriver\ChromeDriver;
$mink = new Mink(array(
    'browser' => new Session(new ChromeDriver('http://localhost:9222', null, ''))
$driver = $mink->getSession()->getDriver();

The available options are documented here:

Screenshots are supported using the Mink driver interface method getScreenshot().

Related projects

Behat extension

To use this driver with Behat, try the dmore/behat-chrome-extension Behat extension.

Docker image

A Docker image is used to execute tests against the targeted browser(s), and includes recent Chrome Stable, Chrome Beta and Chromium.