JP2007102665A - Check device of requester program and test value input support device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an input support device capable of easily testing a program of a requester computer, and a check device testing a program of a requester computer using a value inputted by such input support. <P>SOLUTION: An acquisition means 4 acquires an argument of a method designated and its type, and when a message generated by a requester 51 is captured by a given test value, a SOAP (simple object access protocol) message type name acquisition means 7 acquires a type name from a body part. A file acquisition means 8 acquires WSDL (Web services description language) from a SOAP header part. A type information extraction means 100 specifies and extracts a message for input and output from a WSDL tree as corresponding message type information. A test value input prompting means 11 displays the acquired argument and the type thereof to prompt an operator to input a test value. An expected value input support means 12 displays corresponding message type information to prompt input of a message value expected to be exchanged to the input of the test value, and stores, upon input thereof, the input value as an expected value. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an input support device, and more particularly to input support using WSDL (Web Services Description Language).

  2. Description of the Related Art Today, web services are known in which business data is exchanged between computers by sending and receiving SOAP (Simple Object Access Protocol) messages between computers using HTTP. In such a web service, the service providing computer is called a provider computer, and the service using computer is called a requester computer. When using the service, it is necessary to create a requester program for creating a message to be transmitted to the provider computer.

  In the conventional requester program check, an HTTP proxy server is provided between the requester computer and the provider computer, and a SOAP message exchanged between the two is extracted by the proxy server, and this is visually observed by a human. In response to an input to the requester computer, it is determined whether or not a desired message is exchanged between the requester computer and the provider computer.

  However, the above check method has the following problems.

  (1) The SOAP message exchanged between the two needs to be analyzed for the number of tests, which is complicated.

  (2) Even after the test is completed, when the program of the provider computer is upgraded, it is necessary to analyze the SOAP message again. In web services, such version upgrades may be made frequently.

  Note that Patent Document 1 discloses using the difference data of the WSDL file before and after the change for the requester program in the client computer as the correction method when the interface of the web service is changed. Once you have not created the correct requester program, you cannot use it.

