EDUCBA

EDUCBA

MENUMENU
  • Free Tutorials
  • Free Courses
  • Certification Courses
  • 600+ Courses All in One Bundle
  • Login
Home Software Development Software Development Tutorials Software Testing Tutorial System Integration Testing
Secondary Sidebar
Software Testing Tutorial
  • Types of Testing
    • Adhoc Testing
    • Types of System Testing
    • Manual Testing Types
    • Unit Testing Types
    • Unit Testing Benefits
    • Agile Testing
    • What is Agile Testing
    • Acceptance Testing
    • Stress Testing Types
    • Alpha and Beta Testing
    • Application Testing
    • Automation Testing
    • Automation Testing Advantages
    • Benchmark Testing
    • Black Box Testing
    • Domain Testing
    • Dynamic Testing
    • Ecommerce Testing
    • Fuzz Testing
    • Gray Box Testing
    • GUI Testing
    • Installation Testing
    • Interface Testing
    • Interoperability Testing
    • Mainframe Testing
    • Manual Testing
    • Mutation Testing
    • Monkey Testing
    • Negative Testing
    • Penetration Testing
    • Penetration testing phases
    • Penetration testing framework
    • Protocol Testing
    • Recovery Testing
    • Regression Testing
    • Mobile Penetration Testing
    • Accessibility Testing
    • Sanity Testing
    • Scalability Testing
    • Security Testing
    • Spike Testing
    • Stability Testing
    • State Transition Testing
    • Static Testing
    • Gatling Load Testing
    • System Integration Testing
    • Structural Testing
    • Locust Load Testing
    • System Testing
    • Control Flow Testing
    • Unit Testing
    • Cypress testing
    • Volume Testing
    • Web Testing Application
    • What is Exploratory Testing
    • What is Stress Testing
    • What is Usability Testing
    • White Box Testing
    • Types of White Box Testing
    • Compatibility Testing?
    • Use Case Testing
    • Beta Testing
    • Integration Testing
    • Non Functional Testing
    • Non Functional Testing Types
    • What is Functional Testing
    • Functional testing types
    • Cookie Testing
    • Alpha Testing
    • Boundary Value Testing
    • Equivalence Class Testing
    • Glass Box Testing
    • SOA Testing
    • Smoke Testing
    • Visual Testing
    • Visual Paradigm
    • Model-Based Testing
  • Basics
    • What is Software Testing
    • Careers in Software Testing
    • Defect Life Cycle in Software Testing
    • Bug Life Cycle
    • Levels of Software Testing
    • Software Testing Life Cycle
    • Software Tester Work
    • Software Testing Principles
    • Software Testing Services
    • Testing Methodologies
    • Test Approaches
    • Grey Box Testing
    • Types of Software Testing
    • What is a Bug in Software Testing
    • Benefits of Automation Testing
    • What is Automation Testing?
    • Types of Automation
    • Typical Journey of a Software Tester
    • Automation Testing Process
    • Mobile Automation Testing
    • Automation Testing Life Cycle
    • Software Quality Assurance
    • Software Quality Assurance
    • What is Test Environment?
    • Verification and Validation Testing
  • Testing techniques
    • Software Testing Methodologies
    • Black Box Testing Techniques
    • Static Testing Techniques
    • Test Case Design Techniques
    • What is Static Analysis
  • Testing tools
    • Manual Testing Tools
    • Visual Testing Tools
    • Automation Testing Tools
    • Functional Testing Tools
    • GUI Testing Tools
    • Penetration Testing Tools
    • Performance Testing Tools
    • SOA Testing Tools
    • Accessibility Testing Tools
    • What is QTP
    • Regression Testing Tools
    • Security Testing Tools
    • Test Management Tools
    • Defect Management Tools
    • Code Coverage Tools
    • Test Coverage Tools
    • Defect Tracking Tools
    • Continuous Integration Tools
    • Install Bugzilla
    • Test data generation tool
    • Unit Testing Tools
    • Web Testing Tools
    • Stress Testing Tools
    • Performance Monitoring Tools
    • Mobile Testing Tools
    • Responsive Testing Tool
    • Cross Browser Testing Tools
    • Risk Based Testing
    • Database Testing Tools
    • WinRunner
    • What is Squish?
    • CubicTest
    • What is WinRM?
    • Bugzilla Tool
    • Code review tools
    • Penetration Testing Open Source Tools
  • Advance
    • Cyclomatic Complexity
    • Decision Table Testing
    • Decision Tree Algorithm
    • What is Continuous Integration
    • Mantis Bug Tracker
    • Equivalence Partitioning
    • Gantt Chart Software
    • Acceptance Testing Types
    • Load testing tools
    • Install TestNG
    • Install Unity
    • Defect Management Process
    • Test Plan Template
    • Testing Interview Questions
    • Testing of Mobile application
    • What is Test Automation Frameworks
    • Test Automation Framework
    • Application of Automation
    • Test Automation Process
    • Automation Testing Roles and Responsibilities
    • What is Instruction Cycle?
    • What is Cucumber?
    • 15 Best Popular Bug Reporting Tools
    • What is Automated Testing?
    • Software Maintenance Types
    • Types of Penetration Testing
    • Software Reliability
    • Best Gantt Chart Software
    • Code Coverage
    • Branch Coverage
    • Decision Coverage
    • Statement Coverage
    • What is Test Case
    • Types of Test Case
    • What is Test Scenario
    • Formal Review
    • Alpha Beta Pruning
    • What is Cyclomatic Complexity?
    • Test Coverage
    • How to Write Test Case
    • Testing Documentation
    • Performance Testing Life Cycle
    • Test Harness
    • Test Strategy
    • Software Incident Management
    • What is Debugging
    • What is Defect?
    • Listeners in TestNG
  • Inteview Questions
    • Automation Testing Interview Questions
    • Manual Testing Interview Questions
    • ISTQB Interview Questions
    • Cucumber Interview Questions
    • Software Testing Interview Questions
    • Penetration Testing Interview Questions

Related Courses

Software Testing Course

Penetration Training Course

TestNG Training Course

System Integration Testing

By Priya PedamkarPriya Pedamkar

system interation testing

Introduction to System Integration Testing (SIT)

System Integration Testing or SIT is the process of comprehensive testing performed on the application software along with the complete system, which is usually made of more than one smaller unit of software and hardware. The primary goal of executing this type of testing is to make sure of the functional characteristics of the software and hardware systems are in sync with one another. Usually, in SIT, the individual modules are tested separately first, and then tested again after combined it into a single solid system.

System integration testing

System Integration Testing (SIT) is carried out after the sub-systems have individually undergone Unit Testing and that testing has been passed. SIT then tests the system as a whole, after it has been integrated. The result of SIT is then passed on to User acceptance testing (UAT).

Benefits of System Integration Test

Following are the benefits given below.

Start Your Free Software Development Course

Web development, programming languages, Software testing & others

  • SIT helps in detecting defects at an early stage. The defects found during SIT are sent back to be fixed by the development team. This helps in saving time and the cost of getting it fixed at a later stage, which can be more expensive.
  • SIT helps in getting an early opinion on the acceptability of a module in the system.
  • SIT helps in exposing the faults that can take place when integrated components interact.
  • There are several modules in a system and unit testing all the modules individually takes time. Even if each unit is tested individually, even then there is a possibility that it can fail when integrated as a whole as there are many problems that ascend when sub-systems interact with each other.

Thus, SIT is essentially required to uncover and fix the issues before sending the system to the user.

Approaches for Performing SIT

Let’s look at the different approaches for performing SIT, let’s understand this one by one.

All in One Software Development Bundle(600+ Courses, 50+ projects)
Python TutorialC SharpJavaJavaScript
C Plus PlusSoftware TestingSQLKali Linux
Price
View Courses
600+ Online Courses | 50+ projects | 3000+ Hours | Verifiable Certificates | Lifetime Access
4.6 (86,328 ratings)

1. Top-Down Approach

This is an incremental approach, where the testing begins at the topmost module of an application. The functionality of the modules at a lower level is simulated with the help of stubs. The top module is integrated with the stubs of the modules at the lower levels, one by one to test their functionalities. Once each test is completed, the respective stub is replaced by the real module. This way of testing continues until the whole system is tested.

Advantage

  • No need for drivers and the functionality of the system is used to specify the test cases.

Disadvantage

  • There is a dependency on the availability of the functionality of the lower level modules.
  • There can be a delay in testing as the real modules are substituted with stubs.
  • Writing stubs is difficult.

Top Down Approach

2. Bottom-up Approach

 This is an incremental approach, where first, the lowest level modules are brought together to form clusters. Then a driver is made to get the input and output of the test case. Then the cluster is tested. After the cluster is tested, the driver is removed, so that the cluster can be combined with the upper level. This way of testing continues until the whole system is tested.

Advantage

  • Stubs are not needed in this approach.
  • Testing becomes easier as the process ascends because the use of drivers is reduced.

