Purpose of this Article
Once your data mapping is complete, it is essential to thoroughly test the data that has been migrated to Mercury. This ensures the accuracy and integrity of your information prior to your Mercury Implementation going live.
This article outlines how your team should approach testing and what checks to perform. Treating this as a high-priority task will help keep your project on track.
Overview of the Testing Process
The testing process will be led by our team, who will guide you through each stage. You will need to nominate a group of testers—ideally users who are familiar with your existing system and who will easily recognise the data once it is moved into Mercury.
We recommend focusing on your most active Client records, including all related data. Reviewing your top 5 to 10 Clients usually gives a meaningful sample set.
Who Should Be Involved in Testing
We suggest selecting a group of recruiters from different teams within your organisation. This is particularly important if you manage different types of recruitment or hold different types of data across business areas or client types. Involving a cross-section of users will help ensure a thorough and representative test.
What to Test
Testing should be conducted field by field, comparing the data in your legacy system to the data in Mercury. You will be guided through the fields in scope on the agreed mapping document that details what has been included in the migration.
Tip: If possible, use two screens or devices side-by-side to compare the old and new systems more easily.
Important: Do not compare any records that may have been updated after the migration snapshot was taken. If you are unsure of the cut-off date, please ask us
How to Provide Feedback
As testing sessions are guided by our team, simply notify the person running your UAT session whenever you encounter an issue, change request, or question. They will log all feedback centrally and ensure it is reviewed and addressed.
What Happens Next
Once testing is complete, we will provide a summary of all proposed changes. We’ll confirm which can be included within the project scope and identify any that may be chargeable or deferred until after Go-Live due to time constraints.
If you have any questions during the testing process, please reach out to your Mercury Project Manager.