Skip to main content

Requirements Testing

The testing in which Test Data, conditions and the procedure generated from the requirement, that testing is called Requirements Testing. Requirements Testing includes function and Non Functional Testing.

As we know that Software Requirement document is the very important part in the software development process. and we also know that most of the bugs in the software is due to our Software Requirement document have many errors. Software Requirement document have many Functional and incompletion errors.  So if we correct the Requirement error in early phase of the software development then we make safe ourself to fix them in later stage because in later stage due to error multiplication the cost is very high to fix them.

Requirements Testing is the testing the requirement that are these requirement are feasible or not. Because there are many condition for completion of the project . These may be time, resource, budget etc. In the Requirements Testing we check the technology that will be used and what is the purpose to develop that software.  

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Integration Testing

When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.