JP2012048669A - Management method and management device of load test for web system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management method of a load test in which the number of test participants can be limited for each load test.SOLUTION: A test management server 3 transmits load test notification information to each user terminal 1. The user terminal 1 displays the notification information on a display 16 according to a tool bar program 18. When a user selects the displayed load test to apply for participation in the test, the test management server 3 receives the participation application in the order of receipt until the number of participants reaches the upper limit of a range of the number of participants necessary for the load test, and registers the users in a test registrant management database 38. When a test execution period of the each load test starts, the test management server 3 transmits a test schedule file with a registered URL written thereon to the user terminals 1 operated by the registered users. Each of the user terminals 1 transmits a message to the URL specified by the test schedule file.

Description

  The present invention relates to a management method and a management apparatus for managing a load test performed on a web system operated so as to execute processing in response to a request from a user terminal received through a network.

  A network such as the Internet is a network system that connects a large number of servers that provide a certain service and a large number of user terminals that request the service in a spider web. And the server which provides a service performs the process according to the said request message by receiving the request message from each user terminal, and responds the process result to a request origin terminal. Such processing by the server is executed for each request message from the user terminal, but the number of processes that can be executed simultaneously depends on the processing capability of the server. Therefore, when request messages from many user terminals are concentrated at once, the processing load on the server exceeds the processing capacity of the server, the processing speed of the server is extremely reduced, or the server is down. Failures such as waking up can occur. Further, when a large number of request messages are concentrated on one communication path and exceed the communication capacity, a failure such as congestion of the communication path may occur. Therefore, when starting a new service on the network, prior to the start of the service, a large number of servers that provide the service through the network (a number sufficiently exceeding the maximum number of accesses assumed in the service specifications) It is necessary to test whether or not a failure has occurred by actually sending a dummy request message.

  Conventionally, such a test (hereinafter referred to as “load test”) includes a large number of virtual clients internally logically generated by a server that provides a load test service (hereinafter referred to as “load test server”). Was simultaneously sent to the test target server (hereinafter referred to as “test target server”), but recruited collaborators for the load test and actually requested from terminals owned by many collaborators. There has also been a proposal for automatically transmitting a message to a test target server (Patent Document 1).

  According to the method described in the above patent document, the address information of the test target server and the specification information of the test execution date are written in an encrypted file (connection destination information file) so that the collaborator cannot arbitrarily look into And provided to the collaborator's terminal. Then, the automatic connection program installed in the terminal reads the connection destination information file and automatically transmits a request message to the address specified in the file at the specified execution date and time.

JP 2002-132532 A

However, the automatic transmission of the request message is always executed as long as the terminal on which the automatic connection program and the connection destination information file are installed is activated at the execution date and time of each load test and is connected to the network. The number of terminals that send messages is unlimited. Therefore, an unrealistic load that far exceeds the load required for the load test may be applied to the test target server. Since the result of the load test performed in such a state is not reliable, the significance of executing the load test is lost.

  Accordingly, an object of the present invention is to provide a load test management method and management apparatus for a web system that can limit the number of test participants for each load test.

  In order to solve the above-mentioned problem, in the present invention, the server (test management apparatus) has the identification information, the destination information of the request message, the test execution period, and the required number of participants range for each load test. By referring to the first database registered in association with each other, the notification information of each load test is transmitted to the terminal. Then, the terminal that has received the load test notification information presents the notification information to the operator, and when the operator specifies one of the load tests using the input device, the identification information of the specified load test is obtained. The participation application information including it is transmitted to the server (test management device). Then, the server (test management apparatus) that has received the participation application information refers to the first database, and the number of received participation application information including the same load test identification information as the participation application information is the identification information of the load test. As long as the upper limit of the corresponding participant range is not exceeded, the destination information corresponding to the identification information and the schedule information specifying the test execution period are transmitted to the terminal that transmitted the participation application information. Then, the terminal that has received the schedule information transmits a request message including the destination information specified by the schedule information during the test execution period specified by the schedule information.

  Even if the operator of the terminal identifies one of the load tests based on the notification information and transmits the participation application information to the server (test management device), the same load test is performed. On the other hand, if the number of pieces of participation application information already transmitted from another terminal to the server (test management device) exceeds the upper limit of the participant range registered in the first database for the load test, the operator Schedule information is not transmitted to the terminal. In that case, since the operator's terminal does not send a request message regarding the load test, an unrealistic load that far exceeds the load required for the test is prevented from being applied to the test target server. The

  Therefore, according to the present invention, the number of test participants can be limited for each individual load test.

1 is a block diagram showing a schematic configuration of a network in which a load test management method for a web system according to the present invention is implemented. Table showing data structure of user database Table showing the data structure of the test load registration database Table showing data structure of test registrant management database Flow chart showing processing contents of load management system at the time of test registration Flow chart showing the processing contents of the load test toolbar program Flow chart showing the processing contents of the load test toolbar program The flowchart which shows the processing content of the load management system at the time of access from a user terminal The flowchart which shows the processing content of the load management system at the time of access from a user terminal Flowchart showing processing contents of load management system executed periodically Flow chart showing processing contents of test target device Diagram showing screen image of load test toolbar Figure showing the update permission screen Figure showing the load test entry screen Table showing data structure of test schedule file

