<Company Name>

Ojo Podo
<Iteration/ Master> Test Plan
Version <1.0>

[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square
brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should
be deleted before publishing the document. A paragraph entered following this style will automatically be set to
normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for this
document. After closing the dialog, automatic fields may be updated throughout the document by selecting
Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done
separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field
contents. See Word help for more information on working with fields.]
<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Revision History
Date Version Description Author
24/3/2012 1.0 Draft pertama Christian C.

Confidential <Company Name>, 2025 Page 2

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Intended Audience 3
1.4 Document Terminology and Acronyms 3
1.5 References 3
1.6 Document Structure 3

2. Evaluation Mission and Test Motivation 3

2.1 Background 3
2.2 Evaluation Mission 3
2.3 Test Motivators 3

3. Target Test Items 3

4. Outline of Planned Tests 3

4.1 Outline of Test Inclusions 3
4.2 Outline of other candidates for potential inclusion 3
4.3 Outline of Test Exclusions 3

5. Test Approach 3
5.1 Initial Test-Idea Catalogs and other reference sources 3
5.2 Testing Techniques and Types 3
5.2.1 Data and Database Integrity Testing 3
5.2.2 Function Testing 3
5.2.3 Business Cycle Testing 3
5.2.4 User Interface Testing 3
5.2.5 Performance Profiling 3
5.2.6 Load Testing 3
5.2.7 Stress Testing 3
5.2.8 Volume Testing 3
5.2.9 Security and Access Control Testing 3
5.2.10 Failover and Recovery Testing 3
5.2.11 Configuration Testing 3
5.2.12 Installation Testing 3

6. Entry and Exit Criteria 3

6.1 Test Plan 3
6.1.1 Test Plan Entry Criteria 3
6.1.2 Test Plan Exit Criteria 3
6.1.3 Suspension and resumption criteria 3
6.2 Test Cycles 3
6.2.1 Test Cycle Entry Criteria 3
6.2.2 Test Cycle Exit Criteria 3
6.2.3 Test Cycle abnormal termination 3

7. Deliverables 3
7.1 Test Evaluation Summaries 3

Confidential <Company Name>, 2025 Page 3

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

7.2 Reporting on Test Coverage 3

7.3 Perceived Quality Reports 3
7.4 Incident Logs and Change Requests 3
7.5 Smoke Test Suite and supporting Test Scripts 3
7.6 Additional work products 3
7.6.1 Detailed Test Results 3
7.6.2 Additional automated functional Test Scripts 3
7.6.3 Test Guidelines 3
7.6.4 Traceability Matrices 3

8. Testing Workflow 3

9. Environmental Needs 3
9.1 Base System Hardware 3
9.2 Base Software Elements in the Test Environment 3
9.3 Productivity and Support Tools 3
9.4 Test Environment Configurations 3

10. Responsibilities, Staffing and Training Needs 3

10.1 People and Roles 3
10.2 Staffing and Training Needs 3

11. Iteration Milestones 3

12. Risks, Dependencies, Assumptions and Constraints 3

13. Management Process and Procedures 3

13.1 Measuring and Assessing the Extent of Testing 3
13.2 Assessing the deliverables of this Test Plan 3
13.3 Problem Reporting, Escalation and Issue Resolution 3
13.4 Managing Test Cycles 3
13.5 Traceability Strategies 3
13.6 Approval and Signoff 3

<Iteration/ Master> Test Plan

Confidential <Company Name>, 2025 Page 4

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

1. Introduction
1.1 Purpose
Ojo Podo merupakan aplikasi yang akan digunakan untuk mengecek kesamaan dokumen makalah yang berguna
untuk membantu dalam proses pengecekan plagiarism. Departemen software test yang akan melakukan
pengetesan terhadpat software ini
Sistem akan melakukan hal-hal seperti di bawah ini:
 Menyediakan user dengan menu, pentunjuk, dan pesan error kepada penggunadengan pilihan
 Menangani upload dokumen yang akan dicek
 Menangani pengkategorian
 Menyimpan file
 Menangani penambahan atau pengurangan kategori pencarian
 Mengarahkan link download
 Back up secara rutin
 Berjalan pada IIS

1.1. Test Plan Objectives

Test Plan mempunyai beberapa tujuan sebagai berikut:
 Menentukan kegiatan yang diperlukan untuk mempersiapkan Sistem
 Mengkomunikasikan strategi Sistem Pengujian kepada semua pihak bertanggung jawab.
 Menentukan apa saja yang akan dilaporkan pada pihak yang bertanggung jawab.
 Mengkomunikasikan kepada semua pihak yang bertanggung jawab dalam berbagai Dependensi dan Risiko

1.2 Scope

Sistem ini dapat menangani inputan user dari input box maupun secara upload file atau bundle file . Sistem ini

akan menyediakan pengaturan menu dan menyediakan pesan error untuk memberi petunjuk pada pengguna.

Sistem akan melakukan back up secara otomatis setiap 30 hari.

