Cv-050 Conversion Test Plans
Cv-050 Conversion Test Plans
Cv-050 Conversion Test Plans
Author:
<Author>
Creation Date:
Last Updated:
Document Ref:
Version:
DRAFT 1A
Approvals:
<Approver 1>
<Approver 2>
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
17 of 18
Contents
1.1
1.2
Introduction............................................................................................................... 1
5.1
Conversion Unit Test Plan and Results for <Business Object To Be Converted>........9
6.1
6.2
7.1
8.1
8.2
Open Issues.............................................................................................................. 15
Closed Issues............................................................................................................ 15
<Subject>
File Ref: 260933608.doc
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.
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
client staff member who is responsible for signing off on the accuracy of the testing
procedures
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 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?
(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?
(v. )
17 of 18
Doc Ref:
Seq.
Process
Description
Test
Download Components
Component
Upload Components
Translation Logic
Components
Interface Programs
Component
Component
Component
Component
(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
(v. )
17 of 18
Doc Ref:
(v. )
17 of 18
Doc Ref:
Test #
Datatyp Not
e
null?
%
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:
(v. )
17 of 18
Doc Ref:
Test #:
Order #:
Failure?:
Resolution:
(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
4
5
Interface/Validation
Program
(v. )
17 of 18
Doc Ref:
Action/Test Type
Expected Results
Actual Results
Failure Resolution
(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.
(v. )
17 of 18
Doc Ref:
6.1
Oracle Column
Datatype
Not
null?
Custom?
Test Description:
Custom?
Target Applications
(Navigation Path/Object
Name)
% Verified
Test #
Notes
(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:
(v. )
17 of 18
Doc Ref:
(v. )
17 of 18
Doc Ref:
7.1
<Target Application>
Business Object:
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
(v. )
17 of 18
Doc Ref:
8.1
ID
Issue
Resolution
8.2
ID
Open Issues
Responsibility
Target Date
Responsibility
Target Date
Impact Date
Closed Issues
Issue
Resolution
Impact Date
(v. )
17 of 18
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: