I've been Googling to read up and understand what UATs are and how to conduct them, but I'm not quite understanding how to apply it in this scenario.
My acceptance criteria would be that all historic data from duplicate profiles that are transactions, interactions, and custom fields like
strings get merged into the master record.
I'm confused about the "testing" part of UAT...what is there to test? don't we just look at the profiles and confirm that the data is there? Does that count as testing?
I'm struggling to build a test plan because I don't really see what there is to test.
Any help/suggestions/readings/articles is immensely appreciated.
Background: We have about 3 million records (record being the constituent profile in the CRM), and we have identified at least a quarter of the records are duplicates (common cases being a person has 5+ profiles).
We've gone through the activities of building our criteria and identifying which of these duplicates would be marked as the master record, the duplicate records would then be merged into the master record.
Our next step is to validate the master records to ensure the historic profile data from duplicate records remains intact (transactions, interactions, and any custom fields like booleans and strings that were added on as part of their registrations, merged into the master record).
Task: I am to build a UAT plan for multiple teams to validate the merge (I did express that my background is not related to what is being asked...but I'll try, because no one else in the company has any idea what to do at this point, budget is really really tight so cannot hire contractors)