End-to-end test suite making use of state objects.

[avandeursen]

Re-implementation of the Angular Phonecat Protractor test scenarios.

This reimplementation has two 'state objects', which are page-objects derived from a state machine. The actual statechart used is shown below.

As a result, the scenarios themselves are more robust and easier to follow, since the protractor details are hidden in the state objects. Furthermore, the diagram guides the design of the actual scenarios.

Note that the state object methods return promises.

See also:

• My short blog post Beyond Page Objects briefly explaining the use of state objects.
• My ACM Queue article Beyond Page Objects: Testing Web Applications with State Objects.
• That same article in the Communications of the ACM: Testing Web Applications with State Objects.

[avandeursen]

Note: This pull request thankfully uses @felthat's fix to the original protractor test suite available from angular#267.

That fix is unrelated to the use of page/state objects, but just need to get the tests working in the first place.