Be the first to like this
Planning, designing, implementing, and tracking results for QA and test automation can be challenging. It is vital to ensure that any tools selected will work 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. Mike Sowers discusses his experiences creating an automation architecture, establishing tool deployment plans, and selecting and reporting tool metrics at a large financial institution. Mike will share things that went right, such as including the corporate architectural review board; and things that went wrong, such as allowing too much organizational separation to occur between testers and automation engineers. Discover how you can improve the implementation of test automation at your organization.