Embodiments of a load test management method and management apparatus for a web system according to the present invention will be described below with reference to the drawings.
<System configuration>
FIG. 1 is a schematic block diagram showing a hardware configuration of a group of devices involved in such a load test management method.

  As shown in FIG. 1, the devices involved in the load test management method include a plurality of user terminals 1 (only one is shown in FIG. 1 for simplification) and a plurality of test target devices 2 ( In FIG. 1, only one unit is shown for simplicity) and one test management server 3 is included. The user terminal 1, the test target device 2, and the test management server 3 are connected to each other through the Internet N and can communicate with each other.

The user terminal 1 is a general personal computer having an Internet connection function that is owned or occupied by an individual user. Therefore, the user terminal 1 includes a CPU (Central Processing Unit) 10, a hard disk 11,
A removable disk 13, a communication device 14, a RAM (Random Access Memory) 15, a display 16 and an input device 17 are provided.

  Among these, the CPU 10 is a central processing unit that controls the entire user terminal 1.

  The RAM 15 is a main storage device in which a work area is expanded when the CPU 10 executes various processes.

  The communication device 14 is an interface with the Internet N, and a modem, a network card, a router, or the like is used depending on the type of communication medium connected to the Internet N.

  The removable disk 13 is a magnetic disk such as a flexible disk and a flexible disk drive, an optical disk and an optical disk drive such as a DVD disk and a CD-ROM, or a memory card and a card slot.

The hard disk 11 is a storage device that stores various programs and various data read and executed by the CPU 10. The various programs stored in the hard disk 11 and read and executed on the RAM 15 by the CPU 10 include a browser program 19 that is generally distributed, and a load test toolbar program 18 for the user terminal 1 to execute a load test. It is included. The load test toolbar program 18 is downloaded from the test management server 2 through the communication device 14 and the Internet N according to the function of the browser program 19 or distributed in a form stored in the removable disk 13 and installed in the startup folder in the hard disk 11. Is done. Therefore, when the main power is turned on to the user terminal 1, the toolbar program 19 is automatically activated to display a toolbar as shown in FIG. 12 in one corner of the display 16, and the user terminal 1 is shut off. It will continue to run until The load test toolbar program 18 is updated from time to time by the test administrator.
The update module 33 reflecting the latest update can be downloaded from the test management server 1 through the Internet N. Then, the load test toolbar program 18 installed in the hard disk 11 of the user terminal 1 is updated by the downloaded update module 33, whereby the update of the load test toolbar program 18 is also completed on the user terminal 1. It is.

  The display 16 displays a screen that is a result of processing by the CPU 10.

  The input device 17 is a device that inputs various commands to the CPU 10 when operated by an operator. Specifically, the input device 17 is a pointing device such as a keyboard, a mouse, or a touch panel.

  As described above, when the user terminal 1 receives the schedule information specifying the destination information and the test execution period, the terminal transmits a request message including the destination information specified by the schedule information during the test execution period specified by the schedule information. It corresponds to.

  The test target device 2 is a web server device operated by a web service provider. After the operation, the test target device 2 changes the content of the HTTP request message according to the HTTP request message transmitted from any of the terminals 1. Various types of processing are executed, and the execution result is returned to the message transmission source terminal 1. Therefore, the test target device 2 has the CPU 20, the communication device 24, the RAM 25, and the hard disk 21 connected to each other via the bus B as a hardware configuration.

  Among these, the CPU 20 is a central processing unit (computer) that controls the entire test target device 2. The RAM 25 is a main storage device in which a work area is expanded when the CPU 20 executes various processes. The communication device 24 is an interface with the Internet N.

  The hard disk 21 is a storage device that stores various programs and various data that are read and executed by the CPU 20.

  The various programs stored in the hard disk 21 and read out to the RAM 25 by the CPU 20 include programs for executing the various processes described above (WWW server programs and some CGI programs or application programs such as servlets and virtual machines). )It is included. Among these programs, the program for providing the load test target service is the test target system program 22, and the test target device 2 executing the test target system program 22 is “test target system (2, 22)”. Is. Further, the various programs stored in the hard disk 21 include a load acceptance system program 23 for recording the execution result of the load test. The test target apparatus 2 executing the load acceptance system program 23 is “load acceptance system (2, 23)”.

  The test management server 3 is a web server device as a load test management device operated by a provider (hereinafter referred to as “test administrator”) that provides a load test proxy service to the operator of the test target device 2. . Therefore, the test management server 3 has the CPU 30, the communication device 34, the RAM 35, and the hard disk 31 connected to each other via the bus B as a hardware configuration.

  Among these, the CPU 30 is a central processing unit (computer) that controls the entire test management server 3. The RAM 35 is a main storage device in which a work area is expanded when the CPU 50 executes various processes. The communication device 34 is an interface with the Internet N.

  The hard disk 31 is a storage device that stores various programs and various data that are read and executed by the CPU 30.

  Various programs stored in the hard disk 31 and read out and executed by the CPU 30 on the RAM 32 include a program for executing the above-described load test proxy service (www server program, and some CGI programs or servlets). And a load management system program 36) including an application program such as a virtual machine. The test management server 3 executing the load management system program 36 is “load management system (3, 36)”. The various data that can be stored in the hard disk 31 includes a test load registration database 37, a test registrant management database 38, and a user database 39.

  As shown in FIG. 2, the user database 39 has a record for registering personal information for each user registered as a load test cooperator with the operator of the test management server 3. Each record includes a unique user ID, a name indicating the real name, a cookie used in the current session, an IP address (fixed address or rental address), and information about the incentive recipient (eg, credit card number, Each of the fields stores prize exchange points or product discount points. When a cookie or IP address assigned to a certain user is updated, the cookie and IP address in the record corresponding to the user are updated by being overwritten with the latest one.

  As shown in FIG. 3, the test load registration database 37 has a record for registering detailed information for each load test requested to be managed by the test manager 2 by the operator of the test target apparatus 2. Each record includes “test ID” which is identification information for uniquely identifying the load test, and “load (unit: qps [query per second”) to be applied to the test target system (2, 22) in the load test. Number]) ”,“ URL ”which is destination information of the test target system (2, 22) to which the user terminal 1 should send a request message for the load test,“ test execution period ”in which the load test is executed, “Reception period” in which test participants are invited to participate in the test, and the range of the number of users (registrants) required to execute the load test. The record's number range (number of participants range) "from each field to each store, are configured. Accordingly, the test load registration database 37 is registered in the first database in which the identification information, the request message destination information, the test execution period, and the necessary number of participants range are registered in association with each other for each load test. Equivalent to.

  The application of the load test contract to the test manager of the operator of the test target apparatus 2 is performed online or offline. The operator of the test target apparatus 2 that has applied for a load test contract in this manner is referred to as a “test requester”. At the time of this application, the test requester specifies the URL, the load value, and the test execution period from the information described above, and notifies the test agent. On the other hand, the load management system (3, 36) automatically generates the test ID, the reception period, and the registrant number range.

