~/talk

There is Such a Thing as Too Much Testing

Talkat RubyConf 2009 · 2009-11-19..11-21· [testing, ruby]
links:none on file
slides:none on file

Concrete claims and examples about when testing helps and when it hurts backed by numbers and tools: 20 minute build on a Java/WebSphere project, 80% of Selenium tests failing over 36 hours on eight machines, coverage moving from 21% to 25% on a huge app, and projects with near 100% coverage that run in ten seconds. Describes WebUnit, Selenium, rspec, webrat, Blue Ridge and jazzrb, what got built (signup flow, link‑building app, big portal), and which suites proved brittle or valuable.

AI-written summary · about

  1. 0:00Start
  2. 1:31Structure of this talk
  3. 2:42The Dealer Portal
  4. 5:33The Huge Financing App
  5. 8:45The IP Space Manager
  6. 10:32The Small Social Start-up
  7. 16:19The VOIP Signup ARP
  8. 17:14The VOIP Signup App
  9. 27:04What's the Right Level?
  10. 35:04It is of supreme importance to keep your test suite fast and reliable
  11. 36:34Slow Test Suite?
~/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.