Test Plan Template

LOGO

Project NAME:
TEST PLAN

http://www.h2kinfosys.com

LOGO… Project Name Test Plan

USA: 770 777 1269 | UK: 020 3371 7615 | Email: h2kinfosys@gmail.com



Contents
1 Document Information...................................................................................4

1 Document Status Codes................................................................................5

2 Revision History.............................................................................................6

3 Reference Data................................................................................................7

4 Acronyms........................................................................................................8

5 Background.....................................................................................................9

6 Test Overview...............................................................................................10

7 Test Platform/Team.......................................................................................11

8 Introduction...................................................................................................12
1. Installation scenarios ....................................................................................12
2. 12
3. Installation scenarios.....................................................................................13
4. 13

9 Risk Analysis & Contingencies...................................................................14

10 Test Strategy...............................................................................................15
1.1 Integration Testing.......................................................................................15
1.2 Stress Testing..............................................................................................15

11 Pass/Fail Criteria.........................................................................................16

12 Entrance/Exit Criteria.................................................................................17

13 Schedule......................................................................................................19

14 Test Results................................................................................................20

15 Test Cases...................................................................................................21

16 Recommendations......................................................................................23

17 Conclusions................................................................................................24

18 Appendix.....................................................................................................25




1 Document Information

Title:

Filename:




1 Document Status Codes

Work In Progress An incomplete document, designed to guide
discussion and generate feedback, which may
include several alternative requirements for
consideration.

Draft A document in specification format considered largely
complete, but lacking review. Drafts are susceptible
to substantial change during the review process.

Issued A stable document, which has undergone review and
is suitable for product design and development, and
cross-product interoperability.

In Revision Similar to Work In Progress, but indicates that a prior
version has been issued. The document is now
being revised to incorporate new or updated
information.

Closed A static document, reviewed, tested, validated, and
closed to further change requests.




2 Revision History

Date Author Description




3 Reference Data

Document ID Author Date




4 Acronyms
Term Definition
CRA Central Report Application




5 Background
The Back ground info of components / projects




6 Test Overview
For <Project > testing, the following features will be tested:

•

• GUI changes to search xyx…




7 Test Platform/Team

Equipment
•
•
• Sun x2530
•
• Internet Explorer 8/ Firefox 3.x
•
• SOAP UI client (
•

Test Team

Rao Tambareni




8 Introduction

Purpose
This document details the test findings from <Project > testing.

Test Scope
Provide test coverage to include:
• Common
• Integration
•
•
• Full new feature set
•

Features To Be Tested

1. Installation scenarios

The test environment must be staged prior to beginning the installation process for the QA
test cycle. Environment staging will include procuring adequate hardware and proper
network communications.
• Configure client

2.

•

2.1.1 System Scalability Test Configuration




•

Features With Limited Testing

3. Installation scenarios
This section contains any information related to any requirements and test
scenarios

Features Not To Be Tested

4.
•




9 Risk Analysis & Contingencies
The following items present a potential risk to the testing effort. If these issues are not resolved, they may
have an impact on the testing effort
Risks

• Ongoing modifications to key design documents during final development cycles

•

Contingencies

•




10 Test Strategy
The software release delivery method from the development group to the quality assurance group
will be an integration tested, fully functional build.

Testing Priorities

• Upgrade testing

• General system sanity testing performed to ensure that all internal and external
components are registered properly to validate testing environment set-up

• Defect testing based on list of target defects for each code drop

• New feature requirements testing followed by evaluation of affected internal components

• Comprehensive regression of applicable

1.1 Integration Testing
• Joint testing between
• Joint testing between other QA and QA for client testing and various

1.2 Stress Testing
The stress testing will be broken into two types: scalability testing and load testing.
QA will perform basic load testing

The Systems Verification organization will be performing systems scalability testing




11 Pass/Fail Criteria
The feature requirements will be organized into test case form per component. The test case format will
consist of titles, summaries and step by step actions to be taken to produce an expected result. Upon test
case execution, if it is evaluated that any of the expected results are not satisfied, then that test case will be
considered “failed”. The test case will be marked “failed” in the test case tracking tool (Quality Center) and a
defect will be entered using the defect tracking tool (Quality Center). The QA Metrics Intranet site will also
provide access to the defects. Based on various defect reviews, all failed requirements defects must be
corrected and retargeted to a subsequent point release for reevaluation. Severity of defects will be
assigned based on the following criteria:

• Severity 1 – Blocker - Defect blocks all further activities (most critical)
• Severity 2 – Critical - Defect prevents major functionality execution
• Severity 3 – Normal - Defect prevents expected results but “work arounds” allow most
functionality execution to continue
• Severity 4 – Minor - Defect typically is cosmetic in nature (most trivial)
• Severity 5 – Enhancement – Not a defect; no requirements impact and typically includes new ”nice
to have” features

Defect management will consist of the following methods for blocking, reopening, closing, and targeting
defects during verification:

Blocking a defect: The defect cannot be tested. The defect status is left as “Resolved Fixed” and
comments added related to why it cannot be tested. The target milestone is changed to “---“.

Reopening a defect: The defect has been tested and failed. The defect status is changed to “Reopened”
and comments added related to why it failed. The target milestone is changed to “---“. The version is
changed to the current release version.

Closing a defect: The defect has been tested and passed. Add comments related to successful test
results.

All test cases which produce the expected results will be considered “passed” and tracked as a successful
execution/demonstration of the feature. Both TestLink and the QA Metrics Intranet site will display overall
progress.




12 Entrance/Exit Criteria

Entrance criteria

• All applicable code successfully merged to new build

• All applicable new feature coding in new build

• All applicable unit testing completed

• All applicable integration testing completed

• All applicable sanity testing completed

• QA code

• Install instructions (turnover doc)

Exit criteria

To test lab 

• No severity 1 or 2 defects

• All test cases executed

• All applicable regression test cases executed

• All applicable upgrade path testing completed

• All applicable fresh install testing completed (as required)

• All applicable image install testing completed (as required)

• All applicable migration path testing completed (as required)

To production




• Passed QA

• No severity 1 or 2 defects

• All test cases executed

• All applicable regression test cases executed

• All applicable upgrade path testing completed

• All applicable fresh install testing completed

• All applicable image install testing completed (as required)

• All applicable migration path testing completed (as required)

• Passed customer test lab acceptance testing (as required)




13 Schedule
TBA




14 Test Results
Upon completion of the QA testing cycle a test summary report will be produced detailing testing
metrics and results. Various methods will be used to monitor testing progress during the QA cycle
including QA Metrics, Quality Center, defect reviews, and staff meetings.




15 Test Cases
A limited set of test cases will be added below to review some of the verification steps/expected
results of key new features. It is expected that adding a test case review will enhance testing
coverage and possibly extend testing coverage. Any updates and/or new test case ideas will be
discussed for the possibility of including them in the test case suite in Quality Center.

Test Case # Description Steps To be Taken Expected Results Requirement #




16 Recommendations
None




17 Conclusions
None




18 Appendix


Test Plan Template

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Test Plan Template

Similar to Test Plan Template (20)

More from H2Kinfosys

More from H2Kinfosys (18)

Recently uploaded

Recently uploaded (20)

Test Plan Template