Requirements Based Testing
Overview
In this tutorial, we will learn about Requirements Based Testing. It ensures the product meets the user’s requirements and works as expected.
Requirements Based Testing
Requirements-based Testing( RBT ) is a testing approach in which test cases, conditions, and test data are derived from the software requirements. It includes functional testing and also non-functional testing.
Stages in RBT
The different stages in RBT are as follows:
- Understanding Requirements
- Create Test cases
- Execute Test cases
- Verify Test Results
- Log & Manage Defects
- Regression Testing
- Test Coverage
Understanding Requirements
The first step in RBT is having a clear, detailed, well-documented set of requirements. These requirements can be functional or non-functional. Review of the requirements to identify any ambiguities, inconsistencies, or gaps. This stage includes the participation of stakeholders, domain experts, developers, and testers.
Create Test Cases
Based on the final reviewed requirements, testers create detailed test cases. The test cases are designed to verify that each requirement is implemented correctly. Each test case will include the following parameters:
- A description of what aspect of the requirement is being tested.
- Initial state or precondition
- The test inputs
- The steps that need to be followed during the test.
- The test data required for testing.
- The Expected outcomes or results.
Execute test cases
Testers execute the test cases against the system under test on the QA environment. This stage involves carrying out the test steps, documenting the results, and comparing them against the expected outcomes.
Verify Test Results
Verify if the expected and the actual results match each other for the test cases. If a piece of functionality does not work as expected, testers mark the test case as failed. They log this as a defect in the defect tracking system. They provide details about the issue, including steps to reproduce the error, the test case that failed, screenshots, logs, etc.
Log & Manage Defects
Defects detected during testing go through the defect life cycle and are tracked to resolution. Defect stats are maintained to give the software team the project’s overall status.
Regression Testing
When defects are fixed, regression testing is performed to ensure that the changes have not introduced new bugs and that the software is working as expected.
Test Coverage
Verify that the tests cover both functional and non-functional requirements of the software. RBT is completed only when all the functional and non-functional testing is complete.
The goal of requirements-based testing is to validate that the developed software meets the user requirements.
—
Software Testing Tutorials:
