The process of requirements based testing deals with validating whether the requirements are complete, consistent , unambiguous, complete and logically connected. With such requirements, we can proceed to develop test cases to ensure that the test cases fullfill all the requirements. Testing in this technique revolves around requirements. The strategy of Requirement based testing is to integrate testing throughout the life cycle of the software development process, to assure quality of the Requirement Specification. The aim is defect prevention than defect detection.
Taking Requirement Based testing into account, testing is divided into the following types of activity :
Testing should be defined in quantifiable terms. The goal is considered to be achieved only when test coverage is 100%.
Test cases must be in accordance with requirements specification.
Join the logical parts together to form/build test cases .
Execute the test cases to evaluate the results.
Check whether actual results deviate from the expected ones.
Check for functional test coverage.
Test manager is responsible for monitoring the test case executions, that is, the tests passed or failed, or to ascertain whether all tests have been successfully performed.
Various studies have shown that software projects fail due to the following reasons:
So the requirements based testing process addresses each of the above issues as follows :
Structure or architecture of an application is the foundation upon which rest of the things depend. Structural testing can thus be implemented at all levels or at any phase throughout the software development life cycle.