Test Plan Workshop

Test Plan Workshop
By: Dung Nguyen

Date: June 08, 2007
December 9, 2021 Confidential 1

Contents
Introduction
What is test plan?
Explain all sections of the current template

INTRODUCTION
The purpose of this course is to explain the meaning of each

sections of QC's current Test Plan template. It also provides the
way to develop the its contents. Completing this course will help
QC members having understanding to write test plans for a
software project.

What is test plan
A document that provides information on

The goals and objectives of testing within the scope of
the iteration (or project)
The items being targeted
The approach to be taken
The resources required
The deliverables to be produced

Test plan template – Table of contents
There are 7 sections in the current template
1. Introduction
2. Target Test Areas
3. Test Specifications
4. Milestones
5. Test Cycle Entry and Exit Criteria
6. Environmental Needs
7. Risks
Test plan template – Introduction
1. Introduction
1.1 Purpose
Provide a high level list of the major target test functions.
List the Requirements for Test
Describe the testing strategies to be employed on each target test
functions
Identify the required resources and schedule the Test execution
1.2 Scope
Test Plan is for release <RELEASE NO.>
Ex: Extract from Test Plan CPD 1.5

This Test Plan is for release 1.5.

1. Introduction (Cont.)
1.3 Document Terminology and Acronyms
Provides the definitions of any terms, acronyms, and abbreviations
required to properly interpret the Test Plan

CPD - Cart Picking Director
HHT - Handheld Terminal
DM - Data Management
HC – Host Communication
RCV – Receiving
INS – Inspection
SC – Storage Card-rack
SP – Storage Pallet
RCVINS - Receiving Inspection
SHPINS – Shipping Inspection
CP – Cart Picking
QTY – Quality

1. Introduction (Cont.)
1.4 References
Provides a list of the documents referenced elsewhere within the
Test Plan
S0148.0-R-001-Software Requirements Specification.doc
S0148.0-P-002-Software Development Plan.doc
Requirement (WMSV10).doc
HHT_Spec(WMSV10).doc
DM_Screen(WMSV10).doc
HostCom(WMSV10).doc
Screen&Lable(WMSV10).doc
HHTScreen2(WMSV10).doc

Test plan template – Target Test Areas
2. Target Test Areas

Provides a high level list of the major target test areas such as:
Software
Hardware
…
Note
This list should include both items produced directly by the project
development team, and items that those products rely on

GUI
Functional

Test plan template – Test Specifications
3. Test Specifications
Includes the following 3 subsections:
Test Specifications is requirement for test (What to test)
Resource is assigned to do it (Who to test)
Test Type is QC member name ( How to test)

Test Spec Resource Test Type Note
Start System Nguyen Van A Functional/GUI CPD server –
System Operation
Stop System Nguyen Van A Functional/GUI
Suspend System Nguyen Van A Functional/GUI
Resume System Nguyen Van A Functional/GUI
… … …
Test plan template – Milestones
4. Milestones
Purpose:
The key schedule milestones that set the context for the Testing effort
Includes 3 sub items:

Milestones
Start Date
End Date
Milestones Start Date End Date

Develop Test Plan Sep 17,2003 Sep 19,2003
Review Test Plan Sep 19,2003 Sep 19,2003
Development Test Case Oct 6,2003 Oct 22, 2003
… … …

Test plan template – Test Cycle Entry and
Exit Criteria
5. Test Cycle Entry and Exit Criteria
5.1 Entry Criteria
Specifies the criteria(tiêu chuẩn) to be used to determine whether
the test activities will start
Ex
First Build successful
First Build is defined in the project plan at 60% function completed?
5.2 Exit Criteria

Specifies the criteria that will be used to determine whether the test
effort for the current Test Cycle of this Test Plan is deemed
sufficient.
Should refer to Quality Plan and Acceptance Criteria
Ex???

Test plan template – Test Cycle Entry and
Exit Criteria (Cont.)
5. Test Cycle Entry and Exit Criteria (Cont.)
5.3 Abnormal Termination
Specifies the criteria that will be used to determine whether testing
should be prematurely suspended or ended for the current test
cycle, or whether the intended build candidate to be tested must be
altered

Over 50% of executed test cases are failed

Test plan template – Environmental
Needs
6. Environmental Needs
Includes the following 3 subsections:
6.1 Hardware and Software
6.2 Productivity and Support Tools
6.3 Test Environment Configurations

Needs (Cont.)
6. Environmental Needs (Cont.)
6.1 Hardware and Software
Specifies the system resources for the test effort. It includes the
following 3 three sub items:
Resource:
Resource
• The name/IP Address of the system resource
Configuration:
Configuration
• Specifies the hardware configuration
Installed OS, Software:

Software
• Specifies the list of OS, Software need to be installed and versions
of those

Needs (Cont.)
6.1 Hardware and Software (Cont.)
Resource Configuration Installed OS, Software

• Processor: P4- 1GHz·
• RAM: 1Gb MB
Data Management • HDD: 20 GB
Server • Network adapter 100Mb • Windows 2000 Server
Ethernet /Professional
• Processor PIII 700MHz • Oracle 9i
• Ram: 256Mb • JVM 1.4.2 or higher
Data Management • HDD 20Gb
Client • Network adapter 100Mb
Ethernet
… … …