[Provide a brief description of the audience for whom you are writing the Test Plan. This helps readers of your
document identify whether it is a document intended for their use, and helps prevent the document from being
used inappropriately.
Note: Document style and content often alters in relation to the intended audience.
This section should only be about three to five paragraphs in length.]
1.3 Document Terminology and Acronyms
Acronim telah terdapat pada glossary
[This subsection provides the definitions of any terms, acronyms, and abbreviations required to properly
interpret the Test Plan. Avoid listing items that are generally applicable to the project as a whole and that are
already defined in the project’s Glossary. Include a reference to the project’s Glossary in the References
section.]
1.4 References
[This subsection provides a list of the documents referenced elsewhere within the Test Plan. Identify each
document by title, version (or report number if applicable), date, and publishing organization or original

Confidential <Company Name>, 2025 Page 5

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

author. Avoid listing documents that are influential but not directly referenced. Specify the sources from which
the “official versions” of the references can be obtained, such as intranet UNC names or document reference
codes. This information may be provided by reference to an appendix or to another document.]
1.5 Document Structure
[This subsection outlines what the rest of the Test Plan contains and gives an introduction to how the rest of the
document is organized. This section may be eliminated if a Table of Contents is used.]
2. Evaluation Mission and Test Motivation
[Provide an overview of the mission and motivation for the testing that will be conducted in this iteration.]
2.1 Background
[Provide a brief description of the background surrounding why the test effort defined by this Test Plan will be
undertaken. Include information such as the key problem being solved, the major benefits of the solution, the
planned architecture of the solution, and a brief history of the project. Where this information is defined in
other documents, you can include references to those other more detailed documents if appropriate. This
section should only be about three to five paragraphs in length.]
2.2 Evaluation Mission
[Provide a brief statement that defines the mission for the evaluation effort in the current iteration. This
statement might incorporate one or more concerns including:
 find as many bugs as possible
 find important problems, assess perceived quality risks
 advise about perceived project risks
 certify to a standard
 verify a specification (requirements, design or claims)
 advise about product quality, satisfy stakeholders
 advise about testing
 fulfill process mandates
 and so forth
Each mission provides a different context to the test effort and alters the way in which testing should be
approached.]
2.3 Test Motivators
[Provide an outline of the key elements that will motivate the testing effort in this iteration. Testing will be
motivated by many thingsquality risks, technical risks, project risks, use cases, functional requirements, non-
functional requirements, design elements, suspected failures or faults, change requests, and so forth.]
3. Target Test Items
The listing below identifies those test itemssoftware, hardware, and supporting product elements that have
been identified as targets for testing. This list represents what items will be tested.
[Provide a high level list of the major target test items. This list should include both items produced directly by
the project development team, and items that those products rely on; for example, basic processor hardware,
peripheral devices, operating systems, third-party products or components, and so forth. Consider grouping the
list by category and assigning relative importance to each motivator.]
4. Outline of Planned Tests
[This section provides a high-level outline of the testing that will be performed. The outline in this section

Confidential <Company Name>, 2025 Page 6

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

represents a high level overview of both the tests that will be performed and those that will not.]
4.1 Outline of Test Inclusions
[Provide a high level outline of the major testing planned for the current iteration. Note what will be included
in the plan and record what will explicitly not be included in the section titled Outline of Test Exclusions.]
4.2 Outline of Other Candidates for Potential Inclusion
[Separately outline test areas you suspect might be useful to investigate and evaluate, but that have not been
sufficiently researched to know if they are important to pursue.]
4.3 Outline of Test Exclusions
[Provide a high level outline of the potential tests that might have been conducted but that have been explicitly
excluded from this plan. If a type of test will not be implemented and executed, indicate this in a sentence
stating the test will not be implemented or executed and stating the justification, such as:
 “These tests do not help achieve the evaluation mission.”
 “There are insufficient resources to conduct these tests.”
 “These tests are unnecessary due to the testing conducted by xxxx.”
As a heuristic, if you think it would be reasonable for one of your audience members to expect a certain aspect
of testing to be included that you will not or cannot address, you should note it’s exclusion: If the team agrees
the exclusion is obvious, you probably don’t need to list it.]
5. Test Approach
[The Test Approach presents the recommended strategy for designing and implementing the required tests.
Sections 3, Target Test Items, and 4, Outline of Planned Tests, identified what items will be tested and what
types of tests would be performed. This section describes how the tests will be realized.
One aspect to consider for the test approach is the techniques to be used. This should include an outline of how
each technique can be implemented, both from a manual and/or an automated perspective, and the criterion for
knowing that the technique is useful and successful. For each technique, provide a description of the technique
and define why it is an important part of the test approach by briefly outlining how it helps achieve the
Evaluation Mission or addresses the Test Motivators.
Another aspect to discuss in this section is the Fault or Failure models that are applicable and ways to
approach evaluating them.
As you define each aspect of the approach, you should update Section 10, Responsibilities, Staffing, and
Training Needs, to document the test environment configuration and other resources that will be needed to
implement each aspect.]
5.1 Initial Test-Idea Catalogs and Other Reference Sources
[Provide a listing of existing resources that will be referenced to stimulate the identification and selection of
specific tests to be conducted. An example Test-Ideas Catalog is provided in the examples section of RUP.]
5.2 Testing Techniques and Types
5.2.1 Data and Database Integrity Testing
[The databases and the database processes should be tested as an independent subsystem. This testing should
test the subsystems without the target-of-test’s User Interface as the interface to the data. Additional research
into the DataBase Management System (DBMS) needs to be performed to identify the tools and techniques that
may exist to support the testing identified in the following table.]

Confidential <Company Name>, 2025 Page 7

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Technique Objective: [Exercise database access methods and processes independent of the UI so
you can observe and log incorrect functioning target behavior or data
corruption.]
Technique:  [Invoke each database access method and process, seeding each with
valid and invalid data or requests for data.
 Inspect the database to ensure the data has been populated as
intended and all database events have occurred properly, or review the
returned data to ensure that the correct data was retrieved for the
correct reasons.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 base configuration imager and restorer
 backup and recovery tools
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so forth)
 database SQL utilities and tools
 Data-generation tools]
