ISTQB CTFL-2018 Practice Test - Questions Answers, Page 24
List of questions
Related questions
Question 231

Consider the following code
int premium=2500;
if <age<30)
{
premium = premium +1500:
}
Which options suits for a correct combination of Boundary value and expected result. Assume first number as boundary followed by expected result.
Explanation:
Boundary value analysis is a technique to test the values at the boundaries of an equivalence partition. In this case, the age variable has two equivalence partitions: less than 30 and greater than or equal to 30. The boundary values are 29 and 30. The expected result for age 29 is that the premium is increased by 1500, so the final value is 4000. The expected result for age 30 is that the premium remains unchanged at 2500. This is explained in the syllabus under section 4.3, 'Black-box Test Techniques'1.
Reference: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB
Question 232

Why is it important to select a test technique?
Explanation:
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.
Question 233

What is a peer review?
Explanation:
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.
Question 234

The following condition is given:
Integer x, y; IFx>0ANDx< 100
y = y + x; END-IF
Using boundary analysis for x. which test cases are required?
Explanation:
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.
Question 235

Which of the following statements contradicts the general principles of testing?
Explanation:
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.
Question 236

Which of the following statements is true?
I) Test planning activities include selecting the test object
II,) Test strategy implementation is NOT a part of test planning
II,I) Choosing appropriate test techniques is part of test design
IV) Test schedule and exit criteria modification are part of test planning
Explanation:
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
Question 237

Which test level is concerned with testing the smallest bodies of software?
Explanation:
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
Question 238

Which of the following would be the LEAST likely to be used as the basis fcr a test exit criteria?
Explanation:
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
Question 239

Which of the following metrics is from the test design phase?
Explanation:
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.
Question 240

Which of the following BEST matches the attributes with a level of testing?
I, Stubs and drivers are often used
II, The test environment should correspond to the production environment
II,I, Finding defects is not the main focus
IV Testing can be based on use cases
V, Testing is normally performed by testers
VI, Testing for functional and non-functional characteristics
Explanation:
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
Question