Integration Testing .pdf
Original filename: Integration Testing.pdf
Author: Shikha Sharma
This PDF 1.5 document has been generated by Microsoft® Word 2013, and has been sent on pdf-archive.com on 15/06/2020 at 09:28, from IP address 217.138.x.x.
The current document download page has been viewed 47 times.
File size: 412 KB (3 pages).
Privacy: public file
Download original PDF file
Integration testing is done to test the modules/components when Integrated to verify that they work
as expected i.e. to analyze the modules that are working fine individually does not have issues when
When Talking in terms of testing a big program with a black box testing procedure, involves the
mixture of many modules that are tightly coupled with each other. We can use the Integration testing
procedure concepts for analyzing these types of scenarios.
The Significance of Integration testing is also rather straightforward- Integrate/combine the device
tested module by one and examine the behavior as a joint unit.
The main function or purpose of the testing is to Check the Interfaces involving the units/modules.
We normally do Integration testing after"Unit testing". Once all of the individual units are made and
tested, we start joining those"Unit Tested" modules and begin doing the integrated testing.
The main function or purpose of the testing is to test the Interfaces between the units/modules.
The individual modules are tested in isolation. Once The modules are unit tested, they are integrated
one by one, till all the modules are incorporated, to check the combinational behavior, and confirm
whether the requirements are executed properly or not.
Here we need to understand that Integration testing does not occur at the end of the cycle, instead,
it's conducted simultaneously with the evolution. So in the majority of the times, all the modules aren't
actually available to test and this is exactly what the challenge comes to examine something which
Why Integration Testing?
We feel that Integration testing is complex and needs Some development and logical ability. That's
true! Then what is the aim of incorporating this testing in our testing strategy?
Here are some reasons why:
In the real world, when programs are developed, it is Broken down into multiple modules and
individual programmers are assigned 1 module. The logic executed by a single programmer is quite
different than a different programmer, therefore it becomes important to check if the logic
implemented by a programmer is according to the expectations and producing the suitable value in
accordance with the prescribed criteria.
A lot of time the face or the structure of data varies when It travels from 1 module into another. Some
values are appended or eliminated, which causes issues in the later modules.
Modules also socialize with a few third-party tools or APIs Which also need to get analyzed the
information accepted by that API / instrument is correct and the answer generated can be as expected.
A Common problem in analyzing -- Regular requirement change! :-RRB- A lot of moment developer
deploys the changes without device testing it. Integration testing gets significant at that moment.
1. There are several benefits of the testing and several of them Are listed below.
2. This testing makes sure that the incorporated Modules/components work correctly.
3. Integration testing may be initiated once the modules to be Analyzed are readily available. It
does not demand the other module to be done for testing to be performed, as Stubs and
Drivers may be used for exactly the exact same.
4. It finds the errors linked to the interface.
Listed below are a few challenges that are included in the Integration Test.
1. Integration testing entails examining two or more integrated Systems so as to make sure that
the system operates correctly. Not just the integration hyperlinks should be analyzed but
exhaustive testing taking into consideration the surroundings ought to be done in order to be
certain that the integrated system functions correctly.
2. There might be different avenues and permutations which can be applied to test the
3. Managing Integration testing becomes more complex due to Few variables involved in it like
the database, Platform, surroundings, etc..
4. While integrating any new platform with the legacy system, It requires a whole lot of changes
and testing efforts. The same applies while integrating any 2 legacy systems.
5. Adding two Unique methods developed by 2 Different businesses is a big challenge as to how
one of the systems will impact another system if any modifications are complete in any one
of these systems isn't certain.
6. To Be Able to minimize the impact when Creating a system, Few things should be taken into
account like integration with Other systems, etc.,.