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.
| |
Component testing is that in which we test those test objects which are separately testable as a isolated unit without integrating with other components (e.g. modules, programs, objects, classes, etc.).
A group of component is known as module testing.
What is Component Testing?
Testing of separate software component is known as component testing.
Component Testing is considered as the Module Testing, because we are testing each module or component differently and effectively.
Suppose there is only a one project which consists of 10 components and we are testing each component differently and effectively than it is known as component testing.
Suppose there is only a one project which consists of 10 components and we are testing each component differently and effectively than it is known as component testing.
What is Module Testing
A group of component is known as module testing.
Component testing is fulfilled by programmers on the code written by them and with the support of development environment, such as a unit test structure or debugging tool.
For Example there are two web pages. In one of the web pages there are a many certain fields like username, address, mobile no. etc in which data has to be entered. In the other (second) web page also there are certain fields which carry forward the data from the first page. Testing the functionality of these individual pages is called Component Testing.
After component Testing we always done the Integration Testing. While doing proper black box testing and white box testing by tester first of all Component Testing is done.
After component Testing we always done the Integration Testing. While doing proper black box testing and white box testing by tester first of all Component Testing is done.
Before component Testing Unit Testing is always done by the developers. While doing proper Unit Testing the Developers run each functions and method of the Component effectively.
Conclusion:-
Component Testing is like "Unit Testing" with the difference that entire Stubs and Simulators are retrieved with the real objects. So here a Unit is a component, and integration of one or various such components is also a Component.
