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.

What is difference between web site testing, desktop application testing and wireless application testing? what is the difference in testing strategy to test them?

2175

---

What is Dynamic Binding and Dynamic Loss?

2104

---

what is the main field of bugzilla which we fill to report bug to any developers???give some brief description??

2146

---

What is change request, how you use it?

1309

---

please give information about ERP Projects and how V-model use in project

2916

---

How can you define state tanstion testing aswell decesion testing with examples.how you can differ them too??

2505

---

What is deferred status in defect life cycle?

1268

---

Please is there any one working with ITR.COM? Having interview with them. Any tips will help.

1915

---

In Quality Center, If we can reuse a non reusable test script as template test, then what is the need of defining reusable test scripts? What additional functionality does Reusable test scripts add when compared to non reusable test scripts?

3052

---

aplitue questions will be based on wich type ?

2573

---

How do u prepare test environment for ur application?

2201

---

What is 'Account Conditioning'?

4567

---

What is bug priority?

1387

---

what is Test management fundamental?

2324

---

Scenario-based testing Option 1 concentrates on actor and software interaction Option 2 misses errors in specifications Option 3 misses errors in subsystem interactions Option 4 Both 1 abd 2

3594

---