Answer / poonam

Hi Dinesh,

I don't agree with you that snapshots are not compu;sory in
the bug report. From my view point, snapshots provide
better undertstanding to the bug/defect described in the
report.

And sometimes,you can define the bug with description so at
that time you can only tell the problem with help of screen-
prints or snapshots of the problem

Answer / dinesh

it is ok to have all fields as mentioned by poonam except the attachments/snapshot in the bug report.

Answer / poonam

To start with give a brief description of the bug/defect
and tell about its severity, type of defect it is, project
name, enviornment in which its tested,status, expected
result , actual result and details as what steps needs to
follow to re-create the same defect and also its always
better to attach screen-prints with the defect report.

What is the Stub abd the driver ?Are these both using at the time of Top-up approach of integration testing and bottom-down approach testing .?

3 Answers   Kanbay,

---

Why we use Excell sheet not the Microsoft Word to write test cases and all? Why ?

3 Answers  

---

Mapping the test cases with the requirement. What is this process called?

6 Answers   iSoft,

---

What testing procedure you follow? how

0 Answers   RBS,

---

Can u specify one Deadlock or Processlock issue in a client server application?

1 Answers   Kanbay,

---

What kind of input do we need from the end user to begin proper testing?

0 Answers  

---

What is test strategy??

3 Answers  

---

if bugs found then it fixed then it's status is close. same bugs arise inafter 2 3 months in same module then what can do as tester

6 Answers  

---

What is Buddy Testing?

2 Answers  

---

What type of SQL queries will be asked in the Testing interview?

4 Answers  

---

What is your testing approach/plan if requirements are frequently changing?

2 Answers  

---

who will prepare tracebility matrix?

2 Answers  

---