Add e2e tests
To run end to end tests:
- Start up the webpack dev server with either gulp serve or gulp watch.
- Run "npm run e2e" to get automated tests. By just running "protractor" in the root directory, you will see test logs with greater verbosity.
E2E Test Generator
I've added a component e2e test file generator, and updated the component module generator with a default route of the component name. In order for the component to be tested, two tasks must still be accomplished.
- New component must be added to the components.js file.
- There must be a link to the route somewhere in the app for ui-router to recognize it.
How about now, guys?
Removed extraneous code, added environment variables, using relative paths, and the developer experience is so much better.
gulp e2e
- bundles our source with webpack
- serves a webserver
- updates selenium
- runs selenium
- runs protractor (with verbosity this time!)
- exits process after protractor is finished
npm e2e
- Runs gulp e2e
update on this ? Ive used most of this stuff and I can get the protractor to run properly, but as you say, when used with gulp it doesnt want to exit..
I currently working on getting rid of gulp completely. This will simplify stuff.
Do we have a working version of the latest here? Curious...