SUMMARY OF THE INVENTION An object of the present invention is to provide an input support apparatus that can easily test a requester computer program. It is another object of the present invention to provide a check device that tests a program of a requester computer using a value input by such input support.

  1) A requester program check device according to the present invention is a requester program check device for checking an object-oriented requester program used in a requester computer that makes a request to a provider computer that provides a web service, wherein 1) the requester Input request means to display all requester classes and target methods for the program and prompt the operator to specify the requester class and target method to be tested. 2) If specified, scan the requester class using the reflection API. To obtain the "return value type", "method name", "number of arguments", and "argument type" of the specified method, and scan the source code using this to match the method information. Get the name of the argument of the specified Method argument acquisition means for storing as argument information of the method, 3) argument candidate storage means for storing a plurality of value candidates for each argument type, and 4) value candidates for each argument type acquired from the argument candidates Candidate assigning means arbitrarily extracting and giving to the requester program as set information, 5) When a request message is given from a request message capturing device that captures a request message transmitted by the requester program to the provider computer, its body part A SOAP message extracting means for extracting a SOAP message, 6) a message type name acquiring means for analyzing a tree structure of the SOAP message and acquiring a type name of the message, and 7) an IP including the given request message From the packet, specify the URI of the provider computer. 8) WSDL file acquisition means for acquiring the WSDL file of the provider program in the provider computer from the specified URI, 8) Tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of the XML element 9) For the operation specified by the SOAP message type name in the tree structure of the acquired elements, refer to the port type definition part, specify the message for input and output, and specify the type of the message. , Type information extracting means for extracting as message type information corresponding to the specified method, 10) displaying the argument type based on the argument obtained by the method argument obtaining means and the type information of the argument, Test value input prompting means for prompting test value input, 11) The message type information of the input message is displayed on the screen, and the requester program is prompted to create a request message for the input of the test value. A request expected value acquisition means for performing, 12) displaying the type information of the message for output on the screen, and when the request message created by the requester program is given to the test target input, the provider Prompt for input of response message expected to be created by computer, and when input, expected response value acquisition means for storing as expected response value, 13) actual request message created by request program for said test target input and Compare the request expectation value and match 14) When the actual request message is given to the provider computer, the actual response message that is received by the requestor as a response is compared with the expected response value, and the expected response value is notified. Is provided with response expected value comparison means for informing.

  In this way, candidate values for each of the obtained argument types are arbitrarily extracted from the argument candidates, given to the requester program as set information, a SOAP message is generated, WSDL is obtained from the header information, and SOAP is obtained. The operation name is specified from the message, the request message and response message type for the operation is specified from the WSDL, and this is displayed and tested for input support. Further, when a test value is input, an actual message exchanged is compared with the expected value, and a notification is given if they do not match. Therefore, in the test of the requester program, it is possible to perform the test even if the person who tests each input value is not understood by the person who tests the message destination in the requester program. .

  2) An input support apparatus according to the present invention is a value input support apparatus for checking a requester program to be used in a requester computer that makes a request to a provider computer that provides a web service, and 1) from the requester program Specified prompting means for extracting all requester classes and target methods, displaying them in a list, and prompting the operator to specify the requester class and target method to be tested. 2) When the above specification is made, the specified requester class is displayed. An acquisition means for scanning and acquiring an argument for calling a specified method and its type, and 3) arbitrarily extracting a value candidate for each type of argument registered in advance for the acquired argument, and a test candidate Test candidate value generating means to be given to the requester computer as a value; 4) the requester computer When a captured request message is given from a message capture device that captures a message exchanged between the message and the provider computer, a SOAP message type name is acquired from the SOAP message in the body part of this message Means, 5) a WSDL file acquisition means for specifying a URI of the provider computer from an IP packet including the captured request message, and acquiring a WSDL file of a provider program in the provider computer based on the specified URI; 6) A WSDL file tree structure obtaining means for obtaining a tree structure of each element by analyzing the tree structure of the obtained WSDL file, and 7) identified by the SOAP message type name among the tree structures of the obtained elements Type information extraction means for identifying messages for operation input and output and extracting the message type as message type information corresponding to the specified method. 8) Obtained by scanning the requester class Test value input prompting means for prompting the operator to input a test value for the argument and its type, 9) Display the corresponding message type information on the screen for the specified method, and input the test value On the other hand, it is provided with an expected value input support means for prompting input of a message value expected to be exchanged between the requester computer and the provider computer, and storing it as an expected value when input.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the type of request message and response message of the operation from WSDL, and providing input support when displaying and testing this, in the requester program test, what type each input value is Even if the person who tests the message destination in the requester program does not understand it, the test value can be easily input.

  3) A check device according to the present invention includes 1) an input support device according to claim 2, 2) test execution means for giving the test value to the requester computer, and 3) the requester computer and the provider computer for the test value. When the message capturing device captures a message exchanged between them, the message capturing device includes a comparison unit that compares the message with the expected value. Therefore, in the test of the requester program, it is easy to execute the test even if the person who tests each input value is not understood by the person who tests the message destination in the requester program. .

  4) In the checking device according to the present invention, the message exchanged between the requester computer and the provider computer is a request message given from the requester computer to the provider computer, and the expected value input support means is used for input of the operation. The message type information of the message is displayed on the screen, and the request message expected to be created by the requester program is prompted for the input of the positive test value. Therefore, the request message can be easily tested.

  5) In the check device according to the present invention, the message exchanged between the requester computer and the provider computer is a response message given from the provider computer to the requester computer, and the expected value input support means The message type information is displayed on the screen, and when the request message created by the requester program is given to the test target input, the input of the response message expected to be created by the provider computer is prompted. Therefore, the response message test can be easily executed.

  6) The check method according to the present invention causes the computer to execute the following steps: 1) the step of extracting all requester classes and target methods from the requester program; 2) the extracted requester classes and target methods; Step that prompts the operator to specify the requester class and target method to be tested by displaying a list on the monitor. 3) When the requester class and target method to be tested are specified by the operator, the specified requester class is scanned. Step of acquiring an argument for invoking a specified method and its type, and 4) arbitrarily extracting a value candidate for each type of argument registered in advance for the acquired argument as a test candidate value Providing to the requester computer, 5) from the requester computer Capturing a message exchanged with the provider computer, 6) obtaining an XML element of the next layer of the body part from the SOAP message of the body part of the captured message as a type name of the message, 7 ) Specifying the URI of the provider computer from the IP packet including the captured request message, and acquiring the WSDL file of the provider program in the provider computer based on the specified URI; 8) the tree of the acquired WSDL file Analyzing the structure to obtain a tree structure of each element; 9) identifying an input message and an output message of the operation identified by the SOAP message type name from the obtained tree structure; Extracting the type of a message as message type information corresponding to the specified method, 10) prompting an operator to input a test value for the argument obtained by scanning the requester class and its type; 11) Analyze the tree structure to obtain the tree structure of each element, specify the message for input and output of the operation specified by the SOAP message type name, and specify the type of the message as the specified A step of extracting the message type information corresponding to the method, 12) displaying the message type information on the screen, and receiving the test value is expected to be exchanged between the requester computer and the provider computer. Prompt for message value and store it as expected value when input, 13) Step of providing a serial test value to the requestor computer, 14) relative to the test value and capture the messages exchanged between the requestor computer and the provider computer, the step of comparing the expected value and the message.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the request message and response message types for the operation from WSDL, and providing input support when displaying and testing them, what type each input value is in the requester program test? It can be easily tested even if the person who tests the message destination in the requester program does not understand.

  7) A program according to the present invention is a check for checking a requester program used by a requester computer using a computer connected to both a provider computer that provides a web service and a requester computer that requests the provider computer. A program stored as an apparatus, causing the computer to execute the following steps. 1) Step to extract all requester classes and target methods from the requester program, 2) List the extracted requester classes and target methods on the monitor, and prompt the operator to specify the requester class and target method to be tested Step 3) When the requester class and the target method to be tested are specified by the operator, scanning the requester class to obtain an argument for calling the specified method and its type, 4) the acquisition Arbitrarily extracting candidate values for each type of argument registered in advance, and providing them to the requester computer as test candidate values, and 5) capturing a message exchanged from the requester computer to the provider computer. Step 6) The captured message Obtaining the XML element of the next layer of the body part from the SOAP message of the body part as the type name of the message, and 7) specifying the URI of the provider computer from the IP packet including the captured request message Acquiring a WSDL file of a provider program in the provider computer based on the specified URI, 8) analyzing a tree structure of the acquired WSDL file and acquiring a tree structure of each element, 9) A step of specifying an input message and an output message of the operation specified by the SOAP message type name in the acquired tree structure, and extracting the type of the message as message type information corresponding to the specified method 10) said request A step of prompting an operator to input a test value for an argument obtained by scanning a class and its type; 11) analyzing the tree structure to obtain a tree structure of each element; and the SOAP message type name A message for identifying the input and output of the operation specified in (2), and extracting the message type as message type information corresponding to the specified method; 12) displaying the message type information on the screen And prompting the input of a message value expected to be exchanged between the requester computer and the provider computer with respect to the input of the test value, and storing it as an expected value when input, 13) The test Providing a value to the requester computer; 14) for the test value, the requester computer; When capturing messages exchanged between the computer and the provider computer, the step of comparing the expected value and the message.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the request message and response message types for the operation from WSDL, and providing input support when displaying and testing them, what type each input value is in the requester program test? It can be easily tested even if the person who tests the message destination in the requester program does not understand.

  8) A requester program check device according to the present invention is a requester program check device for checking a requester program used in a requester computer that makes a request to a provider computer that provides a web service, and 1) Input prompting means for displaying all program modules and their functions, and prompting the operator to specify the program module to be tested and its functions, 2) if specified, scan the program modules and specify the specified function Function argument acquisition means for acquiring the argument for calling and the type information of the argument, and storing this as argument information of the specified function, 3) Argument candidate storage for storing a plurality of value candidates for each argument type 4) For each type of argument obtained from the argument candidates 5) Candidate assigning means for arbitrarily extracting candidates and giving them to the requester program as set information; 5) A request message captured from a request message capturing device for capturing a request message sent by the requester program to the provider computer A SOAP message extracting means for extracting a SOAP message from the body part of the request message, 6) a message type name acquiring means for analyzing the tree structure of the SOAP message and acquiring a type name of the message; 7) A WSDL file that specifies the URI of the provider computer from the IP packet including the given request message, and obtains the WSDL file of the provider program in the provider computer from the specified URI. 8) Tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of the XML element, 9) Of the tree structure of the acquired element, identified by the SOAP message type name For the operation to be performed, refer to the port type definition part, identify the message for the input and output of the operation, and specify the element hierarchy in the message and the attribute of each element corresponding to the specified function. Element hierarchical information extraction means for extracting as hierarchical information, 10) A test that displays the argument type based on the argument obtained by the function argument acquisition means and the type information of the argument, and prompts the user to input a test value Value input prompting means, 11) referring to the element hierarchy information of the message for input, An attribute is displayed on the screen, and a request message expected to be created by the requester program is prompted for the input of the test value. 12) Referring to the element hierarchy information of the output message, each element and its attributes are displayed on the screen, and a request message created by the requester program is given to the test target input In this case, the provider computer prompts the input of a response message expected to be created, and when input, an expected response value acquisition means for storing the response as an expected response value. 13) Creates a request program for the test target input Compare the actual request message and the expected request value Request expected value comparison means for informing if there is no match, 14) giving the actual request message to the provider computer, comparing the response expected value with the actual response message that is received by the requester as a response, If not, response expected value comparison means for informing is provided.

  In this way, candidate values for each of the obtained argument types are arbitrarily extracted from the argument candidates, given to the requester program as set information, a SOAP message is generated, WSDL is obtained from the header information, and SOAP is obtained. The operation name is specified from the message, the request message and response message type for the operation is specified from the WSDL, and this is displayed and tested for input support. Further, when a test value is input, an actual message exchanged is compared with the expected value, and a notification is given if they do not match. Therefore, in the test of the requester program, it is possible to perform the test even if the person who tests each input value is not understood by the person who tests the message destination in the requester program. .

  9) An input support apparatus according to the present invention is a value input support apparatus for checking a requester program used in a requester computer that makes a request to a provider computer that provides a web service, and 1) the requester program All program modules and their functions are extracted, displayed in a list, and designated prompting means for prompting the operator to specify the program modules to be tested and their functions. 2) When the designation is made, the designated program modules 3) An acquisition means for acquiring an argument for calling a specified function and its type, and 3) arbitrarily extracting a value candidate for each type of argument registered in advance for the acquired argument Test candidate value generating means for giving to the requester computer as a candidate value, 4) the requester computer When a captured request message is given from a message capture device that captures a message exchanged between the data and the provider computer, a SOAP message type name is acquired from the SOAP message in the body part of the message Acquisition means, 5) a WSDL file acquisition means for specifying the URI of the provider computer from the IP packet including the request message, and acquiring the WSDL file of the provider program in the provider computer based on the specified URI; 6) the acquisition A WSDL file tree structure acquisition means for analyzing the tree structure of the WSDL file obtained to obtain the tree structure of each element; 7) Among the acquired element tree structures, an option identified by the SOAP message type name Type information extraction means for identifying messages for input and output of a configuration and extracting the message type as message type information corresponding to the specified function; 8) obtained by scanning the program module Test value input prompting means for prompting the operator to input a test value for the argument and its type, 9) Displaying corresponding message type information on the screen for the specified function, and inputting the test value On the other hand, it is provided with an expected value input support means for prompting input of a message value expected to be exchanged between the requester computer and the provider computer, and storing it as an expected value when input.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the type of request message and response message of the operation from WSDL, and providing input support when displaying and testing this, in the requester program test, what type each input value is Even if the person who tests the message destination in the requester program does not understand it, the test value can be easily input.

  10) A check method according to the present invention is a check method for checking, by a computer, a requester program used in a requester computer that makes a request to a provider computer that provides a web service, and the computer executes the following steps: Let 1) Step to extract all program modules and their functions from the requester program, 2) List the extracted program modules and their functions on the monitor, and prompt the operator to specify the program modules to be tested and their functions Step 3) When the program module to be tested and its function are specified by the operator, scanning the program module to obtain an argument and its type for calling the specified function, 4) acquisition Arbitrarily extracting candidate values for each type of argument registered in advance, and providing them to the requester computer as test candidate values, and 5) capturing a message exchanged from the requester computer to the provider computer. Step 6) The captured message A step of obtaining an XML element of the next layer of the body part from the SOAP message of the body part as a type name of the message; 7) identifying a URI of the provider computer from the IP packet including the captured request message; A step of acquiring a WSDL file of a provider program in the provider computer based on the identified URI; 8) a step of acquiring a tree structure of each element by analyzing a tree structure of the acquired WSDL file; 9) the acquired Identifying a message for input and output of an operation specified by the SOAP message type name in the tree structure, and extracting the type of the message as message type information corresponding to the specified function; 10 ) The program module A step of prompting an operator to input a test value for an argument obtained by scanning a rule and its type; 11) analyzing the tree structure to obtain a tree structure of each element; Identifying messages for input and output of the specified operation and extracting the message type as message type information corresponding to the specified function; 12) displaying the message type information on the screen Prompting input of a message value expected to be exchanged between the requester computer and the provider computer with respect to the input of the test value, and storing it as an expected value when input, 13) the test value 14) providing the requester computer with respect to the test value. When capturing messages exchanged between over data and the provider computer, the step of comparing the expected value and the message.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the request message and response message types for the operation from WSDL, and providing input support when displaying and testing them, what type each input value is in the requester program test? It can be easily tested even if the person who tests the message destination in the requester program does not understand.

  11) A program according to the present invention is a check for checking a requester program used by a requester computer using a computer connected to both a provider computer that provides a web service and a requester computer that requests the provider computer. A program stored as an apparatus, causing the computer to execute the following steps. 1) Step to extract all program modules and their functions from the requester program, 2) List the extracted program modules and their functions on the monitor, and prompt the operator to specify the program modules to be tested and their functions Step 3) When the program module to be tested and its function are specified by the operator, scanning the program module to obtain an argument and its type for calling the specified function, 4) acquisition Arbitrarily extracting candidate values for each type of argument registered in advance, and providing them to the requester computer as test candidate values, and 5) capturing a message exchanged from the requester computer to the provider computer. Step 6) The captured message Obtaining the XML element of the next layer of the body part from the SOAP message of the header part as the type name of the message; 7) identifying the URI of the provider computer from the IP packet including the captured request message; A step of acquiring a WSDL file of a provider program in the provider computer based on the identified URI; 8) a step of acquiring a tree structure of each element by analyzing a tree structure of the acquired WSDL file; 9) the acquired Identifying a message for input and output of an operation specified by the SOAP message type name in the tree structure, and extracting the type of the message as message type information corresponding to the specified function; 10 ) The program module A step of prompting the operator to input a test value for the argument obtained by scanning the message and its type; 11) analyzing the tree structure to obtain a tree structure of each element; Identifying messages for input and output of the specified operation and extracting the message type as message type information corresponding to the specified function; 12) displaying the message type information on the screen Prompting input of a message value expected to be exchanged between the requester computer and the provider computer with respect to the input of the test value, and storing it as an expected value when input, 13) the test value 14) providing the requester computer with respect to the test value. When capturing messages exchanged between provider computers and the step of comparing the expected value and the message.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the type of request message and response message of the operation from WSDL, and providing input support when displaying and testing this, in the requester program test, what type each input value is Even if the person who tests the message destination in the requester program does not understand it, the test value can be easily input.

  In this specification, the “message type” means either a complex type in which the type is represented by another element, or a simple type in which the type is represented by an attribute thereof rather than by another element. It is a concept that includes types. The simple type is the type of the lowest element of the tree structure, and is a type that does not have a lower element as an attribute of the element. For example, in FIG. 24, the element “name” is composed of the attribute “String” type. Has been. The complex type means that the element is composed of one or more other elements. In FIG. 24, the element “userInfo” includes four elements “userName”, “userID”, “address”, It consists of “tel”. The element “userName” has a type of attribute “String”.

1. Functional Block Diagram FIG. 1 shows the overall configuration of a requester program check device 1 according to the present invention. The check device 1 is a requester program check device 1 that checks an object-oriented requester program used in a requester computer 40 that makes a request to a provider computer 61 that provides a web service. In this embodiment, the checker computer 1 And the message transporter server 20.

  The support device 10 includes a specified prompting means 3, an acquisition means 4, a test candidate value generating means 5, a test value input prompting means 11, an expected value input support means 12, a test execution means 13, and a comparison means 14. The message transporter server 20 includes a message capture unit 6, a SOAP message type name acquisition unit 7, a WSDL file acquisition unit 8, a WSDL file tree structure acquisition unit 9, and a type information extraction unit 15.

  The designation prompting means 3 extracts all requester classes and target methods from the requester program of the requester processing means 51, displays them in a list, and prompts the operator to specify the requestor class and target method to be tested. When the designation is made, the obtaining unit 4 scans the designated requester class and obtains an argument for calling the designated method and its type. The test candidate value generation means 5 arbitrarily extracts a value candidate for each type of argument registered in advance for the acquired argument, and gives it to the requester processing means 51 as a test candidate value. The requester processing means 51 generates a request message based on the test candidate value and transmits it to the provider computer 61.

  The message capturing means 6 of the message transporter server 10 captures messages exchanged between the requester computer and the provider computer. The SOAP message type name acquisition means 7 acquires the type name of the message from the SOAP message in the body part of the captured message. The WSDL file acquisition means 8 specifies the URI of the provider computer from the IP packet including the captured request message, and acquires the WSDL file of the provider program in the provider computer based on the specified URI. The WSDL file tree structure acquisition unit 9 analyzes the tree structure of the acquired WSDL file and acquires the tree structure of each element. The type information extraction unit 15 specifies an input message and an output message of the operation specified by the SOAP message type name in the acquired element tree structure, and sets the type of the message to the specified method. Extract as corresponding message type information.

  The test value input prompting means 11 of the support device 10 prompts the operator to input test values for the arguments and their types obtained by scanning the requester class. The expected value input support means 12 displays message type information corresponding to the designated method on the screen, and when the test value input is exchanged between the requester computer and the provider computer. Prompts for the expected message value, and stores it as the expected value when entered. The test execution means 13 gives the test value to the requester computer.

  The requester processing means 51 generates a request message based on the test value and transmits it to the provider computer 61. The message capturing means 6 of the message transporter server 10 captures messages exchanged between the requester computer and the provider computer.

  When the message capturing unit 6 captures a message exchanged between the requester computer and the provider computer, the comparing unit 14 of the support apparatus 10 compares the message with the expected value with respect to the test value.

  In this way, as a candidate for the value of each acquired argument type, a test candidate value is given to the requester program, a SOAP message is generated, WSDL is acquired from the header information, and the operation name is specified from the SOAP message. Then, by specifying the request message and response message types for the operation from WSDL, and providing input support when displaying and testing them, what type each input value is in the requester program test? It can be easily tested even if the person who tests the message destination in the requester program does not understand.

  In this example, the support device 10 is provided with a designated prompting means 3, an acquisition means 4, a test candidate value generating means 5, a test value input prompting means 11, an expected value input support means 12, a test execution means 13, and a comparison means 14. The message transporter server 20 is provided with the message capture means 6, the SOAP message type name acquisition means 7, the WSDL file acquisition means 8, the WSDL file tree structure acquisition means 9, and the type information extraction means 15, but the message transporter server 20 may include at least the message capturing unit 6, and some or all of the other units may be provided in the support device. If the message transporter server only captures messages, it is configured as a message capture device.

