Editing Acceptance testing (section)

== Overview ==
Testing is a set of activities conducted to facilitate the discovery and/or evaluation of properties of one or more items under test.<ref name="ISO 29119 Part 1">{{Cite book |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=45142 |title=ISO/IEC/IEEE 29119-1:2013 Software and Systems Engineering - Software Testing - Part 1: Concepts and Definitions |date=2013 |publisher=[[International Organization for Standardization|ISO]] |access-date=October 14, 2014}}</ref> Each test, known as a test case, exercises a set of predefined test activities, developed to drive the execution of the test item to meet test objectives; including correct implementation, error identification, quality verification, and other valued details.<ref name="ISO 29119 Part 1" /> The test [[deployment environment|environment]] is usually designed to be identical, or as close as possible, to the anticipated production environment. It includes all facilities, hardware, software, firmware, procedures, and/or documentation intended for or used to perform the testing of software.<ref name="ISO 29119 Part 1" />

UAT and OAT test cases are ideally derived in collaboration with business customers, business analysts, testers, and developers. These tests must include both business logic tests as well as operational environment conditions. The business customers (product owners) are the primary [[project stakeholder|stakeholders]] of these tests. As the test conditions successfully achieve their acceptance criteria, the stakeholders are reassured the development is progressing in the right direction.<ref name="ISO 29119 Part 4">{{Cite book |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60245 |title=ISO/IEC/IEEE 29119-4:2013 Software and Systems Engineering - Software Testing - Part 4: Test Techniques |date=2013 |publisher=[[International Organization for Standardization|ISO]] |access-date=October 14, 2014}}</ref>

* User acceptance test (UAT) criteria (in [[agile software development]]) are usually created by business customers and expressed in a [[Domain specific language|business domain language]]. These are high-level tests to verify the completeness of a [[user story]] or stories 'played' during any sprint/iteration. 
* Operational acceptance test (OAT) criteria (regardless of using agile, iterative, or sequential development) are defined in terms of [[Functional requirement|functional]] and [[non-functional requirement]]s; covering key quality attributes of [[software testing|functional stability]], [[portability testing|portability]], and [[reliability theory|reliability]].