JP4575811B2 - Test data generation apparatus, method, and program for message processing system - Google Patents

Description

  The present invention relates to a technique for generating test data and executing a test of a message processing system in which a plurality of devices operate in cooperation while transmitting and receiving messages.

A provisioning technique is known in which a server is newly installed in a large-scale computer system in which devices such as a plurality of servers operate in cooperation, and program installation and initial setting are automatically performed on this server (for example, Patent Document 1).
JP-A-2-2016657

  However, in order to actually operate (release) a server automatically added by provisioning, the following must be confirmed. For example, it is necessary to test and confirm whether or not the added server operates normally alone or whether or not the entire system operates normally when the server passes through the added server. Conventionally, the test data created by the tester is flown and the tester confirms the results. Therefore, they are not complete and may be misunderstood. It was something I wanted.

  Furthermore, when a plurality of servers are added at the same time by provisioning, conventionally, these are released collectively. As a result, if a failure occurs simultaneously in a plurality of newly released servers, the effect on the entire system is large.

  Accordingly, an object of the present invention is to provide a technology for automatically generating highly comprehensive test data for a device newly added to a system in which a plurality of devices such as servers operate in cooperation. is there.

  A further object of the present invention is to provide a technique for automatically performing a test using automatically generated test data and verifying the result.

  An apparatus for generating test data according to an embodiment of the present invention includes a plurality of devices, and the plurality of devices receive test data from a test target device in a message processing system operating in cooperation with each other while transmitting and receiving messages. A device for generating, means for acquiring log data stored in each device from one or more devices in the message processing system, means for registering a message template including parameters, and setting the parameters Parameter input means for accepting input of parameter values, means for generating test data by setting the parameter values accepted by the parameter input means to parameters included in the message template registered by the registration means; .

  An apparatus for generating test data according to one embodiment of the present invention includes a plurality of devices, and the plurality of devices input from a preceding device in a message processing system that operates in cooperation while transmitting and receiving messages to and from each other. A device for generating test data of a test target device that outputs an output request to a subsequent device based on the request, and outputs an output reply to the previous device based on an input reply from the subsequent device, the parameter A first registration unit that accepts registration of a first template that includes an input request message template including a message and an output reply message template corresponding to the input request message template, an input request message template including a parameter, and the input request message Output request message template corresponding to the template A second registration means for accepting registration of a second template including an input reply message template including a parameter and an output reply message template corresponding to the input reply message template; and a parameter value set in the parameter A parameter input means for receiving an input; a parameter value input by the parameter input means for setting a parameter value included in the first template registered by the first registration means; and input request test data and output reply test data; Generating intermediate test data including: output request test data corresponding to the input request test data based on the intermediate test data and the second template registered by the second registration means; and the output reply test Generating an input reply test data corresponding to the over data, and means for generating a final test data.

  In a preferred embodiment, the information processing system further comprises means for acquiring log data stored in each device from one or more devices in the message processing system. The intermediate test data generation unit sets the parameter value input by the parameter input unit or the value extracted from the log data acquired by the acquisition unit to generate the intermediate test data. May be.

  In a preferred embodiment, the intermediate test data generation unit may set the parameter value input by the parameter input unit with priority over the value extracted from the log data.

  In a preferred embodiment, the input request test data is input to the test target device, and the electronic message processing system is operated to execute a test, and the test execution unit operates the electronic message processing system. Means for collecting execution result data including the generated output request, input reply and output reply, comparing the test data generated by the final test data generation means with the execution result data collected by the collection means; And a means for verifying the test result.

  In a preferred embodiment, it may further comprise a change return means for changing the environment of the message processing system and returning the changed environment to the state before the change.

  Hereinafter, an application system according to an embodiment of the present invention and a management apparatus (management server) that manages the application system will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating an overall configuration of a system according to the present embodiment. In this system, an application system 1 that executes predetermined business processing and a client 2 that is used by a customer are connected via a network 9. A management server 15 for managing this system is connected to the application system 1.

  The application system 1 includes a load balancer 10 that distributes requests by distributing requests from the clients 2, a PL server group 11A including a plurality of PL servers 11 that provide input / output interfaces to the clients 2, and various business processes (business A BL server group 12A (first group) including a plurality of BL servers 12 for executing logic, BL), and a DB server group 13A (second group) including a plurality of DB servers 13 for referring to and updating the database 14 Group) and a database (DB) 14. The PL server 11 is an interface device that provides an interface such as control (presentation logic, PL) of a screen displayed on the client 2. The BL server 12 (first device) and the DB server 13 (second device) are internal devices that execute internal processing of the application system 1.

  Each of the client 2, each PL server 11, each BL server 12, each DB server 13, and the management server 15 is configured by, for example, a general-purpose computer system, and each server 2, 11, 12, 13, described below The individual components or functions in 15 are realized, for example, by executing a computer program.

  Each PL server 11 in the PL server group 11A, each BL server 12 in the BL server group 12A, and each DB server 13 in the DB server group 13A have a common configuration, and execute the same processing (FIG. 2). That is, the server groups 11A, 12A, and 13A are multiplexed by a plurality of servers. This is to ensure fault tolerance and processing performance. In each of the server groups 11A, 12A, and 13A, the same processing is performed regardless of which server performs the processing. As a result, each PL server 11, each BL server 12, and each DB server 13 is realized by using a relatively inexpensive personal computer or the like, and load is distributed by the load balancer 10. High performance can be obtained at low cost without introducing a high-speed computer. Furthermore, this system can easily increase / decrease the number of servers 11, 12, 13 as the amount of data to be processed increases / decreases, thereby easily adjusting the processing capacity. In the present embodiment, the management server 15 confirms the normality of the operation of the application system 1, executes processing for testing the newly added servers 11, 12, and 13, and releases the server Execute the process.

  The number of PL servers 11, the number of BL servers 12, and the number of DB servers 13 in this system may be the same or different.

  In the application system 1, a request from the client 2 is transmitted in the order of the PL server group 11A, the BL server group 12A, and the DB server group 13A, and replies to this request are transmitted from the DB server group 13A to the BL server group 12A and the PL server group 11A. Is transmitted to the client 2. More specifically, the request and reply are transmitted as follows, for example.

  When the PL server group 11A receives a request message 21 (see FIG. 2) from the client 2 at the preceding stage, after one PL server 11 executes a predetermined process, an inter-server request message A23 for the BL server group 12A at the subsequent stage. (See FIG. 2) is generated and output.

  When the BL server group 12A receives the inter-server request message A23 from the preceding PL server group 11A, after one BL server 12 executes a predetermined process, the inter-server request message B25 for the subsequent DB server group 13A (FIG. 2) is generated and output.

  When the DB server group 13A receives the inter-server request message B25 from the preceding BL server group 12A, one DB server 13 executes a predetermined process for the DB. Then, an inter-server reply message B35 (see FIG. 2) for the preceding BL server group 12A is generated and output.

  In the BL server group 12A, one BL server 12 generates an inter-server reply message A33 (see FIG. 2) for the preceding PL server group 11A based on the inter-server reply message B35 from the latter DB server group 13A. And output.

  In the PL server group 11A, one PL server 11 generates and outputs a client reply message 31 (see FIG. 2) for the preceding client 2 based on the inter-server reply message A33 from the subsequent BL server group 12A. To do.

  FIG. 2 shows a detailed configuration diagram of the PL server 11, the BL server 12, and the DB server 13.

  The PL server 11 receives the client request message 21 sent from the client 2 via the load balancer 10, converts it into an inter-server request message A 23, and outputs it to any BL server 12. When the inter-server reply message A33 is received from any of the BL servers 12, it is converted into a client reply message 31 and transmitted to the client 2 via the load balancer 10.

  The PL server 11 includes a message identifier assigning unit 111, a PL processing unit 113, a status storage unit 114, a message recording unit 115, and a PL log 117, as shown in FIG.

  When receiving the client request message 21, the message identifier adding unit 111 adds a message identifier thereto. The message identifier is a unique number or character string generated by each PL server 11. For example, a telegram identifier may be generated by combining an IP address assigned to the PL server 11 and a counter value (serial number) in the server 11.

  The PL processing unit 113 executes predetermined processing according to the client request message 21 and the inter-server reply message A33. For example, for the client request message 21, a consistency check of data included in the message is performed, and an inter-server request message A23 is generated. Here, the message identifier assigned to the client request message 21 by the message identifier assigning unit 111 is assigned to the inter-server request message A23, and the client request message 21 and the inter-server request message A23 are associated with each other. For the inter-server reply message A33, a screen (Web page) displayed on the client 2 is synthesized, and a client reply message 31 including the screen is generated. Here, the message identifier assigned to the inter-server reply message A33 is not included in the client reply message 31. However, it is given to the log data of the client reply message 31 stored in the PL log 117 by the message recording unit 115.

  The status storage unit 114 will be described later.

  When receiving the client request message 21 and outputting the client reply message 31, the message recording unit 115 stores information related to each message including the message identifier of each message 21, 31 in the PL log 117. To do.

  FIG. 3 shows an example of the data structure of the PL log 17. The PL log 117 stores a transmission / reception history of messages transmitted / received by the PL server 11 to / from the client 2. For example, the PL log 117 includes a message identifier 51, a transmission server name 52, a reception server name 53, and a message content 54 as data items.

  FIG. 2B shows the configuration of the BL server 12. The BL server 12 receives the inter-server request message A23 sent from the PL server 11, converts it into an inter-server request message B, and outputs it to any of the DB servers 13. When the inter-server reply message B35 is received from any of the DB servers 13, it is converted into an inter-server reply message A33 and transmitted to the PL server 11. The transmission destination of the inter-server reply message A33 is the PL server 11 that is the transmission source of the inter-server request message A23.

  The BL server 12 includes a BL processing unit 123, a status storage unit 124, a message recording unit 125, and a BL log 127 as internal components.

  The BL processing unit 123 executes predetermined processing according to the inter-server request message A23 and the inter-server reply message B35. For example, when the inter-server request message A23 is received, predetermined business processing is executed according to the content of the telegram, and the inter-server request message B25 is generated. Here, the message identifier assigned to the inter-server request message A23 is assigned to the inter-server request message B25, and the inter-server request message A23 and the inter-server request message B25 are associated with each other. Further, when the inter-server reply message B35 is received, predetermined business processing is executed according to the contents of the telegram, and the inter-server reply message A33 is generated. Similarly, in this case, the inter-server reply message A33 is assigned the message identifier assigned to the inter-server reply message B35, and the inter-server reply message A33 and the inter-server reply message B35 are associated with each other.

  The status storage unit 124 will be described later.

  When the inter-server request telegram A23 is received and when the inter-server reply telegram A33 is output, the telegram recording unit 125 stores information related to each telegram including the telegram identifier of each telegram 23, 33 in the BL log 127. To store.

  The BL log 127 stores a transmission / reception history of messages transmitted / received by the BL server 12 to / from the PL server 11. The data structure of the BL log 127 is the same as that of the PL log 117.

  FIG. 2C shows the configuration of the DB server 13. The DB server 13 receives the inter-server request message B25 sent from the BL server 12, and executes DB processing such as reference and update of the DB 14 based on this. And based on this execution result, the reply message B35 between servers is produced | generated, and this is transmitted to BL server 12 of the transmission origin of request message B25 between servers.

  The DB server 13 includes a DB processing unit 133, a status storage unit 134, a message recording unit 135, and a DB log 137 as internal configurations.

  When the DB processing unit 133 receives the inter-server request message B25, the DB processing unit 133 executes processing such as reference and update of the DB 14 according to the content of the message. Based on the processing result, the inter-server reply message B35 is generated. Here, the message identifier assigned to the inter-server request message B25 is assigned to the inter-server reply message B35, and the inter-server reply message B35 and the inter-server request message B25 are associated with each other.

  The status storage unit 134 will be described later.

  When the inter-server request telegram B25 is received and when the inter-server reply telegram B35 is output, the telegram recording unit 135 stores information related to each telegram including the telegram identifier of each telegram 25, 35 in the DB log 137. To store.

  The DB log 137 stores a transmission / reception history of messages transmitted / received by the DB server 13 to / from the BL server 12. The data structure of the DB log 137 is the same as that of the PL log 117 and the BL log 127.

  Here, each message format is shown in FIG. As shown in FIG. 5A, the client request message 21 includes a client request body written in HTML or the like. As shown in FIG. 4B, the client reply message 31 includes a client reply text described in HTML or the like. The inter-server request telegrams 23 and 25 shown in FIG. 10C include an inter-server request text indicating the request contents and a telegram identifier. Similarly, the inter-server reply telegram 33 shown in FIG. , 35 includes an inter-server reply text indicating the reply contents and a telegram identifier.

  FIG. 5 shows a configuration diagram of the management server 15. An input device 7 such as a keyboard or a pointing device and a display device 8 such as a liquid crystal display are connected to the management server 15. The management server 15 includes, as external interfaces, an input / output device control unit 153 that controls these input / output devices, and a system interface 151 that is an interface with the application system 1.

  The management server 15 collects log data from each of the servers 11, 12, 13 and analyzes it. Further, the management server 15 performs automatic test processing such as test data generation, test execution, and test result verification on the servers 11, 12, and 13 automatically deployed in the application system 1 by provisioning or the like. Furthermore, the management server 15 performs release control for actually operating the servers 11, 12, and 13 deployed by provisioning.

  In order to realize these functions, the management server 15 has the following configuration, for example. First, the management server 15 mainly includes a log data collection unit 161, a collection log storage unit 163 that stores collected logs, and a log data analysis unit 165 that analyzes collected log data as a configuration related to log processing. With. The management server 15 mainly includes a user registration unit 171, a registration information storage unit 172, a test data generation unit 173, a test data storage unit 174, a test execution unit 175, as a configuration for automatic testing. A test result storage unit 176, a test result processing unit 177, and a DB setting change unit 178 are provided. Then, as a configuration mainly related to release control, a release management unit 181, a release condition table 182, and a status table 183 are provided. Hereinafter, each configuration will be described in detail.

  The log data collection unit 161 collects log data held by each of the servers 11, 12, and 13 of the application system 1 via the system interface 151 and stores the collected log data in the collection log storage unit 163.

  FIG. 6 shows an example of log data stored in the collected log storage unit 163. The data items of the collected log storage unit 163 are the same as those of the PL log 117, the BL log 127, and the DB log 137. The collected log data includes all logs of the client request message 21, the client reply message 31, the server request messages 23 and 25, and the server reply messages 33 and 35. Can be associated with each other. For example, the records 163a to 163f of FIG. 6 have the same message identifier 51, and thus it is understood that the records are one client request message 21 and a log of each message derived therefrom. Further, in this example, according to the transmission server name 52 and the reception server name 53, the record 163a is the client request message 21, the record 163b is the server request message A23, the record 163c is the server request message B25, and the record 163d is the server reply message. It can be seen that B35, the record 163e is the inter-server reply message A33, and the record 163f is the client reply message 31.

  The reply messages 31, 33, and 35 pass through the same PL server, BL server, and DB server as the PL server, BL server, and DB server through which the request messages 21, 23, and 25 pass. That is, a message having the same message identifier passes the same path in the upward direction from the PL server to the DB server and in the downward direction from the DB server to the PL server.

  The log data analysis unit 165 analyzes the log data stored in the collected log storage unit 163 and confirms the normality of the operation of the application system 1. For example, the log data analysis unit 165 sorts the records of log data collected using the message identifier 51 as a key, or collects a plurality of records having the same message identifier 51 as one group. Further, the log data analysis unit 165 checks the consistency of the message content 54 between records having the same message identifier 51. Then, the input / output device control unit 153 displays these analysis results on the display device 8.

  FIG. 7 is a diagram illustrating an example of a result of the log data analysis unit 165 sorting the records of the log data by the message identifier 51.

  FIG. 8 shows a record group of a telegram identifier “192.168.0.102-0845” extracted by the log data analysis unit 165. The log data analysis unit 165 further performs a consistency check on this record group. For example, in a pair of “sending server name 52 → receiving server name 53”, “client → PL *” “PL * → BL *” “BL * → DB *” “DB * → BL *” “BL * → PL *” Confirm that all of “PL * → client” exist. As a result, it is possible to confirm whether or not the inputted client request message 21 has returned the final client reply message 31 without disappearing in the middle.

  Furthermore, since the ascending message and the descending message pass through the same path, the log data analysis unit 165 checks whether the server names of the PL server and the BL server are the same. In the message content 54, it is checked whether the same value is set for a specific parameter (for example, kozaID = 1234567). Thereby, it can be confirmed whether the content of the inputted client request message 21 is inherited by each message generated thereafter.

  Further, the log data analysis unit 165 refers to the message confirmation table 60 registered in advance, and the record group having the same message identifier 51 matches the correspondence pattern of the request message and reply message registered in this table 60. It is determined whether or not to do. The electronic message confirmation table 60 is registered in advance by the user and stored in the registration information storage unit 172.

  FIG. 9 shows an example of the message confirmation table 60. In the message confirmation table 60, the target server 61, the request message content 62 received by the target server 61, and the reply message content 63 output by the target server are associated with each other. There may be a plurality of reply messages 63 that can be generated for one request message 62. In the case of FIG. 9, the reply message contents 611 to 613 are possible replies to the request message contents 601 for the PL server. Further, it is shown that the reply message contents 614 and 615 are possible as the reply to the request message contents 602 received by the BL server. Furthermore, it is shown that the reply message contents 616 and 617 can be replies to the request message contents 603 of the DB server.

  Then, the log data analysis unit 165 records the client request message 21 received by the PL server from the records having the same message identifier 51 (that is, the record 163a in which the transmission server 52 is the client and the reception server 53 is the PL server). ) And a record of the client reply message 31 (that is, a record 163f in which the transmission server 52 is a PL server and the reception server 53 is a client). Then, it is determined whether the pair of records extracted here matches any of the pair of the request message contents 601 and the reply message contents 611 to 613 in the message confirmation table 60.

  The log data analysis unit 165 similarly extracts the request / reply pair for the BL server and the request / reply pair for the DB server, and determines whether or not the pair matches the pair registered in the message confirmation table 60. To do.

  Thereby, it is possible to confirm whether or not a predetermined reply message is generated for each request message.

  Next, referring to FIG. 5 again, the configuration and processing relating to the automatic test processing will be described.

  The user registration unit 171 receives registration of user setting information input by the user using the input device 7. The user setting information received by the user registration unit 171 is registered in the registration information storage unit 172 and the release condition table 182.

  The registration information storage unit 172 stores information set by the user. In the case of FIG. 5, as the user setting information, the already described message confirmation table 60, the parameter table 70 storing the parameter values set in the test data, the template 80, and the DB setting table 90 are stored. Yes.

  FIG. 10 shows an example of the parameter table 70. That is, in the parameter table 70, a parameter 71 included in the client request message 21 and a plurality of parameter values 72 set to the parameter 71 are registered in association with each other.

  FIG. 11 shows an example of the template 80. That is, FIG. 5A shows a template A in which an input request message 82 and a generated reply message 83 corresponding thereto are associated with each communication pattern 81 for specifying a transmission / reception server. For example, if the messages to be input / output to / from the test target server are X, Y, Z, and W as shown in FIG. 5C, the template A shows the correspondence between X and W. Further, FIG. 5B shows a template B in which a telegram 84 for a preceding stage and a telegram 86 for a subsequent stage of a certain server are associated with each other for each communication pattern 85 that specifies a transmission / reception server. For example, in correspondence with FIG. 5C, the telegram 84 for the previous stage is X or W, the telegram 86 for the subsequent stage is Y or Z, and X and Y or W and Z are associated with each other.

  FIG. 12 shows an example of the DB setting table 90. The DB setting table 90 includes a data setting table 901 shown in FIG. 10A and a data return table 902 shown in FIG. Each of the data setting table 901 and the data return table 902 includes a table name 91 for setting a value, a condition 92 for setting a value, a column name 93 for setting a value, and a setting value 94 as data items. .

  When executing the test, there is a case where it is desired to temporarily change the setting of the DB 14 in order to execute the test under a predetermined condition. For such a case, a value input by the user is stored in the setting value 94 of the data setting table 901. In addition, after the setting of the DB 14 is temporarily changed and the test is executed, it is necessary to restore the setting. Accordingly, the table name 91, condition 92, and column name 93 of the data return table 902 store the table name, condition, and column name when the setting is changed, and the setting value 94 is used when the setting is changed. The value of DB 14 before the change acquired is stored.

  The test data generation unit 173 generates test data based on the log data stored in the parameter table 70, the template 80, and the collected log storage unit 163, and stores the test data in the test data storage unit 174. For example, the parameter value 72 set in the parameter table 70 is prioritized and set for the parameters included in the template 80, and the parameters whose parameter values are not set in the parameter table 70 are extracted from the log data. To set. As a result, the tester only needs to register parameter values for the parameters that he or she pays attention to. In this case, parameters that are not particularly focused are automatically set from the log data. Therefore, since values are set for all parameters in the template 80, the test will not be delayed due to incomplete test data.

  On the other hand, if all parameter values are set in the parameter table 70, log data is unnecessary. Further, when there is no parameter table 70, or when no parameter value is set in the parameter table 70, all parameter values may be acquired from log data to generate test data.

  In the present embodiment, first, test data A (see FIG. 13), which is intermediate test data, is generated based on the template A, the parameter table 70, and log data. Then, based on the test data A and the template B, test data B (see FIG. 14) which is final test data is generated. This will be specifically described below.

  First, the template A in FIG. 11A defines a pair of a request message (X) for each server and a reply message (W) that can be output from each server. Therefore, the test data generation unit 173 sets the values registered in the parameter table 70 shown in FIG. In this example, each value registered in the parameter table 70 is set in the branch ID (sitenID), account ID (kozaID), password (passward), number (item_count), and balance (zandaka).

  At this stage, no value is set for the parameter item in the template A. Therefore, the test data generation unit 173 extracts and sets a value to be set in the parameter item from any record of the log data. In this way, test data A shown in FIG. 13 is generated.

  13 includes a request message (X) 403 from the server A 401 to the server B 402 and a reply message (W) 404 from the server B to the server A for the request message (X) 403. In the example of FIG. 13, the request message (X) 403 of the test data 431 and 432 is common, and a different pattern is set as the reply message (W) 404 for this.

  Next, the template B in FIG. 11B includes a request message (X) and a request message (Y) generated by the request message, and a reply message (W) and a message from the latter stage before it is generated. A pair with the reply message (Z) is defined. Therefore, the test data generation unit 173 applies the request message (X) 403 and the reply message (W) 404 of the test pattern A of FIG. 13 to the template B, and generates messages Y and Z corresponding to each. At this time, parameters already set in the test pattern A are set in the corresponding messages Y and Z, respectively. FIG. 14 shows test data B generated by this processing.

  14 includes a request message (X) 412 for the test target server 411, a reply message (W) 413 corresponding thereto, a request message (Y) 414 for the latter stage, and a reply message (Z from the latter stage). ) 415 and one set. Here, the test data 441, 442, and 443 all share the request message (X) 412. This is because even when the same request message (X) 412 is input, a plurality of patterns can be generated for messages Y, Z, and W derived from the request message, so all patterns for normal operation are prepared. Because.

  The test data storage unit 174 stores the test data B generated as described above.

  The test execution unit 175 acquires test data from the test data storage unit 174, executes the test, and stores the test result in the test result storage unit 176. For example, the test execution unit 175 reads the test data of the test data B one by one from the test data storage unit 174 and inputs the request message (X) 412 to the test target server 411 via the system interface 151. When the request message (X) 412 is input, the test target server 411 executes predetermined processing based on the message 412. As a result, a request message (Y) is output from the test target server 411 to the subsequent server, and the subsequent servers operate accordingly. Finally, a reply message (W) is output from the test target server. Here, the test execution unit 175 obtains the messages Y, Z, and W based on the input request message (X) 412 from the log files of the test target server and the subsequent server, and performs a test in the form of associating them. The result is stored in the result storage unit 176.

  The test result processing unit 177 analyzes the test result by comparing the test result telegram stored in the test result storage unit 176 with the test data B stored in the test data storage unit 174. This analysis result is output to the display device 8.

  For example, the test result processing unit 177 includes the test data stored in the test data storage unit 174 as a combination of the input request message (X) and the message Y, Z, and W obtained as a server processing result. It is determined whether or not it matches any of B. If it matches any one, the application system 1 is considered to be operating normally. On the other hand, if none of them match, it is considered that there is some abnormality in the test target server or the subsequent server. These analysis results are displayed as a list on the display device 8, for example.

  Thereby, it is possible to automatically generate exhaustive test data, perform tests, and analyze the results simply by setting a template and necessary parameters. Furthermore, since the test execution result is displayed on the display device 8, the tester can immediately know whether the system is normal.

  The DB setting change unit 178 changes and restores the operating environment of the application system 1 in order to perform a test. For example, the DB setting changing unit 178 refers to the DB setting table 90 and temporarily changes the contents of the DB 14 via the system interface 151. For example, the DB setting change unit 178 updates the DB 14 based on the data setting table 901 (FIG. 12A). Further, when making the above setting change, the DB setting changing unit 178 sets the state before the change in the data return table 902 (FIG. 12B). After the test is completed, the data return table 902 is referred to return to the previous state.

  For example, in the case of the data setting table 901 illustrated in FIG. 12A, the DB setting changing unit 178 extracts records satisfying the condition 92 from the table set in the table name 91. Then, the column that matches the column name 93 of the record is changed to the value set in the setting value 94. Thereby, the setting of DB when performing a test can be freely changed.

  Next, the configuration and processing related to release control will be described.

  The release management unit 181 inquires the status of each server 11, 12, 13 in the application system 1 via the system interface 151. For example, the status of each server stored in the status storage units 114, 124, and 134 in each server is acquired. The status of each server 11, 12, 13 acquired here is stored in the status table 183.

  Here, the status information stored in the status storage units 114, 124, and 134 in each server will be described.

  In the case of a server newly added to the application system 1, the status “untested” is set in the status storage unit when provisioning is completed. Thereafter, when the above-described test is being executed, the status is changed to “under test” by the test execution unit 175. When it is confirmed from the test results displayed on the display device 8 that all tests have been completed normally and the test executor inputs the test completion, the status storage unit of the server stores the application A status of “Releasable” indicating that the system 1 is officially operable as a part of the system 1 is set. Further, as will be described later, when the release management unit 181 releases, the status “released” is set in the status storage unit in the released server.

  FIG. 15 shows an example of the status table 183. That is, the server name 1831 and the status 1832 are registered in the status table 183 in association with each other. The status 1832 stores the status acquired from the status storage units 114, 124, and 134 of each server.

  In addition, the release management unit 181 determines whether or not the condition set in the release condition table 182 is satisfied for the server whose status 1832 in the status table 183 is “Releasable”, and the condition is satisfied. Release the server in case. Here, in order to release a server, the release management unit 181 designates a release target server and issues a predetermined release processing command. For example, the release processing command is acquired with reference to the command table 184 included in the release management unit 181.

  FIG. 16 shows an example of the command table 184. In the command table 184, a release processing command 1842 is registered for each server type 1841. The release management unit 181 acquires and executes a release processing command according to the type of server to be released.

  FIG. 17 shows an example of the release condition table 182. That is, the release condition table 182 stores the release target server 1821 and the dependent server 1822 in association with each other. Here, the dependent server 1822 is a server that must be released in order to release the release target server 1821. That is, even if the release target server 1821 is in a state that can be released, the release target server 1821 cannot be released unless the dependent server 1822 has been released. The release condition table 182 is set in advance by a system administrator or the like.

  Next, various processing procedures in the system having the above-described configuration will be described with reference to the flowcharts of FIGS.

  First, FIG. 18 shows a processing procedure of the management server 15 when collecting and analyzing logs.

  The log data collection unit 161 collects log data accumulated in each of the servers 11, 12, and 13 in the application system 1 and stores them in the collection log storage unit 163 (S 101). The log data analysis unit 165 classifies the log data stored in the collected log storage unit 163 by using the message identifier included in each record as a key, and extracts the data by message identifier (S102). The log data analysis unit 165 refers to the message confirmation table 60 registered in advance in the registration information storage unit 172, and checks the consistency between messages having the same message identifier (S103). Here, for example, it is determined whether the reply to the request matches a predetermined pattern. Then, the analysis result is displayed and output on the display device 8 (S104).

  Thereby, in the application system 1 which operates by transmitting and receiving messages between a plurality of servers, it is possible to automatically confirm whether or not the messages transmitted and received between the servers are normal. Furthermore, each server group has multiple servers, and even when messages are exchanged through various routes, all messages can be checked without exception, and a comprehensive test must be performed. Can do.

  Next, FIG. 19 shows a processing procedure of the management server 15 when test data is automatically generated and a test is performed.

  The tester registers a test pattern template as a basis of test data and a parameter value set in the template (S201). The log data collection unit 161 collects log data from each of the servers 11, 12, and 13 of the application system 1 and stores it in the collection log storage unit 163 (S 202).

  Then, the test data generation unit 173 generates test data A, which is intermediate test data, based on the template and parameter values registered in the above process and the log data (S203). At this time, parameter values registered by the tester are set first, and values acquired from the log data are set for parameters not set by the tester. Next, the test data generation unit 173 generates test data B, which is final test data, using the test data A and the template (S204).

  Here, when executing the test by flowing the test data, when it is necessary to change the setting of the DB 14 as the test environment, the DB setting changing unit 178 refers to the DB setting table 90 registered in advance. The setting is changed (S205, 206).

  Then, the test execution unit 175 inputs a test data request message to the test target server, operates the application system 1, and performs a test (S207).

  When the execution of the test is completed, if the DB setting has been changed in step S206, the change is returned to the original state and returned to the state before the change (S208, 209).

  The test result processing unit 177 verifies the test result stored in the test result storage unit 176 by comparing with the test data stored in the test data storage unit 174 (S210). Then, the verification result is displayed on the display device 8.

  This allows the tester to automatically generate test data by registering the pattern to be tested as a template and registering important parameter values without creating a lot of test data itself. In addition, the test and the result verification can be automatically performed. Furthermore, parameter values need not be set for all parameters. That is, parameters that are not specified by the tester are extracted from the log data and automatically supplemented, so that the tester can generate test data without setting the parameter values exhaustively. This reduces the burden on the tester.

  FIG. 20 shows a release control processing procedure performed by the management server 15.

  First, the system administrator registers a release condition for releasing a newly added server (S301). The registered release conditions are stored in the release condition table 182. The release management unit 181 acquires the status of the server from the target server for release determination, and stores it in the status management table 183 (S302). If there are multiple target servers, obtain from all target servers.

  The release management unit 181 refers to the status management table 183 and determines whether there is a server that is “release available” (S303). If there is no server that is “Releasable”, the process ends (S303: No).

  On the other hand, when there is a server that is “Releasable” (S303: Yes), the release management unit 181 refers to the release condition table 182 to determine whether or not the release condition of the server is satisfied (S304). ). And when release conditions are not satisfy | filled, it complete | finishes (S304: No).

  When the release condition is satisfied (S304: Yes), the release management unit 181 acquires the release command from the command table 184 according to the type of the release target server, and transmits it to the release target server. Release is executed (S305, 306).

  By repeating the processes after step S303, when there are a plurality of release target servers, release determination and release can be performed sequentially.

  Thus, release determination is performed for each server in accordance with the release conditions for each release target server determined by the system administrator.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

  For example, in the above-described embodiment, the application system 1 has a three-layer structure of the PL server group 11A, the BL server group 12A, and the DB server group 13A, but may have two layers or four or more layers. Furthermore, the application system 1 does not necessarily have a layer structure.

