Smoke test, Alpha test, beta test, and performance test

"Smoke test"This term describes how to change the code.Before embedding it in the product source treeThe process of verifying these changes. The smoke test found a problem during the test and found a bug. Then the developer will fix the bug. In this case, you need to know if this fix solves the program bug or whether it will affect other modules.This problemThis process is called smoke
Test. The smoke test object is the version of each newly compiled software that needs to be officially tested. The purpose is to confirm that the basic functions of the software are normal and subsequent formal tests can be conducted.

 

Alpha TestingIt is a test performed by a user in the development environment or by a user in the company in the simulated actual operating environment. Alpha testing aims to evaluate the flurps (functionality, localization, usability, reliability, performance, and support) of software products ). Pay special attention to the product interface and features. Alpha testing can start at the end of the software product code, 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. Alpha testing refers to a software development company's internal staff simulating various user lines to test the upcoming software products (called alpha version), trying to detect and correct errors. The key to Alpha testing is to simulate the actual operating environment and users' operations on software products as much as possible, and do their best to cover all possible user operations. The software products adjusted through Alpha testing are called Beta versions.

 

Beta testingIs an acceptance test. The so-called acceptance test is a software testing activity carried out before the product is released after the software product completes the functional test and system test. It is the last stage of the technical test and passes the acceptance test, the product will enter the release stage. In general, the acceptance test strictly checks the product according to the product specification, and compares all the requirements of the software product in the Specification line by line to ensure that the developed software product meets the requirements of the user. Beta testing is performed by software end users in one or more room locations. Unlike alpha testing, developers are generally not present in beta testing, because beta testing is a "real" Application of Software in environments that developers cannot control. All problems encountered during the user beta test (real or imagined), and these problems are reported to developers on a regular basis. After receiving issues reported during the beta test, the developer makes necessary modifications to the software product and prepares to release the final software product to all customers.

 

Performance TestingIt uses automated testing tools to simulate a variety of normal, peak, and abnormal load conditions to test various system performance indicators.Both load testing and stress testing are performance tests.The two can be combined. Through the load test, determine the system performance under various workloads, the goal is to test the changes in the system performance indicators when the load increases gradually. Stress testing is to determine the bottleneck of a system or the performance points that cannot be received to obtain the maximum service level tests that the system can provide.The China Software Evaluation Center has summarized the performance test into three aspects: test the client performance of applications, test the network performance of applications, and test the server performance of applications.The purpose of the application performance test on the client is to check the performance of the client application. The test entry is the client. It mainly includes concurrency performance testing, fatigue strength testing, big data testing, and speed testing, among which concurrency Performance
Testing is the focus. The focus of application performance testing on the network is to monitor network application performance, analyze network application performance, and forecast network by using mature and advanced automation technologies. You can use tools to monitor the performance of applications on servers, or use monitoring commands of the system. For example, you can use top commands in Tuxedo to monitor resource usage. The purpose of the test is to fully monitor the performance of servers, operating systems, database systems, and applications on servers.