Professional Documents
Culture Documents
<Project Name>
Version - <Version Number>
<Month Year>
www.brillio.com
TABLE OF CONTENTS
1
Repository Object.........................................................................................3
DOCUMENT PURPOSE..................................................................................4
PROJECT OVERVIEW...................................................................................5
IN SCOPE TESTING....................................................................................6
SOURCE TO STAGING..................................................................................8
6.1
Source Details.............................................................................................8
6.2
Staging Details............................................................................................8
6.3
6.4
Staging Details..............................................................................................................9
Target Details..............................................................................................................10
8.1
8.2
REVISION HISTORY.................................................................................14
Page 2 of 20
Page 3 of 20
Naming Convention
Mapping Name
Session Name
Folder Name
Log Files
<session_name>.log OR <workflow_name>.log
Bad Files
<session_name>.bad
Workflow Names
w_<mapping name>
Table 1: Naming Convention
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.
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>
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>.
Page 7 of 20
Page 8 of 20
6 Source to Staging
Page 9 of 20
Data Mart
<Name/Type of
Database
Used>
Tables Used
Description
<Business Description on
the type of data available at
the source>
Data Model
<Attach the
source data
model>
Page 10 of 20
Data Mart
<Name/Type of
Database
Used>
Tables Used
Description
<Business Description on
the type of data available at
the source>
Data Model
<Attach the
source data
model>
Page 11 of 20
<Name of
Test Case>
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
Page 12 of 20
Page 13 of 20
6.4.1
S.
No
Staging Details
Data Mart
Tables used
Description
Data
Model
<Name/Type of
Database Used>
<Business Description on
the type of data available at
the source>
<Attach
the source
data
model>
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>
<Business Description on
the type of data available at
the source>
<Attach
the source
data
model>
Page 15 of 20
Test Case
<Name
of Test
Case>
7:
Severity
:
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
Page 16 of 20
Page 17 of 20
Data Mart
Tables used
Description
Data
Model
<Name/Type
of Database
Used>
<Business Description on
the type of data available at
the source>
<Attach the
source data
model>
Page 18 of 20
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
Page 19 of 20
9 Revision History
Sl.
No
Version
No
Change
Description
Authored By
Reviewed
By
Approved
By
Date
Page 20 of 20