iSQI CTFL_Syll2018 ISTQB Certified Tester Foundation Level Exam Practice Test

Answer : C

The test organization that has the highest level of independence is C. Independent test specialists for specific test types, such as usability, performance or certification test specialists. Test independence refers to the degree of separation between the tester and the developer or user of the system or component under test. Test independence can help to reduce bias and increase objectivity in testing. Independent test specialists are testers who have specialized skills and knowledge in specific test types or domains and who are not involved in the development or use of the system or component under test. Independent test specialists can provide more reliable and accurate results than testers who are part of the development team or user community. A detailed explanation of test independence can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 9-10.

Answer : B

Static code analysis is a technique that examines the source code or other software artifacts without executing them, and can detect defects, vulnerabilities, code smells, and deviations from standards early in the development process1.According to the ISTQB syllabus, one of the benefits of static testing is early defect detection2, which can reduce the cost and effort of fixing them later.

Answer : D

Pair programming is a software development technique where two programmers work together on the same code at the same workstation. One programmer, called the driver, writes the code while the other programmer, called the navigator, reviews the code and provides feedback and suggestions. Pair programming is not only a coding technique but also an informal review method because it involves constant communication and collaboration between the programmers who check each other's work and share their knowledge and skills. Pair programming can improve the quality and productivity of software development by reducing defects, increasing code readability, enhancing learning opportunities, and fostering creativity and innovation. Pair programming is usually used in agile methods such as Extreme Programming (XP), Scrum, or Kanban. It is not an alternative term for code inspection, which is a formal review method where a group of reviewers examine a piece of code in a structured and systematic way following predefined rules and roles. It is also not done with developer and tester pairing together because pair programming requires both programmers to have similar levels of expertise and familiarity with the code they are working on. You can find more information about pair programming inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, Chapter 31.

Answer : C

Testing is the process of evaluating a software product by learning about it through exploration and experimentation, which includes running tests, observing outcomes, making inferences, and creating and refining test ideas. Testing has many objectives, such as finding defects, providing information, improving quality, reducing risks, etc. One of the objectives of testing is preventing defects, which means avoiding or minimizing the occurrence of defects in the software product by applying good practices and techniques throughout the software development life cycle. Preventing defects can help to save time, cost, and effort in testing and development, and improve customer satisfaction and confidence. A detailed explanation of testing objectives can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 7-8.

Answer : A

Incorrect interface specifications are most likely to be found by a review during static testing. A review is a type of static testing technique that involves a manual examination of a work product by one or more individuals who follow a defined process. A review can be applied to any work product, such as requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. A review can help find defects and improve the quality of any work product at any stage of the software development lifecycle. Incorrect interface specifications are defects that affect the definition and communication of the interfaces between components or systems. These defects can be detected by reviewing the interface specifications document and comparing it with the requirements and design specifications.

Answer : C

To apply to the RAD development model. Metrics are quantitative measures that can be used to monitor, control, and improve the test process and the quality of the system. Metrics can be used for various purposes, such as to identify the percentage of work done in test environment preparation or test case preparation, to measure whether dates of test milestones were met, to compare actual results with expected results, to evaluate the effectiveness and efficiency of testing, etc. However, metrics are not specific to any development model, such as RAD (Rapid Application Development), and can be applied to any type of software development project. A detailed explanation of metrics can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 103-105.

Answer : C

According to the IEEE 829 Standard for Software Test Documentation, an incident report should contain the following information:

Identifier: A unique identifier for the incident report

Summary: A brief summary of the incident

Incident description: A description of the incident, including:

Date: The date when the incident was observed

Author: The name of the person who reported the incident

Source: The software or system lifecycle process in which the incident was observed

Test case: The identification of the test case that caused the incident

Execution phase: The phase of test execution when the incident was observed

Environment: The hardware and software environment in which the incident was observed

Description: A description of the anomaly to enable reproduction of the incident

Expected result: The expected result of the test case

Actual result: The actual result of the test case

Reproducibility: An indication of whether the incident can be reproduced or not

Impact analysis: An analysis of the impact of the incident on other aspects of the software or system

Incident resolution: A description of how the incident was resolved, including:

Resolution date: The date when the incident was resolved

Resolver: The name of the person who resolved the incident

Resolution summary: A brief summary of how the incident was resolved

Status: The current status of the incident (e.g., open, closed, deferred)

Classification information: A classification of the cause and effect of the incident for metrics and reporting purposes

Therefore, among the options given in this question, only (i), (iii), and (iv) are part of an incident report based on IEEE 829.