As shown in FIG. 4, the test registrant management database 38 includes a load test executed by the test management system (3, 36) and each user (test that has been officially approved as a substitute for participating in each test). Each record has a record corresponding to “test ID”, “load”, and “test execution period” as identification information of the load test, and individual identification of the test registrant. Each field stores information “user ID” and “type” indicating whether registration is officially approved or supplementary. Accordingly, the test registrant management database 38 stores in the second database in which the personal identification information corresponding to the terminal that transmitted the participation application information and the load test identification information included in the participation application information are registered in association with each other. ,Equivalent to.

Further, when the test administrator updates the load test toolbar program 18, an update module 33 for reflecting the update on the load test toolbar program 18 on the user terminal 1 is provided by the test administrator on the hard disk. 31 and prepared for a download request by the user terminal 1.
<Processing flow>
Hereinafter, the processing executed by each of the devices 1, 2 and 3 in accordance with the programs (load test toolbar program 18, test target system program 22, load reception system program 23, load management system program 36) in relation to execution of the load test will be described with reference to FIG. The description will be made according to the flowchart of FIG.
[Processing during load test registration]
FIG. 5 shows the test load of the load test executed by the load management system (3, 36) after the contract (contract contract) for the individual load test is concluded between the test requester and the test manager. It is a flowchart which shows the registration process to the registration database 37. FIG.

  In the first step S001 after starting this process, the load management system (3, 36) is based on the URL and load value in the registration target load test specified (input or received) from the test requester. Determine the range of required number of registrants. Specifically, the load management system (3, 36) selects one of (a) browsing system, (b) search system, and (c) registration system as the processing type executed in the load test based on the URL. Classify into: Then, the load management system (3, 36) determines a lower limit value and an upper limit value of the load per registrant for each classified processing type. That is, if the processing type is a browsing system, the lower limit value is determined to be 1 qps and the upper limit value is determined to be 5 qps. If the processing type is a search system, the lower limit value is determined to be 1 qps and the upper limit value is determined to be 3 qps. If so, the lower limit is determined to be 1 qps and the upper limit is determined to be 2 qps. The reason for making the load range per registrant different depending on the processing type is based on the difference in processing load depending on the processing type even if the communication load (qps) is the same. After that, the load management system (3, 36) divides the load value designated by the test requester by the lower limit value and the upper limit value of the load per registrant, thereby obtaining the necessary number of registrants. The upper and lower limit values are determined. For example, if the designated load value is 50 qps and the designated URL is a search system, the lower limit value of the required number of registrants is 17 and the upper limit value is 50. The number range is determined to be 17-50.

  In the next S002, the load management system (3, 36) determines the acceptance period of the registration target load test. Specifically, a predetermined period preceding the test execution period received (inputted or received) from the test requester is determined as the reception period.

