Skip to main content

What Is Integration Testing Explain It with Example?

When individual software modules are merged and tested as a group than it is known as integration testing. Integration testing is sets between Unit Testing and System Testing.


Integration Testing Example

For example you have to test the keyboard of a computer than it is a unit testing, but when you have to combine the keyboard and mouse of a computer together to see its working or not than it is the integration testing. So it is prerequisite that for performing integration testing, a system must be unit tested before.

Black-box test case design tactics are the most typical during integration, although limited amount of testing of white box may be used to ensure description of major control paths. 


Why we need integration testing?

Integration testing is executed to establish whether the components interact with each other consort to the specification or not. Integration testing in large refers to joining all the components resulting in the complete system. It is further performed by the developer or the software Tester or by both. Example- checking that a Payroll system interacts as required with the Human Resource system.

Integration Testing Types

1) Top-Down Integration Testing: As the name suggests, this testing always starts at the top of the program hierarchy and travels towards its branches. This can be done in either depth-first or breadth-first.

2) Bottom-Up Integration Testing: This testing always starts at the lowest level in the program structure.

Techniques of integration testing 


1) Top-down testing approach
2) Bottom-up testing approach
3) Big-Bang testing approach
4) Sandwiched testing approach

Conclusion: 

At last we conclude that Integration testing focuses on testing multiple modules working together and this testing is one of the extensive exercises of the software testing in which particular software modules are merged and tested as a group. 

Comments

  1. good definition with example.....

    ReplyDelete
  2. Clear explanation guys... Good :)

    ReplyDelete
  3. when Programs are base-lined,then corresponding programmers can interconnect a those programs to build a software,here programmers can check correctness of programs interconnection.

    ReplyDelete
  4. If we have 4 apps, in one its 2, in 2nd its 3, in 3rd app, its 2*3 and in 4th, its 6....What testing it would be? Integration testing or System testing, please explain. I faced this question in interview and was dumbstruck.

    ReplyDelete
  5. wheres the example?

    ReplyDelete
  6. Nice and understanding

    ReplyDelete
  7. if we take facebook as example then how to apply integeration testing?

    ReplyDelete
  8. Can any share integration test cases of any application

    ReplyDelete
  9. Very informative and helpful...thnx

    ReplyDelete
  10. integration testiong on pen?????

    ReplyDelete
  11. The goal of integration testing is to make sure a system consisting of a number of components will function according to specifications when all the components are put together. If that is the case, why spend time testing interfaces between interacting modules? Why not just put them all together and test the system as a whole? can anyone Give arguments both for and against with examples.

    ReplyDelete

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application. Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not. Functional testing  is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations. Functional and Non Functional Test Cases Functional test cases target business goals and non functional test cases target performance, resource...