Check that Satellites are correctly attached to their parent Hub/Link and that the Hash_Diff (used for change detection) is calculating correctly. 2. Load Pattern Testing (Technical ETL)
Verify that the hashing algorithm (MD5 or SHA-1) produces identical keys for the same business keys across different source systems. 4. Point-in-Time (PIT) & Bridge Table Validation
Run the same load twice. The system should recognize the data exists and result in zero new inserts. Testing Data Vault-Based Data Warehouse
All source data (even if "dirty") must be stored in the Raw Vault.
Query a PIT table for a specific date in the past. Verify it correctly identifies the "active" Satellite records for that timestamp. 5. Business Vault & Logic Testing Check that Satellites are correctly attached to their
Validate that business rules applied in the Business Vault match the requirements.
Ensure "Zero Keys" or "Ghost Records" exist in Hubs to handle late-arriving data or missing lookups without breaking the model. 3. Data Integrity & Reconciliation This ensures that "what went in is what came out." All source data (even if "dirty") must be
Data Vault should allow for high-concurrency loading.