Acceptance Testing: Alpha and Beta Testing for Software Quality Assurance, Summaries of Business

Download Acceptance Testing: Alpha and Beta Testing for Software Quality Assurance and more Summaries Business in PDF only on Docsity!

Software Testing Level

Part 2

Adam Hendra Brata

Agenda : Part 2

 Acceptance Testing

• Alpha
• Beta

Acceptance Testing

Acceptance Testing

 Acceptance testing is a formal testing conducted to determine whether a system satisfies its acceptance criteria  Acceptance testing consists of comparing a software system to its initial requirements and to the current needs of its end-users or, in the case of a contracted program, to the original contract [Meyers 1979 ].

Purpose of Acceptance Testing

 Other Testing:

• intent is principally to reveal errors  Acceptance Testing:
• a crucial step that decides the fate of a software system.
• Its outcome provides quality indication for customers to determine whether to accept or reject the software product.

Goal of Acceptance Testing

 Goal

• verify the man-machine or human-computer interactions
• validate the required functionality of the system
• verify that the system operates within the specified constraints
• check the system’s external interfaces  The major guide : the system requirements document  The primary focus : software quality factors, especially on usability and reliability [Hetzel, 1984 ].

Alpha & Beta Testing

Alpha Testing

 Alpha testing is a type of acceptance testing; performed to identify all possible issues/bugs before releasing the product to everyday users or public.  The focus of this testing is to simulate real users  The aim is to carry out the tasks that a typical user might perform.  Alpha testing is carried out in a lab environment and usually the testers are internal employees of the organization.

Alpha Testing

 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

14

Beta Testing

 Beta Testing of a product is performed by "real users" of the software application in a "real environment" and can be considered as a form of external user acceptance testing.  Beta version of the software is released to a limited number of end-users of the product to obtain feedback on the product quality. Beta testing reduces product failure risks and provides increased quality of the product through customer validation.  It is the final test before shipping a product to the customers. Direct feedback from customers is a major advantage of Beta Testing. This testing helps to tests the product in real time environment.

Testing Phase

 Alpha and Beta tests are typically carried for "off-the shelf" software or product oriented companies. The Phases of Testing for a product company typically varies from a service oriented organization. Following is the testing phase adopted by product firms

Testing Phase

 Pre-Alpha:

• Software is a prototype. UI is complete. But not all features are completed. At this stage software is not published.  Alpha:
• Software is near its development and is internally tested for bugs/issues  Beta:
• Software is stable and is released to limited user base. The goal is to get customer feedback on the product and make changes in software accordingly