In the next S003, the load management system (3, 36) generates a test ID of the registration target load test, and then receives the load in the registration target load test received (inputted or received) from the test requester. A new record is stored in the test load registration database 37 in which the value of the URL, the URL, the test execution period, the registrant number range determined in S001, and the acceptance period determined in S002 are stored. When S003 is completed, the load management system (3, 36) ends all the processes at the time of load test registration.
[Process when registering user for load test]
Next, based on part of the processing flowchart of the user terminal 1 based on the load test toolbar program 18 shown in FIGS. 6 and 7, and the processing flowchart of the load management system (3, 36) shown in FIGS. A process for recruiting collaborators (participants) in the load test and registering the user who has applied for registration in the test registrant management database 38 will be described.

  As shown in FIGS. 6 and 7, the user terminal 1 (CPU 10) executing the toolbar program 19 repeatedly executes the loop processing of S101 to S105. That is, the user terminal 1 accesses the test management server (load management system) 3 in S101 and transmits an HTTP request message (information request message) for requesting new information. Then, the user terminal 1 checks whether or not the update guide information has been received from the test management server (load management system) 3 in S102, and if not, the user terminal 1 receives the test management server (load management system) in S103. 3, whether or not the load test notification information has been received is checked. If not received, in S104, it is checked whether or not the final confirmation information has been received from the test management server (load management system) 3 and received. If not, in S105, it is checked whether an activation confirmation request has been received from the test management server (load management system) 3.

  On the other hand, the test management server (load management system) 3 executes the processes shown in FIGS. 8 and 9 each time an HTTP request message for a new information request is received from the user terminal 1. Then, the test management server (load management system) 3 checks whether or not the update module 33 exists in the hard disk 31 in the first S201 after the start. Then, if the update module 33 does not exist in the hard disk 31, the test management server (load management system) 3 immediately proceeds to S205. On the other hand, when the update module 33 exists, the test management server (load management system) 3 responds to the access source user terminal 1 with a response message storing the update guide information in S202. Thereafter, in S203, the test management server (load management system) 3 waits for the access source user terminal 1 to transmit an HTTP request message (S107) for an update request within a predetermined time.

  If it is determined in S102 of FIG. 6 that the update guide information (S202) has been received from the test management server (load management system) 3, the user terminal 1 advances the process to S106. In S <b> 106, the user terminal 1 displays the update permission screen shown in FIG. 13 on the display 16 and checks the content input by the user using the input device 17. That is, the update permission screen includes a “YES” button 41 and a “NO” button 42 corresponding to update permission. When the “YES” button 41 is clicked by the input device 17 (pointing device), the user terminal 1 recognizes that the update is permitted, advances the processing to S107, and clicks the “NO” button 42. In this case, it is determined that the update has been rejected, and the process proceeds to S108. In S107, the user terminal 1 transmits an HTTP request message for an update request to the test management server (load management system) 3.

  If it is determined in S203 in FIG. 8 that an HTTP request message (S107) for an update request from the access source user terminal 1 has been received, the test management server (load management system) 3 stores the update request in the hard disk 31 in S204. A response message storing the update module 33 is returned to the access source user terminal 1. After completion of S204, the test management server (load management system) 3 advances the process to S205.

  On the other hand, when the update is rejected, the user terminal 1 accesses the server in S108 of FIG. 6 as in S101, and in S109, the update guide information (S202) as in S102. ) Is received or not. Then, the user terminal returns the process to S108 unless it receives new update guidance information. This is intended to allow only test participation using the latest toolbar 18. When new update guidance information is received (S109: Yes), the user terminal 1 returns the process to S106, and checks whether or not a new update is permitted.

  When the update is rejected as described above, the update request (S107) is not transmitted from the user terminal 1 to the test management server (load management system) 3. Accordingly, in S203, the test management server (load management system) 3 terminates the process with a timeout when an HTTP request message for an update request is not received for a predetermined time.

  In S205 of FIG. 8, the test management server (load management system) 3 refers to the test load registration database 7 and checks whether there is a load test that has entered the acceptance period. If there is no load test that has entered the acceptance period, the test management server (load management system) 3 advances the process to S215. On the other hand, if there is one or more load tests that have entered the acceptance period, the test management server (load management system) 3 performs load tests for all load tests that are currently in the acceptance period in S206. Notification information is generated and transmitted to the access source user terminal 1. That is, the test management server (load management system) 3 refers to the test load registration database 37, reads all records whose current time is included in the reception period, and “test ID” field, “ A response message storing the values of the “test execution period” field and the “acceptance period” field is returned to the access source user terminal 1 prior to the test execution period. When S206 is completed, the test management server (load management system) 3 waits for an HTTP request message (S111) for participation application to be transmitted from the user terminal 1 in S207.

  If it is determined in S103 of FIG. 6 that the load test notification information (S206) has been received from the test management server (load management system) 3, the user terminal 1 advances the process to S110. In S110, the user terminal 1 displays the load test entry screen shown in FIG. 14 on the display 16 based on the received load test notification information. In this load test entry screen, a line is associated with each load test, the value of the “test” field, the value of the “acceptance period” field, the value of the “test execution period” field, the entry check box, and the “type” ”(However, blank at the time of execution of the processing) includes a table 43 in which each column corresponds to each other and an“ OK ”button 44. That is, the user terminal 1 presents notification information to the user. Then, when the user clicks the “OK” button 44 with the check box corresponding to any load test checked using the input device 17 (pointing device), the user terminal 1 Assuming that the user intends to participate in the load test, the process proceeds to S111. On the other hand, when the “OK” button 44 is clicked in a state where none of the check boxes are checked, the user terminal 1 is in a young state when a certain time elapses without any input. Advances the processing to S104 on the assumption that the user does not intend to participate in any load test.

