Incremental Testing
A disciple method of testing the interfaces between unit tested programs as well as between system components.
Types:
1. Top down Testing
2. Bottom up testing
1. Top Down
Begin testing from the top of the module hieracrchy and works down to the bottom using interior stubs to stimulate the lower interfacing modules or program.
It tests the program of LLD. If LLD is not ready means it uses a dummy module called STUB.
LLD - Low Level Design
2. Bottom up
* Begin testing from the bottom of the hierarchy and works up to the top.
* It requires the development of driver module which provide the test input call the module or program being testing and display the test output.
It tests the program of HLD. If it is not ready means it uses a dummy module called DRIVER.
HLD - High Level Design
If both dummy variables STUB and DRIVER are presented in the testing process then it is known as Sandwich Incremental Testing.
A disciple method of testing the interfaces between unit tested programs as well as between system components.
Types:
1. Top down Testing
2. Bottom up testing
1. Top Down
Begin testing from the top of the module hieracrchy and works down to the bottom using interior stubs to stimulate the lower interfacing modules or program.
It tests the program of LLD. If LLD is not ready means it uses a dummy module called STUB.
LLD - Low Level Design
2. Bottom up
* Begin testing from the bottom of the hierarchy and works up to the top.
* It requires the development of driver module which provide the test input call the module or program being testing and display the test output.
It tests the program of HLD. If it is not ready means it uses a dummy module called DRIVER.
HLD - High Level Design
If both dummy variables STUB and DRIVER are presented in the testing process then it is known as Sandwich Incremental Testing.
Post a Comment