in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

The data worehouse ETL Toolkit - Kimpball R.

Kimpball R., Caserta J. The data worehouse ETL Toolkit - John Wiley & Sons, 2005. - 526 p.
SBN: 0-764-57923-1
Download (direct link): thedatawarehouse2005.pdf
Previous << 1 .. 195 196 197 198 199 200 < 201 > 202 203 204 205 206 207 .. 233 >> Next

410 Chapter 10
is not intentionally loaded, be sure to include queries that test data quality in the data warehouse to ensure that data-cleansing transformations are working as expected.
Most likely, issues will be identified during the validation of the test cases. Some of these issues may be bugs discovered in your code, and some may be fresh ideas triggered by the users' exposure to their data in a format that is new to them. It's not uncommon to receive user requests for new requirements during this phase that may need to be added as enhancements. Be careful: Data is not the only thing being tested here. Managing the initial ETL processes is a task in itself; add on bug fixes, additional requests, and ever-changing business rules and the process can become completely unmanageable. In-depth change management techniques are detailed in the "Managing Scope" section of this chapter.
A sample test case template is illustrated in Figure 10.6. It is intended to capture the requirements you are testing; the detailed steps to perform the test; the expected results; and the status of the test: pass or fail. Sample test cases are given to display the level of detail you should capture. This template should be used for all three phases of the testing process.
ETL Deployment
Next comes the moment you have all been waiting for: ETL deployment. To make the migration to production as seamless as possible, be sure to create production support documents. These documents should include following information:
The final lineage report
Procedures for running (and restarting) the incremental load process
Details about the automated load schedule
It is important to create and deliver documented failure recovery procedures. Should a load process fail, users could have access to bad data or data that is not up to date. A plan must be in place to avoid this before the production environment is unleashed to users. Document and test your failure recovery procedures, so that when failures occur, you can quickly recover data and make it available for your users in a timely manner.
Work with the DBA team to create a stable production environment. Load your historical data and kick off the ETL incremental load processes with your production scheduler. Be sure to run tests on data in production (historical and incremental) to ensure data was successfully loaded.
Test Case Template
No. Test Subject Step Test Detail Pass Expected Results Comments
Dependencies /Fail
1 Validate that new products entered A now product and detail will be entered and saved in the Test results are Product ID 89076 and it's detail are
in Ihe transaction system are source system. The incremental load will run. The QA dependent on a displayed in the warehouse exactly as
successfully being loaded into the instance of the warehouse will be queried and results successful they were entered in the transaction
warehouse via the incremental load. will be validated. incremental load. system.
a Log on to the QA instance of your source system.
b Add a now product id of 89076 and detail of your choice to
the transaction system (noting values you enter in the
expected results field for test validation).
Save the new product record.
d Contact the ETL Manger/DBA to request that the
Previous << 1 .. 195 196 197 198 199 200 < 201 > 202 203 204 205 206 207 .. 233 >> Next