Testing of an application when development is nearing completion minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Aim
* is to identify any serious errors
* to judge if the indented functionalities are implemented
* to provide to the customer the feel of the software

A through understanding of the product is done now. During this phase, the test plan and test cases for the beta phase (the next stage) is created. The errors reported are documented internally for the testers and developers reference. No issues are usually reported and recorded in any of the defect management/bug trackers

Role of test lead
1. Understand the system requirements completely.
2. Initiate the preparation of test plan for the beta phase.

Role of the tester
1. To provide input while there is still time to make significant changes as the design evolves.
2. Report errors to developers