Section outline
-
Welcome!
This is the demo version of the ISTQB Advanced Technical Test Analyst course. Many links are disabled (marked as "N/A) and others have partial content. However, you should be able to get an idea of the content with the links available.
To register, just go to https://www.mysoftwaretesting.com.
-
Module 1 - Introduction
The purpose of this module is to explain the structure of the ISTQB certification program and to lay the foundation for the rest of this course.
-
Module 2 - Risk-based Testing
In this module, we will cover the main concepts of risk and how testing can be focused on risk.
-
Module 3 - Structure-Based Testing
In this module, we will delve into structural testing techniques that a technical test analyst needs to know. There are several exercises, which must be performed to truly understand the material so you can answer the exam questions correctly.
It is recommended that you access the links in the order presented below. -
Module 4 - Analytical-Based Techniques
In this module, we will cover two types of analysis: static analysis and dynamic analysis.
Static analysis encompasses the analytical testing that can occur without executing the software. Because the software is not executing, it is examined either by a tool or by a person to determine if it will process correctly when it is executed. This static view of the software allows detailed analysis without having to create the data and preconditions that would cause the scenario to be exercised.
Dynamic analysis requires the actual execution of the code and is used to find coding faults which are more easily detected when the code is executing (e.g., memory leaks). Dynamic analysis, as with static analysis, may rely on tools or may rely on an individual monitoring the executing system watching for such indicators as rapid memory growth. -
Module 5 - Testing Software Characteristics
In general, the Technical Test Analyst focuses testing on "how" the product works (non-functional testing), rather than the functional aspects of "what" it does. These tests can take place at any test level.
For example, during component testing of real time and embedded systems, conducting performance benchmarking and testing resource usage is important. -
Module 6 - Reviews
Technical Test Analysts must be active participants in the review process, providing their unique views. They should have formal review training to better understand their respective roles in any technical review process.
In this short module, we will quickly examine the role of a Technical Test Analyst in performing reviews. -
Module 7 - Tools
While the responsibility for selecting and integrating tools belongs to the Test Manager, the Technical Test Analyst may be called upon to review the integration of a tool or set of tools to ensure accurate tracking of data resulting from various testing areas such as static analysis, test execution automation and configuration management.
In this module, we will look at:
- Integration and Information Interchange Between Tools
- Defining the Test Automation Project
- Specific Test Tools