What is Integration Testing?
INTEGRATION TESTING is defined as a type of testing where software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules, coded by different programmers. The purpose of this level of testing is to expose defects in the interaction between these software modules when they are integrated
Integration Testing focuses on checking data communication amongst these modules. Hence it is also termed as ‘I & T’ (Integration and Testing), ‘String Testing’ and sometimes ‘Thread Testing’.
You are watching: What is the preferred order for performing testing on it projects?
Why do Integration Testing?
How to do Integration Testing?
The Integration test procedure irrespective of the Software testing strategies (discussed above):
Prepare the Integration Tests PlanDesign the Test Scenarios, Cases, and Scripts.Executing the test Cases followed by reporting the defects.Tracking & re-testing the defects.Steps 3 and 4 are repeated until the completion of Integration is successful.
Brief Description of Integration Test Plans:
It includes the following attributes:
Methods/Approaches to testing (as discussed above).Scopes and Out of Scopes Items of Integration Testing.Roles and Responsibilities.Pre-requisites for Integration testing.Testing environment.Risk and Mitigation Plans.
Entry and Exit Criteria of Integration Testing
Entry and Exit Criteria to Integration testing phase in any software development model
Unit Tested Components/ModulesAll High prioritized bugs fixed and closedAll Modules to be code completed and integrated successfully.Integration tests Plan, test case, scenarios to be signed off and documented.
Successful Testing of Integrated Application.Executed Test Cases are documentedAll High prioritized bugs fixed and closedTechnical documents to be submitted followed by release Notes.
Best Practices/ Guidelines for Integration Testing
Study the Architecture design of the Application and identify the Critical Modules. These need to be tested on priority.Obtain the interface designs from the Architectural team and create test cases to verify all of the interfaces in detail. Interface to database/external hardware/software application must be tested in detail.After the test cases, it’s the test data which plays the critical role.Always have the mock data prepared, prior to executing. Do not select test data while executing the test cases.