Scribd
Upload
174 views4 pages

ETL Testing Concepts

ETL testing involves validating data as it moves from a source system to a data warehouse. The ETL process extracts data from sources like databases or files, transforms it to match the data warehouse schema, and loads it into the warehouse. Common types of ETL testing include validating data constraints, comparing source and target counts and values, checking for duplicates, and ensuring historical data remains intact during incremental loads. ETL tools help automate the extract, transform, and load processes.

Uploaded by

poornananda sai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
174 views4 pages

ETL Testing Concepts

ETL testing involves validating data as it moves from a source system to a data warehouse. The ETL process extracts data from sources like databases or files, transforms it to match the data warehouse schema, and loads it into the warehouse. Common types of ETL testing include validating data constraints, comparing source and target counts and values, checking for duplicates, and ensuring historical data remains intact during incremental loads. ETL tools help automate the extract, transform, and load processes.

Uploaded by

poornananda sai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

What is ETL Testing.

ETL stands for Extract-Transform-Load and it is a process of how data is loaded from the source
system to the data warehouse. Data is extracted from an OLTP database, transformed to match the
data warehouse schema and loaded into the data warehouse database. Many data warehouses also
incorporate data from non-OLTP systems such as text files, legacy systems and spreadsheets.

ETL Process:

1. Extract

 Extract relevant data from source

2. Transform

 Transform data to DW (Data Warehouse) format


 Build keys - A key is one or more data attributes that uniquely identify an entity.
Various types of keys are primary key, alternate key, foreign key, composite key,
surrogate key. The datawarehouse owns these keys and never allows any other
entity to assign them.
 Cleansing of data :After the data is extracted, it will move into the next phase, of
cleaning and conforming of data. Cleaning does the omission in the data as well
as identifying and fixing the errors. Conforming means resolving the conflicts
between those data’s that is incompatible, so that they can be used in an
enterprise data warehouse. In addition to these, this system creates meta-data
that is used to diagnose source system problems and improves data quality.

3. Load

 Load data into DW ( Data Warehouse)


 Build aggregates - Creating an aggregate is summarizing and storing data which is
available in fact table in order to improve the performance of end-user queries.
3. ETL Testing Process

Types of ETL Testing :-

1) Constraint Testing(Attribute Check):


In the phase of constraint testing, the test engineers identifies whether the data is mapped from
source to target or not.
The Test Engineer follows the below scenarios in ETL Testing process.
a) NOT NULL
b) UNIQUE
c) Primary Key
d) Foreign key
e) Check
f) Default
g) NULL
2) Source to Target Count Testing:
In the Source to Target data is matched or not. A Tester can check in this view whether it is
ascending order or descending order it doesn’t matter .Only count is required for Tester.
Due to lack of time a tester can follow this type of Testing.

3) Source to Target Data Validation Testing:


In this Testing, a tester can validate the each and every point of the source to target data.
Most of the financial projects, a tester can identify the decimal factors.

4) Threshold/Data Integrated Testing:


In this Testing, the Ranges of the data, A test Engineer can usually identifies the population
calculation and share marketing and business finance analysis (quarterly, halferly, Yearly)

MIN MAX RANGE


4 10 6

5) Field to Field Testing:


In the field to field testing, a test engineer can identify that how much space is occupied in the
database. The data is integrated in the table cum datatypes.

NOTE: To check the order of the columns and source column to target column.

6) Duplicate Check Testing:


In this phase of ETL Testing, a Tester can face duplicate value very frequently so, at that time the
tester follows database queries why because huge amount of data is present in source and Target
tables.
Select ENO, ENAME, SAL, COUNT (*) FROM EMP GROUP BY ENO, ENAME, SAL HAVING COUNT (*)
>1;

Note:
1) There are no mistakes in Primary Key or no Primary Key is allotted then the duplicates may arise.
2) Sometimes, a developer can do mistakes while transferring the data from source to target at that
time duplicates may arise.
3) Due to Environment Mistakes also duplicates arise (Due to improper plugins in the tool).

7) Error/Exception Logical Testing:


1) Delimiter is available in Valid Tables
2) Delimiter is not available in invalid tables(Exception Tables)

8) Incremental and Historical Process Testing:


In the Incremental data, the historical data is not corrupted. When the historical data is corrupted
then this is the condition where bugs raise.

9) Control Columns and Defect Values Testing:


This is introduced by IBM
10) Navigation Testing:
Navigation Testing is the End user point of view testing. An end user cannot follow the friendly of the
application that navigation is called as bad or poor Navigation.
At the time of Testing, A tester can identify this type of navigation scenarios to avoid
unnecessary navigation.

11) Initialization testing:


A combination of hardware and software installed in platform is called the Initialization Testing

12) Transformation Testing:


At the time of mapping from source table to target table, Transformation is not in mapping
condition, then the Test Engineer raises bugs.

13) Regression Testing:


Code modification to fix a bug or to implement a new functionality which makes us to to find errors.
These introduced errors are called regression . Identifying for regression effect is called regression
testing.

14) Retesting:
Re executing the failed test cases after fixing the bug.

15) System Integration Testing:


Types of Etl Bugs

1. User interface bugs/cosmetic bugs:-


Related to GUI of application
Navigation, spelling mistakes, font style, font size, colors, alignment.

2. BVA Related bug:-


Minimum and maximum values

3. ECP Related bug:-


Valid and invalid type

4. Input/output bugs:-
Valid values not accepted
Invalid values accepted

5. Calculation bugs:-
Mathematical errors
Final output is wrong

6. Load condition bugs:-


Does not allows multiple users
Does not allows customer expected load

7. Race condition bugs:-


System crash & hang
System cannot run client plat forms

8. Version control bugs:-


No logo matching
No version information available
This occurs usually in regression testing

9. H/W bugs:-
Device is not responding to the application

10. Source bugs:-


Mistakes in help documents

ETL Tools:
Informatica, Data Stage, AbInitio, COGNOS, IBM DB2

ETL interview questions:

You might also like