2. Hardware Configuration The hardware configuration of the requester computer 50 when the support apparatus 10 shown in FIG. 1 is configured in the requester computer will be described with reference to FIG. FIG. 2 is an example of a hardware configuration configured using a CPU.

  The requester computer 50 includes a CPU 23, a memory 27, a hard disk 26, a monitor 30, a CDD (CD-ROM drive) 25, an input device 28, a communication board 31, and a bus line 29. The CPU 23 controls each unit via the bus line 29 according to each program stored in the hard disk 26.

  The hard disk 26 includes an operating system program 26o (hereinafter abbreviated as OS), a temporary test data storage unit 26d, a requester program 26r, a JVM (Java ™ Virtual Machine) 26j, and a check program storage unit 26p.

  The check program storage unit 26p stores a program for checking the requester program 26r of the requester computer. The program includes a user screen unit 26pu, a requester analysis unit 26pr, a testing framework unit 26pf, and a message management unit 26pk. Processing in each unit will be described later.

  As shown in FIGS. 3 to 5, the temporary test data storage unit 26d stores temporary test data for each argument type. In this embodiment, LINUX (trademark) is adopted as the operating system program (OS) 26o, but the present invention is not limited to this.

  Each of the above programs is read from the CDROM 25a storing the program via the CDD 25 and installed in the hard disk 26. In addition to the CD-ROM, a program such as a flexible disk (FD) or an IC card may be installed on a hard disk from a computer-readable recording medium. Furthermore, it may be downloaded using a communication line.

  In the present embodiment, the program stored in the CD-ROM is indirectly executed by the computer by installing the program from the CD-ROM to the hard disk 26. However, the present invention is not limited to this, and the program stored in the CD-ROM may be directly executed from the CDD 25. Note that programs that can be executed by a computer are not only programs that can be directly executed by being installed as they are, but also programs that need to be converted into other forms (for example, those that have been compressed) In addition, those that can be executed in combination with other module parts are also included.

  The requester program will be described. In the present embodiment, the java (trademark) program shown in FIGS. 6 and 7 is stored as a requester program. Such a java (trademark) program is converted into native code by the JVM 26j and executed.

3. Transporter Server and Provider Computer FIG. 2a shows the hardware configuration of the transporter server. The overall configuration is almost the same as in FIG. The difference is that a transporter unit 126pt and a message capture unit 126pm are stored in the program storage unit 126p. Processing in each unit will be described later.

  When receiving a request from the requester computer 50, the provider computer 61 shown in FIG. 1 performs a predetermined process on the request and returns a message. The provider computer 61 stores a WSDL file composed of the XML data shown in FIGS. The WSDL file describes the contents of data processing performed by the program of the provider computer using XML. Since the hardware configuration of the provider computer is general, a description thereof will be omitted.

4). Check processing The processing of each program stored in the check program storage unit 26p will be described with reference to FIGS.

  The user screen unit 26pu acquires the requester program 26r to be tested, displays a list of requester classes and target methods for the requester program, and prompts the user to select.

  In this case, since only the class “BuyerClient” exists in the requester program, from the class “BuyerClient”, the following methods “order”, “purchase”, “cancel”, “createSOAPMessage”, “createOrderSheetDoc”, “createParchaseDoc” , “CreateCancelDoc”, “toByteArray”, “getMessageManagerURL”, “callWS” are extracted and displayed in a list on the screen.

  The method is described as “qualifier return value method name (argument) {process to be executed}”. Therefore, the user screen unit 26pu analyzes the source code and determines that the line described in the format is a method.

  Here, it is assumed that the method “order” is selected.

  In this embodiment, since there was one class, all methods were extracted assuming that the class was selected. However, if there are multiple classes, the class is displayed once and the class is When selected, the method may be extracted, or all classes and their methods may be displayed in a list to extract the selected method.

  When the class and target method are selected by the user (step S200 in FIG. 11), the requester analysis unit 26pr scans the requester class using the revocation API (step S201), and the designated method “order” is scanned. The type information of the argument is obtained for calling (step S202).

  In this case, since the method “order” is the test target method, the arguments “username”, “ID”, “address”, and “tel” have the type “String” as the types of the arguments of the method “order”. Yes, the argument “detail” is extracted that the type is “List”.

