Level of testing done offshore before submission for User Acceptance testing

The customer gets the first experience of the tested application when it goes into User
Acceptance Testing (UAT). In order to ensure that this experience is exceptional, Wipro rigorously
tests the application before releasing it to the client for UAT. The testing of integrated application
software systems is done in four phases:

Process name:
SUPPLIER / S
Workstream PMs
& IVV

INPUTS
S/W load
developed and
Configuration files

WIPRO TESTING PROCESS

PROCESS
Unit Testing

UNIT Tests
passed

OUTPUT / S

No

Defect Resolution
Process

Yes

Unit Testing: Program Spec

(Internal), Detailed I/f specs,
Configuration/Customization
details, and Unit tested Code
and test execution records

CUSTOMER / S
Customer
(TESTING)

Stage Review
(A)RequisitePro
traceability upto DD
(B) Staging
Environment Created
(C) Build installed and
ready to test
(D) Test Data
(E) Sanitised Build
(F) Installation
document
(G) Exit criteria of MT /
ST are satisfied
(H) Module & System
Test execution results

Module Testing

Stage Review

System Testing

Stage Review

Integration Testing

Module Tests
passed

No

Defect Resolution
Process

Module Testing: Module test

execution reports and module
tested code

No

Defect Resolution
Process

System Testing : System test

execution report and System
tested code

No

Defect Resolution
Process

Integration Testing :
Integration test execution
report and Integration tested
code

No

Defect Resolution
Process

Yes

System Tests
Passed
Yes

Integration
Tests Passed
Yes

Stage Review

If applicable
Regression
Testing

Tests Passed
Yes

Regression Testing :
Unit/Module/System/
Integration /Regression/
Performance Tested code and
test execution records

Wipro Release
Process to
Customer

Unit Testing Phase

The unit testing stage examines how a single component performs in isolation from other units.
Unit testing primarily tests structural characteristics, whereas other stages of testing examine the
functional aspects. Unit testing is conducted throughout the application design stage where the
smallest components are being tested separately. Key component testing activities include (but
are not limited to) verifying data entry, retrieval, update and deletion, data formatting accuracy,
data transfer to other units and time-related behavior.
Module Testing Phase
Following the successful completion of unit testing, the software application will be subjected to
module testing. Module testing will test the application as a whole, as well as any adjoining
interfaces.
System Testing Phase
Sub-systems are integrated to make up systems. System testing examines how two or more subsystems perform in combination as a whole system. The key system testing activity is to test the
overall functioning of the system as well as its performance under stress.
Integration Testing Phase
Complex applications are built by assembling separately constructed components. Integration
refers to this assembly process. Integration testing is the testing of interconnected modules or
sub-system components to ensure that all are capable of inter-working as required. Key
integration testing activities include (but are not limited to) verifying the transfer of data values

between sub-systems, proper operations of the external interfaces between systems, time-related
behavior and the operation of integration software.
Regression Testing Phase
Regression testing examines the effectiveness of the bug fixes and re-runs, the failed test cases
from the system-testing phase as well as any other test cases as required. Only after regression
testing is completed is the system released to the user for acceptance testing.