Skip to content

Record, export and run tests with protractor for angular and non angular webapps

License

Notifications You must be signed in to change notification settings

magestican/protractor-recorder

 
 

Repository files navigation

Protractor Recorder

A web interface to record interactions and export to Protractor.

Demonstration

Example with more three interactions. This demo shows assertive with failure and success, after editing the value inside last action.

Alt Text

Features

General options

  • Base URL;
  • Run speed;
  • List of available drivers;

Record

  • Clicks on elements;
  • Send keys to inputs;
  • Assertions with mouse selection;
  • Mouse moves;
  • Duplicate actions;
  • Drag and drop actions to reorder;
  • Run actions while recording with 'Run from here' option.

Export

  • Selenium Address;
  • Window maximize;
  • Tests with login pages;

Dependencies

  • NodeJs 4.x;
  • Npm 2.x;
  • Bower 1.x;
  • Gulp 3.x;
  • Protractor 3.x.

Getting Started

After install all dependencies successfully, clone this repository and change directory to 'protractor-recorder':

$ git clone https://github.com/ealves/protractor-recorder.git
$ cd protractor-recorder

Execute the following commands to install npm and bower dependencies to Protractor Recorder:

$ npm install
$ bower install

Installing openssl is required to run the server over https and test https websites:

https://wiki.openssl.org/index.php/Binaries

Running Protractor Recorder

Now you will need run two different process, following the order:

#1 - Selenium Webdriver Manager

  • First, start selenium with Protractor Webdriver Manager:
$ webdriver-manager start

#2 - Protractor Recorder Material Interface

  • Start the Angular Material web interface, run:
$ gulp

Usage

  • Access http://localhost:3002/app
  • Enter a url base and click on 'Record' to start recording
  • After end up your test flow on Selenium browser's session, click on 'Export' to export conf.js and spec.js inside folder public/exports.
  • Click on 'Run' to see your test running with a new Selenium session.

Possible issues running webdriver-manager on versions of Chrome 58+ (connection errors) are fixed by forcing webdriver to update :

  • This will force download webdriver 2.29 : webdriver-manager update --versions.chrome 2.29

  • This will force webdriver-manager to use 2.29 : webdriver-manager start --versions.chrome 2.29

About

Record, export and run tests with protractor for angular and non angular webapps

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 73.7%
  • HTML 26.3%