- Hybrid integration testing is also known as “Sandwich integration testing� or “Mixed integration testing�.
- As the name defines, mixed approach is the mixture/combination of top-down integration testing and bottom-up integration testing.
- In top-down integration testing, modules are tested at the top-level first. In bottom-up integration testing, modules at the lower-level tested first after that integrate them into upper-level module then tested.
- In the sandwich/hybrid/mixed integration testing, top modules are tested with the lower-level modules and lower-level modules are combined with the top-level modules and tested.
- Hybrid approach uses both the concepts “stubs� and “drivers�. It is necessary to develop stubs and drivers for testing.
- This approach is used to overcome the disadvantages of top-down approach and bottom-up approach. Big-Bang approach focuses on the middle layer of the system while top-down and bottom-up approach focuses on middle to downwards and middle to upwards respectively.
- This testing is mainly performed for test large projects.
This way helps in faster testing of the module’s interfaces.
Aptitude
- Introduction
- Evolution
- Software
Re-Engineering - SDLC Models
- Waterfall Model
- Aglie Model
- Spiral Model
- RAD Model
- V Model
- Prototype Model
- Iterative Waterfall Model
- Top Down Approach
- Bottom Up Approach
- Big-Bang Approach
- Hybrid Approach
- Software Testing
- White Box Testing
- Black Box Testing
SDLC
SDLC Approach
Software Testing
Hybrid Testing Approach in Software Engineering
Hybrid Testing Approach
Working of Hybrid Testing :
- This approach is convenient for small systems.
- All the modules of the software are combined at once.
- This testing helps software testers in saving integration testing time.
- There is no need of developing stubs and drivers.
- It is cost-effective approach.
Disadvantages of Big-Bang Approach :
- Interface issues of the modules are identified at very late stage.
- It is hard to execute all the cases for integration testing without missing a single scenario.
- Fault Localization is difficult.
- This type of testing can only be performed after all the modules are developed so there will be quite a lot of delay.
- High risk critical modules are not isolated and tested on priority since all modules are tested at once.
- This approach is an high risk associated because all the modules are combined together at same time.
→
←