1 is an overall configuration diagram of a system according to an embodiment. The detailed block diagram of PL server 11, BL server 12, and DB server 13. An example of the data structure of PL log 117, BL log 127, and DB log 137. An example of each message format. The block diagram of the management server 15. FIG. An example of log data stored in the collected log storage unit 163. An example of a result of log data analysis unit 165 sorting each record of log data by message identifier 51. Record group with message identifier “192.168.0.102-0845”. An example of a message confirmation table 60. An example of the parameter table 70. An example of the template 80. An example of the DB setting table 90. An example of test data A. An example of test data B. An example of the status table 183. An example of the command table 184. An example of the release condition table 182. The flowchart which shows the process sequence in the case of collecting and analyzing a log. The flowchart which shows the process sequence in the case of performing test data production | generation and test implementation automatically. The flowchart which shows the process sequence of release control.

Explanation of symbols

1 Application system 2 Client 10 Load balancer 11 PL server 12 BL server 13 DB server 14 DB
15 Management server 21 Client request message 23, 25 Inter-server request message 31 Client reply message 33, 35 Inter-server reply message

Claims (5)

A first server group including a plurality of servers that provide an input / output interface; a second server group including a plurality of servers that execute various business processes; and a plurality of servers that perform database reference and update When the first server group has a third server group and the database, and the first server group receives a request from a client, a request message related to the request is transmitted from the first server group to the second server group, the second server group Are transmitted sequentially from the first server group to the third server group from the first stage to the second stage, and reply messages related to the reply to the request are transmitted from the third server group to the second server group, and from the second server group to the first server group. Are sequentially transmitted from the subsequent stage to the previous server group, and the reply to the request of the client is output from the first server group. Is connected to the message processing system, a management server to perform a test for a given test server in the message processing system,
User setting information including the request message, a reply message corresponding to the request message or a template associated with the request message, and parameter values set in a plurality of parameters in the request message and the reply message, respectively. A user registration unit that accepts registration,
A test data generation unit configured to generate test data by setting the parameter value to a parameter included in the template based on the user setting information;
A test data storage unit for storing the test data generated by the test data generation unit;
Using the request message in the test data stored in the test data storage unit, a test execution unit for testing the test target server;
A test result storage unit that stores a result of the test performed by the test execution unit;
A test result processing unit that determines whether the test result stored in the test result storage unit matches the test data stored in the test data storage unit, and
The user registration unit includes, as the template, a first template in which a request message and a reply message are associated with each other as a communication pattern between servers, a request message from the previous stage as a communication pattern between servers, and the request receiving a request message that may be output to the subsequent stage is generated by message, and the reply message to the previous stage, and a second template and the reply message associated input from downstream before this reply message is generated respectively ,
The test data generating unit is included in the first template, to the parameter name and set of variables as the parameter, to determine the variables to be set by the parameter name, the parameter values to the variable set, the generated intermediate test data including the reply message output from the request message and the server under test to the test target server and is included in the intermediate test data and the second template, the parameter For the set of parameter name and variable, the variable to be set by the parameter name is determined, the parameter value is set to the variable, the request message to the test target server, and the corresponding reply message A message and a request message for the subsequent stage of the test target server; To produce the final test data including the reply message from the rear stage,
The test result processing unit responds to a request message input from the previous stage to the test target server, a reply message output from the target server to the previous stage, a request message output from the test target server to the subsequent stage, and Whether the reply message input to the test target server matches the reply message for the request message of the final test data, the request message for the subsequent stage of the test target server, and the reply message from the subsequent stage. A management server characterized by determining.
Log data collection unit for acquiring log data in which at least a transmission server, a reception server, and message contents are described from one or more servers in the message processing system. Collection for storing log data collected in the log collection unit. A log storage unit,
The test data generation unit sets the parameter value for the parameter for which the user registration unit has received the parameter value, and the parameter for which the user registration unit has not received the parameter value for the parameter. The management server according to claim 1, wherein the test data is generated by setting a value extracted from the log data as a parameter.
In order to change and restore the operating environment of the message processing system, the management server refers to the database setting table registered in advance by the user registration unit, and sets the operating environment of the database in the message processing system The management server according to claim 1, further comprising a database setting changing unit that temporarily changes the operating environment after the change and returns the operating environment after the change to the state before the change.
A first server group including a plurality of servers that provide an input / output interface; a second server group including a plurality of servers that execute various business processes; and a plurality of servers that perform database reference and update When the first server group has a third server group and the database, and the first server group receives a request from a client, a request message related to the request is transmitted from the first server group to the second server group, the second server group Are transmitted sequentially from the first server group to the third server group from the first stage to the second stage, and reply messages related to the reply to the request are transmitted from the third server group to the second server group, and from the second server group to the first server group. Are sequentially transmitted from the subsequent stage to the previous server group, and the reply to the request of the client is output from the first server group. Is connected to the message processing system for a given test server in the message processing system, the management server with the test data storage unit and the test result storage unit to a method of testing,
User setting information including the request message, a reply message corresponding to the request message or a template associated with the request message, and parameter values set in a plurality of parameters in the request message and the reply message , respectively. Accepting the registration of
Generating test data by setting the parameter value to a parameter included in the template based on the user setting information;
Storing the test data generated by the step of generating the test data in the test data storage unit;
Using the request message of the test data stored in the test data storage unit to perform a test on the test target server;
Storing the result of the test performed by the test execution unit in the test result storage unit;
Determining whether a test result stored in the test result storage unit matches the test data stored in the test data storage unit, and
The step of accepting registration of the user setting information includes, as the template, a first template in which a request message and a reply message are associated with each other as a communication pattern between servers, and a request from the previous stage as a communication pattern between servers. A second message in which a message, a request message generated by this request message and output to the subsequent stage, a reply message to the previous stage , and a reply message input from the subsequent stage before the reply message is generated are associated with each other. Accept each template,
The step of generating the test data, the included in the first template, to the parameter name and set of variables as the parameter, to determine the variables to be set by the parameter name, the parameter to the variable Including setting a value and generating intermediate test data including a request message to the test target server and a reply message output from the test target server; and included in the intermediate test data and the second template , For the set of parameter name and variable as the parameter, determine the variable to be set by the parameter name, set the parameter value to the variable, and respond to the request message for the test target server Reply message and subsequent test server And quest message consists of a step of generating a final test data including the reply message from the subsequent stage,
The determining step includes a reply message that the target server outputs to the preceding stage, a request message that the test target server outputs to the subsequent stage, and a test message that is output from the subsequent stage to the request message that is input from the previous stage to the test target server It is determined whether the reply message input to the target server matches the reply message for the request message of the final test data, the request message for the subsequent stage of the test target server, and the reply message from the subsequent stage. A method characterized by performing a test.
A first server group including a plurality of servers that provide an input / output interface; a second server group including a plurality of servers that execute various business processes; and a plurality of servers that perform database reference and update When the first server group has a third server group and the database, and the first server group receives a request from a client, a request message related to the request is transmitted from the first server group to the second server group, the second server group Are transmitted sequentially from the first server group to the third server group from the first stage to the second stage, and reply messages related to the reply to the request are transmitted from the third server group to the second server group, and from the second server group to the first server group. Are sequentially transmitted from the subsequent stage to the previous server group, and the reply to the request of the client is output from the first server group. Is connected to the message processing system, to test for a given test server in the message processing system, a computer program executed by the management server with the test data storage unit and the test result storage unit,
The computer program is stored in the management server.
User setting information including the request message, a reply message corresponding to the request message or a template associated with the request message, and parameter values set in a plurality of parameters in the request message and the reply message, respectively. Accepting the registration of
Generating test data by setting the parameter value to a parameter included in the template based on the user setting information;
Storing the test data generated by the step of generating the test data in the test data storage unit;
Using the request message of the test data stored in the test data storage unit to perform a test on the test target server;
Storing the result of the test performed by the test execution unit in the test result storage unit;
The test result storage unit test results stored in the, and determining whether the match with the test data stored in the test data storage unit, is executed,
The step of accepting registration of the user setting information includes, as the template, a first template in which a request message and a reply message are associated with each other as a communication pattern between servers, and a request from the previous stage as a communication pattern between servers. A second message in which a message, a request message generated by this request message and output to the subsequent stage, a reply message to the previous stage , and a reply message input from the subsequent stage before the reply message is generated are associated with each other. is a step of accepting an and templates, respectively,
The step of generating the test data, the included in the first template, to the parameter name and set of variables as the parameter, to determine the variables to be set by the parameter name, the parameter to the variable Including setting a value and generating intermediate test data including a request message to the test target server and a reply message output from the test target server; and included in the intermediate test data and the second template , For the set of parameter name and variable as the parameter, determine the variable to be set by the parameter name, set the parameter value to the variable, and respond to the request message for the test target server Reply message and subsequent test server And quest message consists of a step of generating a final test data including the reply message from the subsequent stage,
The determining step includes a reply message that the target server outputs to the preceding stage, a request message that the test target server outputs to the subsequent stage, and a test message that is output from the subsequent stage to the request message that is input from the previous stage to the test target server It is determined whether the reply message input to the target server matches the reply message for the request message of the final test data, the request message for the subsequent stage of the test target server, and the reply message from the subsequent stage. A computer program that is a step in which a test is performed .

Images