You are on page 1of 20

ETL Test Case

<Project Name>
Version - <Version Number>
<Month Year>

www.brillio.com

TABLE OF CONTENTS
1

INFORMATICA ETL NAMING CONVENTIONS.....................................................3


1.1

Repository Object.........................................................................................3

DOCUMENT PURPOSE..................................................................................4

PROJECT OVERVIEW...................................................................................5

IN SCOPE TESTING....................................................................................6

OUT OF SCOPE TESTING.............................................................................7

SOURCE TO STAGING..................................................................................8
6.1

Source Details.............................................................................................8

6.2

Staging Details............................................................................................8

6.3

Source to Stage Test Cases...........................................................................8

6.4

Stage to Target Test Cases............................................................................9


6.4.1
6.4.2

Staging Details..............................................................................................................9
Target Details..............................................................................................................10

STAGE TO TARGET TEST CASES...................................................................11

HISTORY TEST CASES...............................................................................12

8.1

History Table Details...................................................................................12

8.2

History Test Cases......................................................................................12

REVISION HISTORY.................................................................................14

ETL Test Case

Page 2 of 20

1 Informatica ETL Naming Conventions


These standards should be followed on all new development and rework of existing
development objects. Any existing objects (i.e. Production) should only be modified if the
opportunity presents itself (i.e. changes to mappings, workflows).

ETL Test Case

Page 3 of 20

1.1 Repository Object


Repository Objects

Naming Convention

Mapping Name

m_<meaningful name> (Examples: m_RefreshSIQREPL,


m_PERSON)

Session Name

s_<mapping name> (Example: s_m_PERSON)

Folder Name

Folder names for new users will be their department followed


by their username. Existing users folder names are typically
their group followed by their user name. Folder Names may
also be based on project, subject area, and promotion group.

Log Files

<session_name>.log OR <workflow_name>.log

Bad Files

<session_name>.bad

Source-name & Target-name

Do not make any distinction here - Informatica color-codes the


sources and targets, so it's easy to tell. We do try to prefix
these with a folder name, so that when shortcuts or global
objects are created we can tell where they originally reside.

Workflow Names

w_<mapping name>
Table 1: Naming Convention

ETL Test Case

Page 4 of 20

2 Document Purpose
<This section shall briefly explain the purpose of the document>.
This document shall list all test cases that were conducted during unit testing by the
developer [or] quality assurance testing by the QA team. The goal is to document all the
test case scenarios for ETL source to stage, stage to target, history and any other data load
activities. The test cases may be grouped into in to the same document or in an excel
spread sheet and the corresponding link can be provided in the section of this document
whichever is easy to maintain and track. Please extend the sections as needed by copying
the single test case templates or add sections by adding further sheets. The description of
how to fill in test case templates can be found within comments in the corresponding cells.
This document needs to be delivered during Unit Testing, QA testing, Pre-Prod Testing/ UAT
testing.

ETL Test Case

Page 5 of 20

3 Project Overview
<Provide the description of the project purpose and objective
Provide Project Drivers which describe the business needs and technical needs that motivate
the project.
Example:

Client Analytics Private Banking currently performs that analysis & reporting of the
data which is available in different database on Sybase. This poses a potential timing
issue for making the data available to the Business Users since lots of manual
processing needs to be done to consolidate the data at one place

Client Analytics Private Banking needs the data to be consolidated at the monthly
level instead of daily level

State once the project is completed, what benefits or outcomes it brings to the
organization or the departments>

ETL Test Case

Page 6 of 20

4 In Scope Testing
<This is the testing scope that needs to be listed which in turn reflects the requirements of
the project>.

ETL Test Case

Page 7 of 20

5 Out of Scope Testing


<Indicate and list the testing exclusions within the project scope. Indicate those that are
completely out of this project and those that are not part of Brillio but delivered by a
different party within Customer organization or outside>.

ETL Test Case

Page 8 of 20

