Skip to main content

Config

Protractor configuration object with an additional section to configure the Serenity/JS framework.

Learn more

Hierarchy

  • Config
    • Config

Index

Properties

Properties

externaloptionalseleniumServerJar

seleniumServerJar?: string

The location of the standalone Selenium Server jar file, relative to the location of webdriver-manager. If no other method of starting Selenium Server is found, this will default to node_modules/protractor/node_modules/webdriver-manager/selenium/

<jar file>

externaloptionalseleniumServerStartTimeout

seleniumServerStartTimeout?: number

The timeout milliseconds waiting for a local standalone Selenium Server to start.

default: 30000ms

externaloptionallocalSeleniumStandaloneOpts

localSeleniumStandaloneOpts?: { port?: any; args?: any; jvmArgs?: string[] }

Can be an object which will be passed to the SeleniumServer class as args. See a full list of options at https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/remote/index.js If you specify args or port in this object, it will overwrite the values set via the deprecated config values seleniumPort and seleniumArgs.

Type declaration

  • externaloptionalport?: any

    The port to start the Selenium Server on, or null if the server should find its own unused port.

  • externaloptionalargs?: any

    Additional command line options to pass to selenium. For example, if you need to change the browser timeout, use seleniumArgs: [‘-browserTimeout=60’]

  • externaloptionaljvmArgs?: string[]

    Additional command line jvm options to pass to selenium. For example, if you need to change the browser driver, use jvmArgs: [‘-Dwebdriver.ie.driver=IEDriverServer_Win32_2.53.1.exe’]

externaloptionalchromeDriver

chromeDriver?: string

ChromeDriver location is used to help find the chromedriver binary. This will be passed to the Selenium jar as the system property webdriver.chrome.driver. If the value is not set when launching locally, it will use the default values downloaded from webdriver-manager.

example: chromeDriver: ‘./node_modules/webdriver-manager/selenium/chromedriver_2.20’

externaloptionalgeckoDriver

geckoDriver?: string

geckoDriver location is used to help find the gecko binary. This will be passed to the Selenium jar as the system property webdriver.gecko.driver. If the value is not set when launching locally, it will use the default values downloaded from webdriver-manager.

externaloptionalseleniumAddress

seleniumAddress?: string

The address of a running Selenium Server. If specified, Protractor will connect to an already running instance of Selenium. This usually looks like seleniumAddress: ‘http://localhost:4444/wd/hub‘

externaloptionalseleniumSessionId

seleniumSessionId?: string

The selenium session id allows Protractor to attach to an existing selenium browser session. The selenium session is maintained after the test has completed. Ignored if seleniumAddress is null.

externaloptionalsauceProxy

sauceProxy?: string

The address of a proxy server to use for communicating to Sauce Labs REST APIs via the saucelabs node module. For example, the Sauce Labs Proxy can be setup with: sauceProxy: ‘http://localhost:3128‘

externaloptionalwebDriverProxy

webDriverProxy?: string

The proxy address that WebDriver (e.g. Selenium commands) traffic will go through which is tied to the browser session.

externaloptionaluseBlockingProxy

useBlockingProxy?: boolean

If specified, connect to webdriver through a proxy that manages client-side synchronization. Blocking Proxy is an experimental feature and may change without notice.

externaloptionalblockingProxyUrl

blockingProxyUrl?: string

If specified, Protractor will connect to the Blocking Proxy at the given url instead of starting it’s own.

externaloptionalsauceUser

sauceUser?: string

If the sauceUser and sauceKey are specified, seleniumServerJar will be ignored. The tests will be run remotely using Sauce Labs.

externaloptionalsauceKey

sauceKey?: string

If the sauceUser and sauceKey are specified, seleniumServerJar will be ignored. The tests will be run remotely using Sauce Labs.

externaloptionalsauceRegion

sauceRegion?: string

If you run your tests on SauceLabs you can specify the region you want to run your tests in via the sauceRegion property. Available short handles for regions are: us: us-west-1 (default) eu: eu-central-1

externaloptionalsauceAgent

sauceAgent?: any

Use sauceAgent if you need custom HTTP agent to connect to saucelabs.com APIs. This is needed if your computer is behind a corporate proxy.

To match sauce agent implementation, use HttpProxyAgent to generate the agent or use sauceProxy as an alternative. If a sauceProxy is provided, the sauceAgent will be overridden.

