Review the Processes for Unit/module Testing Integration Testing and System Testing

Before a software is released to the market for commercial use, it undergoes rigorous testing. Software testing is classified into four different levels, namely Unit Testing, Integration Testing, System Testing and Acceptance Testing. These four levels of software testing are designed to detect errors, evaluate the correctness of beliefs and functioning of the software application. Through this "What is Integration Testing?" article, we will acquire mainly about the second level of testing, Integration Testing. If y'all are new to software testing, be sure to too read the Beginners' Guide for Software Testing.

Let's accept a look at topics covered in this commodity:

• Levels of Software Testing
• What is Integration Testing?
• Advantages of Integration Testing
• How is Integration Testing Washed?
• Types of Integration Testing
• Challenges of Integration Testing

Levels of Software Testing

Software Testing  is a phase within the software development bike in which business-critical software is verified for definiteness, quality, and operation.

At that place are four central levels within software testing, each examining the software functionality from a unique vantage point within the development procedure. The four levels of software testing are as shown in the image below.

This article explains integration testing, the outset level of software testing in detail.

What is Integration Testing?

Integration Testing is a level of software testing where individual units are combined and tested to verify if they are working as they intend to when integrated. The primary aim here is to test the interface between the modules.

But unit testing is not enough for multiple reasons like:

• A module/unit of measurement is usually designed by an individual software developer whose techniques and programming logic differs from that of other programmers
• Often at the time of module evolution, user requirements change and these new requirements may non be unit of measurement tested. This instigates bug
• Problems like data formatting, error trapping, hardware interfaces, and 3rd-party service interfaces are sometimes missed during unit testing

So, no thing how efficiently each module/unit is running, if they aren't properly integrated, information technology will touch on the functionality of the software program. As a solution integration testing is implemented. This commodity 'What is Integration Testing?' further lists out the advantages of integration testing.

Advantages of Integration Testing

Performing integration testing offers a lot of benefits. Some of them are listed below:

• It makes sure that integrated modules work properly as intended
• The tester can get-go testing once the modules to exist tested are available
• It detects errors related to the interface betwixt modules
• Helps modules interact with API's and other third-political party tools
• Typically covers a big volume of the arrangement, so more efficient
• Increases the test coverage and improves the reliability of tests

Software engineers perform integration testing. Sometimes companies employ independent testers to do it for them. But, how is integration testing carried out in reality? Is information technology similar to other testing processes? Allow's check it out the next part of this 'What is Integration Testing?' commodity.

How is Integration Testing Done?

The meaning of integration is quite straightforward – Combine the unit tested module one by ane and test the functionality of the combined unit. Usually, integration testing is carried out after unit testing. One time all the individual units are created and tested, nosotros start combining those tested modules and starting time performing the integrated testing. The main goal here is to test the interfaces between the units/modules. Here are a few uncomplicated steps that will get you started with integration testing:

• Ready the test integration programme
• Determine on the blazon of integration testing approach
• Pattern exam cases, examination scenarios and test scripts accordingly
• Deploy the chosen modules together and get the integration tests running
• Rails the defects and record the test results of tests
• Repeat the higher up steps until the complete arrangement is tested

Remember that priority must be given to the integrated interface links between modules or units. Equally yous tin see, in the 2nd footstep you demand to make up one's mind on the type of integration testing arroyo. Moving ahead in this 'What is Integration Testing?' commodity, let us acquire how these testing strategies are executed, their benefits, and drawbacks.

Types of Integration Testing

Before we starting time discussing the types of integration testing available, we need to empathise the concept of stubs and drivers. While testing, sometimes we face up a situation where some of the modules are nevertheless under development. These modules for testing purpose are replaced with some dummy programs. These dummy programs are called stubs and drivers.

Imagine, we have an application with ii modules i.e, Login Page(Module A) and Admin Page(Module B) .

Case1: Yous have to test the Login Page which is developed and sent to the testing squad. Login Page is dependent on Admin Folio. But the Admin Page is not ready withal. To overcome this situation developers write a dummy program which acts as an Admin Page. This dummy plan is Stub. Stubs are 'Called Programs'.

Case2: You have to test Admin Page simply the Login Page is not prepare yet. To overcome this situation developers write a dummy programme which acts similar the Login Page. This dummy program is Commuter. Drivers are 'Calling programs'.

Now that you are aware of these necessary concepts, permit'south check out different types of integration tests. Integration testing types are categorized into different groups that are listed below:

