Requirements are the basis of testing
A requirement describes what the system must do or how it must be. QA uses requirements as the reference to decide what to test: if the requirement is ambiguous, the test cases will be too. That is why understanding and questioning requirements is a core tester skill.
| Type | Describes | Example |
|---|---|---|
| Functional | What the system does | The user can reset their password |
| Non-functional | How it behaves | The page loads in under 2s |
| Business | The business goal | Reduce cart abandonment by 10% |
A good requirement is clear, complete, consistent, verifiable and unambiguous. If you cannot write a test case from it, it is probably poorly defined.
QuestionToca para voltear
What makes a requirement 'verifiable'?
'The application must be fast' is a problematic requirement because…