What is Alpha and Beta Testing?

What is Alpha and Beta Testing?


Before any software product can be released it must be tested. Typically a formal test strategy is planned and executed on the software before it can be considered for release. Often after the formal phases of testing have been completed, additional testing is performed called Alpha and Beta testing.
Alpha testing is done before the software is made available to the general public.

Typically, the developers will perform the Alpha testing using white box testing techniques. Subsequent black box and grey box techniques will be carried out afterwards. The focus is on simulating real users by using these techniques and carrying out tasks and operations that a typical user might perform. Normally, the actual Alpha testing itself will be carried out in a lab type environment and not in the usual workplaces. Once these techniques have been satisfactorily completed, the Alpha testing is considered to be complete.

The next phase of testing is known as Beta testing. Unlike Alpha testing, people outside of the company are included to perform the testing. As the aim is to perform a sanity check before the products release, there may be defects found during this stage, so the distribution of the software is limited to a selection of users outside of the company. Typically, outsourced testing companies are used as their feedback is independent and from a different perspective than that of the software development company employees. The feedback can be used to fix defects that were missed, assist in preparing support teams for expected issues or in some cases even enforce last minute changes to functionality.

In some cases, the Beta version of software will be made available to the general public. This can give vital 'real-world' information for software/systems that rely on acceptable performance and load to function correctly.

The types of techniques used during a public Beta test are typically restricted to Black box techniques. This is due to the fact that the general public does not have inside knowledge of the software code under test, and secondly the aim of the Beta test is often to gain a sanity check, and also to retrieve future customer feedback from how the product will be used in the real world.
 
Various sectors of the public are often eager to take part in Beta testing, as it can give them the opportunity to see and use products before their public release. Many companies use this phase of testing to assist with marketing their product. For example, Beta versions of a software application get people using the product and talking about it which (if the application is any good) builds hype and pre-orders before its public release.

Author: James S Clark
Source: Link
Facebook: Link

Comments

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component          -   the input(s) to the compo
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components together in one go
Read more