santhaseelan

• Feb 26th, 2015

 

usually for configuration mgmt purpose i think.

Shivakumar

• Mar 5th, 2015

 

We should write bug report when Defect raised by us(Testers). When developer accept that defect then it is called as bug. We need to give the details of the Defect in Defect Reporting Template to DTT (Defect Tracking Team) what ever we raised because if well giving the explanation or report of the Defect like in which build version we found that bug,Test case ID, Test Scenario, Defect Id , Is it Reproducible or not, Environment details (like Operating System,Type of Browser, System Configuration details), Priority of the Bug, etc. How much of details we produce to the developer that much easier to find the bug and developer can fix that defect as early as possible.

tayal.1991

 Profile Answers by tayal.1991 

• Mar 23rd, 2015

 

As i have learned, Test Lead creates the Bug Report, and it is created for the client need. To tell the client how much time has been spend on the project, hot much Defects have been found, how much value add have been raised in the application.

Gaurav.khurana

 Profile Answers by Gaurav.khurana 

• Apr 18th, 2015

 

Bug is what testing team raise and defect it becomes once dev accepts its a problem.. you have interchanged it @shivakumar

Gaurav.khurana

 Profile Answers by Gaurav.khurana 

• Apr 18th, 2015

 

Writing details in bug tracking tool is nothing but - Bug report. When you are sure that there is bug in the system you should open a bug in the tool and mention all the necessary details for it so that it gets fixed.
https://bugs.opera.com/wizarddesktop/ is one example of bug report. its nothing but mentioning proper details for the bug so that it can be fixed

Alex

• Jun 9th, 2015

 

@gaurav.khurana, shivakumar is right, it need not to be interchanged. And reporting a bug is different from bug report. Bug report is summary of bug reported.