Needs (Cont.)
6.2 Productivity and Support Tools
Specifies tools to be employed to support the test process. It includes
the following 4 three sub items:
Tool’s purpose:
purpose
• The purpose of using each tool
Tool Name:
Name
• Specifies the tool’s name
Vendor or In-house:
In-house
• Specifies Vendor’s tool name
Version:
Version
• Specifies versions to be used

Needs (Cont.)
6.2 Productivity and Support Tools (Cont.)
Tool’s purpose Tool Name Vendor or In-house Version

Bug tracker Microsoft Excel Microsoft 2000
Test Report Microsoft Word, Excel Microsoft 2000
… … … …

Needs (Cont.)
6.3 Test Environment Configurations
The Test Environment Configurations needs to be provided and supported
for this project. It includes the following 3 three sub items:
Configuration Name:
Name
• Specifies the short name of the configuration
Description:
Description
• Specifies a short description on the purpose of each configuration
Implemented in Physical Configuration:

Configuration
• How to configure in the real system

Needs (Cont.)
6.3 Test Environment Configurations (Cont.)
Configuration Name Description Implemented in

Physical Configuration
• Install Windows 2000 •Processor: P4- 1GHz·
version • RAM: 1Gb MB
DM Server • Simulator tool • HDD: 20 GB
• JVM: Sun JDK 1.4.2 • Network adapter 100Mb
Ethernet
• Install Windows 2000 •Processor PIII 700MHz
professional version • Ram: 256Mb
DM Client • JVM: Sun JDK 1.4.2 • HDD 20Gb
• Network adapter 100Mb
Ethernet
… … …
Test plan template – Risk
7. Risk
An ongoing or upcoming concern that has a significant probability of adversely
affecting the success of the Test Plan. You must identify mitigation and
contingency strategies for each risk.
It includes the following 3 three sub items:
7.1 Risk
Lists the risk
7.2 Mitigation Strategy

The solution to mitigate the each specified risk
7.3 Contingency (Risk is realized)

When the risk happened, which solution, strategy will be used

Test plan template – Risk
7. Risk (Cont.)
Contingency (Risk is
Risk Mitigation Strategy realized)
Optimize the test schedule Increase testing resource

Not enough time to test and define overtime (human, equipment,..)
strategy at the beginning.
Request IT soon to support Use personal resource
Lack of resource for test the system resource

REFERENCES
Referent Documents:
• Rational Unified Process
Rational Software Corp.
• TL-QCM-001 - Test Plan.doc
GCS Company

THANK YOU FOR YOUR ATTENTION

Test Plan Workshop

Uploaded by

Copyright:

Available Formats

Test Plan Workshop

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Plan Workshop

Uploaded by

Copyright:

Available Formats

Test Plan Workshop

By: Dung Nguyen

December 9, 2021 Confidential 1

What is test plan?

Explain all sections of the current template

December 9, 2021 Confidential 2

The purpose of this course is to explain the meaning of each

December 9, 2021 Confidential 3

A document that provides information on

The items being targeted

The approach to be taken

The resources required

The deliverables to be produced

December 9, 2021 Confidential 4

There are 7 sections in the current template

2. Target Test Areas

5. Test Cycle Entry and Exit Criteria

Ex: Extract from Test Plan CPD 1.5

December 9, 2021 Confidential 6

Ex: Extract from Test Plan CPD 1.5

December 9, 2021 Confidential 7

December 9, 2021 Confidential 8

2. Target Test Areas

Ex: Extract from Test Plan CPD 1.5

December 9, 2021 Confidential 9

Test Specifications is requirement for test (What to test)

Resource is assigned to do it (Who to test)

Test Type is QC member name ( How to test)

Ex: Extract from Test Plan CPD 1.5

Includes 3 sub items:

Milestones Start Date End Date

December 9, 2021 Confidential 11

5.2 Exit Criteria

December 9, 2021 Confidential 12

Ex: Extract from Test Plan CPD 1.5

December 9, 2021 Confidential 13

6.2 Productivity and Support Tools

6.3 Test Environment Configurations

December 9, 2021 Confidential 14

Installed OS, Software:

December 9, 2021 Confidential 15

Ex: Extract from Test Plan CPD 1.5

Resource Configuration Installed OS, Software

December 9, 2021 Confidential 16

December 9, 2021 Confidential 17

Ex: Extract from Test Plan CPD 1.5

Tool’s purpose Tool Name Vendor or In-house Version

December 9, 2021 Confidential 18

Implemented in Physical Configuration:

December 9, 2021 Confidential 19

Configuration Name Description Implemented in

It includes the following 3 three sub items:

7.2 Mitigation Strategy

7.3 Contingency (Risk is realized)

December 9, 2021 Confidential 21

Optimize the test schedule Increase testing resource

December 9, 2021 Confidential 22

December 9, 2021 Confidential 23

December 9, 2021 Confidential 24

You might also like