Checklist for ETL testing In Data Integration Testing Project

1.
Check for the Connection & Availability of the Testing Schema & all the target t
ables that will beinvolved in testing.
?
2.
Check for the Naming Conventions (e.g.) Check whether the names specified in the
mappingdocument matches with that of the Target Tables created in the Testing S
chema.
?
3.
Check for the Data Types/Size of the Columns that are available in the Target ta
ble to avoidunnecessary rejections due to size constraints
?
4.
Check whether all the Lookup tables are loaded with appropriate data. (e.g.) If
there is a mappinglogic which would be performed based on the look-up table valu
es. Then, if there are no valuesavailable in the lookup table then there is all
the possibility that the transformation won't be doneas per our expectations
?
5.
Try to gain insight of the real-time scenario's that the project deals with (e.g
.) There can beoccasions when data in the columns are swapped between Job Title
& Name prefix code, which canbe pointed out by applying common sense
?
6.
Check for the record counts
?
(
e.g
.) Source File contains - > 100 records, Out of which 80 was moved to Staging ta
ble usingBusiness filters. Once the development team loads the data in the targe
t table. Tester has toconsider 3 scenarios:
?
If the target tables have 80 records, it means no records are rejected
?
If the target table have say 60 records, then 20 records should have been reject
ed andshould be available in reject file/Error Table
?
If the target tables have say 85 records, which is fundamentally incorrect.
?
7.
Validate each & every mapping rule specified in the mapping document, by writing

an SQL queryin the form (Staging table + Mapping Rule) - Target table = No Rows
returned. If rows returned,analyze them & find whether the reason for rejection
is appropriate.
?
8.
Check for the Referential Integrity Constraints, by segregation all the Tables w
ith Primary/ForeignKey constraints & write queries for RI validation.
?
9.
Check for duplicates of Primary Key Columns
?
10.
Validate the Null & Non-null Columns
?
11.
Validate the relator tables that help in maintaining the historical data. (
e.g.)
Check the change inrelationships that takes place during Day1, Day2, Day3, etc.
?
12.
Give due importance to the following conditions:
?
?
Certain records might get rejected even before loading the data into the staging
table.
?
Certain records might get rejected after loading into the staging but before mov
ing to thetarget