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