The major inputs for the testing team would be data model and mapping document. When we start our analysis itself we need to make sure that the source table or files are correct.
There is not much difference between functional test plans except few items, here we need to mention the data flow in both scope and out-scope sections.
Test cases will be prepared along with mapping document. In this stage itself, we need to find requirement related defects by doing analysis on source data and mapping documents such as data type, data length, and relationships.
ENTRY CRITERIA FOR TEST DESIGN:
Once all entry criteria’s are all set, initial execution can be performed with bulk load jobs. All the stages from Source to target will be tested one by one.
Then incremental load jobs for all stages will be tested to make sure the changes are reflecting in the target.
ENTRY CRITERIA FOR TEST EXECUTION:
- Test design documents
- Approved Test plan
- Access to ETL jobs and database schema
- ETL jobs
Fixed defects will be retested and validated in the case of any rejection. Based on Impact analysis, the test cases need to be executed as part of defect fix.
The performance of ETL jobs will be validated.
Based on exit criteria of test e execution, the sign off mail to be sent to stakeholders in order to be proceeded push the code to next level.