Big Bang Integration Testing

In this testing approach, once all the modules are developed and tested individually, they are integrated once and tested together at in one case. The only advantage of this blazon of testing is that it is very much suitable for smaller systems.

Disadvantages

• Mistake localization is tough
• A lot of delay before testing
• Critical problems are non resolved on priority
• Hard to find the root crusade of problems

Incremental Integration Testing

Incremental Testing is performed past connecting two or more modules together that are logically related. Afterward more modules are added and tested for proper functionality. This is done until all the modules are integrated and tested successfully. It's further divided into Acme-Down Approach, Bottom-Up Approach, and Sandwich Approach.

Top-Down Integration Testing

The top-down approach starts by testing the top-nearly modules and gradually moving down to the lowest prepare of modules one-by-one. Testing takes place from top to downwards following the control flow of the software system. As there is a possibility that the lower level modules might non have been developed while top modules are tested, nosotros use stubs instead of those not set modules. For unproblematic applications, stubs would simply return the control to their superior modules. For complex applications, they would simulate the full range of responses.

Advantages:

• Error localization is easier
• The exam product is extremely consistent
• The stubs tin exist written in lesser time compared to drivers
• Critical modules are tested on priority
• Major pattern flaws are detected as early as possible

Disadvantages

• Requires several stubs
• Poor back up for early release
• Basic functionality is tested at the end of the cycle

Bottom-Upward Integration Testing

The lesser-upward approach starts with testing the lowest units of the application and gradually moving up 1-by-one. Here testing takes place from the lesser of the control menses to upwards. Once again it's possible that the higher level modules might not have been adult past the time lower modules are tested. In such cases, we simulate the functionality of missing modules by using drivers. These drivers perform a range of tasks such equally invoking module under test, laissez passer exam information or receive output data.

Advantages

• Hither development & testing can exist done together so the product will be efficient
• Examination conditions are much easy to create

Disadvantages

• Requires several drivers
• Data flow is tested very belatedly
• Need for drivers complicates exam information management
• Poor support for early release
• Key interfaces defects are detected late

Sandwich Integration Testing

To overcome the limitations and to exploit the advantages of meridian-down and bottom-upwardly approaches, a hybrid approach of integration testing is used. This approach is known equally sandwich integration testing or mixed integration testing. Here, the system is viewed every bit iii layers. Master target layer in the middle, another layer in a higher place the target layer, and the last layer below the target layer. The meridian-down approach is used on the layer from the tiptop to the middle layer. The lesser-upwards approach is used on the layer from the lesser to middle. Big blindside approach is used for modules in the middle.

Advantages

• Top-Downward and Bottom-Up testing techniques can be performed in parallel or ane subsequently the other
• Very useful for large enterprises and huge projects that farther have several subprojects

Disadvantages

• The cost requirement is very high
• Cannot be used for smaller systems with huge interdependence between the modules
• Different skill sets are required for testers at different levels

These are the different approaches that you tin can use to perform integration testing based on your testing requirements. You should check which testing strategy can be adopted and set the test information and test plan accordingly. As useful as integration testing tin can be, information technology is not without its negative points. You need to understand the challenges that y'all might face when implementing it.

Challenges of Integration Testing

• Managing integration testing is difficult sometimes because of various factors similar database, platforms, environment, etc
• Integrating a new organization to a legacy arrangement or integrating 2 legacy system needs a lot of testing efforts and changes
• Less compatibility between the two systems developed past ii unlike companies is a claiming for programmers
• There are way too many dissimilar paths and permutations to use for testing the integrated systems

Despite these challenges, integration testing is very useful in the software testing process. It is an of import part of the testing cycle that makes it easy finding defects when two or more than units are integrated. With this, we have reached the end of the 'What is Integration Testing?' article. Hope the things that you have learned hither today will assistance you lot as you head out on your software testing journeying.

If you constitute this 'What is Integration Testing?' article relevant, cheque out thealive-onlineSelenium Certification Training by Edureka, a trusted online learning company with a network of more than 250,000 satisfied learners spread across the globe.

Got a question for us? Please mention it in the comments section of this 'What is Integration Testing?' commodity and we will get back to yous.

scrogginsenctiong.blogspot.com

Source: https://www.edureka.co/blog/what-is-integration-testing-a-simple-guide-on-how-to-perform-integration-testing/

Share this post