March 27, 2006 at 11:15 pm
Hi all. I am new to the forum and to Data Warehousing. I am currently into Quality Assurance testing, read a lot on data warehousing and databases with reference tables which I am currently testing. Can anyone please tell me what to test for in a database and where does defects mostly lies in the database developed by the developers.
Tope
March 29, 2006 at 7:13 am
It's a little difficult to do QA on a data warehouse without knowing the data. You will need to know the business rules for the ETL process and have access to both the raw data and the warehouse data. Concentrate on proper changes as expected. Does the table have type1, type2, or type3 changes? Are they properly applied? Are there duplicates in the reference table due to an unexpected change in the downstream system? Again, the key here is to know the data.
After getting familiar with the data, I would mock up the source data for one of the reference tables and alter a field that should cause an exception.
Do the same thing for type1,type2, or type3 changes.
It can be exhausting to validate the data, but keep at it.
Cliff
March 30, 2006 at 8:38 am
Thanks Cliff. I really appreciate the response.
1. What do you mean by Type1, Type2 or Type3 changes?. I am familiar with the data in the Source Tables and like you said, it can be exhausting. I have currently found defects in one of the tables with duplicates records and was just curious that 2. is it just data integrity that i should test for ? and again, there are no business rules at all for this project and all my testing is based on what the developers tell me and the infomation gathered from people and meetings. 3. Are rejects accepted at the target tables 'cos the source table is null and even though the field is not null in the target table. 4. When are rejects acceptable and how does email notification and error handling work in ETL.
Tope
Tope
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply