Using modern design technology and formal technical review can reduce the initial errors in the code, but the error always exists. If the developer can't find the error, the customer will find them. More and more software organizations recognize that software testing is one of the important elements of software quality assurance. Many software development organizations will use 30% -40% or even more project resources for testing, software testing technology and software test strategies Highly valued and extensive applications. This article does not want to be in-depth theoretical analysis on software testing technology and software testing strategies, but to list a pressure test example in a software system test phase, hoping to communicate with friends who work related to software testing through this example. First introduce the background background of the software in the instance, the software is a typical three-layer C / S architecture MIS system (client / application server / database tube), the intermediate layer is a business logic layer, the application server processes all business logic However, the application server itself does not provide load balancing capabilities, but uses the ORB (Object Request Agent) software provided by the development tool to ensure load balancing between multiple application servers. The purpose of this test is to perform a pressure test of a single application server to find the maximum number of clients that a single application server can support. The basis for testing pressure estimates is: Assume that in the actual ring, the user only enables all application servers for all business processing. The method is to test the operation of the application server according to 1 to 10 times the normal business pressure estimate.
The detailed plan of the pressure test is as follows:
Pressure test plan
1. Test Plan Name Hebei Province Public Security Traffic Management Information System Pressure Test Plan. 2, Test Content 2.1 Background This test is the pressure test in this test refers to the system load of the simulated software and hardware environment and the user's use process. For a long time to run the test software to test the reliability of the measured system, but also test the test The response time of the system.
The actual use environment of the user: ◇ The Microsoft Cluster consisting of two IBM XSeries250 PC Server; ◇ Database management system uses oracle8.1.6; ◇ Application server program and database management system running on Microsoft Cluster. ◇ There are 200 users to use client software for business processing, and the total traffic of the software is processed annually: 1.5 million business / year.
2.2 Test Item Application Server Pressure Test; 2.3 None Tests ◇ The internal function of the system's client application; the amount of data in the database on the program performance. 3, test plan 3.1 Test intensity Estimation takes the following principles when testing pressure estimates: ◇ The annual business volume is completed in 8 months, 20 working days per month, 8 hours each working day; ◇用 80-20 Principle, 80% of the business in each working day is completed in 20%, that is, 80% of the business per day is completed within 1.6 hours; test pressure estimates: about 1 million in the whole year, 15% of them The business handles each service needs to submit 7 requests for the application server; 70% of business handles each business needs to submit 5 requests for the application server; the remaining 15% of the business submits 3 requests to the application server per service. According to the previous statistics, the annual business increment is 15%, considering the need for business development in the next three years, the test needs to be done twice the existing traffic. The total number of requests per year is: (100 * 15% * 7 100 * 70% * 5 100 * 15% * 3) * 2 = 3 million times / year. The number of requests per day is: 300/160 = 1.875 million times / day. The number of requests per second is: (18750 * 80%) / (8 * 20% * 3600) = 2.60 times / sec. Under normal circumstances, the ability to apply the server to process the request should be: 3 times / second. 3.2 Test Environment Preparation 3.2.1 Preparation of Basic Hardware and Software Environment 1) Network Environment: The company's internal Ethernet, with the server's connection rate is 100m, and the connection rate with the client is 10 / 100M adaptive. 2) Use two IBM XSeries250 (1G memory) PC Server as Microsoft Cluster, install system software Windows 2000 Advance Server and Microsoft Cluster Server (MSCs). 3) Installation and configuration of the database management system: Install Oracle8.1.6 on the IBM XSeries server used, the database is configured with Oracle Fail Safe (OFS). Install the database management system and support software (including Visibroker and BDE Administrator). 4) Install the test server program. 5) The client's PC: 10 sets (PII600 / 128M RAM). 3.2.2 System Client Test Programs Writing System Client Test Using Delphi, requires test programs to implement: 1) Simulate a function of sending requests to the application server and receive response information. Two cases are required to alternately: the first, the request is included at least 10 parameters, the parameter type covers characters, the date, digital type; the received response information is not less than 1 parameter; the second, the request is not Less than 1 parameter; the received response information includes at least 10 parameters, parameter type covers characters, date, digital type. 2) The number of client test programs running on each PC must be set by parameters, the time interval (unit: milliseconds), run time (unit: hour). 3) Establish test records in the database, generate test records, and write to the database to the test records without being implemented by the application server.
The log content includes: the machine name of the test request, the client test program number, issues a request time, receive the response time, whether it is successful. Table Name: Test_log, Field Name: Machine, ID, Start_time, End_Time, Flag. 3.2.3 System This data is prepared for investigating the system's response performance, refer to the actual operational situation and development of the system after a period of time. The business table involved in business processing requires preparation of this data according to the design size. The validity of the required data records meet the system requirements, specific requirements for data validity see the database design and system design documentation. 3.3 Destructive Testing The number of client connections in the design connection is tested, adding the design frequency of the application server processing request to 1-10 times, each testing the status of the error and the ratio of the error, and the detection of whether it is unrecoverable. System design should consider implementation of load mitigation error automatic recovery in severe error. Plan time: 2 days; this time includes destructive repair and automatic recovery of time required. Record the memory and CPU usage of IBM XSeries PC Server every 10 minutes during the test, including the percentage of memory occupation of the measured program, the percentage of the memory occupancy of the database management system, and the percentage of the operating system's memory usage. 3.4 Strength Stability Test Select a load of the load than the design load (the frequency of the application server processing is 1.5 times the design frequency of the application server processing request), and performs a 24-hour stability test. 3.5 Test Methods and Tools Black Box Test Test Tools: No items - free test tools you have prepared. 3.6 Test Time Plan 3.6.1 Environment Preparation: 2 days. Among them: the basic hardware, software environment and system of this data: 1 day, system client test procedure preparation and testing: 1 day. 3.6.2 Broken Level Test: 2 days. 3.6.3 Strength Stability Test: 1 day. 3.7 Problems in Test 3.7.1 Pause Standards and React Requirements Suspension Standard: The test software frequently occur frequently in strength stability test (more than 1 time per hour). User or company requires a pause test. Startup requirements: After the debugging, the test is expected to start the test when the reliability of the test software is increased. 3.7.2 Unpredictable Issues include: ◇ Test environment is destroyed and causing tests; ◇ When the above unpredictable problem occurs, test termination, completed test content preparation test summary report, and in the report The reason for the test termination. 3.8 Test Report 2002.06.21 Test Summary Report Submission Date: 2002.06.21.3.8.1 The test document test record that should be generated (the test person in charge and personnel participating in the test); test summary report. 3.8.2 Test Summary Report The content must be included in the test software name, test item, test environment; the pressure test conclusion of the test software: response time, maximum / minimum, failure, the maximum number of normal continuous operations / The shortest time, concurrent, and the relationship between failures. 4. Personnel and Responsibilities 4.1 Responsibilities Test Engineers: Responsible for writing test plans, tape testing, record, collect, and organize test record data for testing processes, analyze the test results, and write test summary reports. Software Engineer: Responsible for writing, debug client test software; database management system installation, OFS configuration, and system's background data preparation. System Engineer: Hardware maintenance and operating system installation, MSCS configuration. General Engineer: Responsible for approving the test plan and test summary report.
