MYTHBUSTING: Every Project Needs to be Automated
summary
Claim: automation is not mandatory for every project but depends on context. Case details: an insurance mobile app prototype with no signed contract, two platforms, team of three (two experienced), tool choices Appium vs Calabash vs Xcode vs Espresso, language leaning to Python for easy parallel runs, infrastructure choices (local devices vs Sauce Labs), costs of maintenance and flaky UI tests, a misestimate that led to 19 months of UI development that proved inefficient, and a successful TDD cross‑functional team cut manual testing to 5%.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:43uestions may arise?
- 3:48to choose? Why?
- 5:33choose the language?
- 16:37antages of automation
- 23:19ation in SDLC models
- 25:59ation Process
related talks
46mPanel Discussion: Breaking Myths About a Career in Testing
23mWhy testing is also a developer's problem
18mExploration of tools, frameworks to take the pain out of mobile app testing!
24mMastering the mobile testing pyramid
32mWhy testing is a developer's problem
47mWhat are your Automation Strategies?
01h 08mTest Automation Monsters
29mFunctionally Mobile (Automation)