Disadvantage

  • The most important module i.e. the UI is tested at the end.

3. Big Bang Approach

In this approach, the modules of the system are integrated only after all the modules are complete. After integration, testing is carried out on the whole system to check for its working.

Advantage

  • Only one round of SIT is required.

Disadvantage

  • It is difficult to find the root cause of an error.

big bang approach

Process of System Integration Testing

The most common method of performing SIT is through the Data-driven method as it requires the least usage of software testing tools.

In this method, primarily, a data exchange i.e. data import and export take place between the system modules and then the performance of each data field within the individual layer is observed.

Once the software has been integrated, there can be three main states of data flow:

1. Data State when Flowing within the Integration Layer

The integration layer acts as an interface between the data import and export. Basic knowledge of certain schema technologies is required for performing SIT at this layer.

Steps to perform SIT to validate the data exchange:

  • Authenticate the data properties within this layer against the requirements documents.
  • Validate the web service request.
  • Run some unit tests to verify the data mappings and requests.
  • Review the logs.

2. Data state when flowing within the Database layer

Basic knowledge of SQL is required for performing SIT at this layer.

Steps to perform SIT to validate the data exchange:

  • Verify whether all the data has reached and has been committed from the previous level.
  • Authenticate the table and column properties against the requirements documents.
  • Verify the data validation rules and the constraints applied to the database.
  • Check stored procedures for any data to be processed.
  • Review the logs.

3. Data state when flowing within the Application layer

Steps to perform SIT to validate the data exchange:

  • Check for visibility of the fields in the UI.
  • Execute test cases, both positive and negative to confirm the data.

Example of SIT

To make SIT a little clearer, let us take an example of a company that is using software to store the employee details.

This software comprises of two screens in the UI namely Name Screen and Employee ID Screen, and it has a database called Database A. The details entered in Name Screen and Employee ID Screen are entered in the Database A.

After a few years, the company requires additional data from the employees. Thus, an enhancement is required and they develop an Address Screen with another database, Database B. Now, this system having Address Screen and Database B has to be integrated with the existing system, and then this testing done on the whole system for proper functionality is called SIT.

Process of System Integration Testing

To conclude, SIT is an important part of our testing as it gives us the first impression of how well our application is running. It can be done by the means of different approaches and processes, and we can use whichever is suitable for our application.

Recommended Articles

This has been a guide to System Integration Testing. Here we discussed the concepts, approaches, advantages, and disadvantages of System Integration Testing. You can also go through our other suggested articles to learn more –

  1. What is Software Testing?
  2. Testing Interview Questions
  3. Defect Life Cycle in Software Testing
  4. System Design Interview Questions
Popular Course in this category
Software Testing Training (11 Courses, 2 Projects)
  11 Online Courses |  2 Hands-on Projects |  65+ Hours |  Verifiable Certificate of Completion
4.5
Price

View Course

Related Courses

Penetration Testing Training Program (2 Courses)4.9
TestNG Training (4 Courses, 2 Project)4.8
1 Shares
Share
Tweet
Share
Primary Sidebar
Footer
About Us
  • Blog
  • Who is EDUCBA?
  • Sign Up
  • Live Classes
  • Corporate Training
  • Certificate from Top Institutions
  • Contact Us
  • Verifiable Certificate
  • Reviews
  • Terms and Conditions
  • Privacy Policy
  •  
Apps
  • iPhone & iPad
  • Android
Resources
  • Free Courses
  • Java Tutorials
  • Python Tutorials
  • All Tutorials
Certification Courses
  • All Courses
  • Software Development Course - All in One Bundle
  • Become a Python Developer
  • Java Course
  • Become a Selenium Automation Tester
  • Become an IoT Developer
  • ASP.NET Course
  • VB.NET Course
  • PHP Course

ISO 10004:2018 & ISO 9001:2015 Certified

© 2022 - EDUCBA. ALL RIGHTS RESERVED. THE CERTIFICATION NAMES ARE THE TRADEMARKS OF THEIR RESPECTIVE OWNERS.

EDUCBA
Free Software Development Course

C# Programming, Conditional Constructs, Loops, Arrays, OOPS Concept

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA Login

Forgot Password?

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA
Free Software Development Course

Web development, programming languages, Software testing & others

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

Let’s Get Started

By signing up, you agree to our Terms of Use and Privacy Policy.

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy

Loading . . .
Quiz
Question:

Answer:

Quiz Result
Total QuestionsCorrect AnswersWrong AnswersPercentage

Explore 1000+ varieties of Mock tests View more