Test Automation != Less Testers || Faster Testing || More Time For ET
Talkat CAST 2014 · on Wednesday, 2014-08-13· at 14:10· 10th fl Rosenthal Pavillion, Kimmel Center for University Life·
summary
Argument: automating checks does not equal fewer testers, faster testing, or more meaningful exploratory time. Evidence: UI suites often take hours (one example: five hours), mega-suites can take days or a week and a half, and maintenance eats time (typical personal maintenance ~3–4 hours/week). Concrete approach: build reusable tooling—driver factory, data builder, page objects and utilities—to create screenshots and reports that feed morning standups (screenshots at standup), spawn pre-positioned sessions, and speed specific tasks; automation succeeds as support tools, not as mindless test replacements.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:39Does Test Automation Exist
- 12:15Updating Your Automation
- 13:45Application Flow
- 15:35Did the Test Automation Actually Do any Testing
- 19:37Maintain Your Automation
- 20:36Definition for Test Automation
- 23:54Page Object Pattern
- 29:56Exploratory Testing
- 33:05Conclusion
- 53:57Driver Factory Approach
- 57:38What Are the Tools of Our Trade
related talks
51mRedefining test automation
21mThe Essential Pillars of Automation Testing for Success
38mDo We Really Need A Test Automation Engineer?
47mWhat Successful Test Automation is... and Why it's NOT Testing!
16mIsn’t Test Automation a Silver Bullet?
13mBeyond the hype: What test automation really costs
56mThe End Game
28mAutomation does not replace collaboration