Unit testing checklist
A checklist
will aid database programmers to systematically test their code
before formal QA testing.
- Check the mapping of fields that support data staging and in data marts.
- Check for duplication of values generated using sequence generators.
- Check the correctness of surrogate keys that uniquely identify rows of data.
- Check for data-type constraints of the fields present in staging and core levels.
- Check the data loading status and error messages after ETLs (extracts, transformations, loads).
- Look for string columns that are incorrectly left or right trimmed.
- Make sure all tables and specified fields were loaded from source to staging.
- Verify that not-null fields were populated.
- Verify that no data truncation occurred in each field.
- Make sure data types and formats are as specified during database design.
- Make sure there are no duplicate records in target tables.
- Make sure data transformations are correctly based on business rules.
- Verify that numeric fields are populated precisely.
- Make sure every ETL session completed with only planned exceptions.
- Verify all data cleansing, transformation, and error and exception handling.
- Verify stored procedure calculations and data mappings.
