BUG描述措辞标准(国外英语资料).doc

BUG描述语言规范[BUG description specification]The BUG description specificationThe purpose of,Clear and simple description good defects, the defects of writing effective instance, help developers effective defect location and repeat mistakes, to effective positioning error, modify the error.Second, the targetU reduces developer secondary defect ratesU increases the speed at which developers modify defectsImprove the credibility of test quality departmentIncreased collaboration between development and testingU effectively improves the quality of the productThree, scope,This document is suitable for all people in the system product departmentThe elements of defectIf u describe format: fill in the defect, for software module name, the page elements and buttons, key steps, attachment should be by the corresponding [] for description, description of defect error in need quotes + + in bold red color marked;U describe steps: defect description layer, when you need to first describe the defect location and conditions, the second step describing the defect found, I described the result of defects, defect modification Suggestions are given, finally must accessories or snapshot] [attach results;U description method: when filling in a defect, try to use the written language, not in spoken language, ambiguous language, and exciting language (defamation); The state of the defect changes, and the user name, time, and cause of the annotation need to be annotated to change the state;U attachment and snapshot standard format: attachment according to the need of the process and result of defects in [with] and [text], showed the process needed (red arrow) to defect process [description] and [that];U defect subject description: the description of the simple and clear in what position, what kind of condition, what happens as a result, cant completely copy the detailed description of the language;U defect description standard format:Defect description specification:Defect topic: defect location