Hi what is the process of doing UAT.Do you run the test case you made for functional testing of application before the client or test the application on the basis of functional specification document.Do you run the application in presence of client or end user run it themselves and you provide test case you made for testing application along with test report.Or it is completely on client what way they test it in presence of developers,test engineers and project manager from development side.I am little confused about this UAT.Kindly give the answer in detail of handling the UAT(User Acceptance Test).
The question depends on the client. I have participated (and help run) UATs in both fashions. I like to have a set of test cases for the client to use so they can see all of the functionality of the product. You can help narrow this down by asking the client if they want to test a specific area or if the have any scenarios that they want to run. Be mindful that depending on the type of application client based testing may be difficult (if the product is data base driven making sure the client has all the information needed to run their scenarios may be difficult). I do like when the client has his or her own test cases or scenarios because it takes the load off of me but if your product requires any kind of functional work arounds this could be a problem.
I think they client testing should be done with the PM and a product specialist who knows the functionality (unfortunately that is usually the tester). I would first give the users a training session on the functionality of the product and then let them run test scenarios (either ones they have made or one you have provided). In a lot of cases UAT is used not only for the client to test the product but also to train the client on how to best utilize the product.
To find bugs related to usability you will have to test the product from the user's perspective. You can also have periodic reviews from the client while the product is still in development for the usability point of view.
Rather than review if focus is on getting the UAT scope and conditions from client then that would be more helpful. Progress can be tracked during development but UAT should be available before dev starts. If in day to day routine this has been ignored to make room for unplanned randomness for testing then it may not help you in long run.