Quality is delighting customers
Looking out for strategy for testing the document content migration. Here are the details.
We are re-writing a community sharing application where users can share views, articles, contents, images, etc as part of it, as part of it we are migrating the historical content using traditional data migration approach by applying transformation logic at needed places. – I am clear on testing this as its little straight forward of comparing data between source and destination with transformation logic.
But, having difficulty in testing the display of content when accessed through application to view online in the browser.
i.e. lets assume that a document with multiple content types like text, paragraph, images, slideshows, etc was created as part of legacy application. As part of new application, the content types are changed for couple of templates so the look and feel and formatting might get changed.
I could think of testing this by performing one to one comparison of document content and layout between legacy and new version of application. But this is time consuming considering the amount of migrated files content to be tested.
Is there any better approach or automated solution to achieve this?
Migration Testing is a process of migration of old system data into a new system successfully with minimum downtime. It involves maintaining data integrity without any loss of data. After Migration testing, all features of the new system should behave like the existing system, there should be no functionality breach.
Most of the clients nowadays outsource qa for their migration testing needs as this involves a lot of data and manual effort. We can use the below strategy for migration testing:
1. Align Resources: Identify the members from existing who have required knowledge of the system or train new members on the existing system, so that they verify the new system once the system is ready.
2. Risk Analysis: It is very important to evaluate the risk associated with the new system if something did not go well. We should work with all stakeholders of the business to identify those areas and make sure all scenarios are covered while testing.
3. Mitigation Plans: After identification of the risk next important part is to design mitigation. If something major goes wrong then we should have a plan to handle that situation. The team should be ready with a mitigation plan for all major scenarios.
4. Tools Evaluation: Team should analyze and finalize the which will be used after migration for data comparison. We should make a decision on that whether the migration should be manual or automated.