Acceptance testing is formal testing conducted to determine whether or not a system satisfies its acceptance criteria,
and to enable the customer, user or authorized entity to determine whether or not to accept the system.
Acceptance testing is often conducted at the development site, and then at the customer site using the target
How the customer evaluates the deliverables to determine whether they meet predefined set of acceptance criteria is
described in the Product Acceptance Plan. The Product Acceptance Plan describes the roles, responsibilities, required
resources, tasks, test cases and acceptance criteria required to determine the acceptability of the product.
Another useful input to determining the project's readiness for formal test are the Configuration Audit Findings that
report on whether the developed software conforms to its requirements and whether the required work products are
Deficiencies in the Configuration Audit Findings could result in the Acceptance Test being postponed. The Deployment
Manager should review minor deficiencies with the customer, for whose benefit the formal tests are conducted, to
determine whether testing should proceed.
The System Administrator needs to ensure that the infrastructure (hardware and software resources), and support
software is ready for the upcoming test tasks.