Testing Levels
and Types
There are basically three levels of testing i.e. Unit
Testing, Integration Testing and System Testing. Various types of testing come
under these levels.
Unit Testing
• To justify a single program or a section of a individual program.
• Lowest-level component test (Each test validates a single module that, based on the technical design documents, was built to perform a certain task )
• Key foundation for later levels of testing
• Detects 65% - 75% of all bugs
• Stand-alone test (Each test examines an individual component that is new or has been modified.
• Ensures the conformance to each unit in LLD.(Low Level Design)
• Also known as Module test
• Lowest-level component test (Each test validates a single module that, based on the technical design documents, was built to perform a certain task )
• Key foundation for later levels of testing
• Detects 65% - 75% of all bugs
• Stand-alone test (Each test examines an individual component that is new or has been modified.
• Ensures the conformance to each unit in LLD.(Low Level Design)
• Also known as Module test
Integration Testing-
To verify interaction between system components
Prerequisite: unit testing completed on all components that compose a system.
• Testing two or more modules or functions together with the intent of finding interface defects between the modules or functions.
• On a larger level, integration testing can involve a putting together of groups of modules and functions with the goal of completing and verifying that the system meets the system requirements.
• An incremental series of tests of combinations or sub assemblies of selected components in an overall system.
• Integration testing is incremental in that successively larger and more complex combinations of components are tested in sequence, proceeding from the unit level to eventually the full integrated system
• Ensures the conformance to each module in HLD (High Level Design)
System Testing:-
To verify interaction between system components
Prerequisite: unit testing completed on all components that comprise a system.
• Testing more than two modules or functions together with the eager of finding interface defects between the modules or functions
• On a larger level, integration testing can engage a putting together of groups of modules and functions with the goal of completing and justifying that the system meets the system requirements.
• An incremental series of tests of combinations or sub assemblies of prefered components in an overall system.
• Integration testing is incremental in that successively higher and more complex combinations of components are tested in sequence, proceeding from the unit level to eventually the full integrated system
• Clinch the conformance to each module in HLD (High Level Design)
User Acceptance Testing-
• Independent test performed by the enjoyer or QA prior to accepting the delivered system
• Clinch the conformance to the Functional Requirements as specified in the URD
• UAT (User acceptance testing) clinch that the project satisfies the customer requirements.
Types of UAT Testing
• Clinch the conformance to the Functional Requirements as specified in the URD
• UAT (User acceptance testing) clinch that the project satisfies the customer requirements.
Types of UAT Testing
1. Alpha Testing: It is the test done by the client at the developer’s spot.
2. Beta Testing: This is the test done by the end-users at the client’s site or at there own site.
0 Comments