ISTQB Fundation Chapter 3

The correct answer is E. All of the above. This means that all of the listed defects (deviations from standards, requirement defects, design defects, insufficient maintainability, and incorrect interface specifications) are easier to find in reviews than in dynamic testing. Reviews allow for a more thorough examination of the documentation and design, making it easier to identify these types of defects. Dynamic testing, on the other hand, focuses on executing the software and may not uncover these defects as effectively.

Re-testing refers to running a test again to ensure that the previously identified faults or issues have been resolved. On the other hand, regression testing aims to identify any unexpected side effects or new issues that may have been introduced as a result of fixing the faults. Therefore, the correct answer is a) re-testing is running a test again; regression testing looks for unexpected side effects.

Reviews and inspections can be considered part of testing because they help detect faults and improve the quality of the software being developed. Reviews and inspections involve examining the software or its documentation to identify any issues or areas for improvement. By identifying faults early on, they contribute to improving the overall quality of the software. Therefore, option d) is the correct answer.

Inspection is the correct answer because it is a type of review that follows formal entry and exit criteria, including metrics. During an inspection, a team of reviewers examines the work product to identify defects, issues, and areas for improvement. This review process is systematic and structured, with specific criteria and metrics used to evaluate the quality of the product being inspected. Inspection is often used in software development to ensure that the code meets the required standards and specifications.

Reviews should be performed on specifications, code, and test plans. This means that reviews are not limited to a specific type of document or code. They can be conducted on user requirements specifications, code, and test plans to identify any potential faults or errors. Reviews are an effective way of identifying issues and improving the quality of the documents and code being reviewed.

Formal Review or Inspection is led by a trained moderator, not the author, which makes statement i true. There is a formal follow-up process after the review, making statement iii true. The main objective of a formal review or inspection is to find defects, making statement iv true. However, statement ii is false because there are pre-meeting preparations involved in a formal review or inspection. Therefore, the correct answer is B. i, iii, iv are true and ii is false.

A walkthrough is led by the author, meaning that the person who created the product or document being reviewed guides the process. On the other hand, an inspection is led by a trained moderator who is responsible for facilitating the review and ensuring that it is conducted effectively. This difference in leadership roles distinguishes the two approaches.

The objective of testing is to find faults or defects in the software and ensure that it meets the desired quality standards. It is not possible to prove that software has no faults, as testing can only provide information about the presence of faults, not their absence. Therefore, option b) is not a reasonable test objective.

The main objective of reviewing a requirement document as a tester is to ensure that each requirement is traceable to a business need, testable, and uniquely identifiable. This means that the tester needs to ensure that every requirement in the document is aligned with the goals and objectives of the business, can be effectively tested to ensure its functionality, and can be distinguished from other requirements to avoid confusion. By reviewing the requirement document with these objectives in mind, the tester can ensure that the software or system being developed will meet the necessary criteria and perform as intended.

The correct answer is A. Open, Assigned, Fixed, Closed. This is the correct sequence of stages in the bug life cycle. The bug starts in the "Open" state when it is first reported. It is then "Assigned" to a developer or team for investigation and resolution. Once the bug is fixed, it moves to the "Fixed" state. Finally, after verification and testing, the bug is marked as "Closed" to indicate that it has been successfully resolved.

The scribe is responsible for documenting all the issues, problems, and open points that were identified during the review meeting. The scribe's role is to take detailed notes and record all the discussions and decisions made during the meeting. This documentation is essential for keeping a record of the issues raised and ensuring that they are addressed and resolved in a timely manner. The scribe plays a crucial role in maintaining transparency and accountability by accurately recording the outcomes of the review meeting.

The correct order of the phases of the formal review process is as follows:
1. Planning - This involves determining the objectives, scope, and participants of the review.
2. Kick Off - This is the initial meeting where the review is officially started and the objectives and expectations are communicated.
3. Individual Preparations - Participants review the material individually and prepare their comments and feedback.
4. Review Meeting - Participants come together to discuss the material, share their comments, and identify any issues or areas for improvement.
5. Rework - Based on the feedback received during the review meeting, necessary changes and improvements are made to the material.
6. Follow Up - After the review and rework, a follow-up meeting may be held to ensure that all the necessary changes have been implemented and any remaining issues are addressed.

Regression testing should be performed after the software has changed (w) because regression testing is done to ensure that the changes made to the software do not introduce new bugs or issues. It should also be performed when the environment has changed (y) because changes in the environment can impact the functionality of the software. However, it should not be performed every week (v), as this may not be necessary or practical. Similarly, it should not be performed as often as possible (x) or when the project manager says (z), as these factors may not necessarily indicate the need for regression testing.

The expression that best matches the given characteristics is b) s = 4 and 5, t = 3, u = 2, v = 1. This is because the characteristics mentioned in the question, such as being led by a trained moderator or leader and using entry and exit criteria, align with the features of peer review. Peer review is a review process where a trained moderator or leader leads the review, there is no management participation, and entry and exit criteria are used. Therefore, the correct answer is b) s = 4 and 5, t = 3, u = 2, v = 1.

The statement "inspection is appropriate even when there are no written documents" is not true because inspections typically involve reviewing written documents or artifacts to identify defects or areas for improvement. Without any written documents, there would be nothing to inspect. Inspections require tangible evidence to assess and evaluate.

In the Planning phase of a formal review, selecting the personnel and allocating roles is an important step. This involves identifying the individuals who will be involved in the review process and assigning specific responsibilities to each person. By carefully selecting the right personnel and allocating appropriate roles, the review can be conducted efficiently and effectively. This ensures that all necessary perspectives and expertise are included in the review, leading to a comprehensive evaluation of the subject matter.

The purpose of the review planning phase is to allocate the individual roles. This means that during this phase, the participants in the review process are assigned specific roles and responsibilities. This helps in ensuring that each person knows their tasks and can contribute effectively to the review process. By allocating individual roles, the review can be conducted efficiently and smoothly, with everyone aware of their responsibilities and the overall objective of the review.

Adding more engineers to the project can help distribute the workload and accelerate the development process, allowing the team to recover the lost time while maintaining the quality standards. Eliminating requirements could compromise the project's scope and deliverables. Asking current developers to work overtime may lead to burnout and decreased productivity over time, potentially impacting quality. Hiring more software quality assurance personnel is important for maintaining quality but does not directly address the need to make up for lost development time. Therefore, adding more engineers is the most effective solution to bring the project back on schedule without compromising quality.

Reviews, static analysis, and dynamic testing all aim to identify defects in a software system. Reviews involve examining the code or design documentation to detect potential issues. Static analysis involves using tools or techniques to analyze the code without executing it, looking for defects such as coding errors or security vulnerabilities. Dynamic testing involves executing the code and observing its behavior to identify defects. Therefore, the correct answer is A. Identifying defects.

The main purpose of an informal review is to provide an inexpensive way to get some benefit. This suggests that the primary goal of an informal review is to gain some form of advantage or value, without incurring significant costs or resources. This could include obtaining feedback, insights, or improvements in a cost-effective manner. The other options, such as finding defects, learning, or making decisions, may also be potential outcomes of an informal review, but they are not the main purpose as indicated by option A.

The typical costs for an inspection process include setting up forms and databases, analyzing metrics and improving processes, and the time spent on the document outside the meeting. However, writing the documents to be inspected is not included in these costs. This means that the process of actually creating the documents for inspection is separate from the costs associated with the inspection process itself.