Hi

If you found any bug first of all u've to verify it again it is bug or not.. then log the bug in

BTS ( report to dev if BTS not available)..

srinivasulu.B (srinivasulub1981@gmail.com)

Hi Anupam

When we found a bug while testing We need to clarify whether it is bug or not? If u think that's a bug then we have to log the bug if u r using any bug tracking tool. If u r not using any bug tracking tool U have to prepare the bug report in an excel sheet. Assume that u don't have any bug tracking tool.

We have to give a unique bug id to that bug. Give title of the bug then Description Steps to reproduce Expected Result Actual Result Priority Severity Build no. Test case id and Date found by.

If u have bug tracking tool u'll find all these fields in that u simply enter all these in those fields and automatically bug id will be generated.

When we log or enter a bug that should be in Active or New status. When it gets assigned to developer he'll fix the bug and he'll change the status to fixed or resolved After that u have to check or Verify the bug on the new build. If u didn't find any the same bug in the latest build u just close the bug. Otherwise u have to Reopen the bug. In this way bug life cycle goes on.

Cheers

After confirming it as a Bug You have to post it in bug tracking tool. Then the status of the Bug will be New . Your team lead or any senior person will review it and if it is really a bug then he will change the status to Open . If he confirms that it is not a bug he will close the bug and change the status to Closed .

All the Open status bugs will be mailed to the development team. Their team lead will assign the bugs to the corresponding developer. He will change the status to Assign and add the corresponding developer name. When the developer fixes that bug he changes the bug status to Test .

If the development team lead confirms that this is not a bug then he rejects that bug with valid reasons. Then the status of that bug will be Rejected .

If he confirms that this is not required for the current build but may be useful for the future releases then he changes the status of the bug as Deferred . All the Deferred bugs will be considered for future releases

All the Test status bugs will be mailed to the testing team. The corresponding tester tests that bug in the new build or patch and change the status to Closed if it is fixed otherwise to Re-Open if it is not fixed.

All the Re-Open bugs will be mailed to the development team and then the above cycle repeats.

Dileep

Excellent answer.

hi

if you found any bugs first of all you should verify any same bugs are exist in your defect traking tool before login your bug.

regrads

Bala

I would suggest you the following as soon as you find a defect...

1) Confirm whether the finding is actually a defect (refer to Req. Doc) and make sure it is not a duplicate.

2) Try to reproduce in another testing machine... (sometimes defect occur due to session issues which might have been treated as a different defect)

3) Justify that it is a defect by refering to the Req. Doc. Screenshots & logs would be helpful to save the time in reproducing the defect.

And bug life cycle should be altogether a different question.

-- Danny

Scenario 1:When we encounter with a deviation with the behavior w.r.t functionality or GUI as specified in the FRS or GUI specs then we can directly report it as Bug in the Bug Tracking Tool.It is always a good practice to take the screenshot as a proof of evidence to show to the developers that the bug was there in the application when you were testing it if in case the bug is not repoducable at his end. Specify the steps to reproduce the bug if the bug is reproducable.

Scenario 2:When we are not sure whether it is a bug or not we can send it as an observation to the Test Lead he will review it and ask us to report it when he finds that the observation can be reported as a bug in the Bug tracking tool after refering to the documents or communicating with the customer regarding the behavior of the bug and getting it clarified whether it is behaving as intended or is there any deviation in it if there is no proper documentation .