Difference between Unit Testing and Integration Testing
Unit Testing
|
Integration Testing
| ||
1
|
It do not occurs after and before of anything.
|
It occurs after Unit Testing and before System Testing.
| |
2
|
It is not abbreviated by any name.
|
It is abbreviated as �I&T� that is why sometimes also called Integration and Testing.
| |
3
|
It is not further divided into any.
|
It is further divided into Top-down Integration, Bottom-Up Integration and so on.
| |
4
|
It may not catch integration errors, or other system-wide issues because unit testing only tests the functionality of the units themselves.
|
Integration testing uncovers an error that arises when modules are integrated to build the overall system.
| |
5
|
The goal of unit testing is to isolate each part of the program and show that the individual parts are correct.
|
The goal of Integration Testing is to combined modules in the application and tested as a group to see that they are working fine.
| |
6
|
It does not follow anything.
|
It follows unit testing and precedes system testing.
| |
7
|
It obviously starts from the module specification.
|
It obviously starts from the interface specification.
| |
8
|
Unit testing always tests the visibility of code in details.
|
Integration testing always tests the visibility of the integration structure.
| |
9
|
It requires complex scaffolding means frame.
|
It requires some scaffolding means frame.
| |
10
|
It definitely pays attention to the behavior of single modules.
|
It definitely pays attention to the integration among modules.
| |
11
|
It is only the kind of White Box Testing.
|
It is both the kind of Black Box and White Box Testing.
| |
Category: Integration Testing, Unit Testing, Unit Testing vs Integration Testing
0 comments