OUM

CV.050 CONVERSION TEST PLANS

<Company Long Name>
<Subject>

Author:

<Author>

Creation Date:

November 22, 2010

Last Updated:

January 27, 2011

Document Ref:

<Document Reference Number>

Version:

DRAFT 1A

Approvals:
<Approver 1>
<Approver 2>

CV.050 Conversion Test Plans

Doc Ref: <Document Reference Number>

January 27, 2011

DOCUMENT CONTROL
1.1

Change Record
3

Date

Author

Version

Change Reference

22-Nov-10

<Author>

Draft 1a

No Previous Document

1.2

Reviewers

Name

<Subject>
File Ref: 260933608.doc

Position

Open and Closed Issues

(v. DRAFT 1A )

17 of 18

CV.050 Conversion Test Plans

Doc Ref: <Document Reference Number>

January 27, 2011

Contents

Document Control.................................................................................................... iii

1.1
1.2

Change Record........................................................................................................... iii

Reviewers................................................................................................................... iii

Introduction............................................................................................................... 1

Conversion Component Test Plan...........................................................................3

Conversion Data Integrity Test Plan........................................................................5

Conversion Unit Test - <Business Object To Be Converted>................................8

5.1

Conversion Unit Test Plan and Results for <Business Object To Be Converted>........9

Conversion Business Object Test - <Business Object To Be Converted>.........10

6.1
6.2

Conversion Business Object Test Details..................................................................11

Conversion Business Object Test Results.................................................................12

Conversion Validation Test....................................................................................13

7.1

Conversion Validation Test Results...........................................................................14

Open and Closed Issues.........................................................................................15

8.1
8.2

Open Issues.............................................................................................................. 15
Closed Issues............................................................................................................ 15

<Subject>
File Ref: 260933608.doc

Open and Closed Issues

(v. DRAFT 1A )

17 of 18

Doc Ref:

INTRODUCTION
The Conversion Test Plans outline the testing procedures for the unit, business object, and validation
testing for the conversion. These procedures have been designed to be used as a worksheet for the
tester to fill out while performing the testing tasks:

The unit tests determine that each conversion program module is successfully completing
the task as intended. For example, a unit test should test to verify that the download
program module has extracted the expected number of records from the legacy system.

The business object test verifies that the data that has been converted to the target
application is accurate and functioning properly.

Conversion validation testing tests that the converted legacy system data functions
properly within the entire suite of installed Oracle target applications. The conversion
validation test verifies that the data can complete the entire business cycle including
posting to the general ledger.

Distribute the Data Conversion Test Plan to:

developers who are most likely responsible for performing the unit testing of the
conversion programs which they have written

testers who are responsible for performing the conversion business and validation tests

conversion team members

client staff member who is responsible for signing off on the accuracy of the testing
procedures

overall project leader

conversion team leader

Use the following criteria to ensure the quality of this work product:

Does the work product clearly explain each testing process including directions to the
tester?

Is there a table in the template for each program and for each business object which is to
be module tested?

Have all data elements which are important for business testing been selected? As a
rule, most required columns in Oracle should be tested in conversion business object
testing. Also many of the standard Oracle reports should be run as a test of the datas
ability to function in the new application. The users should help determine the important
data elements which should be tested from the legacy system perspective.

Have users input been gathered?

Have the custom reports that need to be developed for business object and validation
testing on both the legacy side and the Oracle side been identified?

Have resources been identified to create any identified custom queries or reports?

Have these testing procedures been reviewed with the client and the testers?

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

Are there trained testers who know how to navigate through the Oracle Application to
perform the business object and validation tests?

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

CONVERSION COMPONENT TEST PLAN

Below is a table listing the conversion components, which need to be component tested:

Seq.

Process

Description

Test

Download Components

Component

Upload Components

Temporary Table Creation

Components

Translation Logic
Components

Interface Programs

Legacy system program to

create ASCII file
Upload script to a predefined
temporary interface table
Interface script to create
temporary information and
update table
Translation of legacy data
elements to Oracle column
requirements
Development of scripts to load
Oracle production tables and
perform data validation

Component
Component
Component
Component

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

Below are tables for recording the component test design for each conversion component.
An explanation of the Conversion Component Test Plan follows.

