System Integration Testing

As Unit testing is done in development environment, SIT is done in QA environment. Here we test entire program and all integrated modules. Success of all dependent systems/environments and impact analysis are taken care in this type of testing. From data volume perspective total 90 % of production volume data should be processed in SIT. Here also we should maintain test case and test plan as two separate documents.

Test plan :

The purpose of this document is to identify the activities of the QA team will conduct during the QA System Integration Test phase of the deliverables. It will identify specific features/functionality to be tested, testing tasks to be performed, personnel and resources necessary to perform those tests, and outline any associated risks/assumptions.

The System Integration (SI) Test Phase will be conducted after the Development Team completes their Unit Testing. SI testing will be completed before formal User Acceptance Testing (UAT) is conducted by the business users.

Test plan consists of:

1)Test Objectives

2)Test Scope

a)In Scope

b)Out of Scope

for example:

1)E2E test not necessary for this change.

2)Outbound to Data mart data move not necessary to check, no impact.

3) Assumptions & Risks

4)Test Strategy

5)Test Schedule

6)Roles and responsibilities

7)Dependencies

8)Functions to be tested

9)Test Management

10)Tools:

examples are-
Mercury Interactive Quality center for defect tracking
QA inspection check list
TOAD – Tool for Oracle Application Development
Tidal – Tool for running the jobs
Putty – Open source SSH client

11)Test Acceptance Criteria

Before exiting the construction phase and entering the System Integration Test Phase the following criteria should be met.

All Unit Testing completed and results documented in a Unit Test Plan.
All known defects exiting Unit Testing should be entered into the Mercury Defect Tracking Tool.
All software should be installed in the ITG environment.
A construction exist review meeting should be held and sign off received to exit the construction phase

12)Test Exit Criteria

a.Test Plan Development.
Test Cases created.
Test Plan Developed.

b.Test Preparation.
Test environment set up and ready.
Test scenarios developed and reviewed.

c. Unit testing.

Program compiles and programmers are confident of requirement functionality.

d.Test in QA environment.

Successful execution of QA scenarios .
Report and track the defects in QA environment.
Critical and major integration defects are closed.
QA test sign off provided to UAT.

e.Regression Testing.Successful execution of Regression Test scenarios.

System and gaps are identified and documented
Critical and serious defects found are tracked and closed.
Regression test sign off by the QA team/IT functional Leads

e.User Acceptance Test (UAT)

System Test environment is set up and stable.
Executed UAT test scenarios successfully.
Critical and serious UAT test defects are closed.
System and process gaps are identified and documented.
UAT test sign off by the Business leads.


13)UAT scope for QA Team.

QA team to assist the UAT team in testing.
QA team to track the UAT defects until closure.
QA team to send Outbound jobs reports based on the request from UAT.

14)Defect Management

15)Approvals

16)Requirements Traceability Matrix (RTM)

A Requirements Traceability Matrix is a method used to validate the compliance of a process or product with the requirements for that process or product. Each requirement is listed in a row of the matrix, and the columns of the matrix are used to identify how and where each requirement has been addressed by the project.