Requirements are essential input to test planning. When
you plan the test effort, you often begin by identifying the project
requirements that were used during development.
By reviewing system requirements in the planning phase of a test
effort, you can reduce rework, errors, and defects. Quality management
teams use requirements to learn this information:
- New developments in the system
- The parts of the system or system features that must be tested
- How secure the system must be
- The intended system behavior for a given operation
- Compliance criteria
- Performance expectations
The role of requirements in testing
In requirements-based
testing, test cases are designed based on test objectives and test
conditions that are derived from requirements. Examples of requirements-based
tests are those that exercise specific functions or probe nonfunctional
attributes, such as reliability or usability.
According to "Requirements
Based Testing Process Overview" from Bender RBT Inc., the requirements-based
testing process supports two goals:
- Validating that requirements are correct, complete, unambiguous,
and logically consistent.
- Defining the smallest set of test cases necessary to ensure that
the design and code fully meet the requirements.