Acceptance testing is the final phase in any systems development project. It comes after the product or solution has been developed and (hopefully) tested thoroughly by its creator. The purpose of acceptance testing is to ensure that the requirements are met.
At this point, it’s up to the client to verify that the system lives up to the agreed-upon specifications, as well as any implicit or expected requirements. Here are eight guidelines to follow when running your own acceptance testing sessions.