Conversion Testing

Approach

Document Summary
Author:
Approved By:
Version:
Status: Draft
Table of Contents
1 DOCUMENT INFORMATION........................................................................................................................3

2 APPROVAL & SIGN OFF.................................................................................................................................4

3 OBJECTIVE........................................................................................................................................................5

4 INTRODUCTION...............................................................................................................................................6

5 SCOPE OF CONVERSION TESTING............................................................................................................7

5.1 CONVERSION TESTING APPROACH.........................................................................................................................9
6 UNIT TEST........................................................................................................................................................10
6.1 DELIVERABLES.................................................................................................................................................10
6.2 UNIT TEST ENTRY CRITERIA.............................................................................................................................11
6.3 UNIT TEST EXIT CRITERIA................................................................................................................................11
7 ASSEMBLY TEST............................................................................................................................................12
7.1 DELIVERABLES.................................................................................................................................................12
7.2 ASSEMBLY TEST ENTRY CRITERIA......................................................................................................................13
7.3 ASSEMBLY TEST EXIT CRITERIA........................................................................................................................13
8 MOCK CONVERSION TEST.........................................................................................................................14
8.1 ENTRY CRITERIA..............................................................................................................................................14
8.2 EXIT CRITERIA.................................................................................................................................................14
8.3 DELIVERABLES.................................................................................................................................................14

Page 2 of 15
7/28/2011
1 Document Information
Version
Description of Change Date Author
No.
0.1 Initial Draft
0.2
0.3
1.0

This document is uncontrolled when printed

Page 3 of 15
7/28/2011
2 Approval & Sign Off
The Information in this document is agreed as correct and required.

Name Role Signature Date

Manager
Integration Team
Lead
Testing Team Lead
Project Manager
Implementation
Project Manager

Page 4 of 15
7/28/2011
3 Objective
The purpose of this document is to outline the test methodology and processes
that will be used by the conversion Team during each conversion testing stage:
component, assembly and mock conversion.

Each of the stages is defined in the table below.

Term Description
Unit Test Tests individual pieces (Units) of the conversion legacy
extract, transform and load programs. The objective of Unit
Test is to ensure that individual components (eg. Extract
program, load program) accurately reflect their associated
design specifications.
Assembly Test Tests the interaction of related groups of Units (Assemblies).
The objective is to ensure that the related load,
transformation and extract components function properly
when integrated. On completion of Unit and Assembly testing,
the group of related units should be technically sound and the
information flow within each conversion object (eg. devices)
should be correct. A successful assembly test will contribute
to the successful execution of the mock conversions.
Mock Conversion Test Tests the complete suite of conversion software and
associated processes. The objective is to ensure that the
required legacy data is converted correctly into CCMS.

Page 5 of 15
7/28/2011
4 Introduction
The Conversion Team intends to conduct a number of mock conversions to test
the go-live conversions for each of the two phases.
To make the mock conversions as accurate as possible, data from each of the
legacy system will be used and the actual ‘go-live’ conversion processes will be
performed; the objective being that no program nor process is performed for the
first time during the ‘go-live’ conversion.

Page 6 of 15
7/28/2011
5 Scope of Conversion Testing
Legacy Data will go through four stages before it is considered to be fully tested
and ready for use by . These four stages are:

Stage Description
Legacy Data Data in original legacy system
Converted Data Data that has been converted through the normal
conversion process (Extract, transform and load)
Quality Converted Data Data that has been validated for completeness and
correctness
Quality Converted Data Data that has been validated for completeness and
that supports Business correctness, and supports business processes
Processes

The diagram below depicts the process surrounding these four stages, and the
corresponding table describes each of these processes.

Unit & Assembly Test Mock Conversion Business Simulation

(2) Assembly Test

(1) Unit Test

Flat File Quality

Transform Quality
Extract Data Load Data Converted Converted
Data Converted
Data Data for
Data
Business Process

(3) Error & Issue

(4) Data
Verification
(8) Conversion
Process

(9) Data
(7) Error & SIR (5) Business
Legacy Cleansing
Analysis Simulation
Data & Collection
(6) SIRs

Page 7 of 15
7/28/2011
 Proce Description Teams
ss Responsible
(1) Data is extracted from legacy system, transformed according to Conversion
business rules and SAP validation and loaded via SAP migration
programs.
(2) Once unit test is completed for all elements of a conversion Conversion
activity, assembly test will be performed for the activity as a
whole. Assembly test ensures that related work unit programs
properly when assembled into batch streams. This will be
especially important in confirming the data mapping between the
legacy systems extracts and the SAP load programs.
(3) Error and issues occurred during unit and assembly test are Conversion
analysed and report to resolution responsible team according to
the categories of errors and issues.
(4) Converted data is reconciled and is verified for completeness and Conversion
correctness. Emphasis is placed on comparing the data between Verification team,
CCMS and legacy system to ensure that the data is accurately Function teams
represented in CCMS.
(5) Business processes are tested using converted data. Conversion Verification team,
delivers a fully populated client to the Product Test Team who Function team,
subsequently test this data using the configured business Testing team,
processes. Integration team
(6) Any issues related to conversion from data verification and Conversion,
business simulation are documented in a SIR and assigned Verification team,
directly to conversion. Function team,
Testing team,
Integration team
(7) All errors, issues, and SIRs which are assigned to conversion are Conversion
analysed and split into three categories:
• Conversion Process : error is due to a fault in the conversion
process
• Data Cleansing: error has occurred because of bad legacy
data
(8) Conversion Process errors, issues, and SIRs are resolved by the Conversion
Conversion Team and incorporated in the next trial conversion
(9) Data Cleansing SIRs are sent to the data cleansing expert who Data Cleansing
analyses them. If data cleansing is required then these SIRs will
be sent to the Data Cleansing team (Deployment) and resolved

The scope of conversion testing is represented in the above diagram by the

dotted line box. In particular, this includes:

• Validation of the content and format of the of data files extracted from the
various legacy systems;
• Validation of the data reconciliation files associated with each extract;
• Verifying the SAP load programs correctly convert data into the SAP CCMS
system;
• Validation of the reconciliation processes that will be used during the actual
go-live conversions.

The following activities are not within the scope of conversion testing:

• Verifying that converted legacy data supports business processes.

A data verification team will be formed after mock conversion #1. It will consist
of business representatives. The conversion team will provide a conversion
Page 8 of 15
7/28/2011
checklist to the data verification team. The conversion checklist includes
minimum test cases according to each object’s mapping rules. The conversion
team and the data verification team will share responsibility for verifying the
quality of converted data. In particular, if the data verification team finds the
data errors during mock conversion data then the conversion team will fix the
error and re-execute the relevant conversion processes to produce a new data
set in the next mock conversion. The data verification team will then re-execute
the relevant test cycles/scripts against this data set to ensure the error has been
fixed.

5.1 Conversion Testing Approach

The conversion testing approach comprise 3 testing stages:

1. Unit
2. Assembly
3. Mock Conversion.

Since the duration of unit and assembly test stage is relatively short, the level of
documentation required for the completion of each test stage is minimal and
consists of a checklist.

Page 9 of 15
7/28/2011
6 Unit Test
The objective of the Unit Test stage is to ensure that individual components
accurately reflect their functional design specifications. This approach of testing
will be also performed during all mock conversions and is expected to become
less of a focus during the later trials. This is due to the fact that most errors will
be detected and resolved during mock conversion #1 and #2.

The conversion of each CCMS object generally involves:

1. The execution of an extract program in the relevant legacy system to create

a file containing the data to convert into CCMS;
2. The subsequent execution of a transformation program to create the load file
from the extract file;
3. The subsequent execution of a load program (BDC, CATT or Data Migration
Tool) to load the data contained in the load file into CCMS.

The extract and transformation developers are responsible for developing the
extract and transformation programs (based on functional designs developed by
the load developers).

It is the responsibility of each functional area load developer within the

Conversion Team to test the load program of each CCMS object. Each load
developer will test that the load program:

• Successfully loads a known sample of data (supplied by the legacy

developers) into CCMS; and
• Provides accurate reconciliation reports/files that count both the number of
successfully loaded records and failed records. For records that have failed to
load into CCMS the log reports/files should provide an explanation of why the
records in question failed validation.

Each function designer is responsible for unit test result of his object. The
function designer should fill out a check field in the data design document. The
team leader of each functional area will review this documentation for
completeness.

6.1 Deliverables
The deliverables for this test phase are:

• Working Legacy Extract Program and output file

• Working Transformation Program and output file
• Working Load Program and upload result in SAP
• Reconciliation report
• Completed Data Design Document and Functional Design for each
conversion object.

Page 10 of 15
7/28/2011
6.2 Unit Test Entry Criteria
Num Entry Criteria
1. Data Design and Program Functional Design is complete and signed-off
2. Coded Program
3. Test conditions have been identified
4. Related test conditions have been grouped into test cycles
5. Legacy test environment hardware and software is set up
6. Legacy test environment contains data that meets testing requirements
7. SAP development environment is set up
8. Common test data is available (if appropriate)
9. Expected results have been produced

