https://github.com/qualityshepherd/protractor-example

Example protractor project that uses page objects...
https://github.com/qualityshepherd/protractor-example

javascript protractor selenium-webdriver testing webdriver

Last synced: 27 days ago
JSON representation

Example protractor project that uses page objects...

• Host: GitHub
• URL: https://github.com/qualityshepherd/protractor-example
• Owner: qualityshepherd
• Created: 2014-09-20T17:10:17.000Z (about 10 years ago)
• Default Branch: main
• Last Pushed: 2023-06-16T18:03:09.000Z (over 1 year ago)
• Last Synced: 2024-09-29T02:01:45.404Z (about 1 month ago)
• Topics: javascript, protractor, selenium-webdriver, testing, webdriver
• Language: JavaScript
• Size: 138 KB
• Stars: 92
• Watchers: 16
• Forks: 98
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Protractor Example

Herein lies an example [Protractor](http://protractortest.org) project, that includes tests (some quite silly) that aim to illustrate solutions for common issues when writing e2e tests.

## Example Protractor project that:

* Makes use of page objects

* Runs tests on [Sauce Labs](http://saucelabs.com)

* Runs multiple browsers at once

* Runs tests sharded (parallel)

* Includes examples tests for both Angular, and non-Angular applications

* Uses [protractor-flake](https://github.com/NickTomlin/protractor-flake) to re-run failed tests

* is written using es6

## Setup:

* Install [Node](http://nodejs.org) (v8.x.x or later)

* `git clone [email protected]:qualityshepherd/protractor-example.git`

* `npm i` to install the project dependencies

## Run tests:

* run tests via plain Protractor `node_modules/.bin/protractor conf.js`

* run tests `npm test` (runs via flake, which re-runs failed tests)

* run with flake `./flake conf.js`

* run on saucelabs`./flake sauceConf.js` (add your username/key)

Or if you're a non-reader, [watch the video...](https://www.youtube.com/watch?v=JIGvty1bQxk)

## Troubleshooting

* run `node -v` and make sure your node version is 8.x.x or greater

* `webdriver-manager` _should_ have updated on install, but if not, run `npm run update` to be sure