Establish an Integrated Test Automation Architecture Prior Year Content

Implementing test automation requires more than selecting the best tool and starting to write automated tests. Because test automation tools must integrate with your development lifecycle and its various project management, build, integration, and release tools, you need an automation comprehensive architecture implementation plan. Drawing on his experiences at a large financial institution, Mike Sowers discusses the steps for a test automation architecture, identifying tool dependencies, establishing deployment plans, and selecting and reporting metrics. Challenges Mike’s organization faced included ensuring that the selected tools worked well with other application lifecycle tools, driving the adoption of automation across multiple project teams or departments, and communicating the quantitative and qualitative benefits to key stakeholders in management. Mike discusses things that went right (such as including the corporate architectural review board) and things that went wrong (allowing too much organizational separation between testers and automation engineers). Take back a To Do list of opportunities and issues to improve your test automation implementation or start a new one.