Definitions[]
Acceptance testing is
| “ | [t]esting conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system.[1] | ” |
| “ | [t]he formal testing conducted to determine whether a software system satisfies its acceptance criteria, enabling the customer to determine whether to accept the system.[2] | ” |
| “ | formal testing conducted to determine whether or not a product or system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the product, system, or component.[3] | ” |
Overview[]
The purpose of system acceptance testing is to verify that the complete system (i.e., the full complement of application software running on the target hardware and systems software infrastructure) satisfies specified requirements (functional, performance, and security) and is acceptable to end users. System acceptance tests are a set of specialized tests run either separately or in some combination in an operational environment (either actual or simulated). Collectively, these tests verify that the entire system performs as intended.
References[]
- ↑ U.S. Food and Drug Administration, Glossary of Computerized System and Software Development Technology 32 (Aug. 1995) (full-text).
- ↑ Auditing and Financial Management: Glossary of EDP Terminology, at 1.
- ↑ DHS Lexicon Terms and Definitions, at 5.
Source[]
- Year 2000 Computing Crisis: A Testing Guide, at 22. ("Overview" section)