Which of the following is NOT an objective of testing?

1. A. Finding defects
2. B. Providing information for decision-making
3. C. Gaining confidence about the level of quality of the software
4. D. Analyzing and removing the cause of failures

Correct Answer: D
Analyzing and removing the cause of failures is not an objective of testing,
but rather a task of development or maintenance. A failure is an event or behavior that deviates from the expected or specified result of a system under test. A failure is caused by an error (also known as a mistake or a fault) in the software code, design, or specification. Analyzing and removing the cause of failures is a process of locating and fixing errors in the software code, design, or specification, which is also known as debugging or defect resolution. Analyzing and removing the cause of failures does not aim to find or report defects, but rather to correct or prevent them. The other options are objectives of testing. Finding defects is one of the main objectives of testing, as it helps to improve the quality and reliability of the software product. Providing information for decision-making is another objective of testing, as it helps to support decision making and risk management. Gaining confidence about the level of quality of the software is another objective of testing, as it helps to assure that the software product meets its requirements and customer or user needs and expectations. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 3.

Which of the following is the main benefit of a configuration management of testware?

1. A. All testware is backed up with restore option, including incident reports and change request
2. B. The testware can be traced to information in requirements tools and to the bug tracking system.
3. C. All testware items are identified, version controlled, tracked tor changes with relation to each other
4. D. There is an easy way to assess the level to test coverage provided by the existing tests

Correct Answer: C
Configuration management of testware is a critical aspect of maintaining the integrity and traceability of test assets throughout the testing lifecycle. The main benefit of configuration management is to ensure that all testware items, such as test cases, test scripts, test data, and test results, are systematically identified, version controlled, and tracked for changes in relation to each other.
Option C accurately describes this benefit. By applying configuration management principles to testware, teams can manage changes to test assets efficiently, ensuring that the testware remains consistent, up-to-date, and aligned with the version of the software under test. This control mechanism facilitates the reproducibility of tests, enhances the reliability of testing activities, and supports traceability from requirements through to defects.
Options A, B, and D describe other aspects of test management and testing processes but do not capture the core benefit of configuration management of testware, which is centered on the systematic control and tracking of testware items.

In what way do Configuration Management effects testing?

1. A. Without proper configuration management, test planning cannot proceed.
2. B. Proper configuration management ensures that testers can uniquely identity the tested item
3. C. Configuration management is important for developers, not for testers
4. D. There is very little influence of configuration management practices on the test project.

Correct Answer: B
Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management affects testing in various ways, such as:
✑ Proper configuration management ensures that testers can uniquely identify the tested item, which can help traceability, reproducibility and accountability.
✑ Proper configuration management ensures that testers have access to consistent versions of software components and testware, which can help reliability, compatibility and efficiency.
✑ Proper configuration management ensures that testers can track changes and defects in software components and testware, which can help verification, validation and reporting.
✑ Proper configuration management ensures that testers can control the configuration of the test environment, which can help stability, security and performance. Configuration management is not a prerequisite for test planning, as test planning can proceed without configuration management, although it may be less effective or accurate. Configuration management is not important for developers only, but for testers as well, as it affects the quality and consistency of the testing process and products. Configuration management has a significant influence on the test project, as it affects various aspects of testing, such as traceability, reproducibility, reliability, compatibility, efficiency, verification, validation, reporting, stability, security and performance. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, Chapter 6, page 60-61.

Which of the following is true about Oracles?

1. A. Sometimes old version of a product can be used as an Oracle
2. B. Oracles help in reproducing the irreproducible bugs
3. C. Oracles are derived from the design
4. D. Oracles can be generated automatically using data generators

Correct Answer: A
An oracle is a mechanism or source that can provide the expected result for a given test input or situation. Sometimes old version of a product can be used as an oracle, if it is assumed that the old version behaves correctly for the test cases that are executed on the new version. This is also known as back-to-back testing. Oracles do not help in reproducing the irreproducible bugs, as they only provide the expected results, not the actual results. Oracles are not derived from the design, but from the requirements or specifications. Oracles cannot be generated automatically using data generators, as data generators only provide test inputs, not test outputs. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 9.

Which of the following statements about static analysis are FALSE?

1. A. Static analysis can be used Instead of dynamic testing.I
2. B. Stalk: analysis can uncover defects like security vulnerabilities.II
3. C. Static analysis can be used to check conformance to specifications and standard
4. D. IV Static analysis typically detects failures prior to component testing.
5. E. II
6. F. I
7. G. Ill
8. H. II
9. I. IV
10. J. I, IV

Correct Answer: D
Static analysis involves analyzing the software's code, design, and structure without executing the program. It can uncover various types of defects, including security vulnerabilities (II) and non-conformance to specifications and standards (III). However, static analysis cannot replace dynamic testing (I), which involves executing the software to observe its behavior under various conditions. Dynamic testing can identify failures that static analysis cannot, such as those related to runtime issues and interaction between different parts of the software. Statement IV is false because static analysis does not detect failures; it detects defects. Failures are observed when the software is executed, which is beyond the scope of static analysis.