Component testing is concerned with testing the smallest bodies of software, such as functions, classes, procedures, or modules. Component testing is also known as unit testing or module testing. Feature testing is a type of functional testing that focuses on verifying a specific feature or functionality of a system. Functional testing is a type of black-box testing that verifies that the system meets its functional requirements and specifications. Subsystem testing is a type of integration testing that verifies that a group of components work together as expected. References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.2

 According to the syllabus, dynamic analysis tools are tools that perform testing or analysis by executing the software or a part of it. Dynamic analysis tools can help detect defects or problems that only appear during runtime, such as memory leaks, performance issues, concurrency errors, etc. The answer A is correct because it suggests using a dynamic analysis tool for detecting a memory leak during performance testing. A memory leak is a situation where a code component fails to release memory after it has finished using it, causing memory exhaustion and degradation of performance. A dynamic analysis tool can monitor the memory usage of the code component and identify any memory leaks. The other answers are incorrect because they suggest using tools that are not suitable for detecting memory leaks during performance testing. A test execution tool is a tool that executes test cases automatically or semi-automatically. A configuration management tool is a tool that controls and tracks changes to the software components and documentation. A coverage measurement tool is a tool that measures how much of the code or functionality has been exercised by a test suite.

References:  Certified Tester Foundation Level Syllabus , Section 4.6.1, page 53-54.

The correct answer is D, as it describes exploratory testing.  Exploratory testing is an experience-based test technique that involves simultaneous learning, test design, and test execution 1 . Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide.  A test charter is a document that specifies the scope, objective, and approach of an exploratory testing session 1 .  Option A is incorrect, as exploratory testing is not a suitable test technique that may replace both black-box and white-box test techniques, but a complementary technique that can be used along with other techniques 1 .  Option B is i ncorrect, as exploratory testing does not require both solid specifications and much project time available for test execution, but can be used in situations where specifications are incomplete or changing and where time is limited 1 .  Option C is incorrect, as exploratory testing is not a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system, but an experience-based test technique that focuses on learning about the system and its behavior 1 . References:  1 , Section 4.2.6

The Test Analysis and Design activity of the test process is the activity where test conditions and test cases are identified and specified based on the test objectives and criteria. The Test Analysis and Design activity also involves identifying and preparing the necessary test data and test environment to support the test execution. Some of the tasks of the Test Analysis and Design activity are:

Reviewing the test basis: This task involves reviewing the requirements, specifications, design documents, or other sources of information that form the basis for testing.

Identifying test conditions: This task involves identifying what needs to be tested based on the test basis and objectives.

Designing and prioritizing test cases: This task involves designing specific scenarios or steps to verify each test condition and assigning priorities to them based on their importance or risk level.

Identifying necessary test data to support the test conditions and test cases: This task involves identifying what data is needed to execute each test case and how to obtain or generate it.

Identifying and preparing the test environment: This task involves identifying what hardware, software, network, data, tools, etc., are needed to execute the test cases and how to set up and maintain them.

Measuring the percentage of prepared test cases with what was actually prepared is not a task of the Test Analysis and Design activity because it does not involve identifying or specifying anything related to testing. Rather, it is a task of the Test Monitoring and Control activity, which involves measuring and reporting the progress and status of testing against the planned activities and criteria. You can find more information about the Test Analysis and Design activity in  A Study Guide to the ISTQB® Foundation Level 2018 Syllabus , Chapter 3 1 .

The requirement given in

the image specifies

the charge for

a money transfer based on

the amount

of money transferred.

The amount can be anywhere from 1 to 5000 euros, with different charges applied for different ranges of amounts.

To test this requirement, we can use equivalence partitioning, which is a specification-based test technique that involves dividing the input or output values into groups or partitions that are expected to be treated in the same way by the system under test. For example, based on the requirement, we can identify the following equivalence partitions for the input amount:

EP1: Amount < 1 (invalid)

EP2: 1 < = Amount < = 1999 (valid, charge = 10 euros)

EP3: 2000 < = Amount < = 5000 (valid, charge = 15 euros)

EP4: Amount > 5000 (invalid)

