Answer Posted / x

A defect/incident is always a reflection of the sympton
experienced when the expected result of a test is not
found. So by this, the only way a defect can be a
duplicate, is if the same identical scenario/symptom is
found in testing.

It is common for a developer to think that if one code
change fixes multiple defects, the defects can be marked as
duplicate. This is incorrect. A fix can apply to multiple
defects, but a duplicate defect should only be labelled as
such when the symptom is the same, not when the fix is the
same.

can u write some high level scenarios on ms outlook express

2729

---

Can you explain decision tables?

1061

---

What criteria would you use to select Web transactions for load testing?

2101

---

WHAT IS PROTOCAL TESTING..EXPLAIN? L2, L3 PROTOCALS TESTING MEANS WHAT?EXPLAIN BRIEFLY

6734

---

Did you ever worked with B.A's and when?

2045

---

Explain the components of a test plan?

1092

---

How to validate a Testcase.and is the testing Methodology.

2292

---

What is the difference between code walkthrough and code review? What is the difference between walkthrough and inspection?

2918

---

IF ASCII_CODE_OF_ENTERED_CHAR is less than 44 THEN reject it ELSE IF ASCII_CODE_OF_ENTERED_CHAR is greater than 56 THEN reject it ELSE it's a digit, so accept it Which one of the following sets of ASCII codes do you use to test the sample code above WITHOUT redundant coverage?

9699

---

What is difference between Build, Version and Release

2196

---

HI, This question is Investment Banking domain related Question. I was asked in an Interview to tell the 5 test cases for Equity,Bond,Futures and options. Please help.. Pragya

4469

---

What are bug leakage and bug release?

1190

---

What is deferred status in defect life cycle?

1157

---

When we are recording in WinRunner and interact with the AUT, what does WinRunner do?

1968

---

1.For a single module how many builds are possible 2.what will be the max or min time to finish up an single module

2011

---