Features

NodeJS Automated Testing

First, make sure you have installed NodeJS. If you haven't, you can easily install it by downloading NodeJS from the NodeJS website.

Getting started

With TestingBot you can easily run your automated tests with any NodeJS test framework, here's a simple example with selenium-webdriver:

npm install -g selenium-webdriver
const webdriver = require('selenium-webdriver');
const capabilities = {
 'platformName' : 'WIN10',
 'browserName' : 'chrome',
 'browserVersion' : 'latest',
 'tb:options': {
	 'name': 'NodeJS Sample Test'
	}
}
async function runTest () {
  let driver = new webdriver.Builder()
    .usingServer('https://api_key:api_secret@hub.testingbot.com/wd/hub')
    .withCapabilities(capabilities)
    .build();
  await driver.get("https://testingbot.com");
  await driver.wait(webdriver.until.titleMatches(/TestingBot/i), 5000);
  await driver.quit();
}
runTest();

This test will start a Chrome browser on Windows in our cloud, go to Google, and search for TestingBot. It will then output the title.
Your test results are now available on the commandline interface, and in our member area.

Make sure to always stop your test (driver.quit()), otherwise it will continue running, leading to a timeout.

Configuring capabilities

To run your existing tests on TestingBot, your tests will need to be configured to use the TestingBot remote machines. If the test was running on your local machine or network, you can simply change your existing test like this:

Before:
const driver = new webdriver.Builder().usingServer('http://localhost:4444/wd/hub').withCapabilities({
  'browserName' : 'firefox'
}).build()
After:
const driver = new webdriver.Builder().usingServer('https://hub.testingbot.com/wd/hub').withCapabilities({
  'browserName' : 'firefox'
}).build()

Specify Browsers & Devices

To let TestingBot know on which browser/platform/device you want to run your test on, you need to specify the browsername, version, OS and other optional options in the capabilities field.

Testing Internal Websites

We've built TestingBot Tunnel, to provide you with a secure way to run tests against your staged/internal webapps.
Please see our TestingBot Tunnel documentation for more information about this easy to use tunneling solution.

The example below shows how to easily run a NodeJS test with our Tunnel:

1. Download our tunnel and start the tunnel:

java -jar testingbot-tunnel.jar key secret

2. Adjust your test: instead of pointing to 'hub.testingbot.com/wd/hub' like the example above - change it to point to your tunnel's IP address.
Assuming you run the tunnel on the same machine you run your tests, change to 'localhost:4445/wd/hub'. localhost is the machine running the tunnel, 4445 is the default port of the tunnel.

This way your test will go securely through the tunnel to TestingBot and back:

const webdriver = require('selenium-webdriver');
const capabilities = {
 'platform' : 'WIN10',
 'browserName' : 'chrome',
 'version' : 'latest',
 'name': 'NodeJS Sample Test'
}
async function runTest () {
  let driver = new webdriver.Builder()
    .usingServer('http://api_key:api_secret@localhost:4445/wd/hub')
    .withCapabilities(capabilities)
    .build();
  await driver.get("https://testingbot.com");
  await driver.wait(webdriver.until.titleMatches(/TestingBot/i), 5000);
  await driver.quit();
}
runTest();

Run tests in Parallel

Parallel Testing means running the same test, or multiple tests, simultaneously. This greatly reduces your total testing time.

You can run the same tests on all different browser configurations or run different tests all on the same browser configuration.
TestingBot has a large grid of machines and browsers, which means you can use our service to do efficient parallel testing. It is one of the key features we provide to greatly cut down on your total testing time.

To run tests in parallel, we recommend using a test runner like WebDriverIO to run your tests simultaneously.

Queuing

Every plan we provide comes with a limit of parallel tests.
If you exceed the number of parallel tests assigned to your account, TestingBot will queue the additional tests (for up to 6 minutes) and run the tests as soon as slots become available.

Mark tests as passed/failed

As TestingBot has no way to dermine whether your test passed or failed (it is determined by your business logic), we offer a way to send the test status back to TestingBot. This is useful if you want to see if a test succeeded or failed from the TestingBot member area.

Install our NPM package to interact with the TestingBot API:

npm install testingbot-api

After your test completed, you can send back the test success state and other meta-data:

var TestingBot = require('testingbot-api');

var tb = new TestingBot({
  api_key: "api_key",
  api_secret: "api_secret"
});

tb.updateTest({
  'test[name]' : 'Example Test',
  'test[success]' : true
}, sessionId, done);

To retrieve the sessionId of the test, please see Get Session ID.

Other NodeJS Framework examples

  • WebDriverIO

    With WebDriverIO you can run Mocha, Jasmine and Cucumber tests.

  • Protractor

    Protractor is an end-to-end test framework for AngularJS applications. Protractor is a NodeJS program built on top of WebDriverJS.

  • Soda

    Selenium Node Adapter. A light-weight Selenium RC client for NodeJS.

  • Nightwatch

    Nightwatch is an automated testing framework written in NodeJS.

  • Intern

    Intern is a nodeJS framework for testing Web sites and applications.

  • WD.js

    WD.js is a NodeJS client for WebDriver/Selenium.

  • Hermione

    Hermione is a Test Framework similar to WebDriverIO, with automatic test retries and plugins.