What is Alpha testing?
Definition
Alpha testing is a very early version of a software product that may not contain all of the features that are planned for the final version. Typically, software goes through two stages of testing before it is considered finished. The first stage, called alpha testing, is often performed only by users within the organization developing the software. The second stage, called beta testing , generally involves a limited number of external users. In contrast to beta testing, alpha software is usually assumed to have some significant bugs or unimplemented portions.
Alpha Testing in Practice
How does Alpha testing work?
Alpha testing is the software prototype stage when the software is first able to run. It will not have all the intended functionality, but it will have core functions and will be able to accept inputs and generate outputs. An alpha test usually takes place in the test lab environment on a separate system.
Typcially, project manager utilizes this prototype to evaluate and provide input to the developer as the design evolves. Although software is usually not distributed to users prior to beta testing, selected end-users may also be involved. Usually, the most complex or most used parts of the code are developed more completely in the alpha, in order to enable early resolution of design questions.
The project manager collaborates with the developer to determine specific goals for alpha testing, and to integrate the results into evolving project plans.
In-depth software reliability testing, installation testing, and documentation testing are not done at alpha test time, as the software is only a prototype.
Setting Expectations for External Customer
If customers will receive alpha software, they must understand that the product will be only minimally functional, and is likely to have problems. Software QA team should check for the most serious problems,like Data loss, System crash etc, but customers must still be informed for unexpected or frustrating experiences.
A letter or e-mail accompanying alpha software is strongly recommended. This letter should make customers aware of:
● The software's limited functionality at this early stage
● The likelihood of experiencing problems
● Their mission: Find problems and provide feedback
● An example Alpha Transmittal Memo is available.
QA Team Involvement
It is understood that alpha software is not fully functional. However, Software QA team should test all software that is to be sent to users or run on customer equipment so that possible serious errors can be removed. Examples of such errors are software behavior that compromises a user's system, or cause data loss. This pre-testing of alpha software that is sent to users will protect the reputation of yorur company with customers.
If desired, the QA team should collect additional early usability feedback on an alpha stage software code, such as feedback on the proposed navigation scheme, and the look and feel of the software.
|