If the point of user acceptance testing is to find out if the user is happy with the software, what sense does it make for some tester to tell them what to look for? Why not just ask the users to try the software and tell the team what they think?
The only answer to that question I’ve ever gotten is “It’s too hard to figure out if they are actually happy, so we’re just trying to figure out if we gave them what they asked for according to the requirements document that they signed off on.” Which boils down to “we’re just getting the users to agree that we should get paid.”
So, if that is your goal, go ahead and use system test cases.
But if your goal is to determine user satisfaction, just let them use the system and tell you what they like and what they don’t like about the system. I’m willing to bet you’ll end up with a better application that way.
Make users happy
08.05.2008 by Алексей Лупан
“User acceptance testing and test cases”, Scott Barber, 2007.