Valid ISTQB-CTFL Dumps shared by ExamDiscuss.com for Helping Passing ISTQB-CTFL Exam! ExamDiscuss.com now offer the newest ISTQB-CTFL exam dumps, the ExamDiscuss.com ISTQB-CTFL exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com ISTQB-CTFL dumps with Test Engine here:
An Incident Management tool implements the following defect states; Open, Assigned, Solved, Closed Consider the following defect report: Id T000561 Test Object "Warehouse Management' application Tester name; John Bishop Date: 10th. April 2010 Test Case MRT558I Status OPEN Severity Serious Priority Problem- After inputting the Total Quantity item = 450 in the SV034 screen, the system shows an unexpected Error message=47 Correction: Developer name: Closing date: Which of the following is a valid criticism of this report?
Correct Answer: B
A valid criticism of this report is that the version of the application is missing. The version of the application is an important piece of information that should be included in a defect report, as it helps to identify which release or build of the software product contains the defect. The version of the application can also help to reproduce and debug the defect, as different versions may have different behaviors or features. The other options are not valid criticisms of this report. The priority, the correction description and the developer name are not missing, but rather not applicable for this report. The priority is a measure of how urgently a defect needs to be fixed, which can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The correction description and the developer name are information that are added after the defect has been resolved, not when it has been reported. There is no link to the applicable requirement (traceability) is not a valid criticism of this report, because traceability is not a mandatory attribute of a defect report, but rather an optional one.Traceability is a relationship between two or more entities (such as requirements, test cases, defects, etc.) that shows how they are related or dependent on each other. Traceability can help to verify that the requirements are met by the test cases and defects, but it is not essential for reporting a defect. The description is not highlighting the source of the problem is not a valid criticism of this report, because highlighting the source of the problem is not a responsibility of the tester who reports the defect, but rather of the developer who fixes the defect. The description should provide enough information to describe what happened when the defect occurred, such as input values, expected results, actual results, error messages, screenshots, etc., but it does not need to explain why or how it happened. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.