Furthermore, the argument “detail” refers to the method “createOrderSheetDoc” called by the method “order”, the argument “goodsname”, and the arguments “goodsname” and “type” have the type “String”. “Price” and “amount” are of type “int”.

  Next, the requester analysis unit 26pr arbitrarily selects values of the same type as the types of the arguments from the data stored in the temporary test data storage unit 26d using the type information of each argument for all the determined arguments. (Step S203 in FIG. 11). Here, since the type of the argument “userName” is “String”, it is assumed that the value “A” is selected as a candidate assuming that it is java.lang.String. It is assumed that the value “0123456789”, the value “abc”, and the value “null” are selected as candidates for the argument “ID”, the argument “address”, and the argument “tel”, respectively. Further, regarding the argument “detail”, the argument “goodsname” and the argument “type” have the values “null” and “abc”, the arguments “price” and “amount” have the value “1”, and the value “127”, respectively. Is selected as a candidate.

  Next, the requester analysis unit 26pr issues a capture start request to the message capture unit 26pm of the transporter server (step S204 in FIG. 11). In response to this request, the message capture unit 26pm starts acquiring an IP packet sent from the requester computer 50 (step S225 in FIG. 12).

  On the other hand, the requester analysis unit 26pr calls the requester program with the selected value (step S205 in FIG. 11). Thereby, the requester program 26r of the requester computer 50 generates a message to the provider 61 with the value of the given argument and transmits it to the provider 61.

  Since the candidate value is an arbitrarily selected value, an error may occur in the value, and there is a possibility that a message to the provider 61 cannot be created. When the requester analysis unit 26pr receives such an error, the requester analysis unit 26pr repeats the processing from step S203 onward while there is a next candidate.

  When the requester computer 50 transmits the IP packet, the message capture unit 26pm of the message transporter server 20 captures this (step S213 in FIG. 12).

  The message capture unit 26pm analyzes the captured IP packet and obtains the destination URL of the destination computer described in the HTTP header (step S214). This is to identify the server that acquires the WSDL. Here, it is assumed that (http://buyerservice.ias.hitachi_system.co.jp) is acquired as the destination URL. The message capture unit 26pm holds the acquired URL in the provider definition file (steps S214b and O212). Specifically, the URI (URL) acquired corresponding to the IP address, requester class, and invocation method name of the requester computer may be stored.

  Next, the message capture unit 26pm analyzes the IP packet and acquires a SOAP message from the HTTP body (step S215).

  Such a SOAP message will be described with reference to FIG. In the web service, messages are exchanged by communication using SOAP. The SOAP message is composed of a protocol header such as HTTP and a SOAP envelope. The SOAP envelope has the role of an “envelope” that wraps the SOAP header and the SOAP body, and the envelope can be freely attached with destination information to the object or additional information such as a message ID as required. . With this incidental information, a destination to the object or a message ID can be freely added if necessary. The acquired data is shown in FIG. In FIG. 14, rows 71 to 73 are supplementary information of the SOAP envelope, and rows 75 and below are SOAP bodies. In this example, the SOAP header is omitted.

  Next, the message capture unit 26pm analyzes the acquired SOAP message to construct a tree structure, and acquires the operation name from the tree structure (step S217 in FIG. 12). In the example of FIG. 11, since <order xmlns = "..."> is present in the line 76 next to the SOAP body tag "<soapenv: Body>", it is determined that "order" is the operation name.

  Next, the message capture unit 26pm acquires WSDL based on the URL acquired in step S214.

  Note that since one WSDL is defined to describe the service of one provider, the WSDL corresponding to the URL can be uniquely identified.

  In this case, since the WSDL file shown in FIGS. 8 to 10 is stored in the provider, the message capture unit 26pm acquires the WSDL file.

  The WSDL file will be described with reference to FIG. The WSDL file includes a message definition unit 151, a port type definition unit 153, a binding definition unit 155, and a service definition unit 157. The message definition unit 151 defines a plurality of messages. Each message describes the type of message exchanged by SOAP and its type. The port type definition unit 153 defines a plurality of operations. Each operation is structurally described as to which operation (input) and output (output) the message defined by the message definition unit 151 is used. The binding definition unit 155 describes in what protocol the functions defined in the message definition unit 151 and the port type definition unit 153 can be used. The service definition unit 157 describes at which URL the Web service having the binding information defined by the binding definition unit 155 can be used.

  That is, each message of the message definition unit 151 is used by each operation of the port type definition unit 153, each operation of the port type definition unit 153 is used by the binding definition unit 155, and each binding of the binding definition unit 155 is a service definition. Part 157.

  In the WSDL file shown in FIG. 8 to FIG. 10, lines 93 to 95 shown in FIG. 9 are message definition parts, lines 101 to 103 shown in FIG. 10 are port type definition parts, and line 105 shown in FIG. Line 107 is a binding definition part, and lines 109 to 111 shown in FIG. 10 are service definition parts. Line 83 (FIG. 8) to line 91 (FIG. 9) specify the type of data used by this Web service.

  The message capture unit 26pm analyzes the acquired WSDL and constructs an XML tree structure. In the present embodiment, an open source XML engine called “XERCES” is used to construct an XML tree structure.

  FIG. 15 shows a tree structure of messages defined in the message definition section in the tree structure. Based on the URL acquired in step S214 and the message type acquired in step S217, the message capture unit 26pm identifies the operation (operation) of the requester program corresponding to the message from the constructed WSDL tree structure. In this case, since the acquired URL is “http://buyerservice.ias.hitachi_system.co.jp” and the message type is “order”, the operation “order” of the type is changed from the WSDL tree structure. Identify. Note that the tree structure of the input / output message for the specified method is used later when an expected value is input.

  In this embodiment, a tree structure is constructed in step S219, and a method is specified in step S220 using the tree structure. Since the method tree structure is required later when inputting expected values, analysis is performed at this stage.

  The message capture unit 26pm stores the requester name, the provider name specified in step S220, and the operation name in association with the method specified in step S200 as the operation name in the operation definition file. In this case, the provider name “BuyerService”, the operation name “order”, the requester name “BuyerClient”, and the operation name “order” are stored.

  The message capture unit 26pm receives the capture end request from the requester analysis unit 26pr, and ends the capture process (step S223).

  Thereby, the data collection process for input support using WSDL ends. Hereinafter, using the data collected in this way, the user inputs test data.

  In step S202, the user screen unit 26pu displays the argument and type information acquired from the requester program (step S225), and prompts the operator to input the argument value (step S226). In this case, the arguments acquired in step S202 are, as types, an argument “userName” —type “String”, an argument “ID” —type “String”, an argument “address” —type “String”, an argument “ "tel"-type "String", argument "detail"-type "list". For argument “detai1”, argument “goodsname” —type “String”, argument “type” —type “String”, argument “price” —type “int”, argument “amount” —type “int” It is.

  Therefore, this is displayed on the screen (not shown), and input of test data is waited for. In this case, it is assumed that the values shown in FIG. 18 are input from the user as test values. The input data is stored in the input information file (step S227). Such file names may be automatically assigned with sequential numbers. In this case, the name of the input information file is “param1_000”. The input information file name is added to the input information name shown in FIG. 19A (step S228).

  Next, the user screen unit 26pu displays the element name, type, and number of messages sent from the requester computer 50 to the provider computer 61 by the operation called by the requester program 26r, and prompts the input (step S229, Step S230). In this case, since the provider name is “BuyerService” and the operation name is “order”, the following element name and type are acquired from the WSDL analyzed in step S219. The operation “order” exists in FIG. In operation “order”, it can be determined from the analysis result of WSDL that messages “orderRequest” and “orderResponse” exist (see lines 106b and 106c). Since the message “orderRequest” is “imput name” and “orderResponse” is “output name”, it can be seen that the former is a message at the time of input to the provider and the latter is a message at the time of output from the provider. In this case, since the element name and type of the message sent from the requester computer 50 to the provider 61 are extracted, the element name and their type of the former message “orderRequest” are extracted from the analyzed WSDL. In this case, it can be seen from the rows 97, 97a, and 97b in FIG. 9 that the element “OrderRequest” is composed of the element “userInfo” and the element “details”. The element “userInfo” is composed of the elements “userName”, “userID”, “address”, and “tel” from the lines 98 and 98a to 98d, and the element “details” is the type of the element “OrderDetail”. It can be seen from the lines 99, 99a to 99d that the element “OrderDetail” is composed of the types of the elements “name”, “type”, “price”, and “amount”. The type of each element is also found by referring to 98a to 98d and 99a to 99d.

  In addition, since the number is “maxOccurs =“ unbounded ”” in the row 97b, it is displayed that there is no limit on the number. The element name is “soapenv: Envelope...” Because this message is a SOAP message.

  As a result, the necessary elements and their types can be acquired for the operation, and these are displayed on the screen to prompt the user to input expected request values for the test value input. When the user inputs an expected value, this is stored in a request expected value file as shown in FIG. 20 (step S231). The expected value name is added to the operation definition file (step S232).

  Next, in response to the input, the user screen unit 26pu displays the element name, type, and number of reply messages that the provider 61 that has received the message generated by the operation called by the requester 51 expects to generate, Input is prompted (steps S233 and S234). In this case, in step S229, it is understood that the message “orderResponse” is a message at the time of output from the provider. Therefore, the element name constituting the message “orderResponse” and its type are extracted from the analyzed WSDL. In this case, it can be seen from FIG. 9 lines 94, 94a, and 94b that the message “orderResponse” is composed of an element “userInfo” and an element “orderID”. The element “userInfo” is composed of elements “userName”, “userID”, “address”, and “tel” from the lines 98 and 98a to 98d, and the type is “String”. . Note that the element “orderID” is of type “String”. The element name can be determined in the same manner as in step S229. The same applies to the number.

  Thereby, since the element name and type of the message at the time of output can be acquired, these are displayed on the screen, and the user is prompted to input the expected response value for the test value input. When the user inputs an expected value, this is stored in an expected response value file as shown in FIG. 21 (step S235). The expected value name is added to the operation definition file (step S236).

  In this example, “orderID” and “userID” are the same (see FIG. 21). In order to distinguish when there are a plurality of orders from one user, for example, “orderID” may be a rule that adds a date and an order to “userID”.

  This completes the test preparation.

  Next, the comparison process will be described with reference to FIG. The testing framework unit 26pf reads the operation definition file shown in FIG. 19 (step S243). Then, the input information file designated by the operation definition file is read (step S244). In this case, the input information file param1_000 is read.

  The testing framework unit 26pf changes the call destination URL to the URL of the transporter (step S245), and calls the requester program 26r with the input information file param1_000 (step S246).

  The requester program 26r receives such input information, generates a message to the provider 61, and transmits the message transporter unit 26pt as a transmission destination.

  The message transporter unit 26pt receives this (step S247), and causes the message management unit 26pk to hold the request message (step S248). The message transporter unit 26pt determines whether to use a pseudo provider. In this case, since it is not used, the provider URI setting file is read (step S249), and the message is transferred to the provider 61 (step S250). This setting file stores the URL of the provider computer specified in step S214 in FIG. 12 in association with the IP address of the requester computer.

  When the message transporter unit 26pt receives the response message from the provider 61 (step S255), the message management unit 26pk holds the response message (step S256), and transmits the response message to the requester program 26r (step S257).

  When receiving the response message, the requester program 26r gives the response message to the testing framework unit 26pf. The testing framework unit 26pf receives this (step S258) and reads the setting file (step S259). The setting file associates a predetermined URL of the transporter server with the IP address of the requester computer. Is remembered.

  The testing framework unit 26pf acquires a message actually transmitted / received from the message transporter unit 26pt (step S260). This is because the message in step S258 is mainly returned to the program as an object for transmitting control, and therefore, in actual comparison, it is necessary to acquire XML format data.

  Examples of a request message and a response message when such input information is input are shown in FIGS. 24 and 25, respectively.

  The testing framework unit 26pf reads the expected value file (step S261), and compares the data of the expected value file with the acquired message (step S262). In addition, since the data of the expected value file and the acquired message are described in the XML format, the XML tree structure is analyzed, the subordinate constituent elements constituting each element, their relations, and further, If the values match, it is determined that they match. For comparison of XML data, for example, a comparator may be added to the XERCES open source program. The comparator only has to delete blank lines or rearrange the order so that each node can be compared while traversing.

  If there is a difference, the testing framework unit 26pf presents the difference (step S263).

  If a pseudo provider is used after step S248, WSDL is acquired (step S251), analyzed (step S252), a request expected value file and a response expected value file are read (step S253), and expected. The processing that the provider 61 will perform from the value and WSDL may be operated in a pseudo manner, and the processing in step S248 may be performed.

  In the above example, the case of performing one set of tests has been described. However, a plurality of test values can be tested at a time. In this case, the input of a plurality of test values may be repeated.

  It is also possible to input a value that does not make a response as a normal result as a test value and test whether a correct error is returned from the provider 61 as a response.

  In this case, an error expected value file may be created together with the request expected value file and response expected value file, and these may be compared. Creation of the expected error value file will be described with reference to FIG.

  The user screen unit 26pu acquires the interface information of the provider error message (step S237 in FIG. 26). In this embodiment, an error message determined by the SOAP standard is adopted as the error message. Therefore, the interface information can be acquired by accessing a URL where the error message determined by the standard exists. . The same is true for displaying candidate elements, prompting input by the user, and storing them in the expected value file (steps S238 to S241). The data structure of the stored expected error value file is shown in FIG. An error message generated by the provider 61 is shown in FIG. In this case, the difference is that the presence / absence of use of the pseudo provider is stored in the operation definition file.

  Thus, in this embodiment, a SOAP message is generated with temporary test data, WSDL is obtained from the header information, the operation name is specified from the SOAP message, and a request message and a response message about the operation are obtained from the WSDL. It is possible to easily input a test value by specifying the type of, and providing input support for displaying and testing this type.

  Therefore, in the test of the requester program, the test can be performed even if the person who tests each input value is not understood by the person who tests the message destination in the requester program.

  Even if the program of the provider 61 is not completed, a test by a pseudo provider is possible as long as the WSDL exists.

5. Other Embodiments In the above embodiment, the reflection API is used to scan the class, obtain the argument type information, and use this to scan the source code to obtain the argument name. Instead of using it, the source code may be scanned to obtain the argument name and argument type.

  In the above embodiment, the case where the requester program is an object-oriented program has been described, but even a conventional procedural program can be similarly applied. In this case, the requester class and method in the above-described embodiment may be made to correspond to the program module and the function constituting the requester program, respectively, and the same processing may be executed.

  The check device 1 can be grasped as a value input support device for checking an object-oriented requester program used in a requester computer that makes a request to a provider computer that provides a web service.

  The check device 1 is a check device for checking an object-oriented requester program used in a requester computer that makes a request to a provider computer that provides a web service, and 1) all requester classes and targets for the requester program. Input prompting means to display the method and prompt the operator to specify the requester class to be tested and the target method. 2) If specified, an argument for scanning the requester class and calling the specified method Method argument acquisition means for acquiring argument type information and storing it as argument information of a specified method, 3) Argument candidate storage means for storing a plurality of candidate values for each argument type, 4) The argument candidate Arbitrarily extract candidate values for each type of argument obtained from Candidate assigning means to be given to the requester program as 5) When a request message is given from a request message capture device that captures a request message transmitted by the requester program to the provider computer, a SOAP message is extracted from the HTTP body part SOAP message extraction means 6) Message type name acquisition means for analyzing the tree structure of the SOAP message to acquire the type name of the message, 7) URI of the provider computer from the IP packet including the captured request message 8) WSDL file acquisition means for acquiring the WSDL file of the provider program in the provider computer from the specified URI, 8) The tree structure of the acquired WSDL file A tree structure acquisition means for acquiring an XML element tree structure, and 9) specifying an input message and an output message of the operation specified by the SOAP message type name from the acquired element tree structure. , Type information extraction means for extracting the message type as message type information corresponding to the specified method, 10) the argument based on the argument acquired by the method argument acquisition means and the type information of the argument 11) A test value input prompting means for prompting a test value to be input, and 11) displaying a message type information of an input message for the operation on the screen, and for requesting the test value, a requester program Prompts for a request message that is expected to be created, Request expected value acquisition means for storing as a value, 12) The message type information of the operation for performing the output processing is displayed on the screen, and a request message created by the requester program is given to the test target input In this case, the provider computer prompts the input of a response message expected to be created, and when input, an expected response value acquisition means for storing the response as an expected response value. 13) Creates a request program for the test target input A request expected value comparing means for comparing the actual request message with the expected request value, and notifying if it does not match, 14) providing the actual request message to the provider computer and receiving the response as a response by the requester Respo Graphics and message, comparing the response expected value, if it does not match with the response expected value comparing means for notifying can be understood as a check device.

  In the above embodiment, the CPU is used to realize the function shown in FIG. 1, and this is realized by software. However, some or all of them may be realized by hardware such as a logic circuit.

  In addition, you may make it make an operating system (OS) process a part of said program.

