Answer Posted / bishwajit rk

Defect and testing two faces of a coin. Without testing,
bugs cannot be possible. All the bug detected are due to
one or other form of testing.
Any defect found during testing need to be thoroughly
explain so that the developer should not come back to u and
ask to explain how u got this defect. The process of
explaining a defect to a developer is actually a Art in
itself. When one filed a defect, he should provide certain
thing such as:
1- Test Environment.
2- URS or SRS (defect related to which section)
3- Software Built No. and Software Built Date.
4- Preconditions.
5- Test Data used.
6- Step by step process to reproduce the defect i.e. What
did u did that the defect surfaced?
7- What was the expected result and what is the actual
result.
8- Log or Snapshot or screenshot should be attached.

I think these steps will enough to define a defect.

how do u manage scripts in winrunner when you application is changing frequently?

1483

---

Can you explain regression testing and confirmation testing?

695

---

What is the difference between web based application and client server application?

5452

---

What are the different ways of doing black box testing?

644

---

what is TAS language which is used as a language for some projects/

1589

---

---

What are tools of performance testing?

709

---

How should validation activities be handled?

688

---

consider therez 1 land and it has mango trees in it, what are the tets cases or how will we count no of mangoes on all trees

1587

---

What processes/methodologies are you familiar with?

1881

---

What is revision history and the content of revision history table?

1555

---

what is entry and exit criteria and explain it?

1023

---

what risks do u faced u r projest how do you solve

1631

---

What is Application Performance testing and Operational performance testing

1571

---

What is un-installation testing?

651

---

how can you test the web environment for security testing?

1441

---