Results 1 to 9 of 9

Thread: Bug report format

  1. #1
    Geek_Guest
    Guest

    Bug report format

    Question asked by sreekanth

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


  2. #2
    Expert Member
    Join Date
    Nov 2006
    Answers
    518

    Re: Bug report format

    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:

    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).

    Lack of WILL POWER has caused more failure than
    lack of INTELLIGENCE or ABILITY.

    -sutnarcha-

  3. #3
    Contributing Member
    Join Date
    Feb 2007
    Answers
    47

    Re: Bug report format

    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

    Last edited by neelim; 04-06-2007 at 12:40 AM.

  4. #4
    Junior Member
    Join Date
    Jul 2007
    Answers
    8

    Re: Bug report format

    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


  5. #5
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Bug report format

    Quote Originally Posted by sutnarcha View Post
    A bug report is a record of all the bugs/defects that are encountered during testing.
    Dear sutnarcha,

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

    Each bug has it's own different bug report.

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  6. #6

    Re: Bug report format

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


  7. #7
    Junior Member
    Join Date
    Dec 2006
    Answers
    2

    Re: Bug report format

    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


  8. #8
    Junior Member
    Join Date
    Jul 2007
    Answers
    4

    Re: Bug report format

    thanks for the easiest answers


  9. #9

    Re: Bug report format

    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.


  10.  Sponsored Ads
    Ad


     

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact