Display mode: ![]()
Rewordifying level: ![]()
Highlighting mode: ![]()
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
Insert a record with a modified attribute. Verify that a new Satellite record is created with the updated data while the old record remains (historical tracking). Testing Data Vault-Based Data Warehouse
Data Vault excels at "insert-only" logic. Your tests should mirror this.
The Business Vault contains transformed data (e.g., calculated fields or cleaned addresses). Check that Satellites are correctly attached to their
All source data (even if "dirty") must be stored in the Raw Vault.
Validate that business rules applied in the Business Vault match the requirements. Data Vault excels at "insert-only" logic
Run row counts and sum-checks between the Source Landing Zone and the Raw Vault.