Success Criteria: [The technique supports the testing of all key database access methods and
processes.]
Special Considerations:  [Testing may require a DBMS development environment or drivers to
enter or modify data directly in the databases.
 Processes should be invoked manually.
 Small or minimally sized databases (limited number of records) should
be used to increase the visibility of any non-acceptable events.]

5.2.2 Function Testing

[Function testing of the target-of-test should focus on any requirements for test that can be traced directly to
use cases or business functions and business rules. The goals of these tests are to verify proper data
acceptance, processing, and retrieval, and the appropriate implementation of the business rules. This type of
testing is based upon black box techniques; that is verifying the application and its internal processes by
interacting with the application via the Graphical User Interface (GUI) and analyzing the output or results.
The following table identifies an outline of the testing recommended for each application.]

Confidential <Company Name>, 2025 Page 8

<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Technique Objective: [Exercise target-of-test functionality, including navigation, data entry,

processing, and retrieval to observe and log target behavior.]
Technique: [Execute each use-case scenario’s individual use-case flows or functions
and features, using valid and invalid data, to verify that:
 the expected results occur when valid data is used
 the appropriate error or warning messages are displayed when
invalid data is used
 each business rule is properly applied]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 base configuration imager and restorer
 backup and recovery tools
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so forth)
 Data-generation tools]
Success Criteria: [The technique supports the testing of:
 all key use-case scenarios
 all key features]
Special Considerations: [Identify or describe those items or issues (internal or external) that impact
the implementation and execution of function test.]

Confidential <Company Name>, 2025 Page 9

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

5.2.3 Business Cycle Testing

[Business Cycle Testing should emulate the activities performed on the <Project Name> over time. A period
should be identified, such as one year, and transactions and activities that would occur during a year’s period
should be executed. This includes all daily, weekly, and monthly cycles, and events that are date-sensitive, such
as ticklers.]

Technique Objective: [Exercise target-of-test and background processes according to required

business models and schedules to observe and log target behavior.]
Technique: [Testing will simulate several business cycles by performing the following:
 The tests used for target-of-test’s function testing will be modified or
enhanced to increase the number of times each function is executed to
simulate several different users over a specified period.
 All time or date-sensitive functions will be executed using valid and
invalid dates or time periods.
 All functions that occur on a periodic schedule will be executed or
launched at the appropriate time.
 Testing will include using valid and invalid data to verify the
following:
o The expected results occur when valid data is used.
o The appropriate error or warning messages are displayed
when invalid data is used.
o Each business rule is properly applied.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 base configuration imager and restorer
 backup and recovery tools
 Data-generation tools]
Success Criteria: [The technique supports the testing of all critical business cycles.]
Special Considerations:  [System dates and events may require special support activities.
 A business model is required to identify appropriate test requirements
and procedures.]

Confidential <Company Name>, 2025 Page 10

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

5.2.4 User Interface Testing

[User Interface (UI) testing verifies a user’s interaction with the software. The goal of UI testing is to ensure
that the UI provides the user with the appropriate access and navigation through the functions of the target-of-
test. In addition, UI testing ensures that the objects within the UI function as expected and conform to
corporate or industry standards.]

Technique Objective: [Exercise the following to observe and log standards conformance and
target behavior:
 Navigation through the target-of-test reflecting business functions and
requirements, including window-to-window, field-to- field, and use of
access methods (tab keys, mouse movements, accelerator keys).
 Window objects and characteristics can be exercised–such as menus,
size, position, state, and focus.]
Technique: [Create or modify tests for each window to verify proper navigation and
object states for each application window and object.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the Test Script Automation Tool.]
Success Criteria: [The technique supports the testing of each major screen or window that
will be used extensively by the end user.]
Special Considerations: [Not all properties for custom and third-party objects can be accessed.]

5.2.5 Performance Profiling

[Performance profiling is a performance test in which response times, transaction rates, and other time-
sensitive requirements are measured and evaluated. The goal of Performance Profiling is to verify performance
requirements have been achieved. Performance profiling is implemented and executed to profile and tune a
target-of-test's performance behaviors as a function of conditions such as workload or hardware
configurations.
Note: Transactions in the following table refer to “logical business transactions”. These transactions are
defined as specific use cases that an actor of the system is expected to perform using the target-of-test, such as
add or modify a given contract.]

Technique Objective: [Exercise behaviors for designated functional transactions or business

functions under the following conditions to observe and log target behavior
and application performance data:
 normal anticipated workload
 anticipated worst-case workload]

Confidential <Company Name>, 2025 Page 11

<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Technique:  [Use Test Procedures developed for Function or Business Cycle

Testing.
 Modify data files to increase the number of transactions or the scripts
to increase the number of iterations that occur in each transaction.
 Scripts should be run on one machine (best case to benchmark single
user, single transaction) and should be repeated with multiple clients
(virtual or actual, see Special Considerations below).]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 an application performance profiling tool, such as Rational Quantify
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so on
 resource-constraining tools; for example, Canned Heat]
Success Criteria: The technique supports testing:
 Single Transaction or single user: Successful emulation of the
transaction scripts without any failures due to test implementation
problems.]
 Multiple transactions or multiple users: Successful emulation of the
