Just general discussion about Data Migration Testing:
It is nice every Software Test Engineer to get involved in project, including data migrations. Data migrations that appear to be simple and straightforward conceptually can quickly become complicated as analysis is done of the source data and how it maps to the target system / database. Even the type of source database / system can have an impact on how the data migration itself is carried out. QA personnel should be involved in all aspects of the analysis and design of the data migration.
Test Engineer begin their test strategical and developing detailed test cases during the analysis phase and can continue to refine and finalize their test cases during the design phase. Involving Test Engineer early on helps immensely in improving the overall quality of each phase of the data migration project.
Every Test Engineer can test during following phase:
1. Pre-Migration Test
2. Migration Test
3. Post Migration Test
Hi Priya !!
You given very valuable information about Data migration but can you eloborate on the following areas:
1. Pre-Migration Test -- What do we do in Pre-Migration Test / How do we start ? / What Testing Strategy do we use for this phase or for Data Migration Testing ?
2. Migration Test -- Similarly answer this too
3. Post Migration Test -- Similar as above.
Please let me know as soon as possible as I am attending Interview on Data Migration in a couple of days.
Mostly deals with verification kind of process, where source and destination are verified and any tech gaps required to fill in will be taken care. In few cases this will be most crucial part of complete process as mapping of both the nodes will be analyzed for data integretity while migrating.
Most likely way to deal is through good review process for each level documentation.
Coming this stage well its just a validation process as per your requirement, hope I dont have to add any thing as its common project requirement.
But destination should be verified for other running application which shares same memory, specialy when it comes to shared memory kind of situtation every needs to be verifed in pre-migration level.
Post - Migration:
Now according to the changes once migration completed successfully try to do a regress check for new environmental stages and any dependencies which again will be best to handle using Impact analysis.