written 5.8 years ago by |
Defect has following attributes:
1) Defect ID: Identifies defect as there are many defects might identified in system. a. i.e. D1, D2, etc.
2) Defect Name: Name of defect which explains the defect in brief. a. It must be short but descriptive. i.e. Login error.
3) Project Name: Indicates project name in which defect is found
4) Module /Sub-module name: for which the defect is found.
5) Phase introduced: Phase of life cycle to which the defect belongs to.
6) Phase found: Phase of project when the defect is found is added here. It is used to find defect leakage or stage.
7) Defect type: Defines defect type. i.e. security defect, functional defect, GUI defect etc.
8) Severity: Declared in test plan, i.e. high medium or low.
9) Priority: defines on the basis of how the project decides a schedule to take the defects for fixing.
10) Summary: Describes short about the defect.
11) Description: Describes it in detail.
12) Status: dynamic field, open, assigned, resolved, closed, hold, deferred, or reopened, etc.
13) Reported by/ Reported on: Who found defect, and on what date.
14) Assigned to: The tester is being assigned to some testing team member.
OR
ID | Unique identifier given to the defect. (Usually Automated) |
---|---|
Project | Project name. |
Product | Product name. |
Release Version | Release version of the product. (e.g. 1.2.3) |
Module | Specific module of the product where the defect was |
Detected Build Version | Build version of the product where the defect was detected |
Summary | (e.g. Summ1.2.3.5) ary of the defect. Keep this clear and concise. |
Description | Detailed description of the defect. Describe as much as possible but without repeating anything or using complex words. Keep it simple but comprehensive. |
Steps to Replicate | Step by step description of the way to reproduce the defect. Number the steps. |
Actual Result | The actual result you received when you followed the steps |
Expected Results | The expected results. |