Editing Acceptance testing (section)

== Process ==
The acceptance test suite may need to be performed multiple times, as all of the test cases may not be executed within a single test iteration.<ref name="ISO 29119 Part 2">{{Cite book |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=45142 |title=ISO/IEC/IEEE 29119-2:2013 Software and Systems Engineering - Software Testing - Part 2: Test Processes |date=2013 |publisher=[[International Organization for Standardization|ISO]] |access-date=May 21, 2014}}</ref>

The acceptance test suite is run using predefined acceptance test procedures to direct the testers on which data to use, the step-by-step processes to follow, and the expected result following execution. The actual results are retained for comparison with the expected results.<ref name="ISO 29119 Part 2" /> If the actual results match the expected results for each test case, the test case is said to pass. If the quantity of non-passing test cases does not breach the project's predetermined threshold, the test suite is said to pass. If it does, the system may either be rejected or accepted on conditions previously agreed between the sponsor and the manufacturer.

The anticipated result of a successful test execution:
* test cases are executed, using predetermined data
* actual results are recorded
* actual and expected results are compared, and
* test results are determined.

The objective is to provide confidence that the developed product meets both the functional and non-functional requirements. The purpose of conducting acceptance testing is that once completed, and provided the acceptance criteria are met, it is expected the sponsors will sign off on the product development/enhancement as satisfying the defined requirements (previously agreed between business and product provider/developer).