Alpha testing is done by the customers in controlled environment in front of the development team. It has less probability of finding errors. It is done during implementation phase of software.

When to Start and Stop Testing of Software (Entry and Exit Criteria)

Process model is a way to represent any given phase of software development that prevent and minimize the delay between defect injection and defect detection/correction.

• Entry criteria, specifies when that phase can be started also included the inputs for the phase.

• Tasks or steps that need to be carried out in that phase, along with measurements that characterize the tasks.

• Verification, which specifies methods of checking that tasks have been carried out correctly.

• Clear entry criteria make sure that a given phase does not start prematurely.

• The verification for each phase helps to prevent defects. At least defects can be minimized.

Exit criteria, which stipulate the conditions under which one can consider the phases as done and included are the outputs for the phase.

a. Exit criteria may include:

1. All test plans have been run

2. All requirements coverage has been achieved.

3. All severe bugs are resolved.

OR

Entry Criteria for Alpha testing:

• Software requirements document or Business requirements specification

• Test Cases for all the requirements

• Testing Team with good knowledge about the software application

• Test Lab environment setup

• QA Build ready for execution

• Test Management tool for uploading test cases and logging defects

• Traceability Matrix to ensure that each design requirement has atleast one test case that verifies it

  Exit Criteria for Alpha testing:

• All the test cases have been executed and passed.

• All severity issues need to be fixed and closed

• Delivery of Test summary report

• Make sure that no more additional features can be included

• Sign off on Alpha testing