It is a functional block diagram of check device 1 concerning the present invention. It is a figure which shows an example of the hardware constitution which implement | achieved the check apparatus 1 shown in FIG. 1 using CPU. It is a figure which shows an example of the hardware constitution which implement | achieved the server for transporters shown in FIG. 1 using CPU. This is a dummy test candidate list. This is a dummy test candidate list. This is a dummy test candidate list. Requester program to be checked. Requester program to be checked. This is the provider's WSDL file. This is the provider's WSDL file. This is the provider's WSDL file. It is an activity diagram of a check program. It is an activity diagram of a check program. It is a figure explaining the data structure of a request message. This is test data generated as a dummy. It is a figure explaining the data structure of a SOAP message. It is the tree structure (part) which analyzed the WSDL file. It is an activity diagram of a check program. It is a figure which shows the data structure of an input information file. It is a figure which shows the data structure of an operation definition file. It is a figure which shows the data structure of a request expectation value file. It is a figure which shows the data structure of a response expected value file. It is a figure which shows the data structure of an error expected value file. It is an activity diagram of a check program. This is a request message generated by the requester. This is a response message generated by the provider. It is an activity diagram of a check program (error processing). It is an error message.

Explanation of symbols

1 ... Screen generator 23 ... CPU
27 ... Memory

