Practice

Etl development life cycle

<<<
>>>
Hi,
To learn etl testing, sql is mandatory and should have knowledge in unix. Any way I will guide you in last section.
ETL Testing:ETL testing is similar to manual testing which we have to do manually with human interaction.
Once after inserting or updating the data into datamart by etl developer then we will test that datamart before loading into the
centralized dataware house. This test is called ETL Testing.
Etl development life cycle:
REQUIREMENT ANLAYSIS
HIGH LEVEL DESIGN
LOW LEVEL DESIGN
DEVELOPMENT
SIT(system integration testing)
REVIEW
TESTING--------->>Etl Testing life Cycle
UAT(user acceptance testing)
PRODUCTION

Test Plan for banking project

Introduction

Banking

Back Ground

Informatica, oracle 10g

Test Items

Fixed Deposit, Withdrawls.

Features to be
tested
Approach

Like password.non secure field to tested

Testing levels

Sanity, smoke

Types of Etl testing

Features Pass &

How many tc pass, tc fail
Fail criteria
Suspension criteria Company will make some rules

Test Environment

Staging server, client server(Alpha), production

server(Beta), live server

Test deliverables

Test cases, bug logging, test procedure

Scheduled tasks

Its a time table of the project or module.

Staff & training

Required persons

Risk and mitigation General Holidays, seek leaves

Sign off

Higher authority

Features not to be
tested

Secure fiels,tables

ETL TESTING LIFE CYCLE:-

Types of ETL Testing :1)

Constraint Testing:
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)
b)
c)
d)
e)
f)
g)
2)

3)

4)

NOT NULL
UNIQUE
Primary Key
Foreign key
Check
Default
NULL
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 doesnt matter .Only count is required for Tester.
Due to lack of time a tester can follow this type of Testing.
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.
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
4

5)

MAX
10

RANGE
6

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)

1)
2)
3)

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:
There are no mistakes in Primary Key or no Primary Key is allotted then the duplicates may arise.
Sometimes, a developer can do mistakes while transferring the data from source to target at that time duplicates may arise.
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)

9)

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.

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:
Integration testing: After the completion of programming process . Developer can integrate the modules there are 3 models
a) Top Down
b) Bottom Up
c) Hybrid

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