Which statement about use case testing is true?

1. A. The lest cases are designed to find defects in the data flew.
2. B. The test cases are designed to be used by real users, not by professional testers
3. C. The test cases are always designed by customers or end users.
4. D. The test cases are designed to find defects in the process flow.

Correct Answer: D
Use case testing is a technique that helps identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. Use cases are descriptions of how users interact with the system to achieve a specific goal. Use case testing is not focused on data flow, but rather on process flow. Use case testing can be performed by professional testers, customers or end users, depending on the context. Use case testing does not require the test cases to be designed by customers or end users, but rather by anyone who has access to the use case specifications. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, Chapter 4, page 36.

Which of the following sentences describe a product risk?

1. A. The application might not be able to provide the expected responsiveness under a load of up-lo 300 concurrent users
2. B. Failure in acquiring an adequate and test automation tool
3. C. A wrong configuration of the test environment that causes incidents related to the environment and not to the software under test
4. D. The development team lacks knowledge of the technology on which the product is based

Correct Answer: A
This question relates to identifying product risks, which are potential problems associated with the product itself, such as software functionality, reliability, usability, and performance. Option A describes a scenario where the application might not meet performance requirements under specific conditions (up to 300 concurrent users), which directly impacts the product's ability to perform its intended function. This is a classic example of a product risk, as it concerns the product's quality and its ability to meet user needs. Options B, C, and D, on the other hand, relate to project risks, which are concerns related to the management and execution of the project, such as tool acquisition, environment configuration, and team expertise, rather than the quality of the product itself.

Software was found lo take much more time than the stated requirement of less than one
second to save a file. Upon investigation it was found that there was an unnecessary check inside a loop which was slowing down the file-save operation. The software not being able to meet the desired response time is an example of

1. A. It is not a defect
2. B. Defect
3. C. Error
4. D. Failure

Correct Answer: D
A failure is an event in which a component or system does not perform a required function within specified limits. A failure is observable by the software users or other stakeholders. A failure is caused by one or more defects in the software. In this case, the software not being able to meet the desired response time is an example of a failure, as it deviates from the stated requirement and affects the user experience. It is not a defect, which is a flaw in the software that causes the failure. It is not an error, which is a human action that produces an incorrect result. It is not a non-defect, as it clearly violates a specified requirement. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 1, page 4.

Which of the following BEST matches the attributes with a level of testing?

1. A. Stubs and drivers are often usedII The lest environment should correspond to the production environment III Finding defects is not the main focusIV Testing can be based on use casesV Testing is normally performed by testersVI Testing for functional and non-functional characteristics
2. B. Component - VI Integration - IV System -1 Acceptance - 111
3. C. Component - IV Integration -1 System - VI Acceptance - V
4. D. Component-I Integration - V System - II Acceptance - IV
5. E. Component - V Integration - II System - IV Acceptance - VI

Correct Answer: D
The relationship between impact analysis and regression testing in maintenance testing is that impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product’s functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 20.

Which of the following BEST describes checklist-based testing?

1. A. Checklist-based testing includes formal tests from detailed lists of test conditions, allowing much repeatability
2. B. Checklist-based testing may involve a list of tests based on what is important to the user as well as an understanding of why and how software fails
3. C. Checklist-based testing, while popular, provides little consistency and few guidelines concerning test case development
4. D. Checklist-based testing is restricted to non-functional testing, including usability, performance, and security test

Correct Answer: B
Checklist-based testing involves using checklists that contain items, such as potential test conditions, that should be tested. These checklists are often based on insights into what is important to the user, potential areas where software might fail, and specific aspects that need to be tested. It provides a structured yet flexible approach to testing, ensuring key areas are covered while allowing testers to use their experience and understanding of the system. Checklist-based testing is not limited to non-functional testing but can be applied to various types of testing, including functional testing.References:
✑ ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 4.4.5.