~/talk

UI Automation: Keeping Pace with Product Evolution

Talkat Agile India 2017 · 2017-03-05..03-12· [testing, frontend-architecture]
links:none on file
slides:none on file

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

  1. 0:00Start
  2. 0:11UI Automation Success: Keeping Pace with Product Evolution
  3. 8:42Time needed depends on effort/people • Automation tasks and effort -Creation (manual and machine) -Execution (machine) -Reporting (machine)
  4. 12:28Maximize ability to contribute - Version Control • Use non binary files. eg. CSV instead of Excel -Smaller, role specific files
  5. 35:18Expresses business intent • Agnostic of - web application itself -Testing tool - interaction code
  6. 43:08Central repository of all elements in the automation code
  7. 43:19Demo of working application and automation code
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.