Gulp Protractor QA warns you on the fly whether all element() selectors could be found or not within your AngularJS view files.
Keeping end-to-end tests up-to-date can be really painful. Gulp Protractor QA warns you on the fly whether all element() selectors could be found or not within your application view files.
TL;DR: a couple of new features and fixes have been added since this screencast publication.
npm install --save-dev gulp-protractor-qa
var gulp = ;var protractorQA = ;
Registering the task
Optional: Set to
true when you want to control yourself when to run task.
In other words, it won't watch files changes.
Where the plugin should watch the changes in order to map all
Where your AngularJS view files are located. Protractor QA will watch the changes in those files to verify if all
element() selectors could be found.
Gulp-protractor-qa is currently watching the following
Note: currently it can't find
by.css() selectors with
0.2.0 api completely rewritten, including:
0.1.18 bug fix: adding support for
0.1.14 showing "
<number> out of
<total> element selectors are been watched" in the log;
0.1.12 bug fix related to
viewSrc now receive
0.1.0 Mapping just two