--- title: Run Selenium tests with NodeJS and Soda description: Cross browser testing with NodeJS and Soda. Run Soda tests on our Selenium grid. source_url: html: https://testingbot.com/support/web-automate/selenium/nodejs/soda md: https://testingbot.com/support/web-automate/selenium/nodejs/soda/index.md --- # NodeJS with Soda **Note:** Soda is a Selenium RC (Selenium 1.0) client that has been deprecated. We recommend using modern alternatives like [WebDriverIO](https://testingbot.com/support/web-automate/selenium/nodejs/webdriverio), [Nightwatch](https://testingbot.com/support/web-automate/selenium/nodejs/nightwatch), or [Playwright](https://testingbot.com/support/web-automate/playwright) for new projects. Install the TestingBot plugin: npm install testingbot You can now run your Selenium tests with NodeJS on our grid. Run this example: node example.js The example below uses the legacy Selenium 1 (RC) protocol via the `testingbot` npm package. TestingBot's hub no longer accepts the RC protocol, so this code will not run as-is. It is kept here for historical reference only, for working Node.js code, see the "After" snippet below or [our Node.js guide](https://testingbot.com/support/web-automate/selenium/nodejs). var soda = require('testingbot'), assert = require('assert'); var browser = soda.createTestingBotClient({ 'url': 'https://www.google.com', 'os': 'Windows', 'browser': 'chrome', 'browser-version': 'latest', 'max-duration': 300 }); // Log commands as they are fired browser.on('command', function(cmd, args) { console.log(' \x1b[33m%s\x1b[0m: %s', cmd, args.join(', ')); }); browser .chain .session() .setTimeout(8000) .open('/') .waitForPageToLoad(5000) .getTitle(function(title) { assert.ok(title.includes('Google')) }) .testComplete() .end(function(err) { if (err) { console.log(err); } }); ## 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', browserVersion: 'latest', platformName: 'WIN11', 'tb:options': { key: 'API_KEY', secret: 'API_SECRET' } }) .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. ![OS selected](https://testingbot.com/assets/environments/svg/windows11-0e1b28bc0fdd5034d3e4d3dc8d346c500a8c6522facf4b45d0da56537c1f1c6d.svg) Windows 11 › ![Browser Selected](https://testingbot.com/assets/environments/svg/chrome-c4081ff447d2d898d4afcb8f074a907c960e6f007716c1a1d119eee6803c4042.svg) Chrome 139 Loading environments... Please wait while we load the available browsers and platforms. ## Testing Internal Websites We've built [TestingBot Tunnel](https://testingbot.com/support/tunnel), to provide you with a secure way to run tests against your staged/internal webapps. Please see our [TestingBot Tunnel documentation](https://testingbot.com/support/tunnel) 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](https://testingbot.com/support/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 { Builder } = require('selenium-webdriver'); const capabilities = { browserName: 'chrome', browserVersion: 'latest', platformName: 'WIN11', 'tb:options': { key: 'API_KEY', secret: 'API_SECRET', name: 'Tunnel Test' } }; // Point to the tunnel running on localhost:4445 const driver = new Builder() .usingServer('http://localhost:4445/wd/hub') .withCapabilities(capabilities) .build(); (async () => { await driver.get('https://www.google.com'); const title = await driver.getTitle(); console.log(title); await driver.quit(); })(); ## 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](https://testingbot.com/support/web-automate/selenium/nodejs/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 determine 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: const TestingBot = require('testingbot-api'); const tb = new TestingBot({ api_key: 'API_KEY', api_secret: 'API_SECRET' }); // Obtain the session id from your WebDriver session after the test runs: // const session = await driver.getSession(); // const sessionId = session.getId(); tb.updateTest({ 'test[name]': 'My Test', 'test[success]': true, 'test[build]': 'build-123' }, sessionId, (error, response) => { if (error) console.error(error); }); ## Other NodeJS Framework examples - [WebDriverIO](https://testingbot.com/support/web-automate/selenium/nodejs/webdriverio) With WebDriverIO you can run Mocha, Jasmine and Cucumber tests. - [CodeceptJS](https://testingbot.com/support/web-automate/selenium/nodejs/codeceptjs) Run acceptance tests with CodeceptJS on TestingBot. - [Protractor](https://testingbot.com/support/web-automate/selenium/nodejs/protractor) Protractor is an end-to-end test framework for AngularJS applications. **Note:** Protractor is deprecated and no longer maintained. - [Nightwatch](https://testingbot.com/support/web-automate/selenium/nodejs/nightwatch) Nightwatch is an automated testing framework written in NodeJS. - [WD.js](https://testingbot.com/support/web-automate/selenium/nodejs/wd) WD.js is a NodeJS client for WebDriver/Selenium. - [Hermione](https://testingbot.com/support/web-automate/selenium/nodejs/hermione) Hermione is a Test Framework similar to WebDriverIO, with automatic test retries and plugins. ### Looking for more help? Have questions or need more information? Reach out via email or Slack. [Email us](https://testingbot.com/contact/new)[Slack Join our Slack](https://join.slack.com/t/testingb0t/shared_invite/zt-3bcw9xch-jk19~6XPs_xBrsAgAedkCw)