What are the properties of a good requirement?
Answers were Sorted based on User's Feedback
Answer / priya
As a tester point of view, a good requirement is defined as
a requirement which can be tested easily by creating test
cases or by writting test scripts
| Is This Answer Correct ? | 14 Yes | 0 No |
Answer / sam
Clear,
Complete
Visible
Consistent
Measurable
Traceable
Resonable
| Is This Answer Correct ? | 9 Yes | 0 No |
Answer / nisant
Good requirement : As per the testers point of view , the
requirement should not be complex .its should be clearly
understood and it should be one to one or one to many
testing approaches required to cover the requirement ,not
many to many . It should be clearly ensure that it should
not escalate any defect in future for the application. It
should be so clear that all flexibility of the requirement
can be easily find out and theses things can be take care
during the preparation and execution of the test cases of
the application .
| Is This Answer Correct ? | 6 Yes | 2 No |
Answer / sunil reddy
a good requirement is easily understandable and testble
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / mubeen akhtar
Is the requirement correct?
Is the requirement complete?
Is the requirement clear?
Is the requirement consistent?
Is the requirement verifiable?
Is the requirement traceable?
Is the requirement feasible?
Is the requirement design independent?
Is the requirement atomic?
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / shivanibehere
Good Requirements are those which are clear not only to the
Programmer but also to the Tester.May be it is in a written
form or in the Graphical form, because good requirements
always make program Bug Free.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / bot
Necessary: meaning there is a need for it. There should be
no requirements just because it is nice to have one because
it will add up to the cost if the product. If the product
can meet real needs without it, then it isn’t necessary.
Cost Efficient: a cheaper cost with good quality is better.
Unambiguous: if the requirement can be interpreted in more
than one way, then it should be clarified. Ambiguous
requirements can lead to misunderstandings and unnecessary
effort.
Concise: meaning it should be simple and clear.
-there are no program that is bug free.
| Is This Answer Correct ? | 0 Yes | 0 No |
consider therez 1 land and it has mango trees in it, what are the tets cases or how will we count no of mangoes on all trees
When do we perform smoke testing?
What is means by Bottle Neck testing ?
What is prior review?
hi plz send me top 30 FAQ's & answers on MANUAL TESTING.... regards Sonia
I am working on dotnet technology. Recently i came to testing. I want to write general test cases for any interface either windows application or web applications. Please cover all these issues: 1) Database issues 2) Integrated Related Issues 3) Business logic issues 4) User Interface issues 5) Network related issues
What scripting language should tester know when his organisation using Automation tool like wise any tool? wht kind of script should tester should be familiar?
write a use case format for login
who wil give the standards of testing ? iso or astm
Do you feel any dis-advantage over the current process? if he/she says any, have You discussed with your Manager reg this ? Why?
what is the diff b/w bug and defect?
1> Which is the latest technology use for login page? 2> What is virtual keyboard? Is it more secure than key board?