Alpha and Beta Testing

Alpha Testing

A software prototype stage when the software is first available for run. Here the software has the core functionalities in it but complete functionality is not aimed at. It would be able to accept inputs and give outputs. Usually the most used functionalities (parts of code) are developed more. The test is conducted at the developer's site only.

In a software development cycle, depending on the functionalities the number of alpha phases required is laid down in the project plan itself.

During this, the testing is not a through one, since only the prototype of the software is available. Basic installation – uninstallation tests, the completed core functionalities are tested. The functionality complete area of the Alpha stage is got from the project plan document.

 

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

 

• Understand the system requirements completely.
• Initiate the preparation of test plan for the beta phase.

 

Role of the tester

• to provide input while there is still time to make significant changes as the design evolves.

• Report errors to developers

 Try installing on system having non-compliant configuration such as less memory / RAM / HDD.

12.7 Beta Testing

The Beta testing is conducted at one or more customer sites by the end-user of the software. The beta test is a live application of the software in an environment that cannot be controlled by the developer.

The Software reaches beta stage when most of the functionalities are operating.

The software is tested in customer's environment, giving user the opportunity to exercise the software, find the errors so that they could be fixed before product release.

Beta testing is a detailed testing and needs to cover all the functionalities of the product and also the dependent functionality testing. It also involves the UI testing and documentation testing. Hence it is essential that this is planned well and the task accomplished. The test plan document has to be prepared before the testing phase is started, which clearly lays down the objectives, scope of test, tasks to be performed and the test matrix which depicts the schedule of testing.

 

Beta Testing Objectives

·         Evaluate software technical content

·         Evaluate software ease of use

·         Evaluate user documentation draft

·         Identify errors

·         Report errors/findings

 

Role of a Test Lead

 

• Provide Test Instruction Sheet that describes items such as testing objectives, steps to follow, data to enter, functions to invoke.
• Provide feedback forms and comments.

 

Role of a tester

 

• Understand the software requirements and the testing objectives.
• Carry out the test cases