Random Thoughts On Protractor
Killing time awaiting my carpool The issue End to end automated testing. I won't get in to the value of this activity. I will simply say that I am faced with a requirement to implement an end to end testing solution that will serve as one of our final release gates. The basic structure is a set of tests that simulate minimal user browser input, tracks the flow through our code base, and evaluates the responses from the live downstream systems. These tests will pass or fail, but there is no guarantee of stability. These tests will fail frequently. Failures will not break the release gate, they will simply be an indication that someone needs to review the results in order to evaluate the health of the product. The tests will be limited to one instance each of the user critical workflows. This means a grand total of somewhere between 9 and 12 tests for ever...until such time that a distinctly new feature is introduced. The Features After some discussion we came up with a set