6 Source to Staging

ETL Test Case

Page 9 of 20

6.1 Source Details


<Fill in the details of the sources in the below table. Refer the example listed below>:
Sl.
No

Data Mart
<Name/Type of
Database
Used>

Tables Used

Description

<List of all the source


tables in the database>

<Business Description on
the type of data available at
the source>

Data Model
<Attach the
source data
model>

Table 2: Source Details

ETL Test Case

Page 10 of 20

6.2 Staging Details


<Fill in the details of the sources in the below table. Refer the example listed below>:
Sl.
No

Data Mart
<Name/Type of
Database
Used>

Tables Used

Description

<List of all the source


tables in the database>

<Business Description on
the type of data available at
the source>

Data Model
<Attach the
source data
model>

Table 3: Staging Details

ETL Test Case

Page 11 of 20

6.3 Source to Stage Test Cases


Test Case

<Name of
Test Case>

ID: <Test Case


ID>
Network
dependen
t:

Severit
y:

1a Fatal

Date:
01.01.2007

Yes

Test
purpose

Test
Criteria

Test Step
N
o

Descripti
on

Step Result
Description

Test Steps
Pass

Fail

N/
A

Waiver

Overall
Result
Observed
Results in
case of
failure
End User
Impact /
Waiver
descriptio
n
Comments

Table 4: Source to Stage Test Cases

ETL Test Case

Page 12 of 20

6.4 Stage to Target Test Cases

ETL Test Case

Page 13 of 20

6.4.1
S.
No

Staging Details
Data Mart

Tables used

Description

Data
Model

<Name/Type of
Database Used>

<List of all the source tables


in the database>

<Business Description on
the type of data available at
the source>

<Attach
the source
data
model>

Table 5: Staging Details

ETL Test Case

Page 14 of 20

6.4.2

Target Details

<Fill in the details of the sources in the below table. Refer the example listed below>
S.
No

Data Mart

Tables used

Description

Data
Model

<Name/Type of
Database Used>

<List of all the source tables


in the database>

<Business Description on
the type of data available at
the source>

<Attach
the source
data
model>

Table 6: Target Details

ETL Test Case

Page 15 of 20

7 Stage to Target Test Cases


Table

Test Case

<Name
of Test
Case>

7:

Severity
:

ID: <Test Case ID>

1a Fatal

Date:
01.01.2007

Stage
to
Target

Network dependent:

Test

Yes

Cases

Test
purpose
Test
Step

Test
Criteria

No.

Step Result
Descripti
on

Test Steps

Description

Pass

Fail

N/A

Wai
ver

1
2
3

Overall
Result
Observed
Results in
case of
failure
End User
Impact /
Waiver
descriptio
n
Comment
s

ETL Test Case

Page 16 of 20

8 History Test Cases

ETL Test Case

Page 17 of 20

8.1 History Table Details


<Fill in the details of the sources in the below table. Refer the example listed below>:
S. No

Data Mart

Tables used

Description

Data
Model

<Name/Type
of Database
Used>

<List of all the source tables


in the database>

<Business Description on
the type of data available at
the source>

<Attach the
source data
model>

Table 8: History Table Details

ETL Test Case

Page 18 of 20

8.2 History Test Cases

Test Case

<Name of
Test Case>

ID: <Test
Case ID>

Severit
y:

Network
dependent:

1a Fatal

Date:
01.01.2007

Table
9:

Yes

Test purpose

Test Step
No
.
Test Criteria

Descripti
on

Step Result
Description

Test Steps
Pass

Fail

N/A

Waive
r

1
2
3

Overall
Result
Observed
Results in
case of
failure
End User
Impact /
Waiver
description

Comments
History Test Cases

ETL Test Case

Page 19 of 20

9 Revision History
Sl.
No

Version
No

Change
Description

Authored By

Reviewed
By

ETL Test Case

Approved
By

Date

Page 20 of 20