Shulou(Shulou.com)06/03 Report--

Software acceptance testing is the last quality inspection activity before the software is put into practical application after the end of software development. This requires the development of strict evaluation standards, and detailed work content, in order to successfully complete the test task. This paper focuses on the work of software acceptance testing. Shandong Software Evaluation Center generally divides the work into the following seven steps when conducting software acceptance testing. There are no clear requirements for the implementation steps, and readers can do it step by step according to the specific situation. 1. Software requirements analysis: understand the software function and performance requirements, software and hardware environment requirements, especially the software quality requirements and acceptance requirements. two。 Preparation of "Software acceptance Test Plan" and "Project acceptance criteria": according to software requirements and acceptance requirements, draw up test plans, test items to be tested, test strategies and acceptance criteria, and pass the plan review with customer participation. 3. Software acceptance test design and test case design: test cases are compiled and reviewed according to the Software acceptance Test Plan and Project acceptance criteria. 4. Build the test environment: establish the test hardware environment, software environment and so on. 5. Test implementation: test and record test results. The test content mainly includes the following 8 aspects, but is not limited to the following stages. (1) Software function confirmation testing: the main contents of functional testing include software installation, uninstall testing, all functional testing and boundary value testing mentioned in the user manual. Relative to the test content, the test criteria can be specified as whether the system under test can be successfully installed and uninstalled according to the description in the user document; whether all the functions mentioned in the user document can be executed smoothly, and in line with the boundary value given in the user document; whether the operation of the software system is consistent with the description in the user document. Therefore, it can be said that functional compliance testing is the most basic test of software system. (2) Security and reliability testing: user authority limit test, trace function test, shielded user operation error response test, system backup and recovery means test, multi-user operation input data validity test, abnormal situation and network fault impact test on the system. (3) ease-of-use testing: ease-of-use testing mainly focuses on the ease of learning and use, online help, the difficulty of functional operation, the clarity of software interface and so on. The test standard mainly examines whether there is online help for the operation of each function item of the software, and whether non-computer professional users can easily operate through the user manual. Its purpose is to measure the difficulty of the popularization of software system. (4) Extensibility testing: any version of the software system has a certain life cycle, and each grid needs to be upgraded for a period of time to expand its functions. In addition, some software systems also need to exchange data with other software systems. This requires testing whether the software system upgrade is convenient and whether there is a non-system data interface to facilitate data transmission. Another main task of this detection is to detect whether users can modify or add or subtract system functions by modifying configuration files or other non-programmatic ways. (5) compatibility testing: compatibility testing is an important part of software testing, which tests whether the software runs normally in different operating systems. Whether it works properly on the specified different database systems, and whether it works properly in the specified different types of hardware environment. (6) efficiency testing: with the increase of the number of local area websites and the use of wide area network, the network transmission time and access time of data have gradually become the bottleneck in the use of software, so how to improve the operation efficiency has become the focus of attention of all aspects. it has also become one of the indicators to measure the quality of software products. To carry out this test, it is highly technical, and it is necessary to know what kind of transmission protocol and what kind of transmission mode are used in the software system to be tested. Testing requires the necessary test environment and the use of dedicated network testing tools. (7) Resource occupancy test: system resources generally refer to internal and external storage, CPU, communication port, network bandwidth and other system resources. How to make rational use of system resources is closely related to the performance of the software system. For example, if the CPU utilization rate of the software system is more than 50%, or the share of memory in the system remains high, the speed of the system will be unbearable; if you occupy the communication port at will, it will make some general communication software unable to run. Similarly, if you use broadcast transmission, it will occupy the network bandwidth and reduce the communication speed of the network. All these will cause no change to the user, so that the user has to upgrade the hardware system or expand the network bandwidth. Therefore, the testing of resource share is becoming more and more important. (8) acceptance of user documentation: the user manual has a complete description of all the functions that can be called by the user; the user manual can fully understand the performance of the product by the user who normally executes the product; the user manual is easy to navigate and has a catalogue and index; all the materials in the document are not misrepresented; the description of the content of the document is consistent with the actual results of the system. The administrator manual has the identification of the software and a description of the operating environment; the administrator manual has instructions on installation and maintenance; and the administrator manual provides boundary values for normal operation. 6. Analysis of test results: analyze the test results according to the acceptance criteria, and make acceptance and test evaluation. 7. Test report: prepare defect report and acceptance test report according to the test results and submit them to the customer.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.