How have you managed UAT

I was just assigned as a ‘manager’ of UAT for our web app.
Could you please give me some good practical resources and advice of how to properly manage the UAT?

I saw this recently asked on one of our Slacks.

What would you advise? Do you have any useful resources on managing the UAT process?

1 Like

I’ve never worked in UAT, I’m more of a technical tester myself, but I have worked closely with UAT testers and their managers. Apart from the obvious need of being tech savvy, UAT tester need to be really strong in their domain knowledge, to have a very deep understanding of the business logic behind the product they are testing. Also, having a good understanding of UI/UX should help considerably.

User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.

A UAT usually happens when the solution is build on behalf of someone. Company A asks Company B, and the UAT is done by A, so that they can test the delivery. If you have multiple layers of requirements, SIT tests the technical req’s and UAT the high level business requirements. YMMV

Often the UAT is performed by company A’s testers or subject matter experts from A. So there are some tricks here:

As always, really, it’s a matte of figuring out what to test and who that has the skills to test it - and then get a collaboration going with them.