Вы находитесь на странице: 1из 7

GE Medical Systems SWAP

Proprietary

Unit Test Plan

(m_swp_phoenix)
Version 1

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

Contents

1. Introduction......................................................................................................................3
2. Requirements...................................................................................................................3
3. Plan..................................................................................................................................3
4. Unit Testing......................................................................................................................3
4.1 Unit Testing of individual mappings:.........................................................................3
4.2 Testing of mappings:..................................................................................................4
5. Appendix: A.....................................................................................................................4

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

1.Introduction
This document describes testing the quality of the data loaded to the data mart. The testing should
be done during the data warehouse building process at stage below.

a) Design Data Mart (DM) depending on the user requirements.


b) Define Informatica mappings to DM
c) Load data to DM

2.Requirements

The following documents and resources should be available to do the testing:

 Approved guidelines & standards for developing mappings, see the “GEDS Informatica
Mapping Guidelines”.
 A reviewer or peer review team from the development team

3.Plan
The testing should be done in the following ways given below:

 Unit testing
The reviewer should perform the testing, whenever the developer completes the development
of report or a mapping.
 Integration testing
This testing should be done once the logical step reached in development of reports and
mappings.

The errors and remarks should be recorded in the respective form given in the appendix to
process on it.

4.Unit Testing
The data warehouse development team should perform the unit testing. The unit testing should
include following areas:

4.1Unit Testing of individual mappings:


The testing of mappings can cover following areas:
 Naming convention of each mappings
 Check for brief description or documentation of the logic and input & outputs
 Check for Inputs & Outputs by running the output to text file or test table.
 Any computation / Aggregation should be cross-checked
 Primary key and sequence generation should be cross checked
 Check for session name and appropriate connections.
 Check appropriate number of records created.

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

 Any lookup connections should be to $source, $target or appropriate connection and have
caching set correctly.

Record the findings of the testing into the template in Appendix A.

4.2Testing of mappings:

The integration testing of mappings should be done to avoid the problems in connection, storage
problems in the database, any memory problem due to load and to check for the consistency of
the mappings

 Schedule and run the mappings into the database (to check possible connection problems and
storage problems), in this case we can use development environment databases.
 Check for incremental mappings that just new records are added and that other detail records
are updated appropriately.
 Test all other points mentioned in the unit testing of mappings

The findings are recorded below.

5.Appendix: A
Sourcing - DW: Informatica Mapping Test Plan.
1)
Mapping Name: m_swp_phoenix Date: Jun 7 , 2004
Description: Loads the data from the
geglb_warehouse_d,
Om_order_detail_f,
PART ,
SWP_CARES_DISPATC
HES_S
Into
DISPATCH_FLS_STG1
Plan Type: Unit Stage: M1 Phase
Plan prepared by: Kuruvella Reviewed By:

Sl To Check Result Remarks


#
1 Name
2 Description
3 Output Data
4 Sequence Generator correct
5 Source and Target links
6 Aggregations/Calculation
7 Session Name and Connection
8 Lookup Connections
9 Number of Rows Added
10 Old details Updated (where appropriate)

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

Expected Load Test:


Source Name: Geglb_warehouse_d (Tera data ), om_order_detail_f(Tera Data),
PART(oracle), swp_cares_dispatches_s
Target Table Name: DISPATCH_FLS_STG1
Source Record Key Checked:

Source Field Name Value Target Attribute Expected Remarks


Value (OK/Issue)
1)DISPATCH_FLS_STG_IDE
NTIFIER
DISPATCH_NO 2)PART_ORDER_NUMBER
PART_LOCAL_ID 3)PART_ID
4)CUSTOMER_CODE
NAME(lkp_field_personnel) 5)EMPLOYEE_NAME
6)SERV_REP_NUM
PART_DESCRIPTION 7)DESCRIPTION
SYSTEM_ID 8)SYSTEM_ID
AREA_CODE 9)AREA_CODE
MMICV_VALUE 10)COST_PRICE
PSI_CODE 11)PSI_CODE
USN 12)USN
13)CUSTOMER_ID
ITEM_TYPE 14)PART_TYPE
- 15)PART_WEIGHT
- 16)COUNTRY_OF_ORIGIN
- 17)EX_FROZEN_LP
DISPATCH_NO 18)DISPATCH_NUMBER
M_SWP_ M_SWP_PHONE
PHONEIX 19)PSOTING_AGENT IX
PHOENIX 20)DATA_ORIGIN PHOENIX
21)WAREHOUSE_POSTING SYSDATE
_TIMESTAMP
- 22)DAY_PARTITION_KEY
INSTALL_DATE 23)INSTALL_DATE
WARRANTY_DATE 24)WARRANTY_EXP_DATE
DISPATCH_ LOCATION 25)CUSTOMER_LOCATION
26)ROUTING_NUMBER
N 27)REPAIR_FLAG N

Light Blue:-Part(oracle)
Light Orange:-swp_cares_dispatches_s
Green:-Look up Geglb_customer_d

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

Lime:-Look up lkp_routing_number
Dark Blue:-generated by Sequence Generator.
Dark Red:-Assigned in Expression
Black:-lkp_customer_d
Red-:Not populated in Target.

Source Queries:-

1)

Select a.customer_key, a.inventory_item_id,


Lpad (to_char (ltrim (rtrim (a.po_number))), 10,'0') as po_number,
a.shipped_quantity, a.system_items_identifier, a.order_number,
(Ltrim (rtrim (system_items_key)) as system_items_key
From om_order_detail_f a, geglb_warehouse_d b
Where a.warehouse_key = b.warehouse_key

2)

Select a.part_local_id, a.part_description, a.mmicv_value, a.item_type,


b.system_items_key from part a , om_order_detail_f b
Where a.part_local_id = b.system_items_key.

3)

Select a.dispatch_loc, a.system_id, a.area_code, a.install_date, a.warranty_date,


a.psi_code, a.usn, a.dispatch_no, a.dispatch_indentifier
From swp_cares_dispatches_s a, om_order_detail_f b
Where a.dispatch_no = b.po_number

Lkp_Routing_number Query:-

Select routing_number from swp_due_in_parts_s a, part b


Where a.part_id = b.part_local_id

4) Lkp_customer_d query

Select a.account_name from geglb_customer_d a, om_order_detail_f b


Where a.customer_key = b.custome_key

9235903.doc. Author: SWaP Team

GE Confidential
GE Medical Systems SWAP
Proprietary

9235903.doc. Author: SWaP Team

GE Confidential

Вам также может понравиться