externaloptionalsauceBuild

sauceBuild?: string

Use sauceBuild if you want to group test capabilites by a build ID

externaloptionalsauceSeleniumUseHttp

sauceSeleniumUseHttp?: boolean

If true, Protractor will use http:// protocol instead of https:// to connect to Sauce Labs defined by sauceSeleniumAddress.

default: false

externaloptionalsauceSeleniumAddress

sauceSeleniumAddress?: string

Use sauceSeleniumAddress if you need to customize the URL Protractor uses to connect to sauce labs (for example, if you are tunneling selenium traffic through a sauce connect tunnel). Default is ondemand.saucelabs.com:443/wd/hub

externaloptionaltestobjectUser

testobjectUser?: string

If testobjectUser and testobjectKey are specified, kobitonUser, kobitonKey, browserstackUser, browserStackKey and seleniumServerJar will be ignored. The tests will be run remotely using TestObject.

externaloptionaltestobjectKey

testobjectKey?: string

If testobjectUser and testobjectKey are specified, kobitonUser, kobitonKey, browserStackUser, browserStackKey and seleniumServerJar will be ignored. The tests will be run remotely using TestObject.

externaloptionalkobitonUser

kobitonUser?: string

If kobitonUser and kobitonKey are specified, testobjectUser, testojbectKey, browserstackUser, browserStackKey and seleniumServerJar will be ignored. The tests will be run remotely using TestObject.

externaloptionalkobitonKey

kobitonKey?: string

If kobitonUser and kobitonKey are specified, testobjectUser, testojbectKey, browserStackUser, browserStackKey and seleniumServerJar will be ignored. The tests will be run remotely using TestObject.

externaloptionalbrowserstackUser

browserstackUser?: string

If browserstackUser and browserstackKey are specified, seleniumServerJar will be ignored. The tests will be run remotely using BrowserStack.

externaloptionalbrowserstackKey

browserstackKey?: string

If browserstackUser and browserstackKey are specified, seleniumServerJar will be ignored. The tests will be run remotely using BrowserStack.

externaloptionalbrowserstackProxy

browserstackProxy?: string

Proxy server to be used for connecting to BrowserStack APIs e.g. “http://proxy.example.com:1234“. This should be used when you are behind a proxy server.

externaloptionaldirectConnect

directConnect?: boolean

If true, Protractor will connect directly to the browser Drivers at the locations specified by chromeDriver and firefoxPath. Only Chrome and Firefox are supported for direct connect.

default: false

externaloptionalfirefoxPath

firefoxPath?: string

Path to the firefox application binary. If null, will attempt to find firefox in the default locations.

externaloptionalseleniumWebDriver

seleniumWebDriver?: WebDriver

externaloptionalnoGlobals

noGlobals?: boolean

Use default globals: ‘protractor’, ‘browser’, ‘$’, ‘$$’, ‘element’, ‘by’. These also exist as properties of the protractor namespace: ‘protractor.browser’, ‘protractor.$’, ‘protractor.$$’, ‘protractor.element’, ‘protractor.by’, and ‘protractor.By’.

When no globals is set to true, the only available global variable will be ‘protractor’.

externaloptionalspecs

specs?: string[]

Required. Spec patterns are relative to the location of this config.

