Answer / savita

Requirements should be simple and straight forward.
Requirements should describe users need and things the
system/application should do to satisfy that need.
Requirements should not be vague.
Requirement should abe accurate and describe the
functionality to be delivered.
Requirements must be feasible, prioritized, necessary for
the project, umambigious and verifiable and correct.


Hope i got it right.Savitamehta25@gmail.com

Answer / ashok.hugar

1) Requirement should be pointwise
2) Requirement should be clear and easy to understand
3) Requirement should cover All the functionality of the
application
4) Requirement should not change frequently


if m wrong mail me correct ans to following id:
hugar.ashok@gmail.com

how cookie and session testing is done ?????

2 Answers   CMC, TCS,

---

when the test plan will be prepared in waterfall model?

3 Answers   Siemens,

---

You are given two scenarios to test. Scenario 1 has only one terminal for entry and processing whereas scenario 2 has several terminals where the data input can be made. Assuming that the processing work is the same, what would be the specific tests that you would perform in Scenario 2, which you would not carry on Scenario 1?

2 Answers   IBM,

---

Can you explain the different maturity levels in staged representation?

0 Answers  

---

pleez mail me testcase examples for web application..at mina_ims@yahoo.com

1 Answers  

---

Explain scrum process

1 Answers  

---

Very Important Note for all the Testers!!! As the S/w Boom is getting considerably decreased...

13 Answers   Accenture,

---

Can you explain how tpa works?

0 Answers  

---

how we can define bug is an valid bug

3 Answers   ADP,

---

How do you prioritize testing tasks within a project?

4 Answers  

---

what is clinet side validation and server validation??

2 Answers   FIC,

---

What is difference between http and https

5 Answers   AZTEC,

---