Download Latest CTFL_Syll2018 Questions

The correct matching of the review types with the review characteristics is as follows:

• Pair review: Informal (2)
• Walkthrough: Purpose includes gaining consensus (3)
• Technical review: Purposes include improving the software product and training the review participants (4)
• Inspection: Formal (1)

Therefore, option C is the correct answer. Options A, B, and D are incorrect, as they do not match the review types with the review characteristics correctly.

References: Section 3.2.1

Test plan is the test document where you would expect to find test exit criteria described. Test exit criteria are the conditions or requirements that must be met before testing can be completed or stopped. Test exit criteria are usually defined during test planning and control phase and evaluated during evaluating exit criteria and reporting phase. Test plan is a document that describes the scope, approach, resources, schedule, risks, metrics etc., for testing activities. Test plan also includes test exit criteria as part of its contents3 defines test exit criteria and test plan as follows:

Test exit criteria: The set of generic or specific conditions for permitting process exit criteria that are defined for each Test Level.

Test plan: A document describing the scope, approach, resources and schedule of intended test activities.

Component testing is a part of the V-Model, which is a development life cycle model that shows the relationship between each phase of development and its corresponding phase of testing. In this model, each level of testing (unit testing, integration testing, system testing, acceptance testing) has a corresponding level of development (component design, component integration, system design, requirements analysis). Component testing is the process of testing individual components or units of software in isolation from other components or systems. Component testing verifies that the components meet their functional and non-functional requirements and work as expected in their intended environment. Component testing is usually done by developers who have access to the component design and code specifications. You can find more information about component testing and the V-Model in Software Testing Foundations: A Study Guide for the Certified Tester Exam, Chapter 22.

How to fix the defect is not needed to specify in a defect report because it is not part of the information that is required to describe, reproduce, and prioritize the defect. How to fix the defect is part of the solution or resolution that is provided by the developers or maintainers who are responsible for correcting the defect. A defect report is a document that records and communicates the details of a defect found during testing. A defect report typically includes the following information:

• Defect ID: A unique identifier for the defect
• Summary: A brief description of the defect
• Severity and priority: An indication of how serious and urgent the defect is
• Test environment details: A description of the hardware, software, network, data, tools, etc., that were used when the defect was found
• How to reproduce the defect: A step-by-step procedure to recreate the defect
• Expected and actual results: A comparison of what should have happened and what actually happened when the defect occurred
• Attachments: Any additional information or evidence that can help understand or resolve the defect, such as screenshots, logs, files, etc.

You can find more information about defect reports in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 5.