In S <b> 111, the user terminal 1 transmits a participation application message storing the test IDs of the load tests corresponding to all the checked check boxes to the test management server (load management system) 3. That is, the user terminal 1 transmits participation application information including the load test identification information specified by the user using the input device 17 to the test management server (load management system) 3. Thereafter, the user terminal 1 waits for a response message (S214) from the test management server (load management system) 3 in S112.

  In S207 of FIG. 8, when the participation application message (S111) from the user terminal 1 is not received for a certain time or longer, the test management server (load management system) 3 advances the process to S215 due to timeout. On the other hand, when the participation application message (S111) from the user terminal 1 is received within a certain time, the test management server (load management system) 3 advances the process from S207 to S208.

  In S208, the test management server (load management system) 3 searches the user database 39 based on the cookie or transmission source IP address included in the participation application message (S111), and operates the access source user terminal 1. Read the user ID of the user. The test management server (load management system) 3 reads out from the test load registration database 37 based on the test ID, the user ID, and the test ID for each test ID included in the participation application message received in S207. The new record including the test execution period (however, the “type” field and the “load” field are blank at the time of this processing) is stored in the test registrant management database 38.

  In next S209, the test management server (load management system) 3 specifies one of the test IDs in all new records registered in the test registrant management database 38 in S208.

  In the next S210, the test management server (load management system) 3 registers the total number of records (number of registrants) including the test ID specified in S209 registered in the test load registration database 37 for the test ID. Check whether the upper limit of the number of people has been exceeded. If the former still does not exceed the latter, the test management server (load management system) 3 registers a “official” value in the “type” field in the new record including the test ID in S211. To do. In other words, the test management server (load management system) 3 is configured so long as the number of pieces of participation application information including the same load test identification information does not exceed the upper limit of the participant range corresponding to the load test identification information. The personal identification information corresponding to the user terminal 1 that has transmitted the participation application information, the load test identification information included in the participation application information, and the information indicating that it is regular registration are associated with each other in the second database. sign up.

  On the other hand, when the number of registrants exceeds the upper limit, the test management server (load management system) 3 becomes “substitute” in the “type” field in the new record including the test ID in S212. Register the value. That is, the test management server (load management system) 3 determines that if the number of pieces of participation application information including identification information of the same load test exceeds the upper limit of the participant range corresponding to the identification information of the load test, The personal identification information corresponding to the user terminal 1 that transmitted the application information, the load test identification information included in the participation application information, and the information indicating that it is an auxiliary registration are registered in the second database in association with each other. To do.

Upon completion of S211 or S212, has the test management server (load management system) 3 completed the processing of S210 to S212 for the test IDs in all new records registered in the test registrant management database 38 in S208 in S213? Check if. If the processes in S210 to S212 have not been completed for the test IDs in all new records, the test management server (load management system) 3 returns the process to S209. On the other hand, if the processing of S210 to S212 has already been completed for test IDs in all new records, each test ID in all new records registered in the test registrant management database 38 in S208 in S214. In addition, the reception response message storing the value of the “type” field registered in S211 or S212 is returned to the access source user terminal 1. When S214 is completed, the test management server (load management system) 3 performs the process in S2.
Proceed to step 15.

  In S112 of FIG. 6, upon receiving the acceptance response message (S214) from the test management server (load management system) 3, the user terminal 1 in S113, for each test ID included in the response message received in S112. The value of “type” is displayed in the “type” column of the table 43 in the load entry screen (FIG. 14). When S113 is completed, the user terminal 1 advances the process to S014.

  In S215 of FIG. 9, the test management server (load management system) 3 operates the access source user terminal 1 by searching the user database 39 based on the cookie or the transmission source IP address included in the information request message (S111). Read the user ID of the user who Then, the test management server (load management system) 3 reads all test IDs corresponding to the read user ID from the test registrant management database 38. Then, the test management server (load management system) 3 refers to the test load registration database 37 and determines whether there is a load test whose acceptance period has expired among the load tests corresponding to all the read test IDs. Check. The test management server (load management system) 3 ends the entire process if there is no load test whose acceptance period has expired, but performs processing if there is one or more load tests whose acceptance period has expired. Proceed to S216.

  In S216, the test management server (load management system) 3 specifies one of all test IDs corresponding to the load test determined to have completed the acceptance period in S215.

  In the next S217, the test management server (load management system) 3 refers to the test registrant management database 38, and the total number of records (number of registrants) including the test ID specified in S216 is related to the test ID. It is checked whether or not the lower limit of the registrant number range registered in the test load registration database 37 is satisfied. If the former satisfies the latter, the test management server (load management system) 3 in S218 confirms the final confirmation information of the activation time of the toolbar, that is, the test load registration database 37 for the test ID specified in S216. The final confirmation information specifying the test execution period registered in is transmitted to the access source user terminal 1. On the other hand, when the former does not satisfy the latter, the test management server (load management system) 3 transmits final confirmation information notifying the termination of the load test to the access source user terminal 1 in S219. When S218 or S219 is completed, the test management server (load management system) 3 advances the process to S220.

  In S220, the test management server (load management system) 3 checks whether or not the processes in S216 to S219 have been completed for all test IDs corresponding to the load test determined to have completed the acceptance period in S215. If the processes from S216 to S219 have not been completed for all the test IDs, the test management server (load management system) 3 returns the process to S216. On the other hand, when the processes of S216 to S219 are completed for all the test IDs, the test management server (load management system) 3 ends all the processes.

