Bindu05

 Profile Answers by Bindu05 

• Mar 30th, 2006

 

1. Complete information such that developers can understand the bug, get an idea of its severity, and reproduce it if necessary.
2.  Bug identifier (number, ID, etc.)
3. Brief description of the bug
4. Steps to reproduce the bug
5.  Current bug status (e.g., 'Released for Retest', 'New', etc.)
6.   The application name or identifier and version
7.   The function, module, feature, object, screen, etc. where the bug occurred
8. Environment specifics, system, platform, relevant hardware specifics ,appserver,database
9.   Test case name/number/identifier
10.    Full bug description
11.  Severity of the bug 
12. Screen shots  where the bug has occured

moonster

• May 12th, 2006

 

you can also put what type of problem is it?Coding, Testing..

BISWAJIT PANI

• Jun 19th, 2006

 

The basic elements in Defect Report are

a) Bug id.

b) Test case id .

c) Project name .

d) Module name

e) Sevirity

f) Priority

g) Status

h) Testing Envirnment

i) Brief Description ( waht is that defect ?)

j) Detailed Description ( Process to Get that defect same as test cases )

k) Snap shot of that page ( if required and possible )

Regards

Biswajit Pani ( 09986183456)

Panibiswajit@yahoo.com

 

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Dec 20th, 2006

 

Hi,

Defect profile Template we used..

1.Defect ID

2.Test Case ID

3. Screen/Page Name

4.TestCase Name

5. Steps(To Reproduce the Bug)

6. Expected

7. Actual

8. Bug Description

9. Severity

10. Priority

Regards

Prasad

Srinivas

• Oct 11th, 2007

 

1. Defect ID
2.Defect Description
3.Name of the Test case (which is faled)
4.Expected Result
5.Actual Result
6.Pre-Conditions
7.Steps to Re-Produce
8.Attach Screen shot

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 17th, 2009

 

Contents of defect are

Defect ID,
Summary,
Description (environments, steps to reproduce, Expected values, Actual outcome),

Status,
Severity,
Priority,
Reproducible (y/n),
Detected by,
Detected on,
Module,
Build/version id,
Test Case ID,
Attachments (screen shots or docs).