naresh reddy

 Profile Answers by naresh reddy 

• Jan 18th, 2007

 

bug tracking is the sequence of steps that we follow when the bug occured.we use some tools.in other way bug tracking is the  "  the way  bug is solved by testung team and the dev team"

sudhir deshmukh

• Jan 24th, 2007

 

Hi, The means of bug tracking is to find out a bug by using a proper process. For that most of the company?s are using bug taking tool like bugzila.Regards,Sudhir

RP2121

• Jan 27th, 2007

 

Hi, The "Bug Tracking" is a Tracking process of the status of the bug once it is detected and reported by the tester. The client and your PM or the test leads gets to know the number of bugs found and what is its status like : Assigned to the developer , Reopened or closed and also the severity and the priority of the bug.This is done with the help of various tools: Bugzilla, Test Director.

Sunitha

• Feb 6th, 2007

 

yes i agree , companies are choosing Bug trackig tool to follow systematic procedure to track Bugs.To avoid Dupilcation and easier to track any one related to Project.

srilathayt

• Feb 9th, 2007

 

bug tracking is nothing but tracking all the defects some companies may use defect profile template to track all the defectsor we can use tools to trackex: bugzilla,issue-tracker, pr-trackerTest director is also acts as a bug tracking tool and management toolneed not to say u abt this

nirmmal

 Profile 

• Feb 11th, 2007

 

Bug tracking is the process you use to address programming errors found. This process includes recording the bug, reviewing it, recording the fix needed, and deciding whether or not the bug will be fixed considering budget and schedule. Keeping good records of decisions made will help to control the scope of the project. Bug tracking also enables you to know what was done with identified issues, why the system was changed, and what future changes to consider.

Harika

• Feb 21st, 2007

 

Bug Tracking is the process/series of steps followed from the time a bug is found, fixed and closed. The steps followed are

1. As soon as the bug is found it's entered in defect tracking system and assigned the status "New"
2. Once it's been analysed and accepted as a genuine defect, the status is changed to "Open" . If the bug is found to be invalid the status is changed to "Reject"
3. It's then assigned to a developer and status is changed to "Assigned To"
4. Once it's fixed by developer status changes to "Fixed/Ready to test".
5. Tester then re-test the fix and if fix works fine, he/she sets the status to "Closed". If the fix doesn't work it's changed to "Re-open".
6. In some cases, if the bug is a major fix then it's postponed to future releases in which case the status is changed to "Deferred" and considered for future release.

Sujatars

 Profile Answers by Sujatars 

• Mar 13th, 2007

 

Bug Tracking is the processof tracking te status of the bug or series of steps followed from the time a bug is found, till the bug is  closed.It helps u avoid duplication of bugs & also enables you to know what was done with identified issues, & the changes made to the system.

subhas

• Mar 18th, 2007

 

real time definition:
 Bug tracking is a process to be followd to track the bug by tester,tech lead/test lead/project lead people from new status  to close status.


         Ex.     New (Defect found by Tester)_____ Tech Lead/test lead/project lead will have to chage the status suppose OPEN --------send to the developer----test it for is it bug or not ------1.if bug then fix it and send it to the tech lead --------tester for regression testing (nothing but re-execution of modified build) 2. if not bug same thing will back to the tech lead------tester for Re-teting (re-execution of same build) this process will go on until the bug status is Close.

if you want more than that or any query on functional testing  can mail me at subhas_hord@yahoo.co.in or 09989620592

Sujatars

 Profile Answers by Sujatars 

• Jun 21st, 2007

 

Bug Tracking is the process of tracking the bug from its origin till the bug gets resolved & s closed.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Dec 10th, 2008

 

Bug tracking: This is a process in which testers can log the issue  found by them and reported to develop ment team to fix, in other words it's a common repository for both testing and dev teams to track all the issues status wise.

 

srinivas

mattathias

 Profile Answers by mattathias 

• Dec 15th, 2008

 

Many good examples here. Would like to add one more: Archerfish. Simple, effective and cheap.

One thing to consider is not so much the tool, but the methodology you use to test. So much bug-testing (for web sites anyway) is simply negative testing: play with it till you break it. It's critical to test according to scripts built on your documentation, so that every feature and function gets addressed thoroughly. Well worth the effort, but often overlooked due to time, budget, etc.) Just my two cents.

imnothegeek_lav

 Profile Answers by imnothegeek_lav 

• Dec 17th, 2008

 

bug tracing means ..keeping a track of the course of the bug from its first occurence to its last occurence .i.e. tester fing a bug & till it is finally fixed(it can be reopened/occur many times between these two)

imnothegeek_lav

 Profile Answers by imnothegeek_lav 

• Dec 17th, 2008

 

bug tracking means ..keeping a track of the course of the bug from its first occurence to its last occurence .i.e. tester finding a bug & till it is finally fixed(it can be reopened/occur many times between these two)

sangeethaarjun

 Profile Answers by sangeethaarjun 

• Mar 11th, 2009

 

Bug tracking is the process of tracking bugs from the time it is identified till it is closed.

status of the bug and responsibility mentioned as follows:

Raised -  Tester
Assigned- Test Lead
Fixed - Developer
Retest- Tester
Closed - Tester
Reraised- Tester

Based on the status of the bug which is tracked in the defect tracking tool e.g: Test director, the respective member will perform the respective task till the bug gets closed to ensure that all the bugs are fixed, retested and closed.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 21st, 2009

 

Bug tracking refers to a process that enables users to accurately and thoroughly understand the given state of a particular defect.  Bug tracking includes the following things:

1) ownership
2) status (ex: 'open,' 'fixed,' etc.)
3) priority and severity levels
4) project and build
5) related test case(s)
6) related requirement(s)
7) history