In big bang Integration testing, individual modules of the programs are not integrated until every thing is ready. This approach is seen mostly in inexperienced programmers who rely on 'Run it and see' approach. In this approach, the program is integrated without any formal integration testing, and then run to ensures that all the components are working properly.
Unfortunately, whilst it may be possible to get away with it within some simple sequential programs, particularly if sensible design methods and good Function and Module Tests have been applied, the use of such an approach large commercial applications is likely to be much less successful.
The application of this method often simply leads the programmer to have to re-separate parts of the program to find the cause of the errors, thereby effectively performing a full integration test although in a manner which lacks the controlled approach of the other methods.
- There are many disadvantages of this big bang approach
- Defects present at the interfaces of components are identified at very late stage.
- It is very difficult to isolate the defects found, as it is very difficult to tell whether defect is in component or interface.
- There is high probability of missing some critical defects which might surfaced in production.
- It is very difficult to make sure that all the cases for integration testing are covered.
Do you like this post?
Subscribe to receive new posts via RSS or email. Join!