Features
Start a free trial

Protractor Automated Browser Testing

Install Protractor:

Copy code
npm install -g protractor

Now, you'll need to create a config file so that Protractor knows it needs to connect to our Selenium Grid.

Create a file called conf.js:

Copy code
exports.config = {
  seleniumAddress: 'https://hub.testingbot.com/wd/hub',
  specs: ['spec.js'],
  maxSessions: 6,  // 6 TOTAL sessions across all capabilities
  multiCapabilities: [{ // in 1 chrome run the 10 specs sequentially
    browserName: 'chrome',
    platform: 'WIN10',
    version: 'latest',
    name: 'My First Protractor test',
    client_key: "api_key",
    client_secret: "api_secret"
  }, { // 5 chrome sessions will start, each running 1 spec file at a time, until all 10 finish
    browserName: 'chrome',
    platform: 'BIGSUR',
    version: 'latest-1',
    name: 'My First Protractor test',
    shardTestFiles: true,
    maxInstances: 5,
    client_key: "api_key",
    client_secret: "api_secret"
  }, { // Same as repeating the previous setup twice
    browserName: 'chrome',
    platform: 'WIN10',
    version: 'latest-2',
    name: 'My First Protractor test',
    shardTestFiles: true,
    maxInstances: 5,
    count: 2,
    client_key: "api_key",
    client_secret: "api_secret"
  }]
}

Next, we'll create a spec.js (which we defined above in the conf file). This will contain the test logic.

Copy code
describe('Protractor Demo App', function() {
  it('should have a title', function() {
    browser.get('http://juliemr.github.io/protractor-demo/');

    expect(browser.getTitle()).toEqual('Super Calculator');
  });
});

To run the test, please run this command:

Copy code
protractor conf.js

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:
Copy code
exports.config = {
  multiCapabilities: [{
    browserName: 'chrome'
  }]
}
After:
Copy code
exports.config = {
  seleniumAddress: 'https://hub.testingbot.com/wd/hub',
  multiCapabilities: [{
    browserName: 'chrome',
    client_key: "api_key",
    client_secret: "api_secret"
  }]
}

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.

1. Select a Platform
2. Select a browser
Copy code

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 Protractor test with our Tunnel:

1. Download our tunnel and start the tunnel:

Copy code
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:

Copy code
exports.config = {
  seleniumAddress: 'http://localhost:4445/wd/hub',
  specs: ['spec.js'],
  multiCapabilities: [{
    browserName: 'chrome',
    client_key: "api_key",
    client_secret: "api_secret"
  }]
}

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, please see the following example:

Copy code
exports.config = {
  capabilities: {
    browserName: 'chrome',
    count: 2 // number of parallel tests
  }
}

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.

Copy code
exports.config = {
  seleniumAddress: 'https://hub.testingbot.com/wd/hub',
  specs: ['spec.js'],
  maxSessions: 6,  // 6 TOTAL sessions across all capabilities
  multiCapabilities: [{ // in 1 chrome run the 10 specs sequentially
    browserName: 'chrome',
    platform: 'WIN10',
    version: 'latest',
    name: 'My First Protractor test',
    client_key: "api_key",
    client_secret: "api_secret"
  }, { // 5 chrome sessions will start, each running 1 spec file at a time, until all 10 finish
    browserName: 'chrome',
    platform: 'BIGSUR',
    version: 'latest-1',
    name: 'My First Protractor test',
    shardTestFiles: true,
    maxInstances: 5,
    client_key: "api_key",
    client_secret: "api_secret"
  }, { // Same as repeating the previous setup twice
    browserName: 'chrome',
    platform: 'WIN10',
    version: 'latest-2',
    name: 'My First Protractor test',
    shardTestFiles: true,
    maxInstances: 5,
    count: 2,
    client_key: "api_key",
    client_secret: "api_secret"
  }],
  onComplete: function (passed) {
      browser.executeScript("tb:test-result=" + (passed ? "passed" : "failed"));
  }
}

Please see the example below, where we use the onComplete callback provided by Protractor.

Copy code
onComplete: function (passed) {
  browser.executeScript("tb:test-result=" + (passed ? "passed" : "failed"));
}

This onComplete handler will be invoked after every Protractor test.
The test status will be sent to TestingBot, where we will display the pass/fail state in your test dashboard.

Other NodeJS Framework examples

  • WebDriverIO

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

  • CodeceptJS

    Run acceptance tests with CodeceptJS on TestingBot.

  • 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.