Alpha and Beta Testing-Acceptance Testing

            Alpha and Beta Testing

Acceptance Testing
  • Making sure the software works correctly for intended user in his or her normal work environment.
  • Alpha test (version of the complete software is tested by customer under the supervision of the developer at the developer’s site)
  • Beta test (version of the complete software is tested by customer at his or her own site without the developer being present)
  • Software can be built as a custom software, (e.g. MIS for a particular organization) for one customer or as a product to be used by many customers.
  • When it is developed as custom software, a series of acceptance tests are conducted to enable the customer to validate all requirements.
  • They are conducted by the end-user rather than software engineers and may be conducted over a period of weeks or months.
  • In case of software being developed as a product it is not possible to have acceptance testing by each end-user and hence a process called alpha and beta testing is followed.
  • The alpha test is conducted by a customer at the developer’s site.
  • The developer records errors and usage problems.
  • They are conducted in controlled environment.
  • The beta test is conducted at one or more customer sites by the end-user of the software.
  • The developer is generally not present.
  • The customer records all problems and reports to the developer at regular intervals.
  • Based on these reports the developer modifies the software and then releases to the entire customer base.

Comments

Popular posts from this blog

Food Ordering System

What is DFD ? or What is Data Flow Diagram?

Rules for Stopping the Decomposition Process in DFD