Which of the following answers describes a reason for adopting experience-based testing techniques?
Answer : D
Experience-based testing techniques leverage the tester's intuition and prior experience to identify defects that systematic techniques might miss. These techniques are valuable because they can uncover issues based on real-world usage and scenarios that aren't always covered by more formalized black-box and white-box methods. The ISTQB CTFL Syllabus v4.0 highlights the complementary nature of experience-based techniques in providing a broader defect detection strategy.
Which of the following statements about white-box testing is FALSE?
Answer : C
Achieving full code coverage does not guarantee that the component or system is fully tested or free of defects. Code coverage metrics indicate the extent to which the source code has been tested, but they do not account for the quality of the tests or whether all possible scenarios have been considered. Other types of testing, including functional, performance, and security testing, are necessary to ensure comprehensive testing. The ISTQB CTFL Syllabus v4.0 highlights that while high code coverage is beneficial, it does not equate to complete testing.
Which ONE of the following statements BEST applies to checklist-based testing?
Answer : B
Comprehensive and Detailed In-Depth Explanation:
Checklist-based testing uses specific test conditions (B) that help testers ensure key aspects are validated. The checklist items can be derived from past defects, requirements, or regulatory standards.
(A) is incorrect because general guidelines lack specificity.
(C) is incorrect because checklists can be used for both manual and automated testing.
(D) is incorrect because checklists are useful for both functional and non-functional testing (e.g., security, performance).
Checklists help ensure completeness without enforcing strictly scripted execution.
An alphanumeric password must be between 4 and 7 characters long and must contain at least one numeric character, one capital (uppercase) letter and one lowercase letter of the alphabet.
Which one of the following sets of test cases represents the correct outcome of a two-value boundary value analysis applied to the password length? (Note: test cases are separated by a semicolon)
Answer : D
The correct outcome of a two-value boundary value analysis applied to the password length is the set of test cases represented by option D. Boundary value analysis is a test design technique that focuses on the values at the boundaries of an equivalence partition, such as the minimum and maximum values, or the values just above and below the boundaries. A two-value boundary value analysis uses two values for each boundary, one representing the valid value and one representing the invalid value. For example, if the valid range of values is from 4 to 7, then the two values for the lower boundary are 3 and 4, and the two values for the upper boundary are 7 and 8. The test cases in option D use these values for the password length, while also satisfying the other requirements of the password, such as containing at least one numeric character, one capital letter, and one lowercase letter. The test cases in option D are:
1RhT: a 4-character password that is valid
rSp53: a 5-character password that is valid
3N3e10: a 6-character password that is valid
8sBdby: an 8-character password that is invalid The test cases in the other options are incorrect, because they either use values that are not at the boundaries of the password length, or they do not meet the other requirements of the password. For example, the test cases in option A are:
1xA: a 3-character password that is invalid, but it does not contain a capital letter
aB11: a 4-character password that is valid
Pq1ZZab: a 7-character password that is valid
7iDD0a1x: an 8-character password that is invalid Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques1
ISTQB Glossary of Testing Terms v4.0, Boundary Value Analysis, Equivalence Partition2
For the same financial institution in Question 12, with the same requirements and expectations, what would be the most likely investment values used in testing if two-point boundary value analysis is used to design test cases specific to the 13% interest rate equivalence partition?
Answer : A
For boundary value analysis, the test cases should include the boundary values just inside and just outside the equivalence partition for the 13% interest rate range:
R100,000 (just inside the previous range)
R100,001 (start of the 13% range)
R500,000 (end of the 13% range)
R500,001 (just outside the range)
These values ensure that both the edges of the partition are tested.
The following rules determine the annual bonus to be paid to a salesman of a company based on the total annual amount of the sales made (referred to as TAS).
If the TAS is between 50k and 80k, the bonus is 10%. If the TAS exceeds 80k by a value not greater than 40k, the bonus is 15%. Finally, if the TAS
exceeds the maximum threshold which entitles to a 15% bonus, the bonus is 22%.
Consider applying equivalence partitioning to the TAS (Note: 1k = 1000 euros).
Which one of the following answers contain only test cases that belong to the same equivalence partition?
Answer : A
This answer is correct because equivalence partitioning is a test design technique that divides the input domain of a system or component into partitions of equivalent data, such that each partition is expected to produce the same output or behavior. Equivalence partitioning aims to reduce the number of test cases by selecting one representative value from each partition. In this case, the input domain of the TAS can be divided into four partitions based on the bonus rules: less than 50k, between 50k and 80k, between 80k and 120k, and more than 120k. The test cases in the answer belong to the same partition, which is between 80k and 120k, and they are expected to produce the same output, which is a bonus of 15%. Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.1
Which ONE of the following tools would be MOST SUITABLE for facilitating the creation of test cases, test data, and test procedures?
Answer : A
Comprehensive and Detailed In-Depth Explanation:
The correct tool for creating test cases, test data, and test procedures is a test design and implementation tool (A).
(B) is incorrect as static testing tools focus on code analysis, not test case creation.
(C) is incorrect because DevOps tools manage automation pipelines, not test design.
(D) is incorrect because test execution tools focus on running tests rather than designing them.
Test design tools help optimize test coverage, reduce redundancy, and improve efficiency.