Integration testing

I have to make a small speach about Integration testing on Wednesday. So, I wrote down some main points I would like to discuss. I think they might be interesting for the readers of my blog. Here are they.


Integration testing ("I&T") is the phase in software testing in which individual software modules are combined and tested as a group.

Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.

Big Bang Testing - in this approach, the program is integrated without any formal integration testing, and then run to ensures that all the components are working properly. Bad way of testing!

Performance testing - The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing.

Load testing - Load testing is usually defined as the process of exercising the system under test by feeding it the largest tasks it can operate with.

Stress Testing - Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how.

Good way of testing - all the units of a system must be integrated consequtively and integrated in step by step process by incrementing the levels of testing at one end to other end.