Acceptance testing is the formal testing phase used to demonstrate that the
software performs as required. This is the final stage in the testing process before
the software is accepted for operational use.
Acceptance testing is the responsibility of the customer. Nevertheless, it has
important implications on the project, as its duration impacts the cost and the
payment schedule.
It is therefore important for both customer and software supplier to ensure the
thoroughness of the acceptance test while minimizing its duration.
The lack of coordination between acceptance testing and other testing phases
( unit testing, integration testing, and system testing), in addition to customer’s
wish to build confidence in the software, lead to a substantial prolongation of
acceptance testing duration.
In this paper, we discuss a practical approach to shorten the time of acceptance
testing, and we propose a framework for “good enough” testing derived from the
following basic ideas: Involving the customer early in the software testing
activities and consider the scope and results of the other testing activities when
planning for acceptance testing.
Combining acceptance testing with other testing activities will save time and
money.