ETL Interface Test Summary

Just finished a project to contact the ETL interface, while still warm to do a summary.

ETL Interface Functional Test Point summary:
1, the data volume check: The target table and the source table data volume is consistent
2, the field is correct: pull the source table field is required fields (there will be a typo paragraph case)
3, the field value conversion correctness: If the date or numeric field is pulled to the target table if the conversion needs to be done, if the conversion needs to be done, the conversion is correct, and whether it conforms to the business logic of the target table. (such as date, the source table is: 2016-
01-01, and after pulling to the target table is: 2016-01-01 00:00:00, if the field in the late need to compare, it is necessary to consider whether 2016-01-01 00:00:00 in the same day. ）
4, Field range validity check: The source table fields value is the maximum value, pull to the target table is full value
5, Field null: Source The field value is empty, pull to the target table is empty (such as the target table that the field cannot be empty, then the field is empty record row will not be able to enter the target table, whether it meets the business logic requirements)
6, check whether there is garbled:
7. Full update: Check the source table for new, modified, deleted records, after repeated pull, the target table is consistent with the last source table data.
8. Incremental update: When checking the source table for new data, whether the target table pulls only the new records in the source table after repeating the pull
9. Check whether data from the specified date is pulled: Check that data outside the specified date exists in the source table and is not pulled to the target table.

ETL performance aspects: The main test data volume, in the source table preparation data, test pull large data amount of time and monitoring database server performance indicators.

ETL Interface Test Summary