DevOps West 2017 Concurrent Session - Why You Shouldn’t Automate – And Why You Will Anyway | TechWell

SEE PRICING & PACKAGES

Thursday, June 8, 2017 - 10:00am to 11:00am

Why You Shouldn’t Automate – And Why You Will Anyway

Add to calendar

Automation has been touted as a way to speed up release delivery, improve quality, and reduce testing costs. However, what if there is a different side to this story? Come hear an opposing view to automation—and why it may actually cost your organization time, resources, and even quality. Kevin Pyles discusses why automation projects continue to fail, why automation checks should take a backseat to manual testing, and why the cost of automation is just too high. Kevin suggests you “just say no” to automation. But with pressure from your manager and great industry marketing hype, chances are you will still go back to your office and automate. Kevin shares a formula to determine if your automation efforts are achieving your desired ROI. He discusses some signs to recognize when your automation efforts are failing. Take this formula and these valuable signs back to your office and evaluate your automation efforts for yourself.

Kevin Pyles
Domo

Kevin Pyles is the senior QA engineer for the mobile web team at Domo Inc., a software company and creator of the Business Cloud. Kevin has been a QA lead or QA manager for more than ten years and has led teams responsible for QA across more than forty concurrent projects. Kevin’s previous teams provided web load testing for more than 600,000 connections/sec and i18N and l10N testing for more than 100 languages and countries. As owner of Turtlesox, LLC, Kevin tinkers with mobile app development and consulting. He is the proud father of six children and married to his best friend and soulmate. Follow Kevin on Twitter @pyleskevin.