Claims (11)

A requester program check device for checking an object-oriented requester program used in a requester computer that makes a request to a provider computer that provides a web service,
An input prompting means for displaying all requester classes and target methods for the requester program, and prompting an operator to specify a requester class and a target method to be tested,
When there is the designation, the requester class is scanned using the reflection API, and the “return value type”, “method name”, “number of arguments”, and “argument type” of the designated method are obtained and used. Scanning the source code to obtain the name of the method argument that matches the method information, and storing it as the argument information of the specified method together with the type information of the method Argument candidate storage means for storing a plurality of value candidates,
Candidate giving means for arbitrarily extracting value candidates for each of the obtained argument types from the argument candidates, and giving them to the requester program as set information;
A SOAP message extracting means for extracting a SOAP message from the body part of the request message when a captured request message is given from a request message capturing device that captures a request message to be transmitted to the provider computer by the requester program;
Message type name acquisition means for analyzing a tree structure of the SOAP message and acquiring a type name of the message;
WSDL file acquisition means for specifying the URI of the provider computer from the IP packet including the given request message and acquiring the WSDL file of the provider program in the provider computer from the specified URI;
A tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of the XML element;
For the operation specified by the SOAP message type name in the tree structure of the acquired elements, refer to the port type definition section to specify messages for input and output of the operation, and the hierarchy of elements in the message Element hierarchy information extraction means for extracting the structure and attributes of each element as element hierarchy information corresponding to the specified method;
Based on the argument acquired by the method argument acquisition means and the type information of the argument, the type of the argument is displayed, and a test value input prompting means for prompting input of a test value;
Referring to the element hierarchy information of the input message, each element and its attributes are displayed on the screen, and the request message expected to be created by the requester program is input for the test value input. Prompt request value acquisition means to store as request expectation value when prompted,
When the request message created by the requester program is given to the test target input by referring to the element hierarchy information of the output message and displaying each element and its attribute on the screen. Prompting the input of a response message that the provider computer is expected to create, and when input, an expected response value acquisition means for storing the response message as an expected response value;
A request expected value comparison means for comparing the actual request message created by the request program with the request expected value for the test target input, and notifying if it does not match,
A response expected value comparing means that gives the actual request message to the provider computer and compares the response expected value with the actual response message that is received by the requester as a response, and notifies if the response does not match,
A requester program check device characterized by comprising: A value input support device for checking a requester program used in a requester computer that makes a request to a provider computer that provides a web service,
All requester classes and target methods are extracted from the requester program, displayed in a list, and designated prompting means for prompting the operator to specify the requester class and target method to be tested,
When the specification is made, an acquisition unit that scans the specified requester class and acquires an argument for calling the specified method and its type;
Test candidate value generation means for arbitrarily extracting a value candidate for each type of argument registered in advance for the acquired argument and giving it to the requester computer as a test candidate value;
When a captured request message is given from a message capture device that captures a message exchanged between the requester computer and the provider computer, a SOAP message type that acquires the type name of the message from the SOAP message in the body part of the message Name acquisition means,
WSDL file acquisition means for specifying the URI of the provider computer from the IP packet including the request message and acquiring the WSDL file of the provider program in the provider computer based on the specified URI;
WSDL file tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of each element;
In the tree structure of the acquired elements, an input message and an output message specified by the SOAP message type name are specified, and the message type is set as message type information corresponding to the specified method. Type information extraction means to extract,
Test value input prompting means for prompting the operator to input a test value for the argument obtained by scanning the requester class and its type,
The message type information corresponding to the specified method is displayed on the screen, and the message value expected to be exchanged between the requester computer and the provider computer in response to the test value input. Expected value input support means for storing as an expected value when prompted,
An input support apparatus comprising: The input support device according to claim 2,
Test execution means for providing the test value to the requester computer;
A comparison means for comparing a message exchanged between the requester computer and a provider computer with respect to the test value from the message capturing device when the message is received from the message capturing device;
A check device characterized by comprising: The check device according to claim 3,
The message exchanged between the requester computer and the provider computer is a request message given from the requester computer to the provider computer.
The expected value input support means displays message type information of an input message for the operation on the screen, and inputs a request message expected to be created by the requester program in response to the input of the positive test value. Prompting,
It is characterized by. The check device according to claim 3,
The message exchanged between the requester computer and the provider computer is a response message given from the provider computer to the requester computer,
The expected value input support means displays the type information of the message for output on the screen, and when a request message created by a requester program is given to the test target input, the provider computer Prompts for a response message that is expected to be created,
It is characterized by. A check method for checking, by a computer, a requester program used by a requester computer that makes a request to a provider computer that provides a web service,
Causing the computer to perform the following steps:
Extracting all requester classes and target methods from the requester program;
A step that lists the extracted requester class and target method on the monitor and prompts the operator to specify the requester class and target method to be tested,
When the requester class to be tested and the target method are specified by the operator, scanning the specified requester class to obtain an argument and its type for calling the specified method;
For the acquired argument, arbitrarily extracting a value candidate for each type of argument registered in advance, and giving the requester computer as a test candidate value;
Capturing messages exchanged from the requester computer to the provider computer;
Obtaining an XML element of the next layer of the body part as a type name of the message from the SOAP message of the body part of the captured message;
Identifying a URI of the provider computer from an IP packet including the captured request message, and obtaining a WSDL file of a provider program in the provider computer based on the identified URI;
Analyzing the tree structure of the obtained WSDL file to obtain a tree structure of each element;
In the acquired tree structure, an input message and an output message specified by the SOAP message type name are specified, and the message type is extracted as message type information corresponding to the specified method. Step,
Prompting the operator to enter a test value for the argument and its type obtained by scanning the requester class;
Analyzing the tree structure to obtain the tree structure of each element, specifying the message for input and output of the operation specified by the SOAP message type name, and specifying the type of the message as the specified method Extracting as message type information corresponding to
The message type information is displayed on the screen, and the test value input is prompted to input a message value expected to be exchanged between the requester computer and the provider computer. Step to remember as,
Providing the test value to the requester computer;
Capturing a message exchanged between the requester computer and a provider computer for the test value, and comparing the message with the expected value;
Check method characterized by. A program that stores a computer connected to both a provider computer that provides a web service and a requester computer that requests the provider computer as a check device that checks a requester program used by the requester computer,
Causing the computer to perform the following steps:
Extracting all requester classes and target methods from the requester program;
A step that lists the extracted requester class and target method on the monitor and prompts the operator to specify the requester class and target method to be tested,
When the requester class to be tested and the target method are specified by the operator, scanning the specified requester class to obtain an argument and its type for calling the specified method;
For the acquired argument, arbitrarily extracting a value candidate for each type of argument registered in advance, and giving the requester computer as a test candidate value;
Capturing messages exchanged from the requester computer to the provider computer;
Obtaining an XML element of the next layer of the body part as a type name of the message from the SOAP message of the body part of the captured message;
Identifying a URI of the provider computer from an IP packet including the captured request message, and obtaining a WSDL file of a provider program in the provider computer based on the identified URI;
Analyzing the tree structure of the obtained WSDL file to obtain a tree structure of each element;
In the acquired tree structure, an input message and an output message specified by the SOAP message type name are specified, and the message type is extracted as message type information corresponding to the specified method. Step,
Prompting the operator to enter a test value for the argument and its type obtained by scanning the requester class;
Analyzing the tree structure to obtain the tree structure of each element, specifying the message for input and output of the operation specified by the SOAP message type name, and specifying the type of the message as the specified method Extracting as message type information corresponding to
The message type information is displayed on the screen, and the test value input is prompted to input a message value expected to be exchanged between the requester computer and the provider computer. Step to remember as,
Providing the test value to the requester computer;
Capturing a message exchanged between the requester computer and a provider computer for the test value, and comparing the message with the expected value;
A program characterized by A requester program check device for checking a requester program used in a requester computer that makes a request to a provider computer that provides a web service,
An input prompting means for displaying all program modules and their functions for the requester program, and prompting an operator to specify a program module to be tested and its functions,
When there is the designation, a function argument acquisition unit that scans the program module, acquires an argument for calling the specified function and type information of the argument, and stores this as argument information of the specified function ,
Argument candidate storage means for storing a plurality of candidate values for each argument type,
Candidate giving means for arbitrarily extracting value candidates for each of the obtained argument types from the argument candidates, and giving them to the requester program as set information;
A SOAP message extracting means for extracting a SOAP message from the body part of the request message when a captured request message is given from a request message capturing device that captures a request message to be transmitted to the provider computer by the requester program;
Message type name acquisition means for analyzing a tree structure of the SOAP message and acquiring a type name of the message;
WSDL file acquisition means for specifying the URI of the provider computer from the IP packet including the given request message and acquiring the WSDL file of the provider program in the provider computer from the specified URI;
A tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of the XML element;
For the operation specified by the SOAP message type name in the tree structure of the acquired elements, refer to the port type definition section to specify messages for input and output of the operation, and the hierarchy of elements in the message Element hierarchy information extraction means for extracting the structure and attributes of each element as element hierarchy information corresponding to the specified function;
Based on the argument obtained by the function argument obtaining means and the type information of the argument, the argument type is displayed, and a test value input prompting means for prompting the input of the test value;
Referring to the element hierarchy information of the input message, each element and its attributes are displayed on the screen, and the request message expected to be created by the requester program is input for the test value input. Prompt request value acquisition means to store as request expectation value when prompted,
When the request message created by the requester program is given to the test target input by referring to the element hierarchy information of the output message and displaying each element and its attribute on the screen. Prompting the input of a response message that the provider computer is expected to create, and when input, an expected response value acquisition means for storing the response message as an expected response value;
A request expected value comparison means for comparing the actual request message created by the request program with the request expected value for the test target input, and notifying if it does not match,
A response expected value comparing means that gives the actual request message to the provider computer and compares the response expected value with the actual response message that is received by the requester as a response, and notifies if the response does not match,
A requester program check device characterized by comprising: A value input support device for checking a requester program used in a requester computer that makes a request to a provider computer that provides a web service,
All the program modules and their functions are extracted from the requester program, displayed in a list, and designated prompting means for prompting the operator to specify the program modules to be tested and their functions,
When the specification is made, an acquisition unit that scans the specified program module and acquires an argument for calling the specified function and its type;
Test candidate value generation means for arbitrarily extracting a value candidate for each type of argument registered in advance for the acquired argument and giving it to the requester computer as a test candidate value;
When a captured request message is given from a message capture device that captures a message exchanged between the requester computer and the provider computer, a SOAP message type that acquires the type name of the message from the SOAP message in the body part of the message Name acquisition means,
WSDL file acquisition means for specifying the URI of the provider computer from the IP packet including the request message and acquiring the WSDL file of the provider program in the provider computer based on the specified URI;
WSDL file tree structure acquisition means for analyzing the tree structure of the acquired WSDL file and acquiring the tree structure of each element;
In the tree structure of the acquired elements, an input message and an output message specified by the SOAP message type name are specified, and the message type is set as message type information corresponding to the specified function. Type information extraction means to extract,
Test value input prompting means for prompting the operator to input a test value for the argument obtained by scanning the program module and its type,
The message type information corresponding to the specified function is displayed on the screen, and the value of the message expected to be exchanged between the requester computer and the provider computer in response to the input of the test value. Expected value input support means for storing as an expected value when prompted,
An input support apparatus comprising: A check method for checking, by a computer, a requester program used by a requester computer that makes a request to a provider computer that provides a web service,
Causing the computer to perform the following steps:
Extracting all program modules and their functions from the requester program;
Steps that list the extracted program modules and their functions on the monitor and prompt the operator to specify the program modules to be tested and their functions;
When a program module to be tested and its function are specified by an operator, scanning the program module to obtain an argument and its type for calling the specified function;
For the acquired argument, arbitrarily extracting a value candidate for each type of argument registered in advance, and giving the requester computer as a test candidate value;
Capturing messages exchanged from the requester computer to the provider computer;
Obtaining an XML element of the next layer of the body part as a type name of the message from the SOAP message of the body part of the captured message;
Identifying a URI of the provider computer from an IP packet including the captured request message, and obtaining a WSDL file of a provider program in the provider computer based on the identified URI;
Analyzing the tree structure of the obtained WSDL file to obtain a tree structure of each element;
In the acquired tree structure, an input message and an output message specified by the SOAP message type name are specified, and the message type is extracted as message type information corresponding to the specified function. Step,
Prompting an operator to input a test value for an argument obtained by scanning the program module and its type;
Analyzing the tree structure to obtain a tree structure of each element, specifying a message for input and output of an operation specified by the SOAP message type name, and specifying the type of the message as the specified function Extracting as message type information corresponding to
The message type information is displayed on the screen, and the test value input is prompted to input a message value expected to be exchanged between the requester computer and the provider computer. Step to remember as,
Providing the test value to the requester computer;
Capturing a message exchanged between the requester computer and a provider computer for the test value, and comparing the message with the expected value;
Check method characterized by. A program that stores a computer connected to both a provider computer that provides a web service and a requester computer that requests the provider computer as a check device that checks a requester program used by the requester computer,
Causing the computer to perform the following steps:
Extracting all program modules and their functions from the requester program;
Steps that list the extracted program modules and their functions on the monitor and prompt the operator to specify the program modules to be tested and their functions,
When a program module to be tested and its function are specified by an operator, scanning the program module to obtain an argument and its type for calling the specified function;
For the acquired argument, arbitrarily extracting a value candidate for each type of argument registered in advance, and giving the requester computer as a test candidate value;
Capturing messages exchanged from the requester computer to the provider computer;
Obtaining an XML element of the next layer of the body part as a type name of the message from the SOAP message of the body part of the captured message;
Identifying a URI of the provider computer from an IP packet including the captured request message, and obtaining a WSDL file of a provider program in the provider computer based on the identified URI;
Analyzing the tree structure of the obtained WSDL file to obtain a tree structure of each element;
In the acquired tree structure, an input message and an output message specified by the SOAP message type name are specified, and the message type is extracted as message type information corresponding to the specified function. Step,
Prompting an operator to input a test value for an argument obtained by scanning the program module and its type;
Analyzing the tree structure to obtain a tree structure of each element, specifying a message for input and output of an operation specified by the SOAP message type name, and specifying the type of the message as the specified function Extracting as message type information corresponding to
The message type information is displayed on the screen, and the test value input is prompted to input a message value expected to be exchanged between the requester computer and the provider computer. Step to remember as,
Providing the test value to the requester computer;
Capturing a message exchanged between the requester computer and a provider computer for the test value, and comparing the message with the expected value;
A program characterized by

Images