SRT Checklist for ETL Testing

Introduction

System Readiness Testing (SRT) is done for the end-to-end testing of deliverables for Data Migration. It will be performed in a Production like environment to verify that Data Migration components meet the requirements. The results of execution will be validated against the test cases identified earlier. SRT will focus on validating and reconciling the data loaded from source system to target system.

The checklist provided in the document could act as a base and cover important points of the preparation stage, the execution stage and the closure stage of SRT.

Checklist

Sr#	Universe area	Checklist	Checked Yes/No/NA	Remarks (if any)
1	Preparation
	1.1	Source Tables(Source files)
	1.1.1	All source files are available in the Source file directory with proper permission.
	1.1.2	All the source tables or source files are loaded in desired location (Eg: Extract tables) before starting the execution.
	1.1.3	In case of source tables, the file is loaded correctly into the table.
	1.1.4	For flat files used as source, the start and end position of the extract fields are as expected.
	1.1.5	The pre check queries that have been created based on the extraction issues in the previous testing cycle have been executed on the new extract files.
	1.2	Documents
	1.2.1	Are the below set of documents ready before starting with the testing. i)Test Case Document ii)Test Strategy iii)Execution Day Wise Plan
	1.3	Lookup Table Setup
	1.3.1	The source tables used as lookups should be loaded before starting with the execution.
	1.3.2	The lookup table setup should be done by loading the latest lookup file into the database.
	1.4	Code Migration
	1.4.1	Code migration needs to done after any pending fixes and testing and review.
	1.5	OutputFileDirectory
	1.5.1	The output file directory is cleared of all the target formats before the execution starts
2	Execution
	2.1	Are all the mappings getting triggered based on the sequence in which they need to run
	2.2	Are all the target files created from a particular mapping.
	2.3	In case two flows are having the same target, the flow which creates the file should run first followed by the flow which appends the target.
	2.4	Are all the output files in the expected structure with number of fields, data values and delimiter.(This point is applicable only if the output generated is file)
	2.5	Audit table is getting updated after completion of each session(audit table is maintained to keep track of number of records processed)
	2.6	Archiving of target formats is done after completion of each session
	2.7	Audit report is verified for number of processed and error records.
	2.8	The input count from the transformation audit count is verified with the Extraction control files
	2.9	If there are records in the error report, check if all the issues present are valid.
	2.10	In case a code fix is done, the change is done in all the impacted mappings.
	2.11	Are the reconciliation reports created out of Transformation are validated with the Extraction reports. (Reports are used to verify if the collection of data is loaded correctly. Validation can be done only if the grouping of data is at a similar level)
	2.12	Communication of the status of execution of flows is sent to the entire team through daily and weekly reports.
	2.13	Are all the defects/issues logged in the issue tracker
	2.14	Are all the test cases in the SRT test case document executed
3	Closure
	3.1	Root Cause Analysis (RCA) and Closure summary documents are done to find the root cause of the issues.
	3.2	Post RCA Analysis, are the action items identified for next round of testing

Posted in: ETL Testing