ADDRESS
-
Address: #12, 3rd Floor
Dental College Main Road,
Munekolalu, Marathahalli,
Bangalore - 560037
Karnataka. - Email: info@krninformatix.com
- Website: www.krninformatix.com
OUR COMPANY
GALLERY
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
ETL testing is done before data is moved into a production data warehouse system. It is sometimes also called as table balancing or production reconciliation. It is different from database testing in terms of its scope and the steps to be taken to complete this.
The main objective of ETL testing is to identify and mitigate data defects and general errors that occur prior to processing of data for analytical reporting.
ETL performance tuning is used to ensure if an ETL system can handle an expected load of multiple users and transactions. Performance tuning typically involves server-side workload on the ETL system. It is used to test the server response in multiuser environment and to find bottlenecks. These can be found in source and target systems, mapping of systems, configuration like session management properties, etc.
The goal of ETL testing is to achieve credible data. Data credibility can be attained by making the testing cycle more effective.
A comprehensive test strategy is the setting up of an effective test cycle. The testing strategy should cover test planning for each stage of ETL process, every time the data moves and state the responsibilities of each stakeholder, e.g., business analysts, infrastructure team, QA team, DBA’s, Developers and Business Users.
Checking data quality during ETL testing involves performing quality checks on data that is loaded in the target system. It includes the following tests
Number checkThe Number format should be same across the target system. For example, in the source system, the format of numbering the columns is x.30, but if the target is only 30, then it has to load not prefixing x. in target column number.
Date CheckThe Date format should be consistent in both the source and the target systems. For example, it should be same across all the records. The Standard format is: yyyy-mm-dd.
Precision CheckPrecision value should display as expected in the target table. For example, in the source table, the value is 15.2323422, but in the target table, it should display as 15.23 or round of 15.
Data CheckIt involves checking the data as per the business requirement. The records that don’t meet certain criteria should be filtered out.
Example − Only those records whose date_id >=2015 and Account_Id != ‘001’ should load in the target table.
Null CheckSome columns should have Null as per the requirement and possible values for that field.
Example − Termination Date column should display Null unless and until its Active status Column is “T” or “Deceased”.
Other ChecksCommon checks like From_Date should not greater than To_Date can be done.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |