There are different bg tracking tools n the market but rational clear quest is the most commonly used tool.

tracking a bug is much easier and communicative when done through a tool.

format of the tool:

(bug id is usually generated by the tool)

outside the excel sheet we might need to fill the fields like:

tester name (uasually genrated with the login name)

date of execution etc.

a <submit> and < cancel> button

'Swetha' is give a good answer. 'Bug tracking' means to track(separate) the bugs from Results.So tracking is different from Reporting. Reporting means post the bug using tracking tools.

Hi

Serverioty of bug depends on how much it will going to affect the system

Priority of bug depend on how much earlier bug should be fixed to carry testing process

Bug Tracking : Any bug that is detected will have a status as New->Next Open->Assigned to developer-->Fixed-->Assigned to tester-->If pass after validation close the defect if fail assign it back to the developer.This is the general flow of bug tracking either you may use a bug tracking tool or an excel sheet.It is convenient to use a bug tracking tool but if we use an excel sheet also we can change the status in each and every phase of bug life cycle.

Defect/Bug Format :

Bug/Defect Id:

Summary :

Steps to Reproduce/Description:xxxxxxxxxxxxxxxxxxxxxx

Detected By :abcd

Version Number :xx.0

Feature/Sub Module/Module :abcd/ab/a

Severity:Critical High Medium Low

Priority :High Medium Low

Reproducible :Yes/No

Assigned to :Developer/Tester/QA Manager/etc

Status :New/Open/Fixed/Closed etc

Test Case Number :xx

Depending upon the company strategy we can add some extra fields in excel sheet or remove some fields which are not needed

Severity is the seriousness or the impact of the defect over the application/product functionality.It can be specified in different ways:

Critical High Medium and Low.

Critical :example like system halt or stuck i.e unable to proceed further testing

High :example like some main features are not working properly where the user has a maximum usage

Medium and Low :This type of defects are not so urgent to be fixed but can wait for some time because there is impact on the functionality is not as severe as in critical and high.But should be fixed before releasing to the client.

Priority :By specifying the priority as high medium and low a developer can understand which defect needs to be fixed prior to which defect.A developer will fix the defects that are having high status next medium next low.

To provide a priority status there is a formula as Priority Severity (vs) Ratings

Ratings:It is decided as Always Sometimes Never.Always means every time defect is reproducible when a certain test case is executed.Sometimes means the defect is occuring for sometimes but not always.Never mean the defect has occured only once but never occured when tried to reproduce

Example :Severity High Ratings Always

Priority High (vs) Always High

Priority should be high because severity is high and the defect is recurring always.This defect needs to be fixed by a developer with high priority.

The ans of this question is simple. You can tell them. how u r report the bug via bug report or Any BuG traking tool. In markt there are many tool availble.

now i have give the Example of the Lotus notes this is one of the Traking tool Now if we are got the 1st build from the development side. Then we start the testing if any bug is found we log on the Lotus notes.
now the Status is open.
if the devloper is fix this bug the status of the bug is Resolved.
after tha the devloper is retun send to me then status of the bug is resolved.
after we are verfiy the bug is fixed or not . if it is fixed then we change the status fix.

• S.No.
  


• Module/Page Name


• Testcase Name


• Description


• Test case Steps


• Expected Result
  


• Actual Result


• Result