Acceptance
Testing |
As in Functional testing, this classification of testing is performed for the explicit purpose of verifying that the system satisfies the user's requirements and meets the user's needs. The focus of Acceptance testing, however, shifts to the user's ability to successfully use the new features. Literally, Acceptance testing may be the final step before the user or another authorized entity "accepts" delivery of the system in acknowledgment that it performs satisfactorily. Acceptance testing can include Alpha and Beta testing (also called "field testing"). Note that the term Acceptance testing can also be used by some organizations to refer to smoke testing, or testing that ensures the code meets the established minimum requirements before turnover to another department. For example, an organization may require that before code can be transferred from Development to QA, a developer must have successfully installed the software on a PC. In this event, QA might perform an installation as a smoke test prior to formally accepting the system for testing. |
At the point the system is thought to be ready for release, or any time there is a need to evaluate the system with regard to user requirements. In special circumstances, Acceptance testing may also refer to smoke testing that QA performs prior to accepting the system for testing. |
Primarily, clients and Acceptance testers, but may also be conducted by Business analysts, System testers or QA. |
