ISTQB CTFL-2018 Practice Test - Questions Answers, Page 27

Component integration testing is the process of testing the interactions between different components of a system. It should always be done before system testing, which is the process of testing the system as a whole. Integration testing can reveal defects in the interfaces and interactions between components, which can affect the functionality and performance of the system. System testing can reveal defects in the system requirements, design, and behavior, which can affect the quality and usability of the system. Therefore, it is logical to perform integration testing before system testing, to ensure that the components work together correctly before testing the system as a whole.

Test implementation and execution is the phase of the test process where test cases are executed and test results are logged. It includes activities such as checking if the preconditions of test execution have been met, executing test cases according to a test procedure, comparing actual results with expected results, logging test results and reporting defects, and repeating test activities as needed. Prioritizing test conditions is not an activity that belongs to test implementation and execution, but rather to test analysis and design, which is the phase where test conditions are identified and test cases are designed.

Reference:Certified Tester Foundation Level Syllabus, Section 4.2.3 and 4.2.4

Black-box testing and white-box testing are two approaches to test design that differ in the way they derive test cases from the test basis. Black-box testing is based on an analysis of the test basis documentation, such as requirements, specifications, user stories, or use cases, without looking at the internal structure or code of the system under test. White-box testing is based on an analysis of the code itself, such as statements, branches, paths, or data flows, to design test cases that cover specific aspects of the code. Black-box testing focuses on the external behavior and functionality of the system, while white-box testing focuses on the internal logic and structure of the system.

Equivalence partitioning is a technique to divide a set of possible inputs or outputs into classes that are expected to behave similarly or produce similar results. For each equivalence class, only one test case is required to represent the whole class. In this case, we can identify the following equivalence classes for the input field 'ZIP code':

Valid ZIP code format and valid ZIP code value (e.g., 12345)

Valid ZIP code format and invalid ZIP code value (e.g., 99999)

Invalid ZIP code format and valid ZIP code value (e.g., 1234)

Invalid ZIP code format and invalid ZIP code value (e.g., ABCDE)

Therefore, four test cases are required to test this field using equivalence partitioning.

The statement that independent testing is necessary because developers don't know any testing is wrong. Developers do know some testing, as they perform unit testing and component testing on their own code. However, independent testing is beneficial because it can provide a different perspective and a higher degree of objectivity than testing done by developers. Independent testers may have different skills, knowledge, experience, and expectations than developers, which can help them find different types of defects and improve the quality of the system.

Integration testing is the process of testing the interactions between different components or subsystems of a system. It has the following characteristics:

It can be done in an incremental manner, meaning that components or subsystems are integrated and tested one by one until the whole system is integrated and tested.

It is usually done before system testing, which is the process of testing the system as a whole against its requirements and specifications.

It includes functional tests, which are tests that verify the functionality and behavior of the system or its components.

It includes non-functional tests, which are tests that verify the quality attributes of the system or its components, such as performance, reliability, security, etc.

Therefore, statements I, II,I, and IV are correct.

Debugging the software to find the reason for defects is not a common objective of testing. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Debugging is usually done by developers after testers have reported defects found during testing. Testing is the process of evaluating software by applying test cases to find defects and provide information on its quality. Testing has several common objectives, such as:

Providing information on the status of the system, such as its readiness for release, its compliance with requirements, its risks and issues, etc.

Preventing defects, by applying good practices throughout the software development lifecycle, such as reviews, inspections, static analysis, etc.

Finding defects in the software, by applying test cases that cover different aspects of the software functionality, quality, performance, security, etc.

Therefore, statement D is not correct.

The statement that component testing tests interfaces between modules and interactions of different parts of a system does not describe component testing. Component testing is the process of testing individual software components that are separately testable, such as modules, programs, objects, classes, etc. Component testing verifies the functionality and quality of the components in isolation from other components. Component testing does not test the interfaces or interactions between components, as this is done in integration testing.

Any software development product can undergo static testing, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing is a type of testing that does not involve executing the software or system under test, but rather analyzing it using various techniques, such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Static testing can help find defects and improve the quality of any software development product at any stage of the software development lifecycle.