

Testing etl processes code#
What changes in requirements and code were applied according to specifications.Questions to Consider When Planning DW/BI Regression Tests We differentiate between two types of changes in the database applications environment:Ĭode Changes: Involves changes made to the code of the database modules (ex., ETL’s)ĭatabase Component Changes: Involves changes made to the definition of the database components or actual data Steps to Develop Priorities for DW/BI Regression TestsĬhange identification is the first step in change impact analysis.
Testing etl processes software#
Test case prioritization involves selecting test cases that reveal maximum defects in the components of the software and assigning high significances to them. In this article, we delve deeper into a process for selecting regression test cases to be run after changes to DW ETL code or data.Ī regression test selection process may be considered effective and efficient when its objective is to select, from the original/current test suite, test cases that can reveal defects in new or modified data, ETL’s, or report generating programs. Testing conducted for the purpose of evaluating whether specific changes to the system has introduced new defects.A repetition of tests intended to show that the software’s overall behavior is unchanged except as required by adjustments to the software or data.Its purpose is to determine if changes have regressed other attributes of data and reports. Testing performed after developing functional improvements or repairs to data and reports.In the first article of this series on DW/BI regression testing, DW/BI regression test planning was defined accordingly:
