Top down integration is primarily considering as an approach where modules are developed and testing of that modules always starting at the finest level of the programming hierarchy and continuing towards the lower levels.
There are few drawbacks to this procedure as well:
Top down strategy of integration testing is an incremental approach because we proceed one level at a time. It can be determine either in "depth first search" and in "breadth first search" manner.
So now the question arises what does depth and breadth mean?
Depth means we always proceed from the top level complete the way down to the lowest level.
Below is given the meaning of breadth.
Below is given the meaning of breadth.
What is the meaning about breadth?
Breadth on the other hand is different with depth so breadth means that we start at the top of the hierarchy and then steadily go to the next level. We develop and test entire modules at this level before continuing with another level.
Below given are some major benefits of top-down integration testing:
1. Having the framework, we can test major or supreme functions early in the development process.
2. At the same time, we can also test any interfaces that we have considered and thus obviously identify any errors in that area special or very early.
3. The supreme or major benefit of this practice is that we include a partially working framework to show to the clients and to the top management too.
This of course increases everybody's confidence in the development squad and also in the model itself.
TOP DOWN STRATEGY DRAWBACKS
There are few drawbacks to this procedure as well:
1. Impose stubs does not permit all the essential upward data flow.
2. Not enough data in the stubs to fee back to the calling module so this means the top-level modules cannot be really tested perfectly and every time the stubs are replaced with the real modules, the modules which are calling should be properly re-tested again for integrity.
Conclusion:
At end we conclude that this top down integration testing procedure allows us to originate or establish a framework of the system or product.
Now what is your viewpoint regarding top-down strategy of integration testing.
Bottom up strategy just as the name itself clears, is the opposite of powerful top down strategy. This sort of mechanism starts with building and testing the modules first which are obviously comes under the category of low level, than definitely proceeding towards the working its way ups the hierarchy.
BOTTOM UP STRATEGY BENEFITS
The advantages of bottom up integration are like that:
1. There is never urgency or hurry for any kind of program stubs as we always start developing and testing with the definite or absolute modules.
2. Always Starting at the bottom of the hierarchy again means that the critical modules are generally built and tested first and therefore any errors or mistakes in these forms of modules are find out early in the process.
Apart from top-down integration, there are some disadvantages of this procedure too which are given below:
1. In respect to test the popular modules we have to always form the test drivers first because they are more confused than compare to stubs. Also in addition to test these modules they themselves have to be tested so more time and efforts are needed to accomplish this complicated task.
2. One big disadvantage of bottom up strategy is that in this sort of testing no working model can be represented or you can say guided or tested as far as several modules have been built. This again means that a little form of errors in any of the interface is cached very late in the process.
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.
