Skip to content

running.md

Latest commit

 

History

History
217 lines (164 loc) · 9.22 KB

running.md

File metadata and controls

217 lines (164 loc) · 9.22 KB

Running Intern

Built-in runners

The Node and browser built-in runners load configuration information from the command line / query args and/or a config file. There are no special command line flags; in both cases, command line options are config properties.

Node

The node runner is a built in script for running Node-based unit tests and WebDriver tests. Usage can be very simple:

$ node_modules/.bin/intern

Of course, it can be called from a package.json file even more simply:

{
    "scripts": {
        "test": "intern"
    }
}

By default, the runner looks for an intern.json config file in the project root. This can be changed by providing a config property on the command line, like config=tests/myconfig.json. The runner will also accept any other config properties as command line arguments. For example,

$ node_modules/.bin/intern suites=tests/foo.js grep=feature1

would only load the suite in tests/foo.js, and would only run tests containing the string ‘feature1’ in their IDs.

Browser

The browser runner is a built-in HTML page for running browser-based unit tests. To use it, serve the project root directory using a static webserver and browse to (assuming the server is running on port 8080):

http://localhost:8080/node_modules/intern/

Similar to the Node runner script, the browser runner will accept a config argument, or any other config properties, as query args.

http://localhost:8080/node_modules/intern/?suites=tests/foo.js&grep=feature1

Note that the browser runner can only be used to run unit tests, not functional (i.e., WebDriver) tests.

Grunt

Intern includes a Grunt task that can be loaded with

grunt.loadNpmTasks('intern');

The task may be configured using the same options as are used in an intern.json file. For example, consider the following intern.json file:

{
  "suites": "tests/unit/**/*.js",
  "require": "tests/pre.js",
  "loader": {
    "script": "dojo",
    "config": {
      "packages": [{"name": "app", "location": "."}]
    }
}

An equivalent Grunt config that used the Node executor would look like:

module.exports = function (grunt) {
    grunt.initConfig({
        intern: {
            node: {
                options: {
                    suites: "tests/unit/**/*.js",
                    require: "tests/pre.js"
                    "loader": {
                        "script": "dojo",
                        "config": {
                            "packages": [{"name": "app", "location": "."}]
                        }
                    }
                }
            }
        }
    });

    // Loading using a local git copy
    grunt.loadNpmTasks('intern');
};

Note that the Grunt task runner doesn’t use the config file loading logic employed by the Node and browser runners. The assumption is that Grunt will be used to construct the desired config.

Custom Node Script

Intern may also be configured and run with a custom script. The basic steps this script must perform are:

  1. Import/require the Node executor
  2. Construct a new instance of Node and assign it to the intern global. The config should include at least one suite and a reporter. 
    global.intern = new Node({
    suites: 'tests/unit/a.js',
    reporters: 'runner'
 });
  3. Call intern.run()

Custom HTML Page

Intern may be configured and run in a browser with a custom HTML page. The basic steps are:

  1. Load the Browser executor (<script src="node_modules/intern/browser/intern.js"></script>). The intern.js script will automatically initialize a Browser executor and assign it to an intern global.
  2. Configure the executor. Include at least one suite at a reporter. 
    intern.configure({
    suites: 'tests/unit/a.js',
    reporters: 'html'
});
  3. Call intern.run()

WebDriver servers

When running functional tests, Intern communicates with remote browsers using WebDriver. To do this, it either uses a browser-specific WebDriver server, generally managed by Selenium, or a remote testing service such as BrowserStack.

Bare WebDriver server

To use a bare WebDriver, such as chromedriver, use the following steps:

  1. Download the latest version of the WebDriver
  2. Set the tunnel config property to 'null'
  3. Run the WebDriver on port 4444 with a base URL of 'wd/hub'. Alternatively, using the tunnelOptions config property, set port to a particular port and pathname to the WebDriver’s base URL).
  4. Set the environments config property to 'chrome'.
  5. Run Intern

💡 To verify that the WebDriver is running on the proper port and path, open a browser to http://localhost:4444/wd/hub/status. It should return a JSON response with a status` field of 0.

Selenium

If you’d rather let Intern manage WebDrivers, you can use Selenium. Intern defaults to using the 'selenium' tunnel, so configuration is simpler than for a bare WebDriver.

  1. Set the environments config property to the name of the desired browser ('chrome', 'firefox', etc.)
  2. If using 'firefox' or 'internet explorer', also provide the driver name in the tunnelOptions config property: 
    {
    "tunnelOptions": {
        "drivers": [ "firefox" ]
    }
}
  3. Run Itnern

Cloud service

Intern comes with built-in support for 4 cloud testing services via the digdug library: BrowserStack, CrossBrowserTesting, Sauce Labs, and TestingBot. Basic usage for each of these is provided in the following sections.

💡 Cloud hosts typically have their own unique capabilities options, so be sure to read the capabilities documentation for the provider you’re using.

BrowesrStack

  1. Sign up for BrowserStack Automate
  2. Get your Automate username and password from the Automate account settings page
  3. Set the tunnel config property to 'browserstack'
  4. Set your username and access key in one of these ways:
    • Define BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY environment variables
    • Set browserstackUsername and browserstackAccessKey in your Gruntfile’s intern task options
    • Set username and accessKey on your tunnelOptions configuration option
  5. Run Intern

CrossBrowserTesting

  1. Sign up for a trial account
  2. Get your authkey from your account settings page
  3. Set the tunnel config property to 'cbt'
  4. Set your username and access key in one of these ways:
    • Define CBT_USERNAME and CBT_APIKEY environment variables
    • Set cbtUsername and cbtApikey in your Gruntfile’s intern task options
    • Set username and accessKey on your tunnelOptions configuration option
  5. Run Intern

Sauce Labs

  1. Sign up for a Sauce Labs account
  2. Get your master account access key from the sidebar of the Account settings page, or create a separate sub-account on the sub-accounts page and get a username and access key from there
  3. Set the tunnel config property to 'saucelabs'
  4. Set your username and access key in one of these ways:
    • Define SAUCE_USERNAME and SAUCE_ACCESS_KEY environment variables
    • Set sauceUsername and sauceAccessKey in your Gruntfile’s intern task options
    • Set username and accessKey on your tunnelOptions configuration option
  5. Run Intern

TestingBot

  1. Sign up for a TestingBot account
  2. Get your API key and secret from the Account settings page
  3. Set the tunnel config property to 'testingbot'
  4. Set your API key and secret in one of these ways:
    • Define TESTINGBOT_KEY and TESTINGBOT_SECRET environment variables
    • Set testingbotKey and testingbotSecret in your Gruntfile’s intern task options
    • Set username and accessKey on your tunnelOptions configuration option
  5. Run Intern