The set of amounts that covers all equivalence partitions is C. 0-100-2000-6000. This set of amounts includes one value from each equivalence partition and ensures that all possible scenarios are tested. For example:

TC1: Amount = 0 - > Invalid input

TC2: Amount = 100 - > Valid input, charge = 10 euros

TC3: Amount = 2000 - > Valid input, charge = 15 euros

TC4: Amount = 6000 - > Invalid input

The other sets of amounts do not cover all equivalence partitions because they either include values that belong to the same partition or exclude values that belong to different partitions. For example:

A. 0-1999-2000-5000 - > This set of amounts does not cover all equivalence partitions because it includes two values that belong to EP2 (1999 and 2000) and excludes any value that belongs to EP3.

B. 1-2000-5001-10000 - > This set of amounts does not cover all equivalence partitions because it includes two values that belong to EP4 (5001 and 10000) and excludes any value that belongs to EP2.

D. 99-1-2000-4999.99 - > This set of amounts does not cover all equivalence partitions because it includes a value that is not an integer (4999.99), which violates the assumption that only integer values can occur.

You can find more information about equivalence partitioning in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 4, Section 4.2.

Component testing is a part of the V-Model, which is a development life cycle model that shows the relationship between each phase of development and its corresponding phase of testing. In this model, each level of testing (unit testing, integration testing, system testing, acceptance testing) has a corresponding level of development (component design, component integration, system design, requirements analysis). Component testing is the process of testing individual components or units of software in isolation from other components or systems. Component testing verifies that the components meet their functional and non-functional requirements and work as expected in their intended environment. Component testing is usually done by developers who have access to the component design and code specifications. You can find more information about component testing and the V-Model in  Software Testing Foundations: A Study Guide for the Certified Tester Exam , Chapter 2 2 .

The ‘Standard for Software Test Documentation’ specification (IEEE 829) is a standard that defines a set of documents that can be used to document the test process and its outcomes. The standard provides an outline for each document, specifying its purpose, content, and format. However, the standard does not prescribe how to apply it in different contexts or projects. It is up to each organization or project to decide how to adapt the standard to their specific needs and situation. Therefore, the standard is not a rigid or mandatory requirement that must be followed strictly by all testers. Rather, it is a flexible and adaptable guideline that can be used as a reference or a starting point for creating test documentation regimes. You can find more information about IEEE 829 and test documentation in  A Study Guide to the ISTQB ® Foundation Level 2018 Syllabus , Chapter 5 1 .

A potential infinite loop is a type of defect that can be typically identified using static analysis by tools 1 .  Static analysis is a technique that examines the source code or other software artifacts without executing them, and can detect defects, vulnerabilities, code smells, and deviations from standards early in the development process 1 .  Static analysis tools are software tools that automate the static analysis technique and provide various features and functionalities to support it 1 .  Static analysis tools can identify a potential infinite loop by analyzing the control flow and data flow of the source code and checking for conditions or statements that may cause an endless repetition or iteration 1 .  A potential infinite loop can cause serious problems in software performance, functionality, reliability, and security 1 . Therefore, a potential infinite loop is a type of defect that can be typically identified using static analysis by tools.

Testing is the process of evaluating a software product by learning about it through exploration and experimentation, which includes running tests, observing outcomes, making inferences, and creating and refining test ideas. Testing has many objectives, such as finding defects, providing information, improving quality, reducing risks, etc. One of the objectives of testing is preventing defects, which means avoiding or minimizing the occurrence of defects in the software product by applying good practices and techniques throughout the software development life cycle. Preventing defects can help to save time, cost, and effort in testing and development, and improve customer satisfaction and confidence. A detailed explanation of testing objectives can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 7-8.

 According to the syllabus, product risks are risks that affect the quality of the software product, such as defects, failures, or non-compliance with requirements or standards. Product risks can be identified and analyzed during the test planning phase, and mitigated by appropriate test design and execution. The answer C is correct because it lists three product risks: failure prone software delivered, software does not perform its intended functions, and poor data integrity and quality. The other answers are incorrect because they include project risks, which are risks that affect the management and control of the testing process, such as insufficient staff, test environment issues, or schedule delays.

References:  Certified Tester Foundation Level Syllabus , Section 2.1.1, page 20-21.