UI Automation: Keeping Pace with Product Evolution
summary
Examines how UI automation breaks as web apps change (e.g., jQuery→Angular rewrites, applet→web migrations, web→mobile extensions) and identifies recurrent change patterns. Demonstrates, with live examples, techniques for structuring automation code and frameworks so tests require minimal updates when the underlying UI or framework evolves.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:11UI Automation Success: Keeping Pace with Product Evolution
- 8:42Time needed depends on effort/people • Automation tasks and effort -Creation (manual and machine) -Execution (machine) -Reporting (machine)
- 12:28Maximize ability to contribute - Version Control • Use non binary files. eg. CSV instead of Excel -Smaller, role specific files
- 35:18Expresses business intent • Agnostic of - web application itself -Testing tool - interaction code
- 43:08Central repository of all elements in the automation code
- 43:19Demo of working application and automation code
related talks
53mAdvanced Patterns for Automated UI Testing
08mEvolving of test automation past to present
48mChallenges in UI Automation and How to Solve Them
27mKnowing your automation
54mThe Zen of UI Test Automation
55mModern Web Testing: Going Beyond Selenium
30mHow AI is Transforming Test Automation
32mLiving on Crotches or UI Automation Antipatterns
