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

The purpose of selecting a test technique is to increase the effectiveness of the test process by creating tests with higher chance of finding bugs. Test techniques do not define the number of regression cycles, nor are they the only way to test a software application. Test techniques may help reduce the number of tests, but that is not their primary goal.

A peer review is a review done by colleagues at the same organizational level, such as developers, testers, or managers. An informal review without moderator is called a walkthrough. A review done by developers and testers together is called an inspection. A review done by developers only is not a specific type of review.

Using boundary analysis for x, the test cases are required to cover the values on and around the boundaries of x > 0 and x < 100. Therefore, the test cases should include -1, 0, 1, 99, 100, and 101. The value 0.1 is not a boundary value, and the values -500 and 500 are too far from the boundaries to be relevant.

The general principles of testing state that testing can show the presence of defects, but not their absence. Running the same test set more often will not increase the likelihood of finding new defects, unless the system or its environment changes. Therefore, statement A contradicts the general principles of testing. Statement B is true, as testing is context-dependent and should be tailored to the specific situation of a project. Statement C is also true, as early testing can help prevent defects and reduce rework. Statement D is true, as it reflects the Pareto principle or the 80/20 rule, which states that most defects are found in a small subset of a system's modules.

Statement I is true, as test planning activities include defining the test object, which is the component or system to be tested. Statement II, is false, as test strategy implementation is part of test planning and involves defining the test approach and test levels to be applied. Statement II,I is true, as test design activities include choosing appropriate test techniques to derive test cases from test conditions. Statement IV is true, as test planning activities include defining and updating the test schedule and exit criteria throughout the project lifecycle.

Reference: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.1

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.

Reference: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.2

The cost of testing performed so far is not a test exit criteria, as it does not reflect the quality or completeness of the testing process.Test exit criteria are usually based on factors such as the number of unfixed defects, the confidence of testers in tested code, the test coverage achieved, and the test schedules

The percentage of test conditions covered by test cases is a metric from the test design phase, as it measures how well the test cases cover the test basis13. The other metrics are from the test execution phase or the test closure phase.

Explanation: The attributes that best match each level of testing are as follows14: Component testing: Stubs and drivers are often used (I), as they simulate the behavior of missing or incomplete components. Integration testing: Testing for functional and non-functional characteristics (VI), as integration testing verifies that components interact correctly and meet their specified requirements. System testing: The test environment should correspond to the production environment (II,), as system testing evaluates the system's compliance with its specified requirements under realistic conditions. Acceptance testing: Testing can be based on use cases (IV), as acceptance testing validates that the system meets the user's needs and expectations