sample test strategy

8/11/2019 Sample Test Strategy

1/14

1

Page 1 of 14

Sample

Test Strategy Document


2/14

2

Page 2 of 14

1. INTRODUCITON

2. TEST OBJECTIVE

3. TESTAPPROACH

3.1 T EST E NVIRONMENT

3.2 P ROPOSED T EST S CHEDULES

3.3 I N -S COPE

3.4 OUT -S COPE

3.5 I NPUT D ATA

3.6 T OOLS

3.7 S OFTWARE / H ARDW ARE REQUIREMENTS

3.8 A SSUMP TI ON S AND R ISKS

3.9 E NTRANCE / E XI T C RITERIA

3.10 DEFECT T RACKING

4. DIFFERENT TYPE OF TESTSPERFORM

5. TEST TEAM

6. APPENDIX


3/14

3

Page 3 of 14

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

2 Business Overview


4/14

4

Page 4 of 14

2. Test Objective

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

The primary objective is to address the functional tests required for the documented businessrules. The System Testing will be performed to verify the proper interoperability of the differentsub-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/14

5

Page 5 of 14

3TestApproachThe 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.

# Remarks123456789

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 datesare subject to change, and reference should always be made to the updated Microsoft Projectplan. This is available from the XXXXX and project management team of the client.

Project Phase Planned Start PlannedEndOwner

Unit Testing DEV 07-15-2013 08-01-2013

System Integration Test (SIT) QA 08-26-2013 09-30-2013

SAMPLE_PROJECTCP Cycle 1Testing QA 09-01-2013 10-30-2013



Load Test QA 09-23-2013 09-30-2013


6/14

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 ScopeThe following enhancements are in scope of SAMPLE_PROJECT Project

# Integration and Functional Testing1

2

3

4

5

67

8

9

10

11

12

13

14

15

1617

18

19

20

21


7/14

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/4002. Jdk 1.5, 1.63. MQ Setup4. DB 200


8/14

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, noadditional 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 QAenvironment 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 CriteriaBefore 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 UATtesting.

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 notslow down with introduction of new features.


9/14

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/14

10

Page 10 of 14

4 Different Type of Tests PerformTESTS P ERFORMED

Type of Test Will Test Be

Performed?Comments/Explanations Owner

System Testing

System Testing Yes No During thisphase all functionalvalidations in terms of functionalflows, data accuracy, test reports

QA Team

IntegrationTesting

Yes No Integration testing will be explicitlyperformed during the Integration,data validation and reportingtests. Integration is implicit withthe functional test for all therequirements. Interface testingspecifically may utilize existingdevelopment resources

QA Team

Regression Test Yes No Regression testing will beperformed as and when thedefect fixes are deployed in thetest environment.

QA Team

Performance TestPerformance Testing Yes No

Will Perform Performance Testingthat Application Response Timeat GUI level.

QA Team

Load Testing Yes NoThis test is to ensure that Systemprovides acceptable responsetime and completion time toprocess with huge data

Shared DEV / QATeams

Fail Over Test Yes NoThe purpose of this testing is toensure production system isbrought down for any reason. TheFailover Process will haverecovery mechanism.

Shared DEV / QATeams

Smoke Test on Final

Package

Yes No QA


11/14

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, StatusReporting,Monitoring of daily progress,Prepare and ExecuteTest Cases, log and track the application defects, Coordinatewith CFT in resolving discrepancies.

QA Analyst Prepare and Execute Test Cases for SAMPLE_PROJECTenhancements log and track application defects

QA Analyst Prepare and Execute Test Cases for SAMPLE_PROJECTenhancements 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, trackrequirement changes and assist in resolving discrepancies.

BA Analyst Provide Business Requirement Document to the CFT andresponsible to clarify for any questions raised during testingphase.


12/14

12

Page 12 of 14

6 APPENDIX

3.1 Message Types SAMPLE_PROJECT

1234

56789101112131415161718

1920212223

252627282930

313233343536

37


13/14

13

Page 13 of 14

3839

REFFERENCES

Document Location Comments

REVISION HISTORY

RevisionNumber

RevisionDate ReviewerName

Review Comments

v1 12-01-2013 Modified SAMPLE_PROJECT TestCycle Schedules

v2 20-01-2014 Exit Criteria has been modified


14/14

14

Page 14 of 14

RevisionNumber

RevisionDate ReviewerName

Review Comments

Written By

Project Function Name Initials Date

Author / Test Team Mohan Kumar P 08/16/2013

sample test strategy

Documents