[Software testing] α, β, λ test

1. Acceptance test

1.1 Acceptance Test Concept

Typically performed by customers or end users. The goal of acceptance testing, usually focusing on the behavior and functionality of the entire system or product.

1.2 Acceptance test objectives

• Build confidence in the quality of the entire system
• Verify that the system is complete and working as expected
• Verify that the functional and non-functional behavior of the system is as defined

2. α, β, λ test

α, β, and λ are often used to represent the three stages in the software testing process.

2.1 alpha test

• Testing phase: the first phase of acceptance testing

• Full name: alpha test

• Testers: joint participation of users, testers, and developers

• Test Type: Internal Test (Internal Test)

• Test focus: functionality, localization, usability, reliability, performance, and support for the product's interface and special

• Testing purposes:

  • From the perspective of actual end users, test the functions and performance of the software to find errors that may only be found by end users.

• Test instruction:

  • It can start when the software product coding is finished, or after the module (subsystem) test is completed, or after it is determined that the product has reached a certain degree of stability and reliability during the test process.
  • Alpha testing releases are called alpha releases .

2.2 Beta test

• Testing phase: the second phase of acceptance testing

• Full name: beta testing

• Testers: end users, lay testers, specific user groups

• Test type: external test (public test after internal test)

• Test focus: product supportability, including documentation, customer training and support for product production capabilities.

• Purpose of the test: to obtain feedback from different user groups and to check the compatibility of different types of products, etc.

• Test instruction:

  • Most of the imperfections in the software have been eliminated, but there may still be bugs and bugs.

  • When the alpha test reaches a certain degree of reliability, the beta test can be started.

  • The version released after the beta test is called the beta version. It can be said that the beta test is a pre-release test .

2.3 Lambda test

• Testing phase: the third phase of acceptance testing

• Full name: Gamma test

• Test instruction:

  • The product is already quite mature, and it can be released on the market only by further optimization in some places.
  • After the software is ready for release and fulfills various requirements, lambda testing begins. No other internal testing is required for testing. Except in high-pressure situations where development cycle times are extremely short and time-to-market requirements are extremely fast.