Fostering Long-Term Test Automation Success Prior Year Content
In today’s environment of plummeting software delivery cycle times, test automation becomes a more critical and strategic necessity. How can we possibly keep up with software delivery’s explosive pace while retaining satisfactory test coverage, keeping the reins on costs, and reducing risk? Carl Nagle maintains that the long-term solution is a greater level of “sustainable” test automation. The SAFS method separates test design from test execution with a data-driven/action-based approach that encapsulates volatile application-specific data into readily localizable “maps” for simple maintenance. Test designs (scripts) are completely independent of the ready-to-run SAFS engines that will execute them. And since the test design methodology does not change over long periods of time, testers can focus more on getting robust automation in place quickly, with little attention paid to each new technology, testing tool, or test IDE. Join Carl to learn how test automation thrives when testers and tools are not tied up in application-specific silos.