NOTE: This fork of Protractor supports AngularDart (for use with protractor-dart) and may not work reliably with AngularJS.
Protractor is an end to end test framework for AngularJS applications built on top of WebDriverJS. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
Protractor can be run as a standalone binary, or included into your tests as a library. Use Protractor as a library if you would like to manage WebDriver and your test setup yourself.
For more information
To run the sample tests
Install protractor with.
npm install -g protractor
Start up a selenium server (See the appendix below for help with this). By default, the tests expect the selenium server to be running at
The node module's example folder contains a simple test suite which runs against angularjs.org. Run with:
Using the Protractor runner
The Protractor runner is a binary which accepts a config file. Install protractor with
npm install -g protractor # Run the line below to see command line options protractor
You will need a configuration file containing setup info and test files containing the actual test scripts. The config file specifies how the runner should start webdriver, where your test files are, and global setup options. The test files use Jasmine framework by default (read about using mocha instead).
Create a configuration file - an example with detailed comments is shown in
node_modules/protractor/referenceConf.js. Edit the configuration file to point to your test files.
// myConf.jsexportsconfig =seleniumAddress: ''specs: 'myTest.js' 'myTestFolder/*Test.js'
The configuration file must specify a way to connect to webdriver. This can be
seleniumAddress: The address of a running selenium server.
seleniumServerJar: The location of the selenium standalone .jar file on your machine. Protractor will use this to start up the selenium server.
sauceKey: The username and key for a SauceLabs account. Protractor will use this to run tests on SauceLabs. If none of the above are specific, Protractor will try to start the standalone .jar from the default location in node_modules/protractor/selenium.
The runner exposes global variables
element. Check out getting started docs to learn how to write a test.
Cloning and running Protractor's own tests
Clone the github repository.
git clone https://github.com/angular/protractor.git cd protractor npm install
Start up a selenium server. By default, the tests expect the selenium server to be running at
Protractor's test suite runs against the included testapp. Start that up with
Then run the tests with
Appendix A: Setting up a standalone selenium server
WebdriverJS does not natively include the selenium server - you must start a standalone selenium server. All you need is the latest selenium-server-standalone.. To drive individual browsers, you may need to install separate driver binaries.
webdriver-manager script is included in the npm package to manage downloads for you. To see the options, run
npm install -g protractor webdriver-manager
Download and start the selenium server with
webdriver-manager update webdriver-manager start
Note the Java Development Kit (JDK) is also required to run the webdriver. You may have to download and install it if your computer does not already have it.
For alternate ways to download and start the selenium standalone, see the webdriver docs.