YouTube Link: https://youtu.be/8UfQ8quw0Eg (**Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **) This Edureka PPT on "What is Integration Testing?" will help you get in-depth knowledge on integration testing and why it is important to subject software builds to integration tests before moving on to next level of testing. Levels of Software Testing What is Integration Testing? Different Approaches to Integration Testing How to do Integration Testing? Examples of Integration Testing Integration Testing Challenges & Best Practices Follow us to never miss an update in the future. YouTube: https://www.youtube.com/user/edurekaIN Instagram: https://www.instagram.com/edureka_learning/ Facebook: https://www.facebook.com/edurekaIN/ Twitter: https://twitter.com/edurekain LinkedIn: https://www.linkedin.com/company/edureka Castbox: https://castbox.fm/networks/505?country=in

2. LEVELS OF SOFTWARE TESTING
WHAT IS INTEGRATION TESTING?
DIFFERENT APPROACHES TO INTEGRATION TESTING
HOW TO DO INTEGRATION TESTING?
www.edureka.co
EXAMPLES OF INTEGRATION TESTING
INTEGRATION TESTING CHALLENGES & BEST PRACTICES

3. www.edureka.co

4. www.edureka.co
Software Testing is a process used to identify the
correctness, completeness and the quality of developed
compute software. It includes a set of activities
conducted with intent of finding errors in software so
that it could be corrected before the product is released
to end users.

5. Levels of
Software
Testing
www.edureka.co
Unit
Testing
Integration
Testing
System
Testing
Acceptance
Testing
Testing individual components Testing component groups
Testing the integrated system Testing the final system

6. www.edureka.co
No. Its not. Even after testing each
module individually defects still exist.
Because…..Just Unit Testing is not
enough, is it?
➢Differentprogramminglogic
➢Changeinuserrequirements
➢Databaseissues
➢Interfaceissues
➢Inadequateexceptionhandling

7. www.edureka.co

8. www.edureka.co
What is Integration Testing?
Integration Testing is a level of software testing where individual units are combined and the connectivity or data
transfer between these units is tested. The main aim of this testing is to recognize the interface between the modules.

9. www.edureka.co
Ensures modules work together properly
Integration
Testing
Helps to uncover errors that lie in interfaces
Ensures that newly added components are not affected

10. www.edureka.co

11. Difference between Stubs & Drivers
APPLICATION
Component1:
Component2:
STUBS DRIVERS
Login Page
(Module A)
Admin Page
(Module B)
Dummy
Admin Page
STUB
“Called
Program”
Login Page
(Module A)
Admin Page
(Module B)
Dummy Login
Page
DRIVER
“Calling
Program”

12. www.edureka.co
Testing takes place from top
to bottom, following the
control flow or
architectural structure
Testing takes place from
the bottom of the control
flow upwards
All components or modules are
integrated simultaneously,
after which everything is tested
as a whole
Top–Down Approach(TDA) Bottom-UP Approach(BUA) Big Bang Approach
Integration Testing Approaches

13. www.edureka.co
Top–Down Approach(TDA)
M1
M1 M2 M3 M4
M1 M2 M3 M4 M5
M1 M2 M3 M4 M5 M6 M7
M1
M2 M3
M5
M4
M6 M7
Testing takes place from top to bottom, following the control flow or architectural structure
Advantages
Disadvantages
➢Extremely consistent
➢Less time required
➢Fault localization is easier
➢Detects major flaws
➢Requires several stubs
➢Poor support for early release
➢Basic functionality is tested late

14. www.edureka.co
Bottom-UP Approach(BUA)
M2
M1 M2 M3 M4 M5 M6 M7
M1
M2 M3
M5
M4
M6 M7
Advantages
Disadvantages
➢Efficient application
➢Less time requirements
➢Test conditions are easier to create
➢Requires several drivers
➢Data flow is tested late
➢Poor support for early release
➢Key interface defects are detected late
Testing takes place from the bottom of the control flow, upwards
M6 M4 M7
M6 M7
M3 M5
M5

15. www.edureka.co
Big Bang Approach
M1
M1 M2 M3 M4 M5 M6 M7
M1
M2 M3
M5
M4
M6 M7
Advantages
Disadvantages
➢All components tested at once
➢Convenient for small systems
➢Saves testing time
➢Lot of delay before testing
➢Difficult to trace cause of failures
➢Possibility of few missing interface links
➢Critical modules are not prioritized
M2 M7 M5M3 M4 M5
All components or modules are integrated simultaneously, after which everything is tested as a whole

16. Sandwich Integration Approach
M1M1
M1M2 M1M3 M1M4
M1M5 M1M6 M1M7
Layer 1:
Layer 2:
Layer 3:
➢Also called Hybrid Integration Testing or
Mixed Integration Testing
➢Middle layer is the target layer
➢Top-Down approach is topmost layer
➢Bottom-Up approach is lowermost layer
➢Advantage: Both layers can be tested in
parallel
➢Disadvantage: High cost, big skill set,
extensive testing is not done

17. www.edureka.co
Choose the module to be tested
Decide the type of integration testing
Deploy the selected modules & start
testing
Perform functional & structural
testing
Record, analyse & report the results
Repeat above steps until complete
system is fully tested
Software Build
Deploy for next
level testing

18. www.edureka.co

19. www.edureka.co
Example of Integration Testing
Consider an application with three modules, Login Page, Mailbox, and Delete emails. All these modules are integrated
logically by programmers.
Login Page Mail Box Delete Emails

20. www.edureka.co
Example of Integration Testing
Consider an application with three modules, Login Page, Mailbox, and Delete emails. All these modules are integrated
logically by programmers.
Test the interface link
between Login Page and the
Mail Box Page
Check the interface link
between Mail Box & the
Delete Email Module
Enter the login details & click
on login button to login
From mail box select the
email you want to delete &
click on delete
You should be directed to the
Mail Box Page
Selected email should be
deleted and should appear in
the Trash Folder
Test Case ID Test Case Objective Test Case Description Expected Outcome
A
B

21. Integration Testing Challenges & Best
Practices www.edureka.co

22. www.edureka.co
02Multiple ways for testing
03 Issues when integrated with legacy system
04Challenging test cases
05 Time Constraints
Challenges of Integration Testing
01 Difficult Test Data Management
Steps to kick of integration testing
➢Focus on architecture of application
➢Identify each module
➢Check the how data is communicated
➢Understand the user requirements
➢Create multiple test conditions
➢Focus on one test condition at a time

23. Copyright © 2017, edureka and/or its affiliates. All rights reserved.
www.edureka.co

24. www.edureka.co