test(e2e): run instrumentation against live sites running Angular

[btford]

To avoid ever releasing a problematic version of Batarang again, I want to run the instrumentation code against a few Angular production apps.

Here's my list of apps:

• https://console.developers.google.com/project
• http://www.istockphoto.com/
• https://docs.angularjs.org
• https://angularjs.org
• https://www.virginamerica.com/
• http://plnkr.co/

Here are my pending tasks for implementing these tests:

• Find a way to have webdriver (via protractor) launch a specific profile of Chrome
• Run these tests before releases, and periodically (maybe once a day) to account for changes in these production apps

I'll need to strike a balance between making tests comprehensive, yet easy to maintain if the app changes in production. The benefit of having better integration tests needs to outweigh the cost of keeping them up-to-date.

[jkirkpatrick]

I think some simple sanity checks will go a long way without reducing flexibility. If any of the sites listed undergo a major change and it breaks these tests, that test should be quickly removed or replaced without too much pain. The required tests against those sites seem to be fairly simple and probably should stay that way.

I can/have started:

• https://angularjs.org - use the example on the homepage / protractor example (Protractor tests with multiple chrome profiles #197)
• https://docs.angularjs.org - simple check/visit, should find searchbox and navigation
• http://www.istockphoto.com/ - search for "batarang" should return images (currently 2)
• http://plnkr.co/edit/?p=catalogue - suggestions for validating???
• https://www.virginamerica.com/ - search for trip???

The google redirects to non-angularjs login page if there isn't a session/login, unlike the others.