Bug report format

[B]Question asked by sreekanth[/B]

Explain about bug report format? Please give a example for bug reporting

A bug report is a record of all the bugs/defects that are encountered during testing.

Each company has their own format for this report. General format can be made with following details::D

Defect ID, description, build version ID, feature/module, test case title that failed, reproducible or not, status (new/reopen/close), severity, priority, testers name, reviewers name, date of defect detection, name of developer assigned to, suggested fix (solution).:cool:

Standard bug reporting format
----------------------------------
date of logging:
logged by:
product / software under test:
version:
behavior in other similar products/softwares:
------------------------------------------
earlier versions of product/software: affected / not affected / not applicable
parallel products/softwares of current version: affected / not affected / not applicable
other products/softwares: acrobat / quarkxpress / ms word /others
details of operating system under test:
--------------------------------------
operating system language
operating system tested: windows macintosh solaris unix
operating system affected: windows macintosh solaris unix
system configuration under test: processor ram hard disk
space specific information required to isolate defect / bug:
-------------------------------------------------
ime used during testing (if req.): windows: microsoft default ime / atok 16 / others
macintosh: kotoeri (default ime on mac) / mac vje delta / others
solaris: solaris default ime / others
web browser information (if req.):
browser tested: internet explorer (ie) / netscape / safari / others
browser affected: internet explorer (ie) / netscape / safari / others
printer information (if req.): printer tested: postscript / pcl / others
printer affected: postscript / pcl / others
font information (if req.):
fonts tested: truetype / type 42 / opentype / type 1(t1) / others
fonts affected: truetype / type 42 / opentype / type 1(t1) / others

client / server information (if req.):
client information: operating system: windows / macintosh / solaris / others
processor: ram:
server information:
operating system: windows / macintosh / solaris / others
processor: ram:
application server: weblogic / websphere / sybase / others
testing tool used: winrunner / silk test / load runner / others
component / feature affected:
any other specific information (if req.):
1)
2)
3)
core information required to re – produce the bug / defect:
----------------------------------------------------------
problem title:
pre – requisites:
steps to reproduce the bug:
step no. Description
1
2
3
4
5
actual result:
expected result:
other related information:
--------------------------
nature of testing performed: integration / acceptance /structured / regression / end to end / installer / workflow / adhoc / dongle / performance / others
test case number failed: 10.p.23.5 (eg.) / na
nature of bug: new bug / resulted from a bug fix
ref. Bug number: 224488 (dummy)
version / build number tested: nature of build / software tested: installer / release / others
phase of testing: pre ec phase / alpha phase / beta phase / fc phase / rc phase / gm phase
whether bug is reproducible: yes / no
occurrence of bug: when: always / sometimes (not consistently occurring)
where: on all systems / only specific to a particular system
is this bug document specific: yes / no if yes, path of the attached document:
any other attachments (if any): path:
probable affected areas:
what works and what doesn't / notes / comment’s:
1)
2)
3)

-------------
neelima

A bug report is to report a bug with other details. General format---
date, bugid, description, test case id, problem in severity, problem in prioity, author, assigned to, version, expected closing date, actual closing date, status

[QUOTE=sutnarcha;9847]A bug report is a record of [b]all the bugs/defects[/b] that are encountered during testing.

[/QUOTE]

Dear sutnarcha,

A bug report is not a record of [b]all the bugs/defects[/b] but [b]it's record of individual bug [/b]that is encountered during testing.

[b]Each bug has it's own different bug report.[/b];)

Nice answare....even i came to know so many things

Bug report can be done different way but , the main gole is to explain the developer that where the bug is found and how it found .otherwise they will not accept it as a bug

thanks for the easiest answers

Bug Report is a report which has the details of the Defects raised and their impact on the modules. The General format of the report is shown below, however it may differ from company to company.

Defect ID, description, version ID, module, Subject, reproducible or not, status (new/reopen/close), severity, priority, testers name, defect detected date, assigned person.