Está en la página 1de 11

Archive Model Test Plan

Version Enterprise Planning 7.3

Version 8.1

Change Control

Date Version Author Change Description

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.

To accomplish this, first a back up of the Contributor application to be

archived will need to be taken. This can be done by doing a simple Go To
Production on the application to acquire a “hot” back-up DAT file. Once
there is a confirmed DAT file back up, we will then restore the database
using SQL Enterprise Manager. Restore it to a new database name, than
link to new application within the Contributor Admin console.

10/7/2010 Page 5 of 11
Version 8.1

4. Test Description

4.1 Steps

Follow these steps to restore a Contributor Application to a new database name:

1. From the Contributor Admin Console, Expand the application you want to backup,
expand Development, and expand Data store options, then select Data store
2. Make a note of the location that you're backing up your files to, and then click Backup.
3. Launch SQL Enterprise Manager and browse to Databases.
4. Right-click Database and select 'All tasks', then 'Restore database'.
5. In the Restore as Database field, type the new name for the database (make certain
there are no uppercase characters in the name).
6. In the Restore section click From Device, click Select Devices, click Add.
7. In the File name section browse to the location where you saved your backup
8. Select the .dat file that was saved in step 2, then click OK, click OK again, then click
OK again.
9. Go to the Options tab and in the Move to physical filename field, type the path where
you want to restore the new database to. Do the same for both the log file and the dat
10. Go to the General tab, select View Contents and make sure you check off the latest
backup set date. (The date should correspond to the date when you performed your
backup in step 2.)
11. Click OK, and click OK again. The SQL Restore is complete.
12. Launch Contributor Admin Console, right-click your Datastore server and select Link
to Existing Application.
13. You should see the Application name of the new database you just restored, check
that off and select.
14. Validate the application from the web

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.

4.3 End User Notification

4.4 Archive Procedure

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.

5.2 Test Environment

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.

Components/Mod Test Name Scri Tested By Date Comment

ule pt ID

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

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.

cript_V 1.0.doc

Tests_Runs_ Control

10/7/2010 Page 9 of 11
Version 8.1

8. Test Plan

8.1 Roles and Responsibilities

Identify the individuals or groups responsible for providing

• the test cases
• the test platforms and environment

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

Identify individual testing roles responsible for:

• preparing
• executing
• managing
• witnessing
• checking
• resolving or escalating issues

Name Role Responsibilities

8.2 Test Schedule

Tasks/Weeks Week 1 Week 2 Week 3 Week 4 Week 5 Week 6

Prepare scripts
Execute Run 1
Execute Run 2
Execute Run 3

10/7/2010 Page 10 of 11
Version 8.1

9. Test Results Summary

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