1

Page 1 of 14












Sample

Test Strategy Document

















2


Page 2 of 14


1.INTRODUCITON

2.TEST OBJECTIVE

3. TESTAPPROACH

3.1TEST ENVIRONMENT

3.2PROPOSED TEST SCHEDULES

3.3IN-SCOPE

3.4OUT-SCOPE

3.5INPUT DATA

3.6TOOLS

3.7SOFTWARE / HARDWAREREQUIREMENTS

3.8ASSUMPTIONS AND RISKS

3.9ENTRANCE / EXIT CRITERIA

3.10 DEFECT TRACKING

4. DIFFERENT TYPE OF TESTSPERFORM

5.TEST TEAM

6.APPENDIX


3


Page 3 of 14

1Introduction
The purpose of this document is to define the scope of the testing process, define the
deliverables for the test team, and outline the associated tasks.





2 Business Overview














4


Page 4 of 14

2. Test Objective

The goal of New SAMPLE_PROJECT Project testing is to determine the readiness for production
deployment of the application. This determination will be made by Project Leadership, the QA
team. As evidenced by test coverage of said requirements as well as the nature and severity of
unresolved defects (if any).


The primary objective is to address the functional tests required for the documented business
rules. The System Testing will be performed to verify the proper interoperability of the different
sub-systems involved.


The purpose of this test strategy is to:

Identify the key testing areas of SAMPLE_PROJECT
Design high level strategy to test SAMPLE_PROJECT Project
Provide Overview of the types of the testing will be performed
Focus on Standard Test Team deliverables
Risks or Assumptions
Define Test Methodology, Tools, and Reporting Structured
In-Scope and Out-Scope




5


Page 5 of 14

3TestApproach
The current plan is used to perform System Testing, Integration Testing, Regression Testing,
Load Testing and Smoke Test at final package. Three phases of SIT will be performed to prove
the integrity of the data and New SAMPLE_PROJECTArchitecture.


# Remarks
1
2
3
4
5
6
7
8
9
10





3.1 Test Environment


3.2 Proposed Testing Schedule

Below are the current dates for the various testing phases that apply for this project. These dates
are subject to change, and reference should always be made to the updated Microsoft Project
plan. This is available from the XXXXX and project management team of the client.

Project Phase Planned Start Planned
End
Owner
Unit Testing DEV 07-15-2013 08-01-2013
System Integration Test (SIT) QA 08-26-2013 09-30-2013
SAMPLE_PROJECTCP Cycle 1
Testing
QA 09-01-2013 10-30-2013
SAMPLE_PROJECTCP Cycle 2
Testing
QA 10-01-2013 11-30-2013
SAMPLE_PROJECTCP Cycle 3
Testing
QA 12-01-2013 12-31-2013
Load Test QA 09-23-2013 09-30-2013
6


Page 6 of 14

FailOver Testing (DB, MQ and
Application failover)
27-01-2014 27-31-2014
Smoke Test on Final Package 15-02-2014 20-02-2014
User Acceptance Test (UAT) UAT-QA













3.3In Scope
The following enhancements are in scope of SAMPLE_PROJECT Project


#
Integration and Functional Testing
1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21



7


Page 7 of 14



3.4Out of Scope

-NA-










3.5Input Data









The sample Security data has been mentioned below

S.No NSCC SAMPLE_PROJECT Remarks





3.6Tools
QTP tool will be used to run SAMPLE_PROJECT Regression Cases.

3.7Software / Hardware Requirements
1. AS/400
2. Jdk 1.5, 1.6
3. MQ Setup
4. DB 200




8


Page 8 of 14





3.8Assumptions &Risks

Assumptions:

A Separate QA test environment will be in place during the designated time for Testing.
This environment will be controlled by the QA team.

All development code will be delivered to on schedule dates.

A set time will be determined for component freeze in the Test environment. At that time, no
additional changes will be introduced unless the release schedule is adjusted.