6.3 Unit Test Exit Criteria

Num Exit Criteria
1. Actual results are documented
2. Unit test is complete( Update Data Design Document)
3. All issues / fixes have been resolved

Page 11 of 15
7/28/2011
7 Assembly Test
Once unit testing is complete for all elements of a conversion object, assembly
testing will be performed for related groups of conversion components. The
objective of assembly testing is to ensure that related work units function
properly when assembled into batch strings. This is especially important in
confirming the data mapping between the legacy systems extracts and the SAP
load programs.

Assembly Test

Unit Test Unit Test Unit Test

Stage 1. Extract Stage 2. Transform Stage 3. Load

SAP Platform

Legacy System SAP

Transaction
RAW Data Migration
Legacy data Tool - Business
Legacy Database (Oracle) Partner Object

Business
Partner
SAP CCS
Extract Transfer (Customer Care
Program SAP Input & Service)
Transform Load Files System
Program

Figure 1 : Component & Assembly Testing

Each functional area within the Conversion Team will perform Assembly Testing.
Broadly speaking, this entails:

• Executing in dependency order, the set of extract, transform and load

programs for each conversion object within a particular functional area;

• Verifying that the sample set of data produced by the extract program could
be loaded into CCMS;

• Validating that the reconciliation totals produced by the extract program

match the totals produced by the load program and associated
reconciliation processes;

• Validating the ‘quality’ of data loaded into CCMS (i.e. legacy data has been
mapped and fields defaulted according to the conversion object’s
functional design).

7.1 Deliverables
The deliverables for this test phase are:

• Tested and working legacy-to-CCMS conversion process for each

CCMS object being converted; and
• Completed Assembly Test Checklist (refer Appendix A) for each
CCMS object being converted.

Page 12 of 15
7/28/2011
7.2 Assembly Test Entry Criteria
Num Entry Criteria
1. Unit testing is complete
2. A ‘significant’ sample of legacy data is available for conversion into
CCMS
3. Development CCMS objects have been transported to the relevant SAP
environment (if required)

7.3 Assembly Test Exit Criteria

Num Exit Criteria
1. All ‘High’ and ‘Medium’ category issues / fixes have been resolved
2. Assembly Checklist is complete (refer Appendix A)

Page 13 of 15
7/28/2011
8 Mock Conversion Test
Once all conversion load and extract programs have been component tested and
assembly tested, the end-to-end conversion process for a given phase will be
tested. Following the successful execution of each phase’s conversion
processes, the converted data will then be utilised during product testing to
further confirm the results of the mock conversion.

The execution phase tests and confirms:

• The converted data itself,
• The conversion procedures and steps developed, including any
dependencies,
• The conversion programs (data extraction, formatting and uploading);
• Software configurations;
• Source data;
• Database size estimates and elapsed timings.

8.1 Entry Criteria

Num Entry Criteria
1. Assembly testing is complete

2. Technical testing is complete (if appropriate)

3. Dependency order of conversion objects has been determined
4. Development objects have been transported to the relevant SAP
environment.

8.2 Exit Criteria

Num Exit Criteria
1. Actual results are documented

2. All ‘High’ and ‘Medium’ category issues / fixes have been resolved
3. Product Test have validated ‘correctness’ of data converted into CCMS
4. Results of mock conversion have been collated and distributed to the relevant parties.

8.3 Deliverables
The deliverables for this test phase are:

• Tested end-to-end conversion process; and

• Post-mortem analysis document that discusses the success (or
otherwise) of the conversion execution. This includes process
timings for each object, table space requirements, issues
encountered etc.

Page 14 of 15
7/28/2011
1. Appendix A - Assembly Test Checklist

The following checklist will be used to assembly test conversion objects:

See Assembly Test Checklist.doc

Checklist Ye No
s
All conversion objects ‘upstream’ of the conversion object being tested
have already been loaded into CCMS.

The extract file layout matches the ‘Customer Structure’ that has been
configured in the Data Migration Tool (transaction code EMIGALL).

Migration statistics have been checked and verified.

Record load results due to errors in the extract, transform, and load
program have been logged in Assembly Test-Result Log.xls and Assembly
Test-Error Log.xls

Reconciliation reports accurately reflect the totals associated with

successfully loaded records and failed records.

All issues have been analyzed, documented, and assigned to a person in

charge. – Conversion Issue Log.xls

Any issue and error arising from assembly test is resolved and the related
log files have been updated according to a applied solution.

Page 15 of 15
7/28/2011