This article is about Codeship Basic.

Browser Testing During CI/CD With Codeship Basic

Estimated Reading Time: 1 min


Firefox 35 is installed and available in the PATH.


Chrome and Chromium are both available in the PATH and in /usr/bin/google-chrome and /usr/bin/chromium-browser


Firefox and Chrome both work with Selenium. To support Selenium with Chrome the Chrome Driver is installed as well. Please provide your own Selenium driver (e.g. selenium-webdriver for Ruby) and keep it up-to-date. This will ensure that it will work with the latest version installed on Codeship.


If there are no packages available for your framework or you want to use the Standalone version, please take a look at the script available at codeship/scripts on how to install a custom version.

If you are using NodeJS, you can use the project at to keep your Selenium version updated to the latest available version.


You can use SauceConnect to connect the SauceLabs browser testing service with the application running in your Codeship build.

There is no special integration necessary for SauceConnect on Codeship. Make sure you set the username and api key or other necessary variables in the environment configuration. You can run your tests exactly the same way as you would run them on your own development machine through SauceConnect.


Phantomjs 1.9.7 is installed and available in the PATH.


Casperjs 1.1-beta3 is installed and available in the PATH.


SlimerJS 0.9.5 is installed and available in the PATH.

Need More Help?

Get in touch if you need more help, or post on Stack Overflow using the tag #Codeship.

  • Ask The Helpdesk A Question
  • Code Examples And Sample Projects
    • Was This Article Helpful?