K-Level wise topics for CTAL Technical Test Analyst Exam as per the CTAL syllabus
ISTQB Certified Tester Advanced Level Syllabus had been updated in 2007.
Following K-Level wise topics recommended for study for the Technical Test Analyst exam are based upon this latest syllabus.
(A) CTAL Technical Test Analyst Exam Syllabus Chapter 1: Basic Aspects of Software Testing
Testing in the Software Lifecycle
Level K2: Describe how testing is a part of any software development and maintenance activity
Specific Systems
Level K2: Explain by giving examples the specifics of testing systems of systems
Level K2: Explain why the three main outcomes of testing safety critical systems are required to demonstrate compliance to regulations
Metrics & Measurement
Level K2: Describe and compare the standard testing related metrics
(B) CTAL Technical Test Analyst Exam Syllabus Chapter 2: Testing Processes
Test Analysis & Design
Level K2: Explain the stages in an application�s lifecycle where non-functional tests and architecture-based tests may be applied . Explain the causes
of non-functional testing taking place only in specific stages of an application�s lifecycle
Level K2: Exemplify the criteria that influence the structure and level of test condition development
Level K2: Describe how test analysis and design are static testing techniques that can be used to discover defects
Level K2: Explain by giving examples the concept of test oracles and how a test oracle can be used in test specifications
Test implementation & execution
Level K2: Describe the pre-conditions for test execution, including: testware; test environment; configuration management; and defect management
Evaluating Exit Criteria and Reporting
Level K3: Determine from a given set of measures if a test completion criterion has been fulfilled.
(C) CTAL Technical Test Analyst Exam Syllabus Chapter 3: Test Management
Risks Management
Level K2: Outline the activities of a risks based approach for planning and executing technical Testing
(D) CTAL Technical Test Analyst Exam Syllabus Chapter 4: Test Techniques
Specification based
Level K2: List examples of typical defects to be identified by each specific specification-based Techniques.
Level K3: Write test cases from given software models using the following test design techniques
(The tests shall achieve a given model coverage)
a) Equivalence partitioning
b) Boundary value analysis
c) Decision tables
d) State Transition Testing
Level K4: Analyze a system, or its requirement specification in order to determine which specification-based techniques to apply for specific objectives, and outline a test specification based on IEEE 829, focusing on component and non-functional test cases and test procedures.
Structure based
Level K2: List examples of typical defects to be identified by each specific specification-based Techniques.
Level K3: Write test cases in real-life using the following test design techniques (The tests shall achieve a given model coverage)
a) Statement testing
b) Decision testing
Level K4: Be able to compare and analyze which structure-based technique to use in different situations
Defect and Experience Based
Level K2: Describe the principle and reasons for defect-based techniques and differentiate its use from specification- and structure-based techniques
Level K2: Explain by examples defect taxonomies and their use
Level K2: Understand the principle of and reasons for experienced-based techniques and when to use them
Level K3: Specify, execute and report tests using exploratory testing
Level K3: Specify tests using the different types of software fault attacks according to the defects they target
Level K4: Analyze a system in order to determine which specification-based, defect-based or experienced-based techniques to apply for specific goals.
Static Analysis
Level K3: Use the algorithms �Control flow analysis�, �Data flow analysis� to verify if code has not any control or data flow anomaly
Level K4: Interpret the control and data flow results delivered from a tool in order assess if code has any control or data flow anomaly.
Level K2: Explain the use of call graphs for the evaluation of the quality of architecture. This shall include the defects to be identified, the use for test design and test planning, limitations of results.
Dynamic Analysis
Level K2: Explain how dynamic analysis for code can be executed and summarize he defects that can be identified using that technique, and its limitations
(E) CTAL Technical Test Analyst Exam Syllabus Chapter 5: Test of Software Characteristics
Quality Attributes for Domain Testing
Level K2: Characterize non-functional test types for domain testing by typical defects to be targeted (attacked), its typical application within the application life-cycle, and test techniques suited to used for test design.
Level K4: Specify test cases for particular types of non-functional test types and covering given test objectives and defects to be targeted.
Quality Attributes for Technical Testing
Level K2: Characterize non-functional test types for technical testing by typical defects to be targeted (attacked), its typical application within the application life-cycle, and test techniques suited to used for test design.
Level K2: Understand and explain the stages in an application�s lifecycle where security, reliability and efficiency tests may be applied (including their corresponding ISO9126 sub-attributes)
Level K2: Distinguish between the types of faults found by security, reliability and efficiency tests, (including their corresponding ISO9126 sub-attributes)
Level K2: Characterize testing approaches for security, reliability and efficiency quality attributes and their corresponding ISO9126 sub-attributes.
Level K3: Specify test cases for security, reliability and efficiency quality attributes and their corresponding ISO9126 sub-attributes.
Level K2: Understand and explain the reasons for including maintainability, portability and accessibility tests in a testing strategy
Level K3: Specify test cases for maintainability and portability types of non-functional test
(F) CTAL Technical Test Analyst Exam Syllabus Chapter 6: Reviews
Level K4: Outline a review checklist in order to find typical defects to be found with code and architecture review
Level K2: Compare review types with each other and show their relative strengths, weaknesses and fields of use.
(G) CTAL Technical Test Analyst Exam Syllabus Chapter 7: Incident Management
Level K4: Analyze, classify and describe functional and non-functional defects in understandable defect reports
(H) CTAL Technical Test Analyst Exam Syllabus Chapter 9: Test Tools & Automation
Test Tool Concepts
Level K2: Compare the elements and aspects within each of the test tool concepts �Benefits & Risks�, �Test Tool Strategies�, �Tool Integration�, �Automation Languages�, �Test Oracles�, �Tool Deployment�, �Open Source Tools�, �Tool Development�, and �Tool Classification�
Test Tools Categories
Level K2: Summarize the test tool categories by objectives, intended use, strengths, risks and examples
Level K2: Map the tools of the tool categories to different levels and types of testing
Keyword-Driven Test Automation
Level K3: Create keyword / action word tables using the key-word selection algorithm to be used by a test-execution tool
Level K3: Record tests with Capture-Replay tools in order to make regression testing possible with high quality, many testcases covered, in a short time-frame
Performance Testing Tools
Level K3: Design a performance test using performance test tools including planning and measurements on system characteristics
(I) CTAL Technical Test Analyst Exam Syllabus Chapter 10: People Skills � Team Composition
Communication
Level K2: Describe by example professional, objective and effective communication in a project from the tester perspective. You may consider risks and opportunities.
Note: CTAL Syllabus Chapter 8 on �Standards & Test Improvement Process� is not applicable for the Technical Test Analyst exam.
Best of Luck for the Prestigious CTAL � TTA Certification ! ! ! !
Access the Full Database of All Posts for ISTQB Advanced CTAL Test Analysts Exam Crash Course
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.