In S104 of FIG. 6, when any final confirmation information (S218, S219) is received, the user terminal 1 displays the contents of the received final confirmation information (load test suspension and toolbar activation time) in S114. Display on the toolbar. When S114 is completed, the user terminal 1 advances the process to S105.
[Process during load test execution]
Next, the rest of the processing flowchart of the user terminal 1 based on the load test toolbar program 18 shown in FIG. 7, the processing flowchart of the load management system (3, 36) shown in FIG. 10, and the load acceptance system (2) shown in FIG. , 23), a process for executing the load test will be described.

  The processing in FIG. 10 is periodically interrupted, for example, every hour. Then, in the first S301 after the start, it is checked with reference to the test load registration database 37 whether there is a load test that is currently in the execution period. If there is no test that has yet entered the execution period, the test management server (load management system) 3 ends all the processes. On the other hand, if there is a test that has entered the execution period, the test management server (load management system) 3 sends an information request message (S101) within a predetermined fixed period (for example, 10 seconds) in S302. For each user terminal 1 that has transmitted, the user database 39 is searched based on the cookie or the source IP address included in the information request message, and the user ID of the operating user is read. Then, the test management server (load management system) 3 refers to the test registrant management database 38 and includes the read user ID, the value of “type” is “official”, and the current test execution period is entered. If there is a record that exists, an activation confirmation request message is transmitted to the access source user terminal 1.

  If it is determined in S105 in FIG. 7 that the activation confirmation request message (S302) has been received, the user terminal 1 transmits a response message to the test management server (load management system) 3 in S115. Thereafter, the user terminal 1 waits for reception of a test schedule file (S305) from the test management server (load management system) 3 in S116.

  In 303 of FIG. 10, the test management server (load management system) 3 indicates that the cumulative number of response messages received within a predetermined time (for example, 1 second) after completion of S302 or S304 enters the execution period in S301. It is checked whether or not the load test determined to satisfy the registrant number range registered in the test load registration database 37. That is, the test management server (load management system) 3 checks whether the user terminal 1 corresponding to the personal identification information corresponding to the identification information of the load test that has reached the execution period is activated.

  If the cumulative number of response messages still does not satisfy the registrant number range, the test management server (load management system) 3 in S304 receives an information request message (for example, 1 second) within a predetermined period (for example, 1 second). For each user terminal 1 that has transmitted S101), the user database 39 is searched based on the cookie or the source IP address included in the information request message, and the user ID of the operating user is read. Then, the test management server (load management system) 3 refers to the test registrant management database 38, includes the read user ID, the value of “type” is “substitute”, and enters the current test execution period. If there is an existing record, a connection confirmation request is transmitted to the access source user terminal 1. When S304 is completed, the test management server (load management system) 3 returns the process to S303.

  As a result of repeating the processes of S303 and S304, when it is determined that the cumulative number of received response messages satisfies the required range (S303: Yes), the test management server (load management system) 3 In order to satisfy the load value registered in the test load registration database 37 for each load test, the load is distributed evenly as much as possible to all the registrants whose responses are received in S303. The load value for each registrant is registered in the test registrant management database 38.

Specifically, the test management server (load management system) 3 divides the load value registered in the test load registration database 37 for the load test by the maximum value of the registrant number range, thereby The lower limit of the load per person corresponding to the test processing type is calculated, and the calculated load is assigned to all registrants whose responses have been received in S303. Next, when a surplus occurs in the load values registered in the test load registration database 37 as a result of the assignment, each registrant is registered in a predetermined order (for example, the order in which responses are received in S303). A load value is assigned in units of a predetermined unit from the surplus load. The surplus load is assigned until there is no surplus load.

  For example, when the load value registered in the test load registration database 37 is “50 qps” and the registrant number range is “17 to 50 people”, the load per person corresponding to the processing type of the load test is calculated. The lower limit is “1 qps”. Accordingly, when the allocation unit of the surplus load is “1 qps”, the surplus load does not occur if the number of registrants who received the response in S303 is “50”, but the number of registrants is “40”. Therefore, a surplus load of “10 qps” is generated, so that “2 qps” is assigned to the first to tenth registrants, and only “1 qps” is assigned to the other 30 registrants. If the number of registrants is “25 people”, a surplus load of “25 qps” is generated, so that a total of “2 qps” is allotted. Further, if the number of registrants is “20”, a surplus load of “30 qps” is generated. Therefore, even if a surplus load of “1 qps” is assigned to all of them, “10 qps” still remains. On the other hand, the surplus load in the second round is assigned. Eventually, a total of “3 qps” is assigned to the first to tenth registrants, and “2 qps” is assigned to the other ten registrants.

  After performing the above load assignment and registration, the test management server (load management system) 3 assigns each registrant as a response to the response message (S115) received from the user terminal 1 operated by each registrant. A test schedule file (see FIG. 15) in which the load value, test execution period, URL of the test target system (2, 22), test ID, and user ID of the registrant are described is generated and encrypted. And individually transmitted to the user terminal 1 operated by each registrant. That is, the test management server (load management system) 3 refers to the second database, corresponds to the information indicating that the registration is normal, corresponds to the personal identification information corresponding to the load test identification information, and When the number of user terminals 1 being activated and the number of such user terminals 1 are insufficient for the lower limit of the participant range corresponding to the identification information of the load test, the number is associated with information indicating that the registration is substitute Address information corresponding to the load test identification information and corresponding to the personal identification information corresponding to the load test identification information, and specifying the destination information and the test execution period corresponding to the load test identification information included in the participation application information to the active user terminal 1 The schedule information is transmitted to the user terminal 1.

  When S305 is completed, the test management server (load management system) 3 completes all the processes.

  The user terminal 1 that has received the test schedule file (S305) in S116 of FIG. 7 decrypts the test schedule file received in S116 in S117. Since the test schedule file is encrypted so that it can be decrypted only by the latest version of the toolbar program, the operator of the user terminal 1 that has received the test schedule file steals the URL of the test target system (2, 22). I can't. Therefore, the confidentiality of the URL of the test target system (2, 22) before release is maintained.

