Because there are too many concepts in the type of software testing, I read the book to understand the information, and I find it to be very cumbersome. Sometimes I can’t distinguish several of the meanings, such as load testing, stress testing, and capacity testing. It will confuse alpha testing and beta testing. The most familiar one is regression testing, so today, I specially organize these concepts for easy viewing.
alpha test
Alpha test (α test) is a test performed by a user in a development environment, or a controlled test performed by an internal user in a company that simulates an actual operating environment. Alpha testing cannot be completed by programmers or testers . Errors found in the Alpha test can be immediately reported to the developer at the test site, and the developer can analyze and deal with it in time. The purpose is to evaluate the function, usability, reliability, performance and support of the software product. Pay particular attention to the interface and features of the product. Alpha testing can start after the end of the software product coding, or after the module (subsystem) testing is completed, or after confirming that the product reaches a certain degree of stability and reliability during the test. The relevant manuals (drafts) etc. should be prepared before the Alpha test.
beta test
Beta testing (beta testing) is a test conducted by multiple users of the software in the actual use environment of one or more users. Developers are usually not on the test site, and Beta testing cannot be done by programmers or testers. Therefore, Beta testing is a software field application conducted in an environment beyond the control of the developer . In the Beta test, the user writes down all the problems encountered, including the real ones and those recognized by the supervisor, and reports them to the developer regularly. The developer makes modifications after synthesizing the user reports, and finally delivers the software product to all users use. Beta testing focuses on product supportability, including documentation, customer training, and supporting product production capabilities. Only when the Alpha test reaches a certain degree of reliability, the Beta test can be started. Since the main goal of Beta testing is to test supportability, Beta testing should be managed as much as possible by the person in charge of product release.
Regression Testing
The purpose of regression testing is to ensure the normal function of the original test strategy and method when the program is modified. This is also a test method often used.
To put it bluntly, our testers found a bug when testing the program, and then returned it to the programmer for modification. After the programmer modified and released a new software package or a new software patch package to our testers, we had to test the program again , It has been a process of ensuring that the program runs normally when the previous bug is corrected, and will not bring new errors. Under normal circumstances, there is no need for a comprehensive test, but an effective test based on the modified situation.
Regression testing is the testing performed after the software is modified during the software maintenance phase. Its purpose is to verify that the modifications made to the software are correct.
System test type
<1>User layer
Maintainability test
Test system software and hardware implementation and convenience of maintenance functions.
Security test
Testing the security of the operation, the security of the test data, and the testing of the network security.
<2> Application layer
Performance Testing
①Load test
Pay attention to the performance indicators under various workloads, and test the corresponding output items of the system components when the load gradually increases to an overload state, such as throughput, response time, CPU load, memory usage, etc., to determine the performance of the system .
②stress test
Constantly put pressure on the system to obtain the largest server-level test provided by the system by identifying the bottleneck or unacceptable performance points of a system.
③Capacity test
Determine the maximum number of simultaneous online users that the system can handle.
④Fatigue test
Adopt the maximum number of concurrent users that the system can support under the stable operation of the system, continue to perform business for a period of time, and determine the process of processing the maximum workload intensity performance of the system through comprehensive analysis of transaction execution instructions and resource monitoring indicators.
<3> Application layer
Initial test
Verification of system core functions and basic business processes.