workload without any failures due to test implementation
problems.]
Special Considerations: [Comprehensive performance testing includes having a background
workload on the server.
There are several methods that can be used to perform this, including:
 “Drive transactions” directly to the server, usually in the form of
Structured Query Language (SQL) calls.
 Create “virtual” user load to simulate many clients, usually several
hundred. Remote Terminal Emulation tools are used to accomplish
this load. This technique can also be used to load the network with
“traffic”.
 Use multiple physical clients, each running test scripts, to place a load
on the system.
Performance testing should be performed on a dedicated machine or at a
dedicated time. This permits full control and accurate measurement.
The databases used for Performance Testing should be either actual size or
scaled equally.]

Confidential <Company Name>, 2025 Page 12

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

5.2.6 Load Testing

[Load testing is a performance test that subjects the target-of-test to varying workloads to measure and
evaluate the performance behaviors and abilities of the target-of-test to continue to function properly under
these different workloads. The goal of load testing is to determine and ensure that the system functions
properly beyond the expected maximum workload. Additionally, load testing evaluates the performance
characteristics, such as response times, transaction rates, and other time-sensitive issues).]
[Note: Transactions in the following table refer to “logical business transactions”. These transactions are
defined as specific functions that an end user of the system is expected to perform using the application, such as
add or modify a given contract.]

Technique Objective: [Exercise designated transactions or business cases under varying

workload conditions to observe and log target behavior and system
performance data.]
Technique:  [Use Transaction Test Scripts developed for Function or Business
Cycle Testing as a basis, but remember to remove unnecessary
interactions and delays.
 Modify data files to increase the number of transactions or the tests to
increase the number of times each transaction occurs.
 Workloads should include (for example, Daily, Weekly, Monthly and so
forth) Peak loads.
 Workloads should represent both Average as well as Peak loads.
 Workloads should represent both Instantaneous and Sustained Peaks.
 The Workloads should be executed under different Test Environment
Configurations.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 Transaction Load Scheduling and control tool
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so on)
 resource-constraining tools (for example, Canned Heat)
 Data-generation tools]
Success Criteria: [The technique supports the testing of Workload Emulation, which is the
successful emulation of the workload without any failures due to test
implementation problems.]

Confidential <Company Name>, 2025 Page 13

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Special Considerations:  [Load testing should be performed on a dedicated machine or at a

dedicated time. This permits full control and accurate measurement.
 The databases used for load testing should be either actual size or
scaled equally.]

5.2.7 Stress Testing

[Stress testing is a type of performance test implemented and executed to understand how a system fails due to
conditions at the boundary, or outside of, the expected tolerances. This typically involves low resources or
competition for resources. Low resource conditions reveal how the target-of-test fails that is not apparent
under normal conditions. Other defects might result from competition for shared resources, like database locks
or network bandwidth, although some of these tests are usually addressed under functional and load testing.]
[Note: References to transactions in the following table refer to logical business transactions.]
Technique Objective: [Exercise the target-of-test functions under the following stress conditions
to observe and log target behavior that identifies and documents the
conditions under which the system fails to continue functioning properly
 little or no memory available on the server (RAM and persistent
storage space)
 maximum actual or physically capable number of clients connected or
simulated
 multiple users performing the same transactions against the same data
or accounts
 “overload” transaction volume or mix (see Performance Profiling
above)]
Technique:  [Use tests developed for Performance Profiling or Load Testing.
 To test limited resources, tests should be run on a single machine, and
RAM and persistent storage space on the server should be reduced or
limited.
 For remaining stress tests, multiple clients should be used, either
running the same tests or complementary tests to produce the worst-
case transaction volume or mix.
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]

Confidential <Company Name>, 2025 Page 14

<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Required Tools: [The technique requires the following tools:

 Test Script Automation Tool
 Transaction Load Scheduling and control tool
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so on)
 resource-constraining tools (for example, Canned Heat)
 Data-generation tools]
Success Criteria: The technique supports the testing of Stress Emulation. The system can be
emulated successfully in one or more conditions defined as stress
conditions and an observation of the resulting system state during and after
the condition has been emulated can be captured.]
Special Considerations:  [Stressing the network may require network tools to load the network
with messages or packets.
 The persistent storage used for the system should temporarily be
reduced to restrict the available space for the database to grow.
 Synchronize the simultaneous clients accessing of the same records or
data accounts.]

Confidential <Company Name>, 2025 Page 15

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

5.2.8 Volume Testing

[Volume testing subjects the target-of-test to large amounts of data to determine if limits are reached that cause
the software to fail. Volume testing also identifies the continuous maximum load or volume the target-of-test
can handle for a given period. For example, if the target-of-test is processing a set of database records to
generate a report, a Volume Test would use a large test database, and would check that the software behaved
normally and produced the correct report.]

Technique Objective: [Exercise the target-of-test under the following high volume scenarios to
observe and log target behavior:
 Maximum (actual or physically-capable) number of clients connected,
or simulated, all performing the same, worst case (performance)
business function for an extended period.
 Maximum database size has been reached (actual or scaled) and
multiple queries or report transactions are executed simultaneously.]
Technique:  [Use tests developed for Performance Profiling or Load Testing.
 Multiple clients should be used, either running the same tests or
complementary tests to produce the worst-case transaction volume or
mix (see Stress Testing) for an extended period.
 Maximum database size is created (actual, scaled, or filled with
representative data) and multiple clients are used to run queries and
report transactions simultaneously for extended periods.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 Transaction Load Scheduling and control tool
 installation-monitoring tools (registry, hard disk, CPU, memory, and
so on)
 resource-constraining tools (for example, Canned Heat)
 Data-generation tools]
Success Criteria: [The technique supports the testing of Volume Emulation. Large quantities
of users, data, transactions, or other aspects of the system use under
volume can be successfully emulated and an observation of the system
state changes over the duration of the volume test can be captured.]
Special Considerations: [What period of time would be considered an acceptable time for high
volume conditions, as noted above?]

Confidential <Company Name>, 2025 Page 16

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

5.2.9 Security and Access Control Testing

[Security and Access Control Testing focuses on two key areas of security:
 Application-level security, including access to the Data or Business Functions
 System-level Security, including logging into or remotely accessing to the system.
Based on the security you want, application-level security ensures that actors are restricted to specific
functions or use cases, or they are limited in the data that is available to them. For example, everyone may be
permitted to enter data and create new accounts, but only managers can delete them. If there is security at the
data level, testing ensures that “user type one” can see all customer information, including financial data,
however, “user two” only sees the demographic data for the same client.
System-level security ensures that only those users granted access to the system are capable of accessing the
applications and only through the appropriate gateways.]
Technique Objective: [Exercise the target-of-test under the following conditions to observe and
log target behavior:
 Application-level Security: an actor can access only those
functions or data for which their user type is provided
permissions.
 System-level Security: only those actors with access to the system
and applications are permitted to access them.
Technique:  [Application-level Security: Identify and list each user type and
the functions or data each type has permissions for.]
o Create tests for each user type and verify each
permission by creating transactions specific to each user
type.
o Modify user type and re-run tests for same users. In each
case, verify those additional functions or data are
correctly available or denied.
 System-level Access: [See Special Considerations below]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 Test Script Automation Tool
 “Hacker” security breach and probing tools
 OS Security Admin Tools]
Success Criteria: [The technique supports the testing of for each known actor type the
appropriate functions or data affected by security settings can be tested.]

Confidential <Company Name>, 2025 Page 17

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Special Considerations: [Access to the system must be reviewed or discussed with the appropriate
network or systems administrator. This testing may not be required as it
may be a function of network or systems administration.]

5.2.10 Failover and Recovery Testing

[Failover and recovery testing ensures that the target-of-test can successfully failover and recover from a
variety of hardware, software or network malfunctions with undue loss of data or data integrity.
For those systems that must be kept running failover testing ensures that, when a failover condition occurs, the
alternate or backup systems properly “take over” for the failed system without any loss of data or transactions.
Recovery testing is an antagonistic test process in which the application or system is exposed to extreme
conditions, or simulated conditions, to cause a failure, such as device Input/Output (I/O) failures, or invalid
database pointers and keys. Recovery processes are invoked, and the application or system is monitored and
inspected to verify proper application, or system, and data recovery has been achieved.]

Technique Objective: [Simulate the failure conditions and exercise the recovery processes
(manual and automated) to restore the database, applications, and system
to a desired, known, state. The following types of conditions are included in
the testing to observe and log target behavior after recovery:
 power interruption to the client
 power interruption to the server
 communication interruption via network servers
 interruption, communication, or power loss to DASD (Dynamic Access
Storage Devices) and DASD controllers
 incomplete cycles (data filter processes interrupted, data
synchronization processes interrupted)
 invalid database pointers or keys
 invalid or corrupted data elements in database]

Confidential <Company Name>, 2025 Page 18

<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Technique: [The tests already created for Function and Business Cycle testing can be
used as a basis for creating a series of transactions to support failover and
recovery testing, primarily to define the tests to be run to test that recovery
was successful.
 Power interruption to the client: power the PC down.
 Power interruption to the server: simulate or initiate power down
procedures for the server.
 Interruption via network servers: simulate or initiate
communication loss with the network (physically disconnect
communication wires or power down network servers or routers).
 Interruption, communication, or power loss to DASD and DASD
controllers: simulate or physically eliminate communication with one or
more DASDs or controllers.
Once the above conditions or simulated conditions are achieved, additional
transactions should be executed and, upon reaching this second test point
state, recovery procedures should be invoked.
Testing for incomplete cycles uses the same technique as described above
except that the database processes themselves should be aborted or
prematurely terminated.
Testing for the following conditions requires that a known database state
be achieved.
Several database fields, pointers, and keys should be corrupted manually
and directly within the database (via database tools). Additional
transactions should be executed using the tests from Application Function
and Business Cycle Testing and full cycles executed.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 base configuration imager and restorer
 installation monitoring tools (registry, hard disk, CPU, memory, and
so on)
 backup and recovery tools]
Success Criteria: The technique supports the testing of:
 One or more simulated disasters involving one or more combinations
of the application, database, and system.
 One or more simulated recoveries involving one or more combinations
of the application, database, and system to a known desired state.]

Confidential <Company Name>, 2025 Page 19

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Special Considerations:  [Recovery testing is highly intrusive. Procedures to disconnect cabling

(simulating power or communication loss) may not be desirable or
feasible. Alternative methods, such as diagnostic software tools may be
required.
 Resources from the Systems (or Computer Operations), Database, and
Networking groups are required.
 These tests should be run after hours or on an isolated machine.]

5.2.11 Configuration Testing

[Configuration testing verifies the operation of the target-of-test on different software and hardware
configurations. In most production environments, the particular hardware specifications for the client
workstations, network connections, and database servers vary. Client workstations may have different software
loadedfor example, applications, drivers, and so onand, at any one time, many different combinations may
be active using different resources.]

Technique Objective: [Exercise the target-of-test on the required hardware and software
configurations to observe and log target behavior under different
configurations and identify changes in configuration state.]
Technique:  [Use Function Test scripts.
 Open and close various non-target-of-test related software, such as
Microsoft Excel and Word applications, either as part of the test or
prior to the start of the test.
 Execute selected transactions to simulate actors interacting with the
target-of-test and the non-target-of-test software.
 Repeat the above process, minimizing the available conventional
memory on the client workstation.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 base configuration imager and restore
 installation monitoring tools (registry, hard disk, CPU, memory, and
so on)]
Success Criteria: [The technique supports the testing of one or more combinations of the
target test items running in expected, supported deployment environments.]

Confidential <Company Name>, 2025 Page 20

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Special Considerations:  [What non-target-of-test software is needed, is available, and what is

accessible on the desktop?
 What applications are typically used?
 What data are the applications running; for example, a large
spreadsheet opened in Excel or a 100-page document in Word?
 The entire system’s netware, network servers, databases, and so on,
also needs to be documented as part of this test.]

5.2.12 Installation Testing

[Installation testing has two purposes. The first is to ensure that the software can be installed under different
conditionssuch as a new installation, an upgrade, and a complete or custom installationunder normal and
abnormal conditions. Abnormal conditions include insufficient disk space, lack of privilege to create
directories, and so on. The second purpose is to verify that, once installed, the software operates correctly. This
usually means running a number of the tests that were developed for Function Testing.]

Technique Objective: [Exercise the installation of the target-of-test onto each required hardware
configuration under the following conditions to observe and log installation
behavior and configuration state changes:
 new installation: a new machine, never installed previously with
<Project Name>
 update: a machine previously installed <Project Name>, same version
 update: a machine previously installed <Project Name>, older
version]
Technique:  [Develop automated or manual scripts to validate the condition of the
target machine.
o new: never installed
o same or older version already installed
 Launch or perform installation.
 Using a predetermined subset of Function Test scripts, run the
transactions.]
Oracles: [Outline one or more strategies that can be used by the technique to
accurately observe the outcomes of the test. The oracle combines elements
of both the method by which the observation can be made and the
characteristics of specific outcome that indicate probable success or
failure. Ideally, oracles will be self-verifying, allowing automated tests to
make an initial assessment of test pass or failure, however, be careful to
mitigate the risks inherent in automated results determination.]
Required Tools: [The technique requires the following tools:
 base configuration imager and restorer
 installation monitoring tools (registry, hard disk, CPU, memory, and
so on)]

Confidential <Company Name>, 2025 Page 21

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Success Criteria: [The technique supports the testing of the installation of the developed
product in one or more installation configurations.]
Special Considerations: [What <Project Name> transactions should be selected to comprise a
confidence test that <Project Name> application has been successfully
installed and no major software components are missing?]

6. Entry and Exit Criteria

6.1 Test Plan
6.1.1 Test Plan Entry Criteria
[Specify the criteria that will be used to determine whether the execution of the Test Plan can begin.]
6.1.2 Test Plan Exit Criteria
[Specify the criteria that will be used to determine whether the execution of the Test Plan is complete or that
continued execution provides no further benefit.]
6.1.3 Suspension and Resumption Criteria
[Specify the criteria that will be used to determine whether testing should be prematurely suspended or ended
before the plan has been completely executed, and under what criteria testing can be resumed.]
6.2 Test Cycles
6.2.1 Test Cycle Entry Criteria
[Specify the criteria to be used to determine whether the test effort for the next Test Cycle of this Test Plan can
begin.]
6.2.2 Test Cycle Exit Criteria
[Specify the criteria that will be used to determine whether the test effort for the current Test Cycle of this Test
Plan is deemed sufficient.]
6.2.3 Test Cycle Abnormal Termination
[Specify 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.]
7. Deliverables
[In this section, list the various artifacts that will be created by the test effort that are useful deliverables to the
various stakeholders of the test effort. Don’t list all work products; only list those that give direct, tangible
benefit to a stakeholder and those by which you want the success of the test effort to be measured.]
7.1 Test Evaluation Summaries
[Provide a brief outline of both the form and content of the test evaluation summaries, and indicate how
frequently they will be produced.]
7.2 Reporting on Test Coverage
[Provide a brief outline of both the form and content of the reports used to measure the extent of testing, and
indicate how frequently they will be produced. Give an indication as to the method and tools used to record,
measure, and report on the extent of testing.]
7.3 Perceived Quality Reports
[Provide a brief outline of both the form and content of the reports used to measure the perceived quality of the
product, and indicate how frequently they will be produced. Give an indication about to the method and tools
used to record, measure, and report on the perceived product quality. You might include some analysis of
Incidents and Change Request over Test Coverage.]

Confidential <Company Name>, 2025 Page 22

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

7.4 Incident Logs and Change Requests

[Provide a brief outline of both the method and tools used to record, track, and manage test incidents,
associated change requests, and their status.]
7.5 Smoke Test Suite and Supporting Test Scripts
[Provide a brief outline of the test assets that will be delivered to allow ongoing regression testing of
subsequent product builds to help detect regressions in the product quality.]
7.6 Additional Work Products
[In this section, identify the work products that are optional deliverables or those that should not be used to
measure or assess the successful execution of the Test Plan.]
7.6.1 Detailed Test Results
[This denotes either a collection of Microsoft Excel spreadsheets listing the results determined for each test
case, or the repository of both test logs and determined results maintained by a specialized test product.]
7.6.2 Additional Automated Functional Test Scripts
[These will be either a collection of the source code files for automated test scripts, or the repository of both
source code and compiled executables for test scripts maintained by the test automation product.]
7.6.3 Test Guidelines
[Test Guidelines cover a broad set of categories, including Test-Idea catalogs, Good Practice Guidance, Test
patterns, Fault and Failure Models, Automation Design Standards, and so forth.]
7.6.4 Traceability Matrices
[Using a tool such as Rational RequisistePro or MS Excel, provide one or more matrices of traceability
relationships between traced items.]
8. Testing Workflow
[Provide an outline of the workflow to be followed by the Test team in the development and execution of this
Test Plan.]
The specific testing workflow that you will use should be documented separately in the project's Development
Case. It should explain how the project has customized the base RUP test workflow (typically on a phase-by-
phase basis). In most cases, we recommend you place a reference in this section of the Test Plan to the relevant
section of the Development Case. It might be both useful and sufficient to simply include a diagram or image
depicting your test workflow.
More specific details of the individual testing tasks are defined in a number of different ways, depending on
project culture; for example:
 defined as a list of tasks in this section of the Test Plan, or in an accompanying appendix
 defined in a central project schedule (often in a scheduling tool such as Microsoft Project)
 documented in individual, "dynamic" to-do lists for each team member, which are usually too detailed to be
placed in the Test Plan
 documented on a centrally located whiteboard and updated dynamically
 not formally documented at all
Based on your project culture, you should either list your specific testing tasks here or provide some descriptive
text explaining the process your team uses to handle detailed task planning and provide a reference to where
the details are stored, if appropriate.
For Master Test Plans, we recommend avoiding detailed task planning, which is often an unproductive effort if
done as a front-loaded activity at the beginning of the project. A Master Test Plan might usefully describe the

Confidential <Company Name>, 2025 Page 23

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

phases and the number of iterations, and give an indication of what types of testing are generally planned for
each Phase or Iteration.
Note: Where process and detailed planning information is recorded centrally and separately from this Test
Plan, you will have to manage the issues that will arise from having duplicate copies of the same information.
To avoid team members referencing out-of-date information, we suggest that in this situation you place the
minimum amount of process and planning information within the Test Plan to make ongoing maintenance
easier and simply reference the "Master" source material.]
9. Environmental Needs
[This section presents the non-human resources required for the Test Plan.]
9.1 Base System Hardware
The following table sets forth the system resources for the test effort presented in this Test Plan.
[The specific elements of the test system may not be fully understood in early iterations, so expect this section to
be completed over time. We recommend that the system simulates the production environment, scaling down the
concurrent access and database size, and so forth, if and where appropriate.]
[Note: Add or delete items as appropriate.]

System Resources
Resource Quantity Name and Type
Database Server
—Network or Subnet TBD
—Server Name TBD
—Database Name TBD
Client Test PCs
—Include special configuration TBD
requirements
Test Repository
—Network or Subnet TBD
—Server Name TBD
Test Development PCs TBD

9.2 Base Software Elements in the Test Environment

The following base software elements are required in the test environment for this Test Plan.
[Note: Add or delete items as appropriate.]
Software Element Name Version Type and Other Notes
NT Workstation Operating System
Windows 2000 Operating System
Internet Explorer Internet Browser
Netscape Navigator Internet Browser

Confidential <Company Name>, 2025 Page 24

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Software Element Name Version Type and Other Notes

MS Outlook eMail Client software
Network Associates McAfee Virus Checker Virus Detection and Recovery
Software

9.3 Productivity and Support Tools

The following tools will be employed to support the test process for this Test Plan.
[Note: Add or delete items as appropriate.]
Tool Category or Type Tool Brand Name Vendor or In-house Version
Test Management
Defect Tracking
ASQ Tool for functional testing
ASQ Tool for performance testing
Test Coverage Monitor or Profiler
Project Management
DBMS tools

9.4 Test Environment Configurations

The following Test Environment Configurations needs to be provided and supported for this project.
Configuration Name Description Implemented in Physical
Configuration
Average user configuration
Minimal configuration supported
Visually and mobility challenged
International Double Byte OS
Network installation (not client)

10. Responsibilities, Staffing, and Training Needs

[This section presents the required resources to address the test effort outlined in the Test Plan—the main
responsibilities, and the knowledge or skill sets required of those resources.]
10.1 People and Roles
This table shows the staffing assumptions for the test effort.
[Note: Add or delete items as appropriate.]

Confidential <Company Name>, 2025 Page 25

<Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Human Resources
Role Minimum Resources Specific Responsibilities or Comments
Recommended
(number of full-time roles allocated)

Test Manager Provides management oversight.

Responsibilities include:
 planning and logistics
 agree mission
 identify motivators
 acquire appropriate resources
 present management reporting
 advocate the interests of test
 evaluate effectiveness of test effort
Test Analyst Identifies and defines the specific tests to be
conducted.
Responsibilities include:
 identify test ideas
 define test details
 determine test results
 document change requests
 evaluate product quality
Test Designer Defines the technical approach to the
implementation of the test effort.
Responsibilities include:
 define test approach
 define test automation architecture
 verify test techniques
 define testability elements
 structure test implementation
Tester Implements and executes the tests.
Responsibilities include:
 implement tests and test suites
 execute test suites
 log results
 analyze and recover from test failures
 document incidents

Confidential <Company Name>, 2025 Page 26

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Human Resources
Role Minimum Resources Specific Responsibilities or Comments
Recommended
(number of full-time roles allocated)

Test System Administrator Ensures test environment and assets are

managed and maintained.
Responsibilities include:
 administer test management system
 install and support access to, and recovery
of, test environment configurations and test
labs
Database Administrator, Ensures test data (database) environment and
Database Manager assets are managed and maintained.
Responsibilities include:
 support the administration of test data and
test beds (database).
Designer Identifies and defines the operations, attributes,
and associations of the test classes.
Responsibilities include:
 defines the test classes required to
support testability requirements as
defined by the test team
Implementer Implements and unit tests the test classes and
test packages.
Responsibilities include:
 creates the test components required to
support testability requirements as
defined by the designer

10.2 Staffing and Training Needs

This section outlines how to approach staffing and training the test roles for the project.
[The way to approach staffing and training will vary from project to project. If this section is part of a Master
Test Plan, you should indicate at what points in the project lifecycle different skills and numbers of staff are
needed. If this is an Iteration Test Plan, you should focus mainly on where and what training might occur
during the Iteration.
Give thought to your training needs, and plan to schedule this based on a Just-In-Time (JIT) approach—there
is often a temptation to attend training too far in advance of its usage when the test team has apparent slack.
Doing this introduces the risk of the training being forgotten by the time it's needed.
Look for opportunities to combine the purchase of productivity tools with training on those tools, and arrange
with the vendor to delay delivery of the training until just before you need it. If you have enough headcount,
consider having training delivered in a customized manner for you, possibly at your own site.

Confidential <Company Name>, 2025 Page 27

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

The test team often requires the support and skills of other team members not directly part of the test team.
Make sure you arrange in your plan for appropriate availability of System Administrators, Database
Administrators, and Developers who are required to enable the test effort.]
11. Iteration Milestones
[Identify the key schedule milestones that set the context for the Testing effort. Avoid repeating too much detail
that is documented elsewhere in plans that address the entire project.]

Milestone Planned Actual Planned Actual

Start Date Start Date End Date End Date
Iteration Plan agreed
Iteration starts
Requirements baselined
Architecture baselined
User Interface baselined
First Build delivered to test
First Build accepted into test
First Build test cycle finishes
[Build Two will not be tested]
Third Build delivered to test
Third Build accepted into test
Third Build test cycle finishes
Fourth Build delivered to test
Fourth Build accepted into test
Iteration Assessment review
Iteration ends

12. Risks, Dependencies, Assumptions, and Constraints

[List any risks that may affect the successful execution of this Test Plan, and identify mitigation and
contingency strategies for each risk. Also indicate a relative ranking for both the likelihood of occurrence and
the impact if the risk is realized.]
Contingency (Risk is
Risk Mitigation Strategy realized)
Prerequisite entry <Tester> will define the prerequisites that must be  Meet outstanding prerequisites
criteria is not met. met before Load Testing can start.  Consider Load Test Failure

<Customer> will endeavor to meet prerequisites

indicated by <Tester>.

Confidential <Company Name>, 2025 Page 28

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

Contingency (Risk is
Risk Mitigation Strategy realized)
Test data proves to be <Customer> will ensure a full set of suitable and  Redefine test data
inadequate. protected test data is available.  Review Test Plan and modify
 components (that is, scripts)
<Tester> will indicate what is required and will  Consider Load Test Failure
verify the suitability of test data.
Database requires <System Admin> will endeavor to ensure the  Restore data and restart
refresh. Database is regularly refreshed as required by  Clear Database
<Tester>.

[List any dependencies identified during the development of this Test Plan that may affect its successful
execution if those dependencies are not honored. Typically these dependencies relate to activities on the critical
path that are prerequisites or post-requisites to one or more preceding (or subsequent) activities You should
consider responsibilities you are relying on other teams or staff members external to the test effort completing,
timing and dependencies of other planned tasks, the reliance on certain work products being produced.]
Dependency between Potential Impact of Dependency Owners

[List any assumptions made during the development of this Test Plan that may affect its successful execution if
those assumptions are proven incorrect. Assumptions might relate to work you assume other teams are doing,
expectations that certain aspects of the product or environment are stable, and so forth].
Impact of Assumption being
Assumption to be proven incorrect Owners

[List any constraints placed on the test effort that have had a negative effect on the way in which this Test Plan
has been approached.]
Constraint on Impact Constraint has on test effort Owners

13. Management Process and Procedures

[Outline what processes and procedures are to be used when issues arise with the Test Plan and its
enactment.]
13.1 Measuring and Assessing the Extent of Testing
[Outline the measurement and assessment process to be used to track the extent of testing.]
13.2 Assessing the Deliverables of this Test Plan
[Outline the assessment process for reviewing and accepting the deliverables of this Test Plan]

Confidential <Company Name>, 2025 Page 29

 <Project Name> Version: <1.0>
<Iteration/ Master> Test Plan Date: <dd/mmm/yy>
<document identifier>

13.3 Problem Reporting, Escalation, and Issue Resolution

[Define how process problems will be reported and escalated, and the process to be followed to achieve
resolution.]
13.4 Managing Test Cycles
[Outline the management control process for a test cycle.]
13.5 Traceability Strategies
[Consider appropriate traceability strategies for:
 Coverage of Testing against Specifications — enables measurement the extent of testing
 Motivations for Testing — enables assessment of relevance of tests to help determine whether to
maintain or retire tests
 Software Design Elements — enables tracking of subsequent design changes that would necessitate
rerunning tests or retiring them
 Resulting Change Requests — enables the tests that discovered the need for the change to be identified
and re-run to verify the change request has been completed successfully]
13.6 Approval and Signoff
[Outline the approval process and list the job titles (and names of current incumbents) that initially must
approve the plan, and sign off on the plans satisfactory execution.]

Confidential <Company Name>, 2025 Page 30