The Valley of Success
summary
Claims concrete tradeoffs: maintenance cost dominates, not execution time; flaky suites with a 70% failure rate are effectively useless. Practical tools and patterns include Selenium and Sauce Labs, Watir examples, just-in-time data creation instead of fragile fixtures, API calls to create test state, and page objects to hide locators. Tests must be atomic, autonomous and short (failure risk doubles for tests over seven minutes versus under two), and synchronization uses a global abstract wait that asks forgiveness (try action then recover).
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:18Transformational Changes in Testing
- 5:37Costs of Automation
- 6:28Don't Automate Manual Processes
- 10:37Execution Costs: The Need for Speed
- 11:43Types of Maintenance Costs
- 13:49Addressing Maintenance Costs Good Test Practices
- 16:49Scaling Tests
- 17:32Test Writing Approaches
- 18:06Imperative Example
- 18:35Declarative Example
- 21:49Writing Short Tests
- 22:31What is a Test Automation Framework?
- 23:26Using a Test Library or Framework Open Source
- 25:51Components of a Test Framework
- 26:14Starting a Session
- 27:55A Page Object Is...
- 29:57API Interactions
- 32:44Synchronization
- 35:01Abstract Waits
- 37:10Stay in the Valley of Success
related talks
01h 14mContinuous Testing
37mBuilding Quality with Foundations of Mud
48mThere is Such a Thing as Too Much Testing
21mTest Kitchen: A Recipe for Good Tests
25mTest Craftsmanship: Clean code practices for Test Automation
23mAdaptive Testing
46mThe Road to Reliable Automated Tests
57mAdvanced Testing Techniques: Tips from the trenches