26). how will know do written test cases are sufficient to validate application of functionality? 27). how will you prepare test data to validate input object? 28). explain defect status? 29). how will know whether the developer accepted you defects or not? 30). explain acceptance test? 31). explain when we stop testing? 32). explain scope of your project? 33). in which module you conducted testing? 34). explain defects which you found in that module? 35). if defect is not reproducible then what information you will provide to developer 36). if developer is not accepted your defect then what you will do?

1522

---

How can a servlet be used to generate plain text instead of html?

537

---

What is validation in mvc?

1

---

Can google docs open excel?

267

---

What are the trigger events in qtp?

567

---

---

Is salary a ratio or interval?

544

---

How java is similar to c?

580

---

What makes up a server?

479

---

Explain the asp.net mvc request life cycle? : asp.net mvc

492

---

What are the control signals used by the 8085?

699

---

Explain the working of serialization?

481

---

what is ORM (Object-Relationship-Model) in Rails?

539

---

The change in a semi-conductor strain gauge, in resistance on application of strain is mainly due to the change in its

559

---

Explain where are the files placed while deploying the resource adapter in web logic server?

511

---

What does *p++ do?

576

---