Testing process on behalf of system Customers and Users, in order to meet Client specific requirements and additional options, which check implementation robustness and its successful appliance within a Client's particular Environment . source: ITU-T X.290 domain: OSI Conformance Testing usage: EU-P201
Formal testing conducted to determine whether or not a system satisfies its acceptance criteria - enables an end user to determine whether or not to accept the system.
The testing performed by a user to determine that an automated system (equipment or software) for a specific task or environment, e.g., a translator for a specific application and interchange format, performs according to specification.
Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component. [IEEE
Formal testing 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.
Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.
Testing conducted in an operational environment to determine whether a system satisfies its acceptance criteria (e.g., initial requirements and current needs of its user) and to enable the customer to determine whether to accept the system. [IEEE Stds Glossary
In engineering and its various subdisciplines, acceptance testing is performed by the customer on a system prior to the customer accepting delivery or accepting transfer of ownership of that system. For systems, it is performed exclusively through black-box testing. Acceptance testing is also performed on lots (mechanical parts) or batches (chemicals) of manufactured or produced items .