SIT (System Integration Testing) is a high-end testing process in which tester verify that the software will perform successfully, maintain data integrity and provide expected result while coordinating with other system in the same environment. It is supportive for BI (Business Intelligence) reports too.
SIT testing is done in QA environment, in the same manner as unit testing done in development environments. In the testing process, tests entire integrated modules and all programs carefully. In System Integration Testing, success depends on impact analysis and environments/ systems. Also, tester make sure to maintain test plan and test case as two classify documents- total 90% of production volume data should be processed from data volume perspective in SIT.
First, discover the activities of the QA Team throughout the QA System Integration Test phase of the deliverables. This help to find out specific functionality/ features to be tested – what testing tasks a tester needs to perform, determine any associated risks/ assumptions, and resources and personnel required to perform those tests.
Once the development team completes their unit testing, the tester will conduct the System Integration (SI) Test Phase. It is important to complete the SIT before formal UAT (User Acceptance Testing) conducted by the business users.
STI Test Strategy Includes:
- Objectives of STI
- Scope of Testing
- In Scope
- Out of Scope
- E2E test is not compulsory for this modification.
- Outbound to Data mart- data move is not essential to verify, no impact.
- Risks & Assumptions
- Test Planning
- Test Scheduling
- Roles and Obligations
- Functions to be tested
- Test Management
For Instance -
- Defect tracking by Mercury Interactive Quality Center
- Check list of QA Inspection
- TOAD – Tool for Oracle Application Development
- Tidal – Tool for running the jobs
- Putty – Open source SSH client
- Test Acceptance Criteria
Now, tester needs to follow the criteria's given below before exiting the construction phase and entering into the System Integration Test Phase.
- In a Unit Test Plan, all units testing needs to be completed and results needs to be documented.
- All acknowledged defects exiting Unit Testing needs to be submitted into the Mercury Defect Tracking Tool.
- Always install all the software in the ITG environment.
- A development exist review gathering should be held and sign off obtained to exit the construction phase.
- Test Exit Criteria
Test Plan Development
- Test Cases created
- Test Plan Developed
- Set-up the test environment
- Develop and review test scenarios
- Program includes required functionalities and programmers are confident of proper functioning.
Test in QA Environment
- QA scenarios’ successful execution
- Tracking and reporting of defects in QA environment
- Major and critical integration defects are fixed
- Provide QA test sign off to UAT
Regression Test scenarios’ successful execution
- Gaps and systems are recognized
- Critical issues are discovered, tracked and fixed
- The QA team/IT functional Leads signed off the regression test
User Acceptance Test (UAT)
- Setup the System Test environment and check for stability
- Successfully performed UAT test scenarios
- Tested and fixed critical UAT test defects
- Discovered and documented the system and process gaps
- The Business leads signed off UAT test
- UAT scope for QA Team.
- In testing QA team needs to help the UAT team
- Until closure QA team needs to track the UAT defects
- Outbound jobs reports based on the request from UAT needs to be sent by QA team
- Defect Management
- Requirements Traceability Matrix (RTM)
The Requirements Traceability Matrix process is used to substantiate the compliance of a process or product with the requirements for that particular process or product. In each rows and columns of the matrix each requirement is listed and used to find out how and where the project has been addressed each requirement.
Hence using these steps one can enhance an info cube and can create a new BI (Business Intelligence) report.