The user acceptance testing questionnaire is an integral aspect of the entire process of acceptance testing. The user acceptance testing questionnaire helps a firm in receiving feedback related to the testing process and this feedback helps in implementing improved systems and processes.

Each system or process needs to meet certain standards and key user requirements and the results can be monitored only after acceptance testing. Hence, the user acceptance testing questionnaire helps a firm in not only identifying the bottlenecks but also helps them to chart a plan of action based on the feedback.

Sample User Acceptance Testing Questionnaire:

Name of the User: _____________________________

Firm: _________________

System/Process undergoing User Testing:__________________________________

Internal / External: _____________________________ (Internal-Employee/External-User)

Email: _____________________________

Phone Number: ____________________________

  • Which of the following aspects have been considered as a part of user testing probing tests?

a)      Quality of software being used

b)      Involvement of experts with systems and critical thinking skills

c)      Identification of emotional climate

d)     Identification of technical approach to system/process

e)      Identification of challenges faced by system/process

  • Which of the following criteria’s were considered when designing the system/process?

a)      Current motivations

b)      Future deliverables

c)      Current mission

d)     Practices congruent to the working of process

e)      Strategies and techniques

f)       context-driven thinking

  • Have you identified how the system/process might fail in meeting the actual needs of the user acceptance testers during the test? If “yes” then please mention the reasons identified for failure.

a)      Yes

b)      No

c)      Reason for failure:_______________________________

  • Which of the following aspects according to you was missed completely during user acceptance testing?

a)      User stories are atomic

b)      Use of process not elaborate

c)      Process use not meant to be end-to-end

d)     System development process not thorough

e)      System development did not take into account risks

f)       Process implementation challenges