How To Handle Acceptance Testing Feedback
Posted By Anjali Pandey | 30-May-2019
Why Acceptance Testing:
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
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',