Component:
Component Purpose:
Tester:
Date:
Seq.

Action/Test Type

Expected Results

Actual Results

Failure Resolution

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

CONVERSION DATA INTEGRITY TEST PLAN

Below is a table recording the Data Integrity Test Plan. Each entity could have multiple tables to test
depending on the number of data elements that are going to be tested and the number of tables
populated by the entity in Oracle. A table for (later) recording the test results is also provided.
An explanation of the Conversion Data Integrity Test Plan follows:

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

Entity: <Entity Being Converted>

Table Name:
Test Purpose:
Tester:
Oracle Column

Test #

Datatyp Not
e
null?

Test Description: Legacy Custom?

Test Description: Oracle

(Navigation Path/ Object

Name)

(Navigation Path/ Object

Name)

%
Custom Verified Test #
?

Order Number

Order Number

Order Number

________

_________

________

Legacy System

Oracle System

Legacy System

Oracle System

Legacy System

Notes

Oracle System

Test #:
Order #:
Failure?:
Resolution:

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

Test #:
Order #:
Failure?:
Resolution:

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

5
CONVERSION UNIT TEST - <BUSINESS OBJECT TO BE
CONVERTED>
This section contains describes the conversion unit test and provides a record of the unit test results
for the conversion programs for <Business Object To Be Converted>.
This conversion requires the unit testing of the following types of conversion programs:

Seq.

Purpose

Description

1
2
3

Download Program
Upload Program
Interface Table Creation
Program
Translation Program

Legacy system program to create ASCII file

Upload script to a predefined temporary interface table
Interface script to create temporary information and update
table
Translation of legacy data elements to Oracle column
requirements
Development of scripts to load Oracle production tables and
perform data validation

4
5

Interface/Validation
Program

Sequence 1: Download Program

Sequence 2: Upload Program

Sequence 3: Interface Table Creation Program

Sequence 4: Translation Program

Sequence 5: Interface/Validation Program

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

5.1 Conversion Unit Test Plan and Results

for <Business Object To Be Converted>
Program Name:
Program Purpose:
Tester:
Date:
Seq.

Action/Test Type

Expected Results

Actual Results

Failure Resolution

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

6
CONVERSION BUSINESS OBJECT TEST - <BUSINESS OBJECT TO
BE CONVERTED>
This component provides a table to record the business object test plan. Each business object could
have multiple tables for testing, depending on the number of data elements that are going to be
tested and the number of target application tables populated by the business object in the Oracle
target application.
The test procedure for the conversion business object test is as follows:
1.
2.
3.

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

6.1

Conversion Business Object Test Details

Business Object:

<Business Object To Be Converted>

Oracle Table Name:

Test Purpose:
Tester:

Oracle Column

Datatype

Not
null?

Test Description: Legacy

(Navigation Path/Object
Name)

Custom?

Test Description:
Custom?
Target Applications
(Navigation Path/Object
Name)

% Verified

Test #

Notes

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

6.2 Conversion
Business Object Test
Results

Test #

Test Iteration 1
Legacy System

Test Iteration 2
Oracle System

Legacy System

Test Iteration 3
Oracle System

Legacy System

Oracle System

Test #:
Iteration #:
Failure?:
Resolution:

Test #:
Iteration #:
Failure?:
Resolution:

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

CONVERSION VALIDATION TEST

This component provides a table to record the validation test plan. Following is an explanation of the
validation test procedures:
1.
2.
3.

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

7.1

Conversion Validation Test Results

Target Application:

<Target Application>

Business Object:

<Business Object To Be Converted>

Tested by:
Date:

<Legacy System>
Record Totals (1)
Test Method

<Target Application>
Record Totals (2)
Initials

Initials

Variance

Explanation

Record Count
Total Number of Records
Records per Sales rep

(1) Performed as part of the pre-conversion steps

(2) Performed as part of the post-conversion steps

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18

Doc Ref:

OPEN AND CLOSED ISSUES

8.1

ID

Issue

Resolution

8.2

ID

Open Issues

Responsibility

Target Date

Responsibility

Target Date

Impact Date

Closed Issues

Issue

Resolution

Impact Date

Open and Closed Issues

File Ref: 260933608.doc

(v. )

17 of 18