Any new code being delivered in to the test environment during test cycle should be
discussed.

The test team requires test data to perform end to end tests so this will be simulated in QA
environment by using MQ utility and NSCC Simulator.

Risk Analysis:

Delays in receiving code and Test environment availability will delay the test effort.
3.10 Entry/Exit Criteria
Entry Criteria
Before this test phase can begin the following items will need to be completed: -
Operating systems, database and networks configured;
Environments setup and available.
Test Plan/Test Cases are developed based BRDs agreed by CFT.
Enhancement Delivery email to QA
Exit Criteria:
Exit Criteria ensures that the testing of application is completed and ready to deliverfor UAT
testing.

The following are the Check list for QA Gate.

All enhancement test case execution must be 100% completed.

No Showstopper / Critical Defects should exist in the Package.

List all open issues which were medium / low defects.

Zero Defects in Performance Process and Performance of the system must not
slow down with introduction of new features.
9


Page 9 of 14


Sign off is required from CFT for each enhancement.

Release cannot be delivered to UAT with Critical/High priority defects.




3.11 Defect Tracking
Remedy Tool is used to Defect Report and Tracking purpose.









10


Page 10 of 14

4 Different Type of Tests Perform
TESTS PERFORMED
Type of Test
Will Test Be
Performed?
Comments/Explanations Owner
System Testing


System Testing

Yes No

During thisphase all functional
validations in terms of functional
flows, data accuracy, test reports

QA Team

Integration
Testing

Yes No

Integration testing will be explicitly
performed during the Integration,
data validation and reporting
tests. Integration is implicit with
the functional test for all the
requirements. Interface testing
specifically may utilize existing
development resources

QA Team

Regression Test

Yes No

Regression testing will be
performed as and when the
defect fixes are deployed in the
test environment.

QA Team
Performance Test
Performance Testing
Yes No

Will Perform Performance Testing
that Application Response Time
at GUI level.
QA Team
Load Testing
Yes No

This test is to ensure that System
provides acceptable response
time and completion time to
process with huge data
Shared DEV / QA
Teams
Fail Over Test
Yes No

The purpose of this testing is to
ensure production system is
brought down for any reason. The
Failover Process will have
recovery mechanism.
Shared DEV / QA
Teams


Smoke Test on Final
Package
Yes No
QA



11


Page 11 of 14

5 TEST TEAM


TEST TEAM
Name Role Specific Responsibilities/Comments
QA Lead Provide a detailed test plan, Overall test coordination, Status
Reporting,Monitoring of daily progress,Prepare and Execute
Test Cases, log and track the application defects, Coordinate
with CFT in resolving discrepancies.
QA Analyst Prepare and Execute Test Cases for SAMPLE_PROJECT
enhancements log and track application defects
QA Analyst Prepare and Execute Test Cases for SAMPLE_PROJECT
enhancements log and track application defects.
Project
Manager
Review Unit Test Cases also consolidates unit test cases of
all other components, Provide unit test cases to QA, track
requirement changes and assist in resolving discrepancies.
BA Analyst Provide Business Requirement Document to the CFT and
responsible to clarify for any questions raised during testing
phase.

























12


Page 12 of 14

6 APPENDIX
3.1 Message TypesSAMPLE_PROJECT





1

2
3
4


5

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23


25

26
27
28
29
30
31
32
33
34
35
36



37

13


Page 13 of 14

38
39













REFFERENCES


Document Location Comments





REVISION HISTORY
Revision
Number
Revision
Date
Reviewer
Name
Review Comments
v1 12-01-2013 Modified SAMPLE_PROJECT Test
Cycle Schedules
v2 20-01-2014 Exit Criteria has been modified

14


Page 14 of 14

Revision
Number
Revision
Date
Reviewer
Name
Review Comments





Written By
Project Function Name Initials Date
Author / Test Team Mohan Kumar
P
08/16/2013