Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

we are writing bug report in excel-sheet how you are
sending the report to your concern person. (give me the
detail work from bug found, where you are storing and how
you are sending related to your company)

Answer Posted / saurabh_g

Hi ! In our organisaton we use Bugzilla. It is a defect
tracking or incident management tool.

The excel format that you are telling is more
effective/suited for review processes.

If you follow the concept then it goes like dat :
1. Since you want to start from the stage after the bug was
discovered. So document that bug.
Documentation includes :
(a) Bug Desc. (One line)
(b) Steps to reproduce it(for developers).
(c) Screenshots
(d) URL(If you are testing in different builds/iterations)
(e) Test case id that failed because of that bug.
(f) Severity and priority of that bug.
(g) mail it to : concerned dev, cc ur Test lead or
reporting head.
(h) Logs(if possible)
(i) Last but not the least : Bug Status(New)

2. After dev. examines that bug, he will change its status
from new to Invalid/Open/Won't fix/Resolved/Fixed and send
back to you.

3. Verify that bug in new build. If it is fixed again
change the status to Verified and closed.

4. Send it to the concerned dev. and don't forget to put ur
lead in cc.

In case that bug is not fixed you can change the status to
reopen and follow the same procedure (Vicious circle :) ).

Note : Bugs are ideally to be closed at the end (Leave them
as verified after confirming the bug fix). Because there
are chances of that bug coming again after other fixes.

Cheerz,
Saurabh Garg

Is This Answer Correct ?    6 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What is Pre UAT and UAT is there any difference ?

3643


What are the bugs we cannot find in black box?

1208


What is test closure?

1402


What is Bomb Testing?

2276


Can you explain tailoring?

1193


Enlist some bug status along with its description?

1206


What is software review?

1297


What do you like about computers?

2257


What are the typical risks that you identify during test planning and their mitigation plan and Contengency plan.

2578


What are the different types of software testing?

1212


.In languages testing, what is the fixed part and changing part?

2157


i want information about API testing and i want info like how process can be done in company? i want added info like coding ,debugging, desing in c.v ? what should add in c.v for eg banking domin? pls any answer my question?

2159


what are the functional test cases for enter user name,enter pass word,click on ok(only functional test cases)

2492


What is a defect?

1192


What is the purpose of test strategy?

1201