Example: specs: [ ‘spec/*_spec.js’ ]

externaloptionalexclude

exclude?: string | string[]

Patterns to exclude specs.

externaloptionalsuites

suites?: any

Alternatively, suites may be used. When run without a command line parameter, all suites will run. If run with –suite=smoke or –suite=smoke,full only the patterns matched by the specified suites will run.

Example: suites: { smoke: ‘spec/smoketests/.js’, full: ‘spec/.js’ }

externaloptionalsuite

suite?: string

If you would like protractor to use a specific suite by default instead of all suites, you can put that in the config file as well.

externaloptionalcapabilities

capabilities?: { browserName?: string; name?: string; logName?: string; count?: number; shardTestFiles?: boolean; maxInstances?: number; specs?: string[]; exclude?: string[]; seleniumAddress?: string }

Protractor can launch your tests on one or more browsers. If you are testing on a single browser, use the capabilities option. If you are testing on multiple browsers, use the multiCapabilities array.

For a list of available capabilities, see https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities In addition, you may specify count, shardTestFiles, and maxInstances.

Example: capabilities: { browserName: ‘chrome’, name: ‘Unnamed Job’, logName: ‘Chrome - English’, count: 1, shardTestFiles: false, maxInstances: 1, specs: [‘spec/chromeOnlySpec.js’], exclude: [‘spec/doNotRunInChromeSpec.js’], seleniumAddress: ‘http://localhost:4444/wd/hub‘ }

Type declaration

  • [key string]: any
  • externaloptionalbrowserName?: string
  • externaloptionalname?: string

    Name of the process executing this capability. Not used directly by protractor or the browser, but instead pass directly to third parties like BrowserStack and SauceLabs as the name of the job running this test

  • externaloptionallogName?: string

    User defined name for the capability that will display in the results log. Defaults to the browser name

  • externaloptionalcount?: number

    Number of times to run this set of capabilities (in parallel, unless limited by maxSessions). Default is 1.

  • externaloptionalshardTestFiles?: boolean

    If this is set to be true, specs will be sharded by file (i.e. all files to be run by this set of capabilities will run in parallel). Default is false.

  • externaloptionalmaxInstances?: number

    Maximum number of browser instances that can run in parallel for this set of capabilities. This is only needed if shardTestFiles is true. Default is 1.

  • externaloptionalspecs?: string[]

    Additional spec files to be run on this capability only.

  • externaloptionalexclude?: string[]

    Spec files to be excluded on this capability only.

  • externaloptionalseleniumAddress?: string

    Optional: override global seleniumAddress on this capability only.

externaloptionalmultiCapabilities

multiCapabilities?: any[]

If you would like to run more than one instance of WebDriver on the same tests, use multiCapabilities, which takes an array of capabilities. If this is specified, capabilities will be ignored.

externaloptionalgetMultiCapabilities

getMultiCapabilities?: any

If you need to resolve multiCapabilities asynchronously (i.e. wait for server/proxy, set firefox profile, etc), you can specify a function here which will return either multiCapabilities or a promise to multiCapabilities.

If this returns a promise, it is resolved immediately after beforeLaunch is run, and before any driver is set up. If this is specified, both capabilities and multiCapabilities will be ignored.

externaloptionalmaxSessions

maxSessions?: number

Maximum number of total browser sessions to run. Tests are queued in sequence if number of browser sessions is limited by this parameter. Use a number less than 1 to denote unlimited. Default is unlimited.

externaloptionalverboseMultiSessions

verboseMultiSessions?: boolean

Whether or not to buffer output when running tests on multiple browsers in parallel. By default, when running multiple browser sessions, the results are buffered and not logged until the test run finishes. If true, when running multiple sessions in parallel results will be logged when each test finishes.

externaloptionalbaseUrl

baseUrl?: string

A base URL for your application under test. Calls to protractor.get() with relative paths will be resolved against this URL (via url.resolve)

externaloptionalrootElement

rootElement?: string

A CSS Selector for a DOM element within your Angular application. Protractor will attempt to automatically find your application, but it is necessary to set rootElement in certain cases.

In Angular 1, Protractor will use the element your app bootstrapped to by default. If that doesn’t work, it will then search for hooks in body or ng-app elements (details here: https://git.io/v1b2r).

In later versions of Angular, Protractor will try to hook into all angular apps on the page. Use rootElement to limit the scope of which apps Protractor waits for and searches within.

externaloptionalallScriptsTimeout

allScriptsTimeout?: number

The timeout in milliseconds for each script run on the browser. This should be longer than the maximum time your application needs to stabilize between tasks.

externaloptionalgetPageTimeout

getPageTimeout?: number

How long to wait for a page to load.

externaloptionalbeforeLaunch

beforeLaunch?: () => void

Type declaration

    • (): void

    • A callback function called once configs are read but before any environment setup. This will only run once, and before onPrepare.

      You can specify a file containing code to run by setting beforeLaunch to the filename string.

      At this point, global variable ‘protractor’ object will NOT be set up, and globals from the test framework will NOT be available. The main purpose of this function should be to bring up test dependencies.

      Returns void

externaloptionalonPrepare

onPrepare?: () => void

Type declaration

    • (): void

    • A callback function called once protractor is ready and available, and before the specs are executed. If multiple capabilities are being run, this will run once per capability.

      You can specify a file containing code to run by setting onPrepare to the filename string. onPrepare can optionally return a promise, which Protractor will wait for before continuing execution. This can be used if the preparation involves any asynchronous calls, e.g. interacting with the browser. Otherwise Protractor cannot guarantee order of execution and may start the tests before preparation finishes.

      At this point, global variable ‘protractor’ object will be set up, and globals from the test framework will be available. For example, if you are using Jasmine, you can add a reporter with:

      jasmine.getEnv().addReporter(new jasmine.JUnitXmlReporter( ‘outputdir/‘, true, true));

      If you need access back to the current configuration object, use a pattern like the following:

      return browser.getProcessedConfig().then(function(config) { // config.capabilities is the CURRENT capability being run, if // you are using multiCapabilities. console.log(‘Executing capability’, config.capabilities); });

      Returns void

externaloptionalonComplete

onComplete?: () => void

Type declaration

    • (): void

    • A callback function called once tests are finished. onComplete can optionally return a promise, which Protractor will wait for before shutting down webdriver.

      At this point, tests will be done but global objects will still be available.

      Returns void

externaloptionalonCleanUp

onCleanUp?: (exitCode: number) => void

Type declaration

    • (exitCode: number): void

    • A callback function called once the tests have finished running and the WebDriver instance has been shut down. It is passed the exit code (0 if the tests passed). This is called once per capability.

      Parameters

      • externalexitCode: number

      Returns void

externaloptionalafterLaunch

afterLaunch?: (exitCode: number) => void

Type declaration

    • (exitCode: number): void

    • A callback function called once all tests have finished running and the WebDriver instance has been shut down. It is passed the exit code (0 if the tests passed). afterLaunch must return a promise if you want asynchronous code to be executed before the program exits. This is called only once before the program exits (after onCleanUp).

      Parameters

      • externalexitCode: number

      Returns void

externaloptionalparams

params?: any

The params object will be passed directly to the Protractor instance, and can be accessed from your test as browser.params. It is an arbitrary object and can contain anything you may need in your test. This can be changed via the command line as: –params.login.user “Joe”

Example: params: { login: { user: ‘Jane’, password: ‘1234’ } }

externaloptionalresultJsonOutputFile

resultJsonOutputFile?: any

If set, protractor will save the test output in json format at this path. The path is relative to the location of this config.

externaloptionalrestartBrowserBetweenTests

restartBrowserBetweenTests?: boolean

If true, protractor will restart the browser between each test. Default value is false.

CAUTION: This will cause your tests to slow down drastically.

externaloptionaluntrackOutstandingTimeouts

untrackOutstandingTimeouts?: boolean

Protractor will track outstanding $timeouts by default, and report them in the error message if Protractor fails to synchronize with Angular in time. In order to do this Protractor needs to decorate $timeout.

CAUTION: If your app decorates $timeout, you must turn on this flag. This is false by default.

externaloptionalignoreUncaughtExceptions

ignoreUncaughtExceptions?: boolean

If set, Protractor will ignore uncaught exceptions instead of exiting without an error code. The exceptions will still be logged as warnings.

externaloptionalwebDriverLogDir

webDriverLogDir?: string

If set, will create a log file in the given directory with a readable log of the webdriver commands it executes.

This is an experimental feature. Enabling this will also turn on Blocking Proxy synchronization, which is also experimental.

externaloptionalhighlightDelay

highlightDelay?: number

If set, Protractor will pause the specified amount of time (in milliseconds) before interactions with browser elements (ie, sending keys, clicking). It will also highlight the element it’s about to interact with.

This is an experimental feature. Enabling this will also turn on Blocking Proxy synchronization, which is also experimental.

externaloptionallogLevel

logLevel?: ERROR | WARN | INFO | DEBUG

Protractor log level

default: INFO

externaloptionalframework

framework?: string

Test framework to use. This may be one of: jasmine, mocha or custom. Default value is ‘jasmine’

When the framework is set to “custom” you’ll need to additionally set frameworkPath with the path relative to the config file or absolute:

framework: ‘custom’, frameworkPath: ‘./frameworks/my_custom_jasmine.js’,

See github.com/angular/protractor/blob/master/lib/frameworks/README.md to comply with the interface details of your custom implementation.

Jasmine is fully supported as test and assertion frameworks. Mocha has limited support. You will need to include your own assertion framework (such as Chai) if working with Mocha.

externaloptionaljasmineNodeOpts

jasmineNodeOpts?: { showColors?: boolean; defaultTimeoutInterval?: number; print?: () => void; grep?: string; invertGrep?: boolean; random?: boolean; seed?: string }

Options to be passed to jasmine.

See https://github.com/jasmine/jasmine-npm/blob/master/lib/jasmine.js for the exact options available.

Type declaration

  • [key string]: any
  • externaloptionalshowColors?: boolean

    If true, print colors to the terminal.

  • externaloptionaldefaultTimeoutInterval?: number

    Default time to wait in ms before a test fails.

  • externaloptionalprint?: () => void
      • (): void

      • Function called to print jasmine results.

        Returns void

  • externaloptionalgrep?: string

    If set, only execute specs whose names match the pattern, which is internally compiled to a RegExp.

  • externaloptionalinvertGrep?: boolean

    Inverts ‘grep’ matches

  • externaloptionalrandom?: boolean

    If true, run specs in semi-random order

  • externaloptionalseed?: string

    Set the randomization seed if randomization is turned on

externaloptionalmochaOpts

mochaOpts?: { ui?: string; reporter?: string }

Options to be passed to Mocha.

See the full list at http://mochajs.org/

Type declaration

  • [key string]: any
  • externaloptionalui?: string
  • externaloptionalreporter?: string

externaloptionalplugins

plugins?: PluginConfig[]

See docs/plugins.md

externaloptionalskipSourceMapSupport

skipSourceMapSupport?: boolean

Turns off source map support. Stops protractor from registering global variable source-map-support. Defaults to false

externaloptionaldisableEnvironmentOverrides

disableEnvironmentOverrides?: boolean

Turns off WebDriver’s environment variables overrides to ignore any environment variable and to only use the configuration in this file. Defaults to false

externaloptionalng12Hybrid

ng12Hybrid?: boolean

Tells Protractor to interpret any angular apps it comes across as hybrid angular1/angular2 apps (i.e. apps using ngUpgrade) Defaults to false

externaloptionaldisableChecks

disableChecks?: boolean

Protractor will exit with an error if it sees any command line flags it doesn’t recognize. Set disableChecks true to disable this check.

externaloptionalSELENIUM_PROMISE_MANAGER

SELENIUM_PROMISE_MANAGER?: boolean

Enable/disable the WebDriver Control Flow.

WebDriverJS (and by extention, Protractor) uses a Control Flow to manage the order in which commands are executed and promises are resolved (see docs/control-flow.md for details). However, as syntax like async/await are being introduced, WebDriverJS has decided to deprecate the control flow, and have users manage the asynchronous activity themselves (details here: https://github.com/SeleniumHQ/selenium/issues/2969).

At the moment, the WebDriver Control Flow is still enabled by default. You can disable it by setting the environment variable SELENIUM_PROMISE_MANAGER to 0. In a webdriver release in Q4 2017, the Control Flow will be disabled by default, but you will be able to re-enable it by setting SELENIUM_PROMISE_MANAGER to 1. At a later point, the control flow will be removed for good.

If you don’t like managing environment variables, you can set this option in your config file, and Protractor will handle enabling/disabling the control flow for you. Setting this option is higher priority than the SELENIUM_PROMISE_MANAGER environment variable.

externaloptionalseleniumArgs

seleniumArgs?: any[]

externaloptionaljvmArgs

jvmArgs?: string[]

externaloptionalconfigDir

configDir?: string

externaloptionaltroubleshoot

troubleshoot?: boolean

externaloptionalseleniumPort

seleniumPort?: number

externaloptionalmockSelenium

mockSelenium?: boolean

externaloptionalv8Debug

v8Debug?: any

externaloptionalnodeDebug

nodeDebug?: boolean

externaloptionaldebuggerServerPort

debuggerServerPort?: number

externaloptionalframeworkPath

frameworkPath?: string

externaloptionalelementExplorer

elementExplorer?: any

externaloptionaldebug

debug?: boolean

externaloptionalunknownFlags_

unknownFlags_?: string[]

serenity

serenity: SerenityConfig & { runner?: string }

See SerenityConfig