ISTQB - Types of Integration Testing

In last article we have understood all about the incremental testing now we are moving towards the types of integration testing in details. We have seen the Top down integration testing, bottom up integration testing & big bang integration testing. But in this article we will understood remaining integration types along with big bang integration testing. The remaining types of integration testing is, Incremental integration, Functional integration and sandwich integration testing.

ISTQB - Unit Testing Levels

In last article we have listed down the different levels of software testing and this unit testing is the first level. We can consider unit testing as a small part of an application or product and we need to perform testing activity on it. Function testing, Interface testing and Procedure testing can be done in this part. Unit testing will be done by the developer team to verify that code have been written as per expectation and it will meet with all the requirement & design of the product.

As we have discussed, Unit test cases have been written and executed by developer team only. They will prepare test cases and execute it and then they will pass the release to the testing team members. Main goal of the unit testing is, each and every part of the application or product should be verified once in perspective of code and design. Not a single part of the product will be remain without the testing. This will give surety that every part of the application or product will work as expected. 

ISTQB - Integration Testing

In previous article we have understood about the component testing which needs to be done before integration testing. Integration testing can be define as the testing of the different components and interfaces of application.  Integration testing will be done with the different modules of the application which are dependent upon each other. It can be performed between operating system and file system or hardware and any interface of systems. Once 2 module will be developed and integrates together at that time integration testing will be performed for that application or product.

We can take an example of Order Management system web application. In this Order Management system different modules are define like Login page, Customer Details page, Order Details page and Final Transaction page. Here each page is integrated with each other. Customer should not be able to login without the sign up. And each sign up should be saved in customer details module. Customer should be able to place order only after the successful registration or login. And Order will be placed only after transaction will be done successful. Thus, we can say that each pages are integrated with each other. If Order have been placed by any customer and that customer would be deleted by any tester then application should give a validation message. This can call actual integration testing that any dependent data should be deleted and removed from the application. The same any system integration and files integration can be verified.