Validating your dw


Depending on the solution of course there could be other important items to unit test, but these are the high risk areas.Ideally, Unit Testing can be automated since this form of testing is done repeatedly throughout the course of a project.System Integration Testing is completely dependent on successfully Unit Testing your data warehousing solution first!System Integration Testing should accomplish two main objectives.Data that should be validated includes dimension member completeness, base measure accuracy, and business calculations.If the data ties between the data warehouse and the operational report then the data is valid (unless of course the original report is flawed).Our testing team utilizes a data-centric testing approach to ensure that valid and correct data are in the system and these data fulfill business requirements.As with any IT initiative, proper quality assurance processes can make or break a project.



Unit Testing is entirely the responsibility of the developer, and MUST be done during development.Once a number of reports have been validated, then likely you can rest assured that the data within the warehouse is correct.It is imperative to note that data validation should be performed by a business representative!It is critical that data warehousing projects do everything in their power to mitigate this risk.

This article is intended to give an overview of some of the key concepts of quality assurance in data warehousing and business intelligence projects to ensure you don't have to struggle with quality issues on your project.

First you must perform system build testing to ensure that you can successfully build and deploy into your system integration testing environment.