Skip to main content
Introducing the Automate SDK! Get your entire test suite running on BrowserStack in minutes! Learn More.

Selenium with Codeception

A guide to run Selenium Webdriver tests with Codeception on BrowserStack.

Note: Code samples in this guide can be found in the codeception-browserstack sample repo on GitHub


BrowserStack gives you instant access to our Selenium Grid of 3000+ real devices and desktop browsers. Running your Selenium tests with Codeception on BrowserStack is simple. This guide will help you in:

  1. Running your first test
  2. Integrating your tests with BrowserStack
  3. Mark tests as passed or failed
  4. Debugging your app


Before you can start running your Selenium tests with Codeception, ensure that you have:

Running your first test

To run your first Codeception test on BrowserStack, follow the steps below:

  1. Clone the codeception-browserstack sample repo on GitHub using the following command:

    git clone
    cd codeception-browserstack
  2. Install the dependencies using the following command:
     composer install
  3. Setup your credentials in the codeception-browserstack/tests/acceptance.suite.yml file as shown below:

     class_name: AcceptanceTester
         - WebDriver
           host: ''
           port: 80
           browser: chrome
           url: ''
             'browserstack.user': 'YOUR_USERNAME'
             'browserstack.key' : 'YOUR_ACCESS_KEY'
             'name': 'Bstack-[Codeception] Sample Test'
            browser: 'chrome'
            browser: 'firefox'
            browser: 'safari'
            browser: 'internet explorer'
  4. Run your first test using the following command:

     composer parallel
  5. You can visit BrowserStack Automate Dashboard and see your test there once it has successfully completed.
Protip: You can use our capability builder and select from a wide range of custom capabilities that BrowserStack supports.

Details of your first test

When you run the composer parallel command, the test is executed on the browsers specified in the codeception-browserstack/tests/acceptance.suite.ymlfile. The test case searches for the string “BrowserStack” on Google, and checks if the title of the resulting page is “BrowserStack - Google Search”.

  // @group single
  $I = new AcceptanceTester($scenario);
  $I->wantTo('Test Google\'s Search Functionality');
  $I->fillField('q', 'BrowserStack');
  $I->seeInTitle('BrowserStack - Google Search');

Integrating your tests with BrowserStack

In the sample repository, you can find Codeception-BrowserStack/lib/BrowserStackWebDriver.php file which is responsible for configuring your test to run on BrowserStack.

require 'vendor/autoload.php';

// here you can define custom actions
// all public methods declared in helper class will be available in $I

class BrowserStackWebDriver extends \Codeception\Module\WebDriver
    private $bs_local;

    public function _initialize(){
        getenv('BROWSERSTACK_USERNAME') ? ($this->config["capabilities"]["browserstack.user"] = getenv('BROWSERSTACK_USERNAME')) : 0;
        getenv('BROWSERSTACK_ACCESS_KEY') ? ($this->config["capabilities"]["browserstack.key"] = getenv('BROWSERSTACK_ACCESS_KEY')) : 0;

        if(array_key_exists("browserstack.local", $this->config["capabilities"]) && $this->config["capabilities"]["browserstack.local"])
            $bs_local_args = array("key" => $this->config["capabilities"]["browserstack.key"]);
            $this->bs_local = new BrowserStack\Local();


    // HOOK: after suite
    public function _afterSuite() {
        if($this->bs_local) $this->bs_local->stop();

Mark tests as passed or failed

BrowserStack provides a comprehensive REST API to access and update information about your tests. Shown below is a sample code snippet which allows you to mark your tests as passed or failed based on the assertions in your Codeception test cases.

file_get_contents('<session-id>.json', false, stream_context_create(array('http'=>array('method'=>'PUT','header'=>'Content-type: application/json', 'content'=>'{"status":"passed","reason":"<reason>"}'))));

You can find the full reference to our REST API.

Debugging your app

BrowserStack provides a range of debugging tools to help you quickly identify and fix bugs you discover through your automated tests.

Text logs

Text Logs are a comprehensive record of your test. They are used to identify all the steps executed in the test and troubleshoot errors for the failed step. Text Logs are accessible from the Automate dashboard or via our REST API.

Visual logs

Visual Logs automatically capture the screenshots generated at every Selenium command run through your JUnit tests. Visual Logs help with debugging the exact step and the page where failure occurred. They also help identify any layout or design related issues with your web pages on different browsers.

Visual Logs are disabled by default. In order to enable Visual Logs you will need to set browserstack.debug capability to true.

$caps = array(
 "browserstack.debug" => "true"

Sample Visual Logs from Automate Dashboard: BrowserStack Automate Visual Logs

Video recording

Every test run on the BrowserStack Selenium grid is recorded exactly as it is executed on our remote machine. This feature is particularly helpful whenever a browser test fails. You can access videos from Automate Dashboard for each session. You can also download the videos from the Dashboard or retrieve a link to download the video using our REST API.

Note: Video recording increases test execution time slightly. You can disable this feature by setting the capability to false.
$caps = array(
 "" => "false"

In addition to these logs BrowserStack also provides Raw Logs, Network Logs, Console Logs, Selenium Logs, Appium Logs and Interactive session. You can find the complete details to enable all the debugging options.

Next steps

Once you have successfully run your first test on BrowserStack, you might want to do one of the following:

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked

Thank you for your valuable feedback

Is this page helping you?


We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked

Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert