Professional Documents
Culture Documents
For
Version 8.1
Change Control
10/7/2010 Page 2 of 11
Version 8.1
1. Table of Contents
1. Table of Contents__________________________________________________________________3
2. Purpose of Document______________________________________________________________4
3. Testing Approach___________________________________________________________________5
4. Test Description____________________________________________________________________6
4.1 Steps______________________________________________________________________________6
4.2 Assumptions_______________________________________________________________________6
4.3 End User Notification ______________________________________________________________6
4.4 Archive Procedure_________________________________________________________________6
5. Test Preparation____________________________________________________________________7
5.1 Prerequisites_______________________________________________________________________7
5.2 Test Environment__________________________________________________________________7
6. Test List____________________________________________________________________________8
7. Test Scripts_________________________________________________________________________9
8. Test Plan___________________________________________________________________________10
8.1 Roles and Responsibilities________________________________________________________10
8.2 Test Schedule____________________________________________________________________10
9. Test Results Summary____________________________________________________________11
10/7/2010 Page 3 of 11
Version 8.1
2. Purpose of Document
The purpose of this document is to detail the Archive process and implementation of this
process. The tests that shall be carried out as part of the quality management process to
ensure successful project outcome.
10/7/2010 Page 4 of 11
Version 8.1
3. Testing Approach
We will first complete a restore from a set of archived DAT files to ensure the future
capability of restoring from an archive if requested.
10/7/2010 Page 5 of 11
Version 8.1
4. Test Description
4.1 Steps
4.2 Assumptions
It will be assumed if one application restores through the steps outlined in 4.1 that all
applications are safe to archive.
10/7/2010 Page 6 of 11
Version 8.1
5. Test Preparation
5.1 Prerequisites
Describe the prerequisite conditions that must exist before commencing the tests.
Describe the physical characteristics of test environment within which the testing will be
performed. Specify both the necessary and the desired properties of the test
environment. Examples are:
• The necessary hardware
• Software system platforms and supporting applications
• Necessary tools and databases for logging, tracking, and reporting test results
• Supplies needed to perform the tests
• The testing facilities
10/7/2010 Page 7 of 11
Version 8.1
6. Test List
List the performance tests to be conducted. Each test should have an associated script.
10/7/2010 Page 8 of 11
Version 8.1
7. Test Scripts
The purpose of this section is to detail and describe the scripts associated with the tests
above. Each script allows for three runs. The objective of run 1 is to find as many high
priority defects as possible. This run is expected to generate the most number of
defects.
The objective of run 2 is to regression test the fixed defects from run 1 and to determine
if any more defects were caused.
The objective of run 3 is to regression test defects fixed from run two; this is a
condensed run and should progress clean.
The Tests Run Control Sheet provides audit trail for the above runs.
Performance_Test_S
cript_V 1.0.doc
Tests_Runs_ Control
Sheet_V1.0.xls
10/7/2010 Page 9 of 11
Version 8.1
8. Test Plan
Identify key points of contact who may need to be involved during the testing
process. Examples may include contacts among:
• the product developers
• testers
• operations staff
• user representatives
• technical support staff
10/7/2010 Page 10 of 11
Version 8.1
Summarise the results of the Component Test and complete an Issue Form for each
“failed” step of a script. The procedure is to follow the Issue Management Process
outlined in the PSP document.
10/7/2010 Page 11 of 11