Integration Testing

Using this we can test the flow of data from one module to another module. Integration Testing is mostly used to check the data flow of one project module to another project module. 

for example, registration and login, are separate modules, first, we perform the registration process after that login process that will be managed by Integration Testing.

I & T means Integration and Testing,

First, we integrate modules, and after that check.

Integration Testing will be processed when project multiple modules have been completed.

For example, first, we register using the registration form and then check login by the same credential then it will proceed to the dashboard page that will be managed by Integration Testing.

another example we will add employees from the operator module and view the employee by admin module then operator and admin both will be linked with each other.



Type of Integration Testing

1 Top To Bottom:-


we will check the application from the primary module(main module) to the second module(child module).

its flow will be in the forward direction in an application.

for example, if we add staff from admin and check that staff is able to log in, this is an example of the Top to Bottom approach.




2 Bottom to top:-

  We will check the application from the secondary module to the primary module. its flow will be in the backward direction.

for example, Staff will submit the report that will be viewed by the admin then it is called Botton to Top integration testing.




3 Big-Bang Testing:-

We can check randomly to any module of an application to check flow for example if we check that logout is proper working or not then we first login then logout and again press the back button and hit the internal URL that is the example of big-bang testing.