UI Automation Success: Keeping Pace with Product Evolution
Team A's application is evolving fast. Team B is switching UI frameworks (jQuery to Angular). Team C is migrating an applet application to web. Team D is extending a web app to mobile. Can automation help in the following scenarios? Ideally it should.
When applications evolve, test automation code starts failing. If tests are not fixed quickly, automation code becomes stale and the whole suite becomes unusable.
Changes to applications follow specific patterns. Knowing these patterns helps create automation frameworks which can handle them easily. In this talk, through live examples, we will see various ways in which web applications evolve, how they break automation code, and how we can structure the automation code such that there is minimal change required to accommodate changes.
Outline/structure of the Session
We take you through the following:
- Where automation should help. What problems should it solve
- In such problems what are the recurring changes? What patterns do they follow?
- Breaking down automation code into layers
- Demo of an application undergoing changes and how the layers of automation code handle them
The talk should help in understanding patterns of changes in evolving applications and how automation code can be structured to be in step with the product. It helps in understanding what is possible and how efforts can be channeled in teams.
1) Members of agile teams, who do test automation. 2) Decision makers who are looking for process optimization in their testing.