adinakar

 Profile Answers by adinakar 

• Oct 19th, 2007

 

1. Defect ID
2. Corresponding Test Case ID
3. Summary
4. Steps to reproduce
5. Severity
6. Priority
7. Test Cycle
8. Test Phase
9. Test Environment
10. Detailed Description
12. Module/Sub System defect is noticed
13. Attachments
14. Status
15. Detected By
16. Assigned to
17. Detected On

18. Provision for comments

katie

 Profile Answers by katie 

• Nov 27th, 2007

 

Explained totally in www.etestinghub.com

atul_mahajan3

 Profile Answers by atul_mahajan3 

• Aug 5th, 2008

 

In brief

1. Bug ID
2. Bug Description
3. Bug Status : open/closed/duplicate
4. Bug priority and serverity
5. Bug steps to produce
6. Bug Entered/Reported by
7. Bug assigned to
8. Test Case /module found
9.  System information in which produce.

shilpasurya

 Profile Answers by shilpasurya 

• Aug 5th, 2008

 

Attributes of a bug:

Title:
Component(where it was found)
Severity
Priority
Status
Assigned to (developer name)
Found by (tester name)
Date (found)
Resolution
OS(environment found on)
Pre-conditions
Description
Expected Results
Actual Results

Additional Information
Attached snapshots/test logs

We can have more attributes than wrt the reporting software we use.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Dec 9th, 2008

 

I feel this attributes are different company to company, we are followed below ones.

-> Date

-> Defect id ( auto genarated)

-> Module name

-> Server date

-> Bug Description

-> Expected Desc

-> Steps

-> Status

-> Screen shot ( Y/N)

-> Tester Name ( auto genarated)

-> Reviewed by

-> Developer

-> Comments

-> Re-opened ( Y/N)

 

Srinivas

Shakkila

 Profile Answers by Shakkila 

• Dec 9th, 2008

 

Here are some of the bug attributes,

1. Bug's Occurence ( Source or which version of the application it has occured ).
2. Severity and prority of the bug in order to resolve it.
3.Current status of the bug ( Whether it s opened or closed or in watch list )
4.Reproduction of the bug using the current environment and screen shots.
5. In which test phase or test cycle does it belong to ?
6. The type of the bug . Is it Major or minor ?

kk01041883

 Profile Answers by kk01041883 

• Jan 17th, 2010

 

Bug attributes

1. Synopsis - Brief description about the issue
2. Description - Steps to reproduce the defect
3. Serverity
4. Priority (Optional)
5. Regression or New issue
6. Raised build number
7. Action to be taken by
8. Resolver (Development lead or Manager)
9. Release version
10. Module name i.e Under which part of the application the issue is raised. This will help the development where the issue needs to be fixed in the application.