africahaser.blogg.se - List of integration techniques

List of integration techniques software#

Secanrios2: We also perform the integration testing on Spam folders.

Now, we will log out as P and login as Q and move to the Inbox and verify that if the mail has reached.

After that, we send a mail to Q and verify in the Send Items folder of P to check if the send mail is there.

Now we click on the Send and also check for Save Drafts.

First, we login as P users and click on the Compose mail and performing the functional testing for the specific components.

The different integration scenarios are as follows: Then only we can perform integration testing. Let us assume that we have a Gmail application where we perform the integration testing.įirst, we will do functional testing on the login page, which includes the various components such as username, password, submit, and cancel button. Any scenarios can be called as integration scenario only if the data gets saved in the destination.įor example: In the Gmail application, the Source could be Compose, Data could be Email and the Destination could be the Inbox. Each integration scenarios should compulsorily have source→ data→destination. Note: Any application in this world will do functional testing compulsory, whereas integration testing will be done only if the modules are dependent on each other. If it happens, then there is a bug in the code, and we will send it to the development team for fixing that bug. If it does, then the test would be a pass.Īnd negative testing means, if the total balance is Rs15, 000 and we are transferring Rs20, 000 and check if amount transfer occurs or not, if it does not occur, the test is a pass. Here positive testing implies that if the total balance is Rs15, 000 and we are transferring Rs1500 and checking if the amount transfer works fine.

Perform positive and negative integration testing.

If we find any bugs then communicate the bug reports to developers and fix defects and retest.

Input data plays a significant role in testing.

Choose input data for test case execution.Design test cases to verify each interface in detail.Examine the structure and architecture of the application and identify the crucial modules to test them first and also identify all possible scenarios.First, determine the test case strategy through which executable test cases can be prepared according to test data.We always do integration testing by picking module by module so that a proper sequence is followed, and also we don't miss out on any integration scenarios.We go for the integration testing only after the functional testing is completed on each module of the application.Click on the transaction, in P and Q, the message should be displayed regarding the data and time of the amount transfer.Also, we check if the amount of balance has reduced by Rs200 in P user account.Therefore, the integration test is successful. Now logout as P and login as user Q and go to amount balance page and check for a balance in that account = Present balance + Received Balance. First, we will login as a user P to amount transfer and send Rs200 amount, the confirmation message should be displayed on the screen as amount transfer successfully.Let us see one sample example of a banking application, as we can see in the below image of amount transfer. Once all the components or modules are working independently, then we need to check the data flow between the dependent modules is known as integration testing. The goal of integration testing is to check the correctness of communication among all the modules.

List of integration techniques software#

The Software is developed with a number of software modules that are coded by different coders or programmers. Unit testing uses modules for testing purpose, and these modules are combined and tested in integration testing. The focus of the integration testing level is to expose defects at the time of interaction between integrated components or units. In this testing, units or individual components of the software are tested in a group. Integration testing is the second level of the software testing process comes after unit testing.