~/talk

Living on Crotches or UI Automation Antipatterns

TalkinRussianat TestCon Moscow 2017 · 2017-04-26..04-27· [testing, frontend-architecture]
links:none on file
slides:none on file

Shows how common UI automation antipatterns — an imbalance of few unit tests vs many flaky UI tests, over-engineered frameworks, and bad practices like 300–500 useless UI scripts, hardcoded credentials/URLs, duplicated Gherkin scenarios and brittle conditional assertions — sink projects. Recommends concrete fixes: map manual test cases to automated suites, parameterize runs via command-line or CI (Maven/CI), extract test-data constants, and add custom matcher messages so failures explain why.

AI-written summary · about

  1. 0:00UI automation intro
  2. 2:07Testing pyramid antipatterns
  3. 7:26Antipattern 'And off we go'
  4. 10:18Positive tests limits
  5. 12:54Antipattern 'No easy way'
  6. 17:26Antipattern 'Fill all fields'
  7. 20:18Gherkin limitations
  8. 23:49Hardcoded test data
  9. 26:25Hardcoded config
  10. 29:18Antipattern 'Something broke'
  11. 30:44Q&A
~/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.