Skip to content


TestingBot is a cloud-based cross-browser testing platform that helps in both manual and automated browser compatibility testing. Users can perform live interactive testing of their website or web app on different browsers and operating systems right from their own browser.

Integration with Zebrunner allows users to:

  1. Launch tests against TestingBot environment via Zebrunner UI
  2. View remote web driver session artifacts (such as video recording, session log and metadata) on test results page
  3. Have access to Hub credentials in Quick Access pane on test runs view

Note: integration is supported on a per-project basis, meaning that different projects in Zebrunner can be connected to different TestingBot accounts.


  • Your Zebrunner account should have Administrator role within a project, where integration needs to be enabled.


The following steps needs to be completed to configure TestingBot integration:

  1. Log in to your TestingBot account and go to Account view
  2. Copy Key and Secret: TestingBot Account page
  3. Log in to your Zebrunner account and go to Integrations section of a project, where integration needs to be configured
  4. In the grid of available integrations find TestingBot tile and click on it
  5. Enter your hub url, key and secret to the corresponding fields and hit Save Zebrunner TestingBot integration view

Integration is now configured. You can check if TestingBot is configured properly and reachable by clicking on Test button. Additionally, it can be enabled or disabled if needed by clicking power icon in the upper right corner.

Launching tests against TestingBot#

With integration configured it is now possible to launch tests against TestingBot Selenium hub. In order to do so, go to Launcher view on test runs page, select a suite you want to launch and pick TestingBot from the list of available testing platforms. Zebrunner launcher window with TestingBot selected option You'll have access to capability generator as it is provided by TestingBot. Web driver session artifacts will be accessible on test details view automatically. Additionally, TestingBot hub credentials will be seen to project members with role of Engineer (or higher) in Quick Hub Access pane.

Note: TestingBot will only be visible as an option for Launcher if it is enabled in integration settings.