先决条件 – 集成测试
1. 自上而下的集成测试:
自顶向下集成测试也称为增量集成测试。在这种自上而下的方法中,首先测试较高级别的模块,然后测试较高级别的模块,然后测试较低级别的模块。然后这些模块进行相应的集成。这里上层模块是指主模块,下层模块是指子模块。这种方法使用Stubs,主要用于模拟子模块,如果调用的子模块没有开发,这个Stubs 可以作为暂时的替代。
2. 自下而上的集成测试:
自底向上集成测试是集成测试的另一种方法。在这种自下而上的方法中,首先测试较低级别的模块,然后测试较低级别的模块,然后测试较高级别的模块。然后这些模块进行相应的集成。这里低层模块是指子模块,高层模块是指主模块。这种方法使用测试驱动程序,主要用于启动和传递所需的数据到子模块,如果需要,从更高级别的模块到更低级别的模块。
下图表示自顶向下和自底向上集成测试方法。
自顶向下集成测试和自底向上集成测试的区别:
S.No. | TOP DOWN INTEGRATION TESTING | BOTTOM UP INTEGRATION TESTING |
---|---|---|
01. | Top Down Integration testing is one of the approach of Integration testing in which integration testing takes place from top to bottom means system integration begins with top level modules. | Bottom Up Integration testing is one of the approach of Integration testing in which integration testing takes place from bottom to top means system integration begins with lowest level modules. |
02. | In this testing the higher level modules are tested first then the lower level modules are tested and then the modules are integrated accordingly. | In this testing the lower level modules are tested first then the higher level modules are tested and then the modules are integrated accordingly. |
03. | In this testing stubs are used for simulate the submodule if the invoked submodule is not developed means Stub works as a momentary replacement. | In this testing drivers are used for simulate the main module if the main module is not developed means Driver works as a momentary replacement. |
04. | Top Down Integration testing approach is beneficial if the significant defect occurs toward the top of the program. | Bottom Up Integration testing approach is beneficial if the crucial flaws encounters towards the bottom of the program. |
05. | In Top Down Integration testing approach the main module is designed at first then the submodules/subroutines are called from it. | In Bottom Up Integration testing approach different modules are created first then these modules are integrated with the main function. |
06. | It is implemented on Structure/procedure-oriented programming languages. | It is implemented on Object-oriented programming languages. |
07. | The complexity of this testing is simple. | The complexity of this testing is complex and highly data intensive. |
08. | It works on big to small components. | It works on small to big components. |
09. | In this approach Stub modules must be produced. | In this approach Driver modules must be produced. |