The document discusses end-to-end (E2E) testing using Protractor. It explains that Protractor allows testing applications like a real user would by running tests in a browser. It also supports features like automatic waiting and Angular-specific locators. The document provides instructions on setting up Protractor, test file structure, writing tests, running specific test suites, enabling multiple browsers, using onPrepare, and parameters. It notes that Protractor can also be used for non-Angular applications by accessing the webdriver directly.

1. Weavora Consulting LLC
Writing end-to-end tests has never been so fun

2. Whats the idea behind E2E testing?
How would the users see my application?
Is my backend communicating with my frontend?
Can I release this code?
It does NOT replace Unit Testing!

4. Why protractor???
Test Like a User
Protractor runs tests against your application running in a real browser, interacting with it
as a user would.
For AngularJS Apps
Protractor supports Angular-specific locator strategies.
Also we can decrease size of code. For example on php looks like:
on js:

5. Why protractor???
Automatic Waiting!!!
You no longer need to add waits and sleeps to your test. Protractor can
automatically execute the next step in your test the moment the
webpage finishes pending tasks, so you don’t have to worry about
waiting for your test and webpage to sync.

6. Setup
npm install -g protractor
Try running protractor --version to make sure it's working ( I’ve following version : 2.0.0 )
Install webdriver if it needed:
webdriver-manager update
webdriver-manager start

7. Tests directory structure

8. Write a test
Protractor needs two files to run, a spec file and a
configuration file.
For example spec.js:
The describe and it syntax is from the Jasmine framework

9. Write a test
And conf.js

10. Separate your tests in various test suites
Running specific suite of tests
protractor protractor.conf.js --suite homepage

11. Enable multiCapabilities

12. Using onPrepare
Set window size before starting the tests

13. Using params
Your config.js

14. Using params
Your test

15. "But, I want to use
Protractor in a non-
AngularJS app"

16. You only need to access the webdriver instance by
using browser.driver:

17. You only need to access the webdriver
instance by using browser.driver:
In your config.js
In your test

18. E2E testing is a complement to Unit testing
Avoid using CSS attributes
It’s hard to write
Just have fun testing with Protractor
Final thoughts

19. Any questions?