~/talk

Seven Proven Ways to Ruin Your Test Automation

TalkinGermanat HUSTEF 2018 · 2018-10-29..10-31· [testing, developer-experience]
links:none on file
slides:none on file

This talk lists seven concrete failure modes that destroy test automation: hoarding knowledge in a single ‘knowledge champion’, vendor tool lock-in, brittle capture‑replay scripts, automating fragile/manual workflows and interdependent tests, pretending management support, setting impossible targets, and developers constantly changing UI objects. For each problem it points to explicit test automation patterns and modular design practices (documented on a patterns wiki) as the countermeasures.

AI-written summary · about

  1. 0:00Introduction
  2. 3:51Ignoring docs
  3. 7:54Unrealistic expectations
  4. 12:12Overcomplicating scripts
  5. 16:20Lack of maintenance
  6. 20:33Management's role
~/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.