Protractor Automated Browser Testing

Install Protractor:

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 conf.js:


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',
    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',
    shardTestFiles: true,
    maxInstances: 5,
    client_key: "api_key",
    client_secret: "api_secret"
  }, { // Same as repeating the previous setup twice
    browserName: 'chrome',
    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), which will contain the test.

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:

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
exports.config = {
  multiCapabilities: [{
    browserName: 'chrome'
  }]
}

After
exports.config = {
  seleniumAddress: 'https://hub.testingbot.com/wd/hub',
  multiCapabilities: [{
    browserName: 'chrome',
    client_key: "api_key",
    client_secret: "api_secret"
  }]
}


Specifying the operating system, browser and version

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


To see how to do this, please select a combination of browser, version and platform in the drop-down menus below.


1. Select a Platform
2. Select a Browser


Reporting Test Results

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:


Use a custom reporter to report back the test results to TestingBot.

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

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

specDone: function(result) {
  tb.updateTest({
    'test[name]' : result.description,
    'test[success]' : result.status
  }, browser.sessionId, function(done) {});
}

Testing Internal/Staged 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 WebDriver 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 securily through the tunnel to TestingBot and back:


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

Parallel Testing

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.


Queueing

Every plan we provide comes with a limit of concurrent VMs (how many tests you can run in parallel).
For example: if you have a plan with 5 concurrent VMs, it is possible to start more tests. TestingBot will queue the additional tests and run the tests as soon as slots become available.


To run tests in parallel, please see the following example:


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

Other Options

We offer many other test options, for example: disable video recording, specifying a custom Firefox Profile, loading Chrome/Firefox/Safari extensions, running an executable before your test starts, uploading files, ...
See our list of test options for a full list of options to customize your tests.

Pick a NodeJS test framework

  • Webdriver.io

    Webdriver/Selenium 2.0 javascript bindings for NodeJS.

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