Answer / 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

Answer / sanjeev sharma

Writing is easy, but writing clearly is hard. When it comes
to write bug explanations… well, writing seems to get even
harder, as far as the IT professional is concerned.
http://sanjevsharma.blogspot.com/2008/10/writing-bug-reports.html

The company has software running in its production environment that was designed and tested on its quad- processor servers with 16 GB of RAM. In order to meet budget constraints, its disaster recovery plan calls for this same software to be installed on functionally identical servers, which are dual-processor with 12 GB of RAM. The test group has been tasked with confirming that the software is going to work on the hardware proposed in the disaster recovery plan. -what testing types is being used in the scenario above?

2 Answers  

---

plz explain about tracebility matrix with example? thanks in advance

2 Answers  

---

What is the difference between volume and load?

2 Answers   Gtech,

---

What is the diff. between Sanity , smoke and ad-hoc testing?

8 Answers  

---

can any one tell me what is the difference between Integration testing and End-End testing? plz dont tell me Integration is whitebox testing and done by developers, where as End-End is blockbox testing and done by testers.

3 Answers  

---

How many process areas are present in CMMI and in what classification do they fall in?

0 Answers  

---

What are the types of testings that can be performed on a login window.

6 Answers  

---

how many levels of software testing?

5 Answers  

---

I Want Real Time Examples for High Sevirity and LOW Priority and Also For LOW Severity and High Priority..,.In most Of da companies QUestion Ariese on This Plz Help Me Answers

6 Answers   Adobe,

---

Can you explain boundary value analysis?

0 Answers  

---

What Tester should do after getting Requirement Doc?

11 Answers   CTS,

---

difference between change management and configuration management

0 Answers  

---