In next S118, the test management server (load management system) 3 sends an HTTP request message to the URL specified in the file at a frequency corresponding to the load (qps) specified in the test schedule file. Keep sending. In next S119, the test management server (load management system) 3 checks whether or not the test execution period specified in the test schedule file received in S116 has expired. If the test execution period has not yet expired, the test management server (load management system) 3 returns the process to S118. On the other hand, when the test execution period has expired, or the input device 17
When the load test is forcibly terminated by the user's operation using, the test management server (load management system) 3 advances the process to S120. In S120, the test management server (load management system) 3 waits for an incentive notification (S405) from the test target apparatus 2.

  As the test target system (2, 22), the test target device 2 checks whether or not the HTTP request message (S118) for the load test is received from the user terminal 1 in S401 in FIG. If not received, the process proceeds directly to S403. If a message is received, the process requested by the message is executed and a reception log is recorded in S402. Then, the process proceeds to S403.

  In S403, the test target apparatus 2 checks whether the test execution period of the load test for the test target system (2, 22) has expired as the load receiving system (2, 23), and the test execution period has yet expired. If not, the process returns to S401, and if the test execution period has expired, the process proceeds to S404.

  In S <b> 404, the test target apparatus 2 communicates with the test management server 3 as the load reception system (2, 23) and accesses the test registrant management database 38. Then, the test target device 2 collates the contents of the test registrant management database 38 with the reception log.

  In next step S405, the test target apparatus 2 provides an incentive corresponding to the distributed load to the registrant who has transmitted the load as planned in the test registrant management database 38 as a result of the collation in S404. And notify the registrant who has not transmitted the load as planned without incentive. At the same time, the test target terminal 2 sends the same notification to the test management server 3 and requests the registrant who has incentive to give the incentive. When S405 is completed, the test target apparatus 2 ends all the processes.

  When receiving the incentive notification (S405) from the test target apparatus 2 in S120 of FIG. 7, the user terminal 1 in S121, when the content of the incentive notification received in S120 (present or absent, and there is an incentive) Is displayed on the load test toolbar. When S121 is completed, the user terminal 1 returns the process to S101.

  As described above, according to the present embodiment, even if the load test toolbar program 18 is executed on the user terminal 1 that is owned or occupied by the user and is registered in the user database 39, Rather than being automatically forced to participate in all load tests registered in the load management system 36, the test execution period of each load test is recognized in advance, and this is taken into consideration and Participation can be determined independently (S111). Accordingly, since each user can know the execution period of the load test in which he / she participates, the user terminal 1 and the load test toolbar program 18 are surely activated during the execution period of the load test. Can do. This increases the probability that the required number of user terminals 1 will participate in the load test within the actual test execution period, thereby reducing the possibility that the load test will be unsuccessful and increasing the reliability of the result of the load test. .

In addition, according to the present embodiment, since it is possible to participate in the load test only by the load test toolbar program 18 having the latest update (S106 to S109), it depends on the difference in the version number of the load test toolbar program 18. Malfunction or system under test (
2, 22) URL leakage can be prevented.

  Further, according to the present embodiment, the test registrant number range is automatically determined according to the total load and the processing type required for each load test designated by the test requester (S001). If the total number of applicants who want to participate in the test does not reach the test registrant number range during the acceptance period, the load test result is not reliable, and the load test is canceled (S219). In addition, users who apply for test participation are officially registered on a first-come-first-served basis, but if the total number of registrants exceeds the upper limit of the test registrant number range during the acceptance period, a significant amount of load is distributed to each participant. If it becomes impossible to do so, or if it is attempted to assign a significant amount of load to all participants, the total amount of load will exceed the necessary amount, so formal registration acceptance is closed (S210). However, since it is left to the user's conscience whether or not the officially registered user turns on the main power supply to the user terminal 1 and activates the load test toolbar program 18 during the test execution period, it is not necessarily officially registered. Not all the users who have been turned on the main power supply to the user terminal 1 and start the load test toolbar program 18 during the test execution period, the number of registrants actually participating in the load test falls below the test registrant number range. It can happen. Therefore, in this embodiment, the user who applied for participation after closing the acceptance of the official participation registrant is registered as a substitute (S212), and the user terminal 1 during the test execution period among all the officially registered users. If the number of persons who turned on the main power supply and started the load test toolbar program 18 falls below the test registrant number range, the number of registrants is increased (S304), and the number of persons required for the load test is increased. Participants are secured (S303).

  In this way, to the users (formal registrants and registrants who have been moved up) confirmed that the main power is turned on to the user terminal 1 and the load test toolbar program 18 is started in the execution period of each load test. On the other hand, the load is distributed as evenly as possible according to the number of people (S305). As a result, the amount of HTTP request messages transmitted to the test target devices (test target systems 2 and 22) via various communication paths is equalized, so that the adverse effect that the load is concentrated only on a specific communication path is prevented. Therefore, it is possible to perform a load test that approximates the actual load condition.

