How To Handle Acceptance Testing Feedback

Posted By Anjali Pandey | 30-May-2019

Why Acceptance Testing:

This is a user experience of how the application works. They are focused on how the application should behave? 'They use a fresh application and that it is easy to follow them or not. The UAT user is based on stories and establishes how well this fulfills their needs. Users do not use the Test-to-Break approach while accepting approval. Rather, UAT is a measurement of how well your app performs in normal user scenarios.


After user acceptance testing, users give their feedback. This feedback can include positive and appreciative comments, bug reports or defects, change requests, and new functionality. 

We need to take action for the following types of feedback:

Bugs/Issues: After the UAT test, users can report any bugs. These issues are of high priority and need to be corrected, especially if the bugs are important in nature. In this case, you also need to review your testing procedure and check that the insects of important nature have survived from the QA.


Change Requests: Sometimes the user becomes more pronounced about his needs, because he has actually used the application in UAT. They can request a minor change in system behaviour. Note that the change request is not similar to a bug. You can chat with the client and buy more time to apply change requests.


New Functionalities: Users can also request new functionality. The difference between the change request and the new functionality is that the change requests are for functionality that has already been implemented, but some tweaking is required. You can communicate with users and know that new functionality is required just before production or you can move forward in the next sprint change.


Conclusion: Although the user's acceptance test is the word 'test', but it is not done in the manner of professional testers. This is 'user-oriented', so the person who operates the UAT will have to understand some factors that are necessary to operate the UAT test smoothly. These factors include the identification of user roles, use of user stories, use of business language and user acceptance test template. After user acceptance testing, you will receive UAT test feedback i.e. bug, change request or new feature request According to the feedback, you take appropriate action, before the software is deployed on production.


Request for Proposal

Recaptcha is required.

Sending message..