Business Impact Delivery Using Test Automation
summary
Argues that adopting Continuous Testing inside CI/CD cuts release time from months to hours, with test automation paying back quickly by catching tiny regressions machines never tire of finding; recommends targeting prioritized coverage rather than 100% and warns that more than 50% of Fortune 500 disappeared since 2000 for failing to digitize. Recommends choosing mainstream tools like Appium and languages JavaScript/Python/Java/C#, avoids homegrown niches, and says QA must hold scripting skills while DevOps glues pipelines together for reliable, repeatable releases.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:32About Me
- 1:55DIGITAL DISRUPTION
- 2:54WHAT IS TEST AUTOMATION ?
- 4:02NEED FOR FASTER TIME TO MARIS
- 5:21CONSUMER DEMANDS A HIGH DEGREE OF RESPONSIVENESS
- 6:23YOUR BRAND IS DIGITAL
- 7:41TEST AUTOMATION AND DEVOPSIS
- 8:27HIGH UPFRONT INVESTMENT
- 9:45SELECTION OF THE RIGHT TOOLS
- 12:13DEFINING THE SCOPE
- 13:07AUTOMATION TEST MAINTENANG
- 14:04TEST AUTOMATION TOOLS AND FRAMEWORKS
- 16:17QUESTIONS?
- 16:54SELECTION OF SCRIPTING LANGUAGES
related talks
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
07mInterview on Regression Testing and Continuous Delivery
44mStrategy for Acing Continuous Testing in DevOps
21mThe Essential Pillars of Automation Testing for Success
26mThe Impact of Testing on a DevOps Pipeline
34mWhy continuous testing is essential
27mYour Roadmap to Continuous Delivery and Continuous Testing
32mBetter Continuous Testing in DevOps
