Integration Testing ~ Tumblia Test Solution

Integration Testing

Definition

Testing the data flow between two or more modules is called integration testing.

Here is the video to demonstrate how to do integration testing

How to identify integration scenario ?

Rule 1: First understand the complete project it means understand how each and every feature / module work.

Rule 2: Understand how features are linked or dependent on each other.

Rule 3: Identify all possible scenarios.

Rule 4: Priorities the scenarios.

Rule 5: Document the scenarios.

Rule 6: Write test case for the scenarios.

Rule 7: Test the software by executing Test case.

Rule 8: While doing software testing if you find any defects communicate to developer.

Rule 9: We should always do +ve and -ve integration testing.

Positive Scenario

Login as user A and send mail to user B by click on compose enter values for all the fields click on send logout as user A . Login as user B click on inbox ans check whether mail is displayed.
Login as use A click on compose enter user B email id for to field and user c email id for cc field and enter the value for remaining field click on send logout as user A login as user B click on inbox and check mail displayed or not logout as user B login as user C click on inbox check whether mail is displayed.
Login as user A click on compose enter values for all the fields click on send, click on sent item check whether mail is displayed.
Login as user A click on compose enter values for all the field click on cancel click on draft check whether mail is displayed.
Login as user A click on inbox select a mail delete the mail click on trash and check whether mail is displayed in trash.
Login as user A click on inbox select a mail mark it as important click on important and check whether mail is displayed.
Login as user A click on compose enter user A email id for both To and CC field and enter the value for remaining field click on send click on inbox check whether mail is displayed.
Login as user A click on inbox select a mail mark it as stared check the mail in starred folder.
Login as user A click on inbox select on inbox reply a mail click on sent item check mail is displayed.
Login as user A click on sent item select a mail mark it as starred click on starred check whether mail is displayed.

Negative Scenario

Login as user A click on compose enter value for all the field click on cancel click on sent item check whether mail is displayed.

Login as user A click on compose enter value for all the field and send mail to user B logout as user A login as user C click on inbox check whether mail is displayed.

Types of Integration Testing

1. Incremental Integration Testing: Incrementally adding the modules and testing the data flow between the modules is called as Incremental Integration Testing.

There are two types of incremental integration testing

Top-Down Incremental Integration Testing: Incrementally adding the modules and testing the data flow between the modules and ensure that the module you are adding is child of the previous module. Here data will flow from parent module to child module, this is called Top-Down Incremental Integration Testing.
Bottom-Up Incremental Integration Testing: Incrementally adding the module and testing the data flow between the modules and ensure that the module you are adding parent of the previous module. Here data will flow from child to parent module, this is called Bottom-Up Incremental Integration Testing.

2. Non-Incremental Integration Testing(Big Bang Method): Here we combine all the modules in one shot and test the data flow between the modules is called as Non-Incremental Integration Testing or Big Bang Method.

What is sandwich testing or hybrid testing ?

It is a combination of top-down and bottom-up incremental integration testing.

When to go for non-incremental integration testing ?

When we don't know parent and child module or when it is difficult to identify parent and child module.
When the data flow is very complex.

Drawbacks of non-incremental integration testing

Chances are there we might repeat same testing because of this time taken will be more.
Chances are there we might miss some of the data flow between the modules.
While testing if you find any defect it will be difficult to identify root cause of the defect.

Assume that there are two modules A and B module A is developed and module B is not developed as a test engineer how you will do integration testing or can you do integration testing or not ?

Yes we can do integration testing by using stubs and drivers.

Stubs: Stubs are the dummy module. It is a program written by the developers, which will receive data and send back same data it will not give valid result. Stubs is also known as Called Program in top-down approach.

Drivers: Drivers are the dummy module. It is a program written by the developers. Drivers will check interface between two modules it means drivers will send the data and receive data with valid result. Drivers are known as Calling Program in bottom-up approach.