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

what is negative testing and positive testing with example?

2 Answers  

---

What is meant by code walkthrough?

5 Answers  

---

What are the two main categories of software testing?

0 Answers  

---

When should testing start in a project? Why?

7 Answers  

---

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it is a valid bug?

11 Answers   GE,

---

what is scenario????

6 Answers  

---

if you have 100 test cases, in that 80 passed and 20 failed, Which test cases your select for Retest and Regression testing?

4 Answers  

---

what is walkthrough?

6 Answers   Semantic Space,

---

Can we include 'Space' and 'Underscore' in alpha characters or alphanumeric characters at the time of Defect Reporting?

2 Answers  

---

how can u do database testing manually?

4 Answers   HCL,

---

what is meant by test stretagy?

2 Answers   Four soft, TCS,

---

what is liquid fuel testing?

0 Answers  

---