"Integration test" (sometimes called Integration and Testing, abbreviated I & T) is the phase of software testing in various software modules that are combined and tested as a group. It follows unit testing and precedes the test system.
Tests of integration as input modules that have been unit tested, groups larger aggregates, applies tests defined in a test plan for integration of these aggregates, and delivers its output data ready for integrated system testing.
Purpose
The purpose of integration is to verify the functional tests, performance and reliability on the major design requirements of the articles. These "design objects", ie sets (or groups of units) shall be exercised through their black box using test interfaces, success and error cases simulated by appropriate parameter and data entry. Simulation of the use of shared data and areas of inter-process communication is tested and subsystems are exercised through their input interface. Test cases are constructed to verify that all components within assemblages interact correctly, for example through procedure calls or process activations, and this is done after the test individual modules, that is to say the unit tests.
The general idea is a "building block" in the check assemblies that are added to a basic check, which is then used to support the integration of new test assemblies.
Some types of integration tests are big bang, top-down and bottom-up.
Big Bang
In this approach, all or most of the developed modules are combined to form a software system or a significant part of the system and then used for integration tests. The Big Bang is very effective method to save time in the integration testing process. However, if the test cases and their results are not properly registered, the whole process of integration will be more complex and prevent the May testing team to achieve the goal of integration.
A type of "Big Bang" integration tests is called usage model testing. Usage type of test can be used in software and hardware integration. The basis of this type of integration is to launch the user tests, as the workload of the user included in similar environments. By testing in this way, the environment is the test, while the individual components are proofed indirectly through their use. Usage type of test has a optimistic approach to the test, because it expects to have some problems with individual components. The strategy relies heavily on the developers of individual components to the test unit for their products. The objective of this strategy is to avoid repeating the tests carried out by developers, and instead of flesh on the problems caused by the interaction of components in the environment. For integration tests, the tests use type can be more efficient and provides better test coverage focused more traditional functional testing. To be more efficient and accurate, care must be used in the definition of the user, as the workload to create realistic scenarios in the exercise of the environment. This gives the integrated environment works as expected for the target audience.
Bottom Up and Top Down
There are two types of integration.
1. Bottom Up
2. Top Down.
Bottom-Up Testing: An approach to integration testing where the lowest level components are tested first, and then used to facilitate testing of components at a higher level. The process is repeated until the element at the top of the hierarchy is tested.
All low or low-level modules, procedures or functions are integrated and tested. After the integration of lower level tests integrated modules, the next level of modules will be trained and can be used for integration tests. This approach is useful only when all or most of the modules of the same level of development loans. This method also allows to determine the levels of software and it is easier to report the progress of testing as a percentage.
Top Down is the procedure where the top integrated modules are tested and part of module testing, step by step, until the end of the relationship with the module. The main advantage of the database is easy to find bugs. Top to bottom, it is easy to find the missing link branch.
Limitations
Any condition not specified in integration tests, apart from the confirmation of the execution of the design items are usually not tested.
Subscribe to this comment's feed
| < Prev | Next > |
|---|
