ISTQB CT-TAS

Description

The Certified Tester Test Automation Strategy (CT-TAS) Specialist qualification is aimed at anyone involved in software testing and test automation. The syllabus presents multiple factors that come into play when planning for test automation within an organization. The Test Automation Strategy syllabus addresses test automation needs beyond those that are technical tool implementation and integration challenges. A strategic view of test automation provides a vision of implementation across projects within an organization in a systematic and consistent manner that ultimately can demonstrate value to the organization.

Chapter 1: Introduction and Objectives of Test Automation Strategy

• The tester understands test automation concepts and learns the selection criteria for candidate projects.
• The tester understands the factors that define a successful test automation implementation.

Chapter 2: Test Automation Resources

• The tester learns the solutions available for test automation and the relative investment for each.
• Software licensing for test automation tools is covered.
• The testers understand the skills needed for test automation.

Chapter 3: Preparing for Test Automation

• The tester learns how test automation is used across and within test levels. 
• Test automation strategies to adequately distribute testing and achieve shift left and shift right are covered.
• The tester learns how test automation supports legacy and Agile projects.
• Test automation within DevOps and continuous testing practices are covered.
• The tester understands how to define criteria for the use of test automation, including tests most suitable for test automation.

Chapter 4: Organizational Deployment and Release Strategies for Test Automation

• The tester learns how test automation can improve time to market.
• The tester understands how to develop operationally relevant automated tests and reporting of defects.
• Test automation deployment strategy and risk mitigation are covered.
• The tester learns about the test automation environment and its dependencies.
• Integrating test automation and test data into a system under test is covered.

Chapter 5: Test Automation Impact Analysis

• Test automation metrics and reporting to help inform decisions are covered.
• A tester learns how to perform a return on investment for test automation.
• Objectives for an organization and a project to use test automation are covered.
• The tester learns how to analyze test reports and inform decision-makers in a clear and understandable way.

Chapter 6: Implementation and Improvement Strategies for Test Automation

• The tester learns how to transition from manual to test automation and to continuous testing.
• Evaluating test automation for continuous improvement is covered.

Business Outcomes:

People who have passed the ISTQB CT-TAS exam should be able to accomplish the following Business Objectives:

• Understand factors from software and systems that influence the success of test automation.
• Identify the costs and risks of implementing a test automation solution.
• Understand the roles and responsibilities of people who are contributing to test automation.
• Plan for the integration of test automation across test levels.
• Identify strategic considerations for test automation implementation in different software development lifecycle models.
• Understand the applicability and viability of test automation.
• Plan test automation solutions that meet the organizational needs.
• Understand test automation deployment strategies.
• Understand test automation dependencies within the test environment.
• Understand the costs of setting up and maintaining test automation.
• Learn which test automation metrics help drive decision-making.
• Identify ways in which test automation brings value to the project and organization.
• Identify test automation reporting requirements to address stakeholder needs.
• Define transitioning activities from manual testing to test automation.
• Define a test automation strategy that ensures projects share assets and methods to ensure consistent implementation across the organization.