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)
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 in this view whether it is ascending order or descending order it doesn’t matter .Only count is
required for Tester.
\NOTE: To check the order of the columns and source column to target column.
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 data types.
\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
) 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
a
No comments:
Post a Comment