· Integration: The process of combining software elements, hardware elements or both into an overall subsystem/system
· Integration testing: Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them
- To check that all data exchanged across an interface agree with the data structure specifications
- To confirm all the control flows
- To check the data reliability
- To check all the communication delays
- To check the Operating system features like memory consumption
Brief Explanation of Integration Testing:
A software system is composed of one or more subsystems, which are composed of one or more units (which are composed of one or more modules). Integration is the process of building a software system by combining subsystems into a working entity. Integration of subsystems should proceed in an orderly sequence. This allows the operational capabilities of the software to be demonstrated early and thus gives visible evidence that the project is progressing
Integration testing focuses on testing multiple modules working together. It tests the reliability and functionality of groups of units (modules) that have been combined together into larger segments. The most efficient method of integration is to slowly and progressively combine the separate modules into small segments rather than merging all of the units into one large component
Integration tests should verify that major components interface correctly. The scope of integration testing is to verify the design and implementation of all components from the lowest level defined in the architectural design up to the system level. The approach should outline the types of tests, and the amounts of testing, required.
The amount of integration testing required is dictated by the need to:
- Check that all data exchanged across an interface agree with the data structure specifications in the Detailed Design Document.
- Confirm that all the control flows in the Detailed Design Document have been implemented.
Note: The amount of control flow testing required depends on the complexity of the software.
Though the errors found in integration testing should be much fewer than those found in unit testing, they are more time-consuming to diagnose and fix. Studies of testing have shown architectural errors can be as much as thirty times as costly to repair as detailed design errors.
Integration test designs, test cases, test procedures and test reports are documented in the Integration Test section of the Software Verification and Validation Plan.
WHITE BOX TESTING
WHITE BOX TESTING PART TWO
WHITE BOX TESTING PART THREE
WHITE BOX BASIC PATH TESTING
BLACK BOX TESTING PART ONE
BLACK BOX TESTING PART TWO
AUTOMATION IN TESTING
AUTOMATED TESTING TOOLS
AUTOMATED TESTING ANALYSIS
AUTOMATION BEST PRACTICES
AUTOMATED TESTING PROCESS
CHECK POINTS IN AUTOMATED TESTING
SILK TEST INTRODUCTION
FEATURES OF SILK TEST
FEATURES OF SILK TEST PART TWO
TEST PLAN FOR SILK TEST
INSTALLATION TIPS FOR SILK TEST
TEST CASES IN SILK TEST