add a link to the design doc

[cnishina]

No description provided.

[cnishina]

Doc not ready. Here's a snippet

Objective

Protractor is the go-to e2e solution for Angular and AngularJS. The APIs are well documented and easy to use. However, Protractor will have a lot of bloat since selenium webdriver has removed/deprecated the control flow. There are several options to update Protractor. We could deprecate the angular/jasmine-wd usage and remove portions of code that rely on these features. Alternatively, we could do a rewrite maintaining the Protractor API but improve its maintainability.

Why it is time to rewrite Protractor:

• Decouple the Protractor framework and the cli. Decoupling the framework will help us run tests in google3 without a harness
• Add unit and integration tests. Currently most of the tests rely on testing Protractor as an e2e suite. In addition to support for Angular, we should also add support for other popular web frameworks like react and vue.
• Improve the google import process. This should be imported similar to the Angular repo. In addition we should add BUILD rules with Bazel.

[cnishina]

Not making it public. Right now we will just keep to some of the above goals. Might be good to put this as part of the general documentation?