Consider using this option if you don’t plan to use Selenium.

Tests can be executed directly through ChromeDriver or GeckoDriver (for Firefox). Running tests inside Docker is as easy as pulling official selenium image and starting a container with Chrome: docker run -net=host -shm-size 2g selenium/standalone-chromeīy using -net=host allow Selenium to access local websites. To enable headless mode (launch tests without showing a window) for Chrome browser using Selenium use this config in : modules : enabled : - WebDriver : url : ' browser : chrome capabilities : chromeOptions : args : Headless Selenium in Dockerĭocker can ship Selenium Server with all its dependencies and browsers inside a single container. Update configuration in : modules : enabled : - WebDriver : url : ' browser : chrome # 'chrome' or 'firefox' Headless Chrome Browser Launch selenium standalone in separate console window: selenium-standalone start The fastest way to get started is to Install and launch Selenium using selenium-standalone NodeJS package. There are multiple ways of running browser tests using WebDriver: Selenium (Recommended)

Run tests in real browsers using the W3C WebDriver protocol. Using PHAR file and composer in the same project can cause unexpected errors. Some modules are bundled with PHAR files. This module was bundled with Codeception 2 and 3, but since version 4 it is necessary to install it separately.

If you use Codeception installed using composer, install this module with the following command: composer require -dev codeception/module-webdriverĪlternatively, you can enable WebDriver module in suite configuration file and run codecept init upgrade4

Install webdriver for chrome