Scribd
Upload
32 views

Integration Testing

Integration testing is a process that tests the interfaces between software modules to evaluate their interaction when integrated together. It involves designing test cases to test modules logically grouped together, such as testing the login and signup features together. Integration testing is performed by first creating a test plan, deciding on an approach like big bang or top-down, designing test scripts, deploying the modules together to run tests, tracking errors, and repeating the process until the system is fully tested.

Uploaded by

Muhammad Sohail Sabir
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
32 views

Integration Testing

Integration testing is a process that tests the interfaces between software modules to evaluate their interaction when integrated together. It involves designing test cases to test modules logically grouped together, such as testing the login and signup features together. Integration testing is performed by first creating a test plan, deciding on an approach like big bang or top-down, designing test scripts, deploying the modules together to run tests, tracking errors, and repeating the process until the system is fully tested.

Uploaded by

Muhammad Sohail Sabir
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Integration Testing

What it is:

• Integration testing is a process of testing the


interface between two separate units or modules.
• Basically it is defined as a type of testing where
software modules are integrated logically and
tested as a group.
• For example, when we check login and sign up
features in an app like Instagram, these are
separate modules but they integrated together and
tested.
Examples

 signing up / logging in the system


 Book issue and book return module

 
Example

 First login as P user and send RS.200 amount,


Confirmation message will appear.
And logout as P.
Check (Total Balance=Present + Sent )
 Login as Q user and go to amount balance page

Check (Total Balance=Present + Received )


Integration Testing is successful
Purpose
 To expose defects in the interaction between
these software modules when they are integrated
 Focus on correctness of interfaces among all
modules
 To evaluate the compliance of a system or
component with specified functional requirements
How it is performed?
 Firstly, start by preparing a test integration plan and the
frameworks to be used.
 Next decide on the type of integration testing approach, this
could be Big Bang, Top-Down, Bottom-Up, or Sandwich testing. 
 Then you’ll need to design test cases, scenarios and test scripts.
 Next you’ll need to deploy the chosen components together to
run the integration testing.
 Then you can track any errors and record the testing results.
 Finally, repeat the process until the entire system is tested.
Who is responsible for IT?

 Specialist Integration Testers


 Developers(in rare cases)
Tools

 Jasmine
 Vector CAST
 Citrus
 FitNesse
 TESSY
 Protractor
 Rational Integration tester
Types/Approaches/Strategies

 Big bang strategy


 Top down strategy
 Bottom up strategy
 Mixed /Sandwich Strategy
 Incremental strategy
Big Bang Approach

All the modules are put together to construct the entire


system which is tested as a whole
All modules are combined together
Example
Advantages Disadvantages

 Convenient for small systems  Difficult to find the root cause


 Save time and effort of error
 Only for round needed for SI  High risk modules are not
tested isolated
 Zero planning
 Overhead because you have to
wait for all the modules to be
integrated

You might also like