Editing Acceptance testing (section)

== User acceptance testing ==

User acceptance testing (UAT) consists of a process of verifying that a solution works for the user.<ref>{{Cite book |last=Cimperman |first=Rob |title=UAT Defined: A Guide to Practical User Acceptance Testing |publisher=Pearson Education |year=2006 |isbn=9780132702621 |pages=Chapter 2}}</ref> It is not [[system testing]] (ensuring software does not crash and meets documented requirements) but rather ensures that the solution will work for the user (i.e. tests that the user accepts the solution); software vendors often refer to this as "Beta testing".

This testing should be undertaken by the intended [[end user]], or a [[subject-matter expert]] (SME), preferably the owner or client of the solution under test and provide a summary of the findings for confirmation to proceed after trial or review. In [[Software development process|software development]], UAT as one of the final stages of a project often occurs before a client or customer accepts the new system. Users of the system perform tests in line with what would occur in real-life scenarios.<ref>{{Cite book |last1=Goethem |first1=Brian |last2=van Hambling |first2=Pauline |title=User acceptance testing : a step-by-step guide |publisher=BCS Learning & Development Limited |year=2013 |isbn=9781780171678}}</ref>

The materials given to the tester must be similar to the materials that the end user will have. Testers should be given real-life scenarios such as the three most common or difficult tasks that the users they represent will undertake.<ref>{{Cite web |date=2021-08-02 |title=2.6: Systems Testing |url=https://eng.libretexts.org/Courses/Prince_Georges_Community_College/INT_2840%3A_Systems_Analysis_and_Project_Management/02%3A_Information_Systems_Development_And_RFP/2.06%3A_Systems_Testing |access-date=2023-02-18 |website=Engineering LibreTexts |language=en}}</ref>

The UAT acts as a final verification of the required business functionality and proper functioning of the system, emulating real-world conditions on behalf of the paying client or a specific large customer. If the software works as required and without issues during normal use, one can reasonably extrapolate the same level of stability in production.<ref>{{Cite book |last=Pusuluri |first=Nageshwar Rao |title=Software Testing Concepts And Tools |publisher=Dreamtech Press |year=2006 |isbn=9788177227123 |page=62}}</ref>

User tests, usually performed by clients or by end-users, do not normally focus on identifying simple cosmetic problems such as spelling errors, nor on [[Software bug|showstopper]] defects, such as [[crash (computing)|software crashes]]; testers and developers identify and fix these issues during earlier [[unit testing]], [[integration testing]], and system testing phases.

UAT should be executed against test scenarios.<ref>{{Cite web |date=2022-04-25 |title=Get Reliable Usability and Avoid Risk with These Testing Scenarios |url=https://www.panaya.com/blog/testing/testing-scenarios/ |access-date=2022-05-11 |website=Panaya |language=en-US}}</ref><ref>{{Cite web |last=Elazar |first=Eyal |date=2018-04-23 |title=What is User Acceptance Testing (UAT) - The Full Process Explained |url=https://www.panaya.com/blog/testing/what-is-uat-testing/ |access-date=2023-02-18 |website=Panaya |language=en-US}}</ref> Test scenarios usually differ from System or Functional test cases in that they represent a "player" or "user" journey. The broad nature of the test scenario ensures that the focus is on the journey and not on technical or system-specific details, staying away from "click-by-click" test steps to allow for a variance in users' behavior. Test scenarios can be broken down into logical "days", which are usually where the actor (player/customer/operator) or system (backoffice, front end) changes.<ref>{{Cite journal |last1=Wysocka |first1=Emilia M. |last2=Page |first2=Matthew |last3=Snowden |first3=James |last4=Simpson |first4=T. Ian |date=2022-12-15 |title=Comparison of rule- and ordinary differential equation-based dynamic model of DARPP-32 signalling network |journal=PeerJ |language=en |volume=10 |at=Table 1: The specifications of the ODE and RB models can be broken down into elements, the number of which can be compared. |doi=10.7717/peerj.14516 |issn=2167-8359 |pmc=9760030 |pmid=36540795 |doi-access=free }}</ref>

In industry, a common UAT is a factory acceptance test (FAT). This test takes place before the installation of the equipment. Most of the time testers not only check that the equipment meets the specification but also that it is fully functional. A FAT usually includes a check of completeness, a verification against contractual requirements, a proof of functionality (either by simulation or a conventional function test), and a final inspection.<ref>{{Cite web |title=Factory Acceptance Test (FAT) |url=http://www.tuv.com/en/corporate/business_customers/materials_testing_and_inspection/supply_chain_services/factory_acceptance_test/factory_acceptance_test.jsp |url-status=dead |archive-url=https://archive.today/20130204215825/http://www.tuv.com/en/corporate/business_customers/materials_testing_and_inspection/supply_chain_services/factory_acceptance_test/factory_acceptance_test.jsp |archive-date=February 4, 2013 |access-date=September 18, 2012 |publisher=TÜV Rheinland }}</ref>
The results of these tests give clients confidence in how the system will perform in production. There may also be legal or contractual requirements for acceptance of the system.