DESCRIPTION OF SYMBOLS 1 User terminal 2 Test object apparatus 3 Test management server 10 CPU
11 Hard Disk 14 Communication Device 16 Display 17 Input Device 18 Load Test Toolbar Program 20 CPU
21 Hard Disk 22 Test Target System 23 Load Acceptance System 24 Communication Device 30 CPU
31 Hard Disk 34 Communication Device 36 Load Management System 37 Test Load Registration Database 38 Test Registrant Management Database 39 User Database

Claims (6)

A load test management method for testing the operation of a web system by automatically transmitting a request message from a terminal to a web system that executes predetermined processing in response to a request message received from a terminal via a network,
For each load test, the server refers to the first database in which the identification information, the destination information of the request message, the test execution period, and the required number of participants range are registered in association with each other for each load test. Send notification information to the device,
The terminal that has received the load test notification information presents the notification information to the operator, and among the load tests notified by the notification information, the load test identification information specified by the operator using the input device Including participation application information to the server,
The server that has received the participation application information refers to the first database, and the number of participation application information received including the same load test identification information as the participation application information corresponds to the load test identification information. As long as the upper limit of the range is not exceeded, the destination information corresponding to the identification information and the schedule information specifying the test execution period are transmitted to the terminal that transmitted the participation application information,
A load test management method for a web system, wherein a terminal that receives the schedule information transmits a request message including destination information specified by the schedule information during a test execution period specified by the schedule information. . 2. The web system according to claim 1, wherein the test management server transmits, for each load test, notification information of the load test to a terminal prior to a test execution period registered in the first database. Load test management method for. The server that has received the participation application information refers to the first database, and the number of participation application information that includes the same load test identification information as the participation application information corresponds to the load test identification information. Unless the upper limit of the range is exceeded, personal identification information corresponding to the terminal that transmitted the participation application information and load test identification information included in the participation application information are registered in the second database in association with each other. When the execution period of each load test registered in the first database is reached, the schedule information is referred to the terminal corresponding to the personal identification information corresponding to the identification information of the load test with reference to the second database. The load test management method for the web system according to claim 2, wherein transmission is performed. The server that has received the participation application information refers to the first database, and the number of participation application information that includes the same load test identification information as the participation application information corresponds to the load test identification information. Unless the upper limit of the range is exceeded, the personal identification information corresponding to the terminal that sent the participation application information, the load test identification information included in the participation application information, and the information indicating that it is regular registration When the number of participation application information received including the same load test identification information as the participation application information exceeds the upper limit of the participant range corresponding to the load test identification information. , Personal identification information corresponding to the terminal that transmitted the participation application information, load test identification information included in the participation application information, and information indicating that the registration is a substitute Are registered in the second database in association with each other, and when the execution period of each load test registered in the first database is reached, the load test is performed by referring to the first database and the second database. Checks whether the terminal corresponding to the personal identification information corresponding to the identification information is activated, corresponds to the information indicating that the registration is normal, and corresponds to the personal identification information corresponding to the identification information of the load test. In addition, when the number of terminals being activated and the number of such terminals are insufficient for the lower limit of the participant range corresponding to the identification information of the load test, they are associated with information indicating that the registration is substitute. To the number of terminals corresponding to the identification information of the load test and corresponding to the identification number of the load test and corresponding to at least the number of shortages being activated. Managing load test for the web system according to claim 3, wherein transmitting the Lumpur information. 2. The load test management method for a web system according to claim 1, wherein the server calculates the number range of participants based on a load amount required for each load test. A load test management device for testing a web system operation by automatically transmitting a request message from a terminal to a web system that executes predetermined processing in response to a request message received from a terminal through a network,
A storage device storing a first database in which identification information, destination information of the request message, test execution period, and necessary number of participants are registered in association with each other for each load test;
Communication connected to a terminal that transmits a request message including the destination information specified by the schedule information during the test execution period specified by the schedule information when receiving the schedule information specifying the destination information and the test execution period via the network Equipment,
By referring to the first database, generating notification information of each load test, transmitting the generated load test notification information to the terminal through the communication device, and by the operator among the load tests notified by the notification information When the participation application information including the identified load test identification information is received from the terminal through the communication device, the number of received participation application information including the same load test identification information as the participation application information is the identification information of the load test. A processing device that transmits the destination information corresponding to the identification information and the schedule information that specifies the test execution period to the terminal that transmitted the participation application information, unless the upper limit of the participant range corresponding to the A load test management device for a web system.

Images