Free ISTQB-CTFL Exam Braindumps

A calculator software is used to calculate the result for 5+6. The user noticed that the result given is 6.
This is an example of;

1. A. Mistake
2. B. Fault
3. C. Error
4. D. Failure

Correct Answer: D
According to the ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 18, a failure is “an event in which a component or system does not perform a required function within specified limits”. In this case, the calculator software does not perform the required function of calculating the correct result for 5+6 within the specified limits of accuracy and precision. Therefore, this is an example of a failure.
The other options are incorrect because:
✑ A mistake is “a human action that produces an incorrect result” (page 25). A mistake is not an event, but an action, and it may or may not lead to a failure. For example, a mistake could be a typo in the code, a wrong assumption in the design, or a misunderstanding of the requirement.
✑ A fault is “a defect in a component or system that can cause the component or system to fail to perform its required function” (page 16). A fault is not an event, but a defect, and it may or may not cause a failure. For example, a fault could be a logical error in the code, a missing specification in the design, or a contradiction in the requirement.
✑ An error is “the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition” (page 15). An error is not an event, but a difference, and it may or may not result in a failure. For example, an error could be a rounding error in the calculation, a measurement error in the observation, or a deviation error in the condition.
References = ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 15-18, 25;
ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 96, page 34.

A test manager decided to skip static testing since he believes bugs can be found easily by doing dynamic testing. Was this decision right or wrong?

1. A. The decision was wron
2. B. Ensuring quality mandates that static testing is performed after performing the dynamic testing.
3. C. The decision was righ
4. D. Static testing is usually redundant if a product is planned to go through a full-cycle of dynamic testing.
5. E. The decision was righ
6. F. Most of the bugs are easier to identify during the dynamic testing.
7. G. The decision was wron
8. H. Static testing can find defects early in the development process, reducing the overall cost of testing and development

Correct Answer: D
Static testing is a form of testing that does not involve executing the software or system under test. It includes activities such as reviews, inspections, walkthroughs, and analysis of documents, code, and models. Static testing can find defects early in the development process, before they become more expensive and difficult to fix in later stages. Static testing can also improve the quality of the software or system by preventing defects from being introduced in the first place. Static testing can complement dynamic testing, which involves executing the software or system under test and checking the results against expected outcomes. Dynamic testing can find defects that static testing may miss, such as performance, usability, or integration issues. However, dynamic testing alone is not sufficient to ensure quality, as it may not cover all possible scenarios, inputs, or paths. Therefore, a test manager who decides to skip static testing is making a wrong decision, as he or she is ignoring the benefits of static testing and relying solely on dynamic testing, which may not be effective or efficient enough to find and prevent
defects. References = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.1.1, page 14; ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 36; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 3, page 9.

Which of the following statements describes regression testing?

1. A. Retesting of a fixed defectI
2. B. Testing of an already tested programII
3. C. Testing of new functionality in a programI
4. D. Regression testing applies only to functional testingV Tests that do not nave to be repeatable, because They are only used once
5. E. II, IV, V
6. F. I, III, IV
7. G. II
8. H. I, IV

Correct Answer: C
Regression testing is the re-running of functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change1 It does not involve retesting of a fixed defect, testing of new functionality, or applying only to functional testing. Tests that are used for regression testing should be repeatable, because they are used to verify the stability of the software after each change2 References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 4, Section 4.2.2, Page 291; ISTQB Glossary of Testing Terms v4.0, Page 292

"Statement Testing" is part of;

1. A. Specification Based testing
2. B. Decision Testing
3. C. Experience based testing
4. D. Structured based testing

Correct Answer: D
Statement Testing is a type of white-box testing technique where the test cases are designed based on the implementation of the software, specifically aiming to execute every statement in the code at least once. This falls under the category of structure-based testing (also known as white-box testing), where the internal structure of the system is used to design test cases. Therefore, option D is correct.

Which of the following is an example of the absence-of-errors fallacy?

1. A. Repeating the same test cases will continue to find new defects, even after dozens of executions
2. B. A small number of modules contains the most defects
3. C. Since testing found very few defects, the system certainly will be successful
4. D. Other than trivial cases, it is not feasible to test all combinations of inputs and preconditions

Correct Answer: C
The absence-of-errors fallacy, as explained in the ISTQB syllabus, is the erroneous belief that having fewer defects found in testing equates to a system being more successful upon release. This misconception can lead stakeholders to undervalue thorough testing. Answer C illustrates this fallacy perfectly: assuming that because few defects were found, the system will be successful, neglects the many other factors that contribute to system success, including user satisfaction and fit-for-purpose.References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.1.5 "Absence-of-errors fallacy".