Software release version description

Before large-scale software is officially released, alpha and beta tests are usually required to test the functions and performance of the software from the perspective of actual end users, to discover errors that may only be discovered by the end user.

 

Alpha testing is a test performed by a user in the development environment. It can also be a controlled test performed by the company's internal users in the simulated actual operating environment. Alpha testing cannot be performedProgramCompleted by the tester or tester. Errors Found during alpha testing can be immediately reported to developers at the testing site for timely analysis and handling. The purpose is to evaluate the functions, usability, reliability, performance, and support of software products. Pay special attention to the product interface and features. Alpha testing can start after the software product code is complete, or after the module (subsystem) test is complete, you can also start after the product reaches a certain degree of stability and reliability during the validation test. Relevant manuals (drafts) should be prepared before Alpha testing.

 

Beta testing (beta testing) is a test performed by multiple users of the software in the actual use environment of one or more users. Developers are usually not present at the test site, and beta testing cannot be completed by programmers or testers. Therefore, beta testing is a field application of software in an environment beyond the control of developers. During the beta test, the user records all problems encountered, including authentic and confirmed by the supervisor, and reports to the developer on a regular basis. The developer makes changes after comprehensive user reports, finally, deliver the software to all users. Beta testing focuses on product support, including documentation, customer training, and support product production capabilities. Beta testing can be started only when Alpha testing reaches a certain degree of reliability. Because the main purpose of the beta test is the test supportability, the beta test should be managed by the person who hosts the product release as much as possible.

 

The organization of alpha and beta testing is difficult, the testing cost is high, the testing randomness is strong, the testing cycle span is long, and the testing quality and efficiency are difficult to guarantee, many professional software may no longer undergo beta testing. With the development of testing technology and the emergence of professional testing services, many software beta tests are outsourced to these professional testing institutions for testing.

 

Alpha and beta testing

After the software is delivered and used, how users actually use the program is unpredictable for developers.

Alpha testing is performed by a user in the development environment, or by a user in the company in the simulated actual operating environment.

Test.

Alpha testing aims to evaluate the flurps (functionality, localization, usability, reliability, performance, and support) of software products.

Interface and features.

Alpha testing can start at the end of the software product code, or after the module (subsystem) test is completed, or after the validation test process

After the product reaches a certain degree of stability and reliability, start again.

Beta testing is performed by multiple software users in the actual use environment. These users return error messages to developers.

During testing, developers are usually not present at the testing site. Therefore, beta testing is a software field application in an environment beyond the control of developers.

During beta testing, the user records all problems encountered, including authentic and subjective ones, and reports to developers on a regular basis.

Beta testing mainly measures the flurps of a product. It focuses on product support, including documentation, customer training, and support for product production capabilities.

Beta testing can be started only when Alpha testing reaches a certain degree of reliability. It is in the final stage of the testing. At the same time, all product manuals

The text should also be finalized in this phase.

 

α, β, and λ are commonly used to represent three stages in the software testing process. α is the first stage and is generally used only for internal testing. β is the second stage, most of the imperfections in the software have been eliminated, but there may still be defects and vulnerabilities. Generally, they are only available to specific user groups for testing. λ is the third stage, at this time, the product is quite mature, and only needs to be further optimized in some places before it can be published.

 

Other related versions:

 

Trial: The trial version usually has time restrictions, and some trial software still has certain functional limitations. Can be registered or purchased as the official version

Unregistered. You can register or purchase the official version.

Demo: demo version. It only integrates several functions of the official version and cannot be upgraded to the official version.

Lite: Lite version.

Full Version: Full version, which belongs to the official version.

 

Development Phase Division:

ALPHA: beta version for internal communication or testing by professional testers. There are many bugs. It is recommended that you do not install them.

Beta (Beta): A Public Beta version that is used for large-scale testing by professional enthusiasts. This version is not suitable for general users.

Gamma (gamma): a fairly mature beta version, which is almost the same as the official version to be released.

RC: Release Candidate.

RC version. It is the abbreviation of release candidate, which indicates the release countdown. The candidate version, in the Gamma stage, has completed all functions and cleared most of the bugs. At this stage, only bugs will be removed, and no major changes will be made to the software. From alpha to Beta to Gamma is an improved relationship, but RC1 and RC2 are usually a trade-off relationship.

Final: official version.

 

Less useful:

Enhance: the enhanced version or enhanced version belongs to the official version 1.

Free: Free Edition

Release: release has a time limit

Upgrade: upgraded

Retail: Retail Edition

Cardware: a type of shared software. You only need to send an email or postcard to the author. (Some authors provide registration codes). Currently, this form is rare. /S

Plus: it is an enhanced version, but most of it is enhanced on the program interface and multimedia functions.

Preview: preview

Corporation & Enterprise: Enterprise Edition

Standard: Standard

Mini: The mini version is also called Lite version with only the most basic functions

Premium: Premium Edition

Professional: Professional Edition

Express: Special Edition

Deluxe: Deluxe Edition

Regged: Registered version