CN105721251A - Reconfigurable testing pile service method and system - Google Patents

Abstract

The invention discloses a method and system for configurable test pile service. The method includes: calling the server to obtain the service request of the hypertext transfer protocol sent by the client, and generating a corresponding calling request according to the service request; The request is sent to the test stub server; the call server receives the configuration result fed back by the test stub server corresponding to the call request, and generates a corresponding service result according to the configuration result and sends it to the client. It can solve the technical problems in the prior art that the process of setting the interceptor in the calling server is complicated, and manual loading and management are complicated.

Description

Method and system for configurable test stub service

technical field

The present invention relates to the field of computer technology, in particular to a method and system for configurable test stub services.

Background technique

Hypertext Transfer Protocol (HyperTextTransferProtocol, HTTP) is the most widely used network protocol on the Internet. All WWW documents must comply with this standard. HTTP is a standard for client and server requests and responses. The client side is the end user and the server side is the website. Usually, an HTTP client initiates a request to establish a Transmission Control Protocol (Transmission Control Protocol, TCP) connection to a designated port on the server. The server side listens to the request sent by the client on the specified port. Once the connection request is received, the server (to the client) sends back a status line, such as "HTTP/1.1200 OK", and a response message, which may be the requested file, an error message, or some other information.

Now, the client's test of HTTP is usually to send the request initiated by the client to the calling server and add an interceptor to the calling server, intercept the request sent by the client, and return the simulated response result according to the intercepted request to test the client Whether the processing after the terminal receives the response meets the expected needs. Adding an interceptor requires modifying the code that calls the server system, and when modifying, the configuration file needs to be manually triggered to reload, which cannot take effect in real time, and the management is complicated, which may easily cause operation and maintenance accidents.

Contents of the invention

In view of this, the embodiments of the present invention provide a method and system for configurable test stub services to solve the technical problems in the prior art that the process of adding an interceptor to a calling server is complicated, and manual loading and management are complicated.

In the first aspect, the embodiment of the present invention provides a method for configurable test stub service, including:

Invoking the server to obtain the service request of the hypertext transfer protocol sent by the client, and generating a corresponding invocation request according to the service request;

The calling server modifies the configuration file, and sends the calling request to the test stub server according to the modified configuration file;

The invocation server receives the configuration result corresponding to the invocation request fed back by the test stub server, generates a corresponding service result according to the configuration result, and transmits it to the client.

In the second aspect, the embodiment of the present invention also provides a system for configurable test stub services, including:

The request acquisition module is configured in the invocation server, and is used to acquire the service request of the hypertext transfer protocol sent by the client, and generate a corresponding invocation request according to the service request;

A modification module, configured on the calling server, is used to modify the configuration file, and send the calling request to the test stub server according to the modified configuration file;

The receiving module is configured on the invocation server, and is used for receiving the configuration result corresponding to the invocation request fed back by the test stub server, and generating a corresponding service result according to the configuration result and sending it to the client.

The method and system for configurable test stub service provided by the embodiment of the present invention obtains the service request of the hypertext transfer protocol sent by the client by calling the server, generates a call request and sends the call request to the test stub according to the modified configuration file The server does not need to install an interceptor in the calling server, which is not only simple and convenient, but also makes the configuration modification take effect in real time. The invocation server receives the configuration result corresponding to the invocation request fed back by the test stub server, and generates a request result according to the configuration result and sends it to the client, so that all processing of the invocation request is performed by the test stub server. The environment is irrelevant, therefore, operation and maintenance accidents caused by configuration problems can be avoided, and all call requests are sent to the test stub server, which is easy to manage and easy to find problems after they occur. Only by changing the test stub server, the configuration result of the call request can be changed, which also makes the change more controllable.

Description of drawings

Other characteristics, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

FIG. 1 is a flow chart of a method for configuring a test stub service provided by Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a method for configuring a test stub service provided by Embodiment 2 of the present invention;

3 is a flow chart of the test stub server outputting the configuration result to the calling server in a method for configuring the test stub service provided by Embodiment 3 of the present invention;

FIG. 4 is a flow chart of the test stub server parsing and invoking requests in a method for configuring a test stub service provided by an embodiment of the present invention;

FIG. 5 is a flow chart of a method for configuring a test stub service provided by Embodiment 4 of the present invention;

FIG. 6 is a flow chart of the test stub server parsing and invoking requests in a method for configurable test stub services provided by an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a system for configuring test stub services provided by Embodiment 5 of the present invention.

detailed description

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, but not to limit the present invention. In addition, it should be noted that, for the convenience of description, only parts related to the present invention are shown in the drawings but not all content.

Embodiment one

FIG. 1 is a flow chart of a method for configuring a test stub service provided by Embodiment 1 of the present invention. This embodiment is applicable to the case of intercepting and processing the service request sent by the client. The method for configurable test stub service provided in this embodiment can be executed by a system for configurable test stub service, and the system can be implemented by software and/or hardware, and integrated into a corresponding terminal device. As shown in Figure 1, the method includes:

S110. Invoke the server to acquire the service request of the hypertext transfer protocol sent by the client, and generate a corresponding invocation request according to the service request.

Exemplarily, the client may be a terminal device held by the customer, such as a desktop computer, a notebook computer, a tablet computer, a mobile phone, and the like. Clients can display HTML content of web servers or file systems through applications such as browsers, and allow users to interact with these files. The service request sent by the client is input by the user through an application program such as a browser, and is processed by the client to generate a request following the hypertext transfer protocol. The specific processing method can be set according to the actual situation. The calling server is a device that can receive the service request sent by the client, and generate a corresponding calling request by parsing the received service request and calling related services of other servers. Each invocation server can receive service requests sent by at least one client. The invocation request can be a request that can be sent to the target web server generated after the invocation server parses the received service request, and can include data such as the Uniform Resource Locator and IP address of the invocation target web server, and the specific content of the invocation service. Wherein, the specific manner of invoking the server to resolve the service request and generate the corresponding invocation request can be set according to the actual situation, and is not limited here.

S120. The calling server modifies the configuration file, and sends the calling request to the test stub server according to the modified configuration file.

Exemplarily, after the invocation server obtains the invocation request, it reads the configuration file in the operating system, and sends the invocation request to the target device according to the data in the configuration file, wherein the configuration file is stored in the invocation server's operating system and contains specific data The file, such as the hosts file, can contain content such as the domain name of the network server and the mapping relationship between the IP address. Call the server to modify the configuration file to ensure that the call request can be sent to the test stub server according to the modified configuration file. The test stub server is a server that can perform specific test functions. Preferably, the test stub server in this embodiment can parse the invocation request, and search the database for the configuration related to the invocation request to generate a configuration result. The same invocation server can receive different service requests and generate different invocation requests, but refer to the same configuration file for subsequent processing of the invocation request. Therefore, it should be noted that the modification of the configuration file by the invocation server in this step is not limited to After calling the request, before receiving the service request sent by the client, or modify the configuration file in real time according to actual needs.

S130. The invocation server receives the configuration result corresponding to the invocation request fed back by the test stub server, generates a corresponding service result according to the configuration result, and transmits it to the client.

Exemplarily, the configuration result is a preset simulated response result for different call requests. The simulated response result may be a set error result, and different call requests may correspond to different simulated response results. When the invocation server receives the configuration result fed back by the test stub server, it means that the test stub server has received the invocation request and responded to generate the configuration result. After the calling server receives the configuration result, it parses the configuration result to generate the corresponding service result. Wherein, the calling server can call the services of other related servers according to the configuration result to generate the service result that the client can respond to. The specific parsing and calling methods of the calling server can be set according to the actual situation, which is not limited here. The client responds according to the received service result. If the service result is an error result, the client's ability to handle the error result can be tested according to the client's response to the error result. It should be noted that after analyzing the received configuration results, the invoking server believes that the configuration results may not be sent to the client. At this time, the invoking server may not send the results fed back by the test stub server to the client, but the invoking server itself Analysis processing can determine the processing capability of the calling server for the configuration result.

In the method of configurable test stub service provided by Embodiment 1 of the present invention, the invocation server can generate a corresponding invocation request by parsing the obtained service request, and send the invocation request to the test stub server according to the modified configuration file, and receive The corresponding configuration results fed back by the test stub server are used for subsequent processing. In this way, there is no need to install an interceptor in the calling server, and the configuration modification can take effect in real time by modifying the configuration file of the calling server, and can avoid operation and maintenance accidents caused by configuration problems. Call requests are sent to the test pile server, which is easy to manage and easy to find problems after they occur.

Further, the method for configuring the test stub service provided by this embodiment may also include:

The test stub server receives the invocation request sent by the invocation server, and outputs a corresponding configuration result to the invocation server according to the invocation request.

Exemplarily, after the test stub server receives the invocation request, it parses the invocation request to obtain a configuration result corresponding to the invocation request, and sends the configuration result to the invocation server, simulating that the target network server completes the response to the invocation request . In this way, only the test stub server needs to be changed to change the configuration result of the call request, which also makes the change more controllable.

Embodiment two

FIG. 2 is a flowchart of a method for configuring a test stub service provided by Embodiment 2 of the present invention. Based on the first embodiment, this embodiment modifies the configuration file of the calling server, and optimizes sending the calling request to the test stub server according to the modified configuration file. Referring to Figure 2, the method includes:

S210, invoking the server to acquire the service request of the hypertext transfer protocol sent by the client, and generating a corresponding invocation request according to the service request.

S220. The invoking server acquires an IP address addition instruction.

Exemplarily, the call server to obtain the IP address addition instruction may be to obtain the IP address addition instruction issued by the call server, or to obtain the IP address addition instruction issued by other devices that interact with the call server for data. The other devices are preferably configuration servers , where the configuration server is a hardware server with data and/or file management functions. Preferably, an instruction is added for invoking the server to obtain the IP address issued by the configuration server. The advantage of using the configuration server to send IP address addition instructions to the calling server is: when there are too many calling servers in the system, the configuration server will uniformly manage the modification of the configuration files of each calling server, which can save modification time and improve modification efficiency. The configuration server may obtain the IP address addition instruction through the visualization window and then send the IP address addition instruction to the calling server, wherein the visualization window is a window displayed on the screen and viewable. The configuration server may also generate an IP address addition instruction according to specific rules, and send the IP address addition instruction to the calling server. The IP address adding instruction may include the IP address of the target device sent by the calling request and the way of adding the IP address. The target device is a device that can receive and parse the call request, but is not limited to the target network server. Preferably, the target device is a test stub server, and the IP address is the IP address of the test stub server. There is no limitation on the time sequence for invoking the server to obtain the IP address addition instruction, that is, the invocation server can obtain the IP address addition instruction in real time.

S230. The calling server adds the IP address of the test stub server to the configuration file according to the IP address adding instruction.

Exemplarily, the calling server adds the IP address of the test stub server in the configuration file according to the IP address addition instruction, preferably, the IP address is added before or after the domain name of the target network server in the configuration file, preferably in the target network Add the IP address after the domain name of the server. If the IP address of other target devices already exists in the configuration file, you can add an instruction according to the obtained IP address at this time, and replace the original IP address in the configuration file with the newly obtained IP address. Further, the calling server can display the process of adding the IP address through a visual window, which is convenient for the user to watch and manually modify during the adding process.

S240. The calling server sends the calling request to a test stub server according to the IP address.

Exemplarily, if the IP address of the test stub server is added in the configuration file, when the invocation server sends the invocation request, it will send the invocation request to the test stub server according to the IP address in the configuration file. Wherein, the specific setting method of the IP address of the test stub server may be set according to the actual situation.

S250. The invocation server receives the configuration result fed back by the test stub server corresponding to the invocation request, generates a corresponding service result according to the configuration result, and transmits it to the client.

In the method of configurable test stub service provided by Embodiment 2 of the present invention, after the call server obtains the call request, it adds an instruction according to the IP address, and adds the IP address of the test stub server in the configuration file, so that the call server will call the Send the request to the test stub server, and respond when the configuration result fed back by the test stub server is received. In this way, all call requests can be sent to the test stub server. Since the test stub server has nothing to do with the online environment, operation and maintenance accidents caused by configuration problems can be avoided, and it is easy to manage and find problems after they occur.

Embodiment three

FIG. 3 is a flow chart of the test stub server outputting configuration results to the calling server in a method for configuring a test stub service provided by Embodiment 3 of the present invention. In this embodiment, on the basis of the first embodiment, the test stub server receives the invocation request sent by the invocation server, and outputs a corresponding configuration result to the invocation server according to the invocation request to optimize the steps. As shown in Figure 3, the output configuration result of the test stub server in the method for configuring the test stub service to the calling server includes:

S310. The test stub server receives the invocation request sent by the invocation server.

Exemplarily, the test stub server can receive all invocation requests sent by at least one invocation server in real time.

S320. The test stub server checks whether there is a configuration related to the invocation request, and if so, outputs the corresponding configuration result to the invocation server according to the configuration, otherwise, sends the invocation request to the target network server .

Exemplarily, after the test stub server receives the invocation request, it checks whether there is a configuration related to the invocation request in the database, and if so, outputs the corresponding configuration result to the invocation server. If there is no configuration related to the invocation request in the test stub server, the invocation request is sent to the external interface, and then sent to the target network server through the external interface. Wherein, the database can be configured in the test stub server or in other servers. If the database is configured in the test stub server, the test stub server directly accesses the database configured in the test stub server when checking whether there is a configuration related to the call request. If the database is configured in other servers, the test stub server needs to access other servers, and check whether there is matching data in the databases of other servers. The type of writing and/or storage of data in the database can be controlled through the configuration server. Preferably, referring to Fig. 4, this step may include:

S321. The test stub server resolves the calling domain name in the calling request.

Exemplarily, invoking the domain name may include determining the Uniform Resource Locator of the target web server and the IP address of the target web server. After receiving the invocation request, the test stub server parses the invocation domain name in the invocation request to obtain the uniform resource locator and IP address of the target network server.

S322. The test stub server checks whether there is a domain name configuration corresponding to the calling domain name in the database.

Exemplarily, a certain number of invocation domain names are pre-stored in the database viewed by the test stub server. After parsing the invocation domain name in the invocation request, the test stub server checks whether the same invocation domain name exists in the database, that is, checks whether there is a domain name configuration corresponding to the invocation domain name in the invocation request in the database. The test stub server can be set to check whether there is a configuration in the database that matches the uniform resource locator and IP address of the target web server in the calling domain name, or it can be set to check whether there are only configurations in the database that match the target web server in the calling domain name For the configuration matching any one of the uniform resource locator or the IP address, the specific setting method can be set according to the actual situation. Wherein, if there is a domain name configuration corresponding to the called domain name in the database, execute S323, and if there is no domain name configuration corresponding to the called domain name in the database, execute S325.

S323. If there is a domain name configuration corresponding to the invocation domain name, the test stub server analyzes the invocation service type in the invocation request.

Exemplarily, if the check result shows that there is a domain name configuration corresponding to the invocation domain name in the database, the test stub server continues to analyze the invocation service type in the invocation request. Wherein, the invocation service type is a service type provided by the invocation target network server, such as opening a home page of the target network server, or playing a video and other services.

S324. The test stub server checks whether there is a service configuration corresponding to the invocation service type in the database, and if so, outputs a configuration result corresponding to the invocation request to the invocation server according to a preset template, Otherwise, send the calling request to the target network server.

Exemplarily, a certain number of invocation service types are pre-stored in the database viewed by the test stub server, and each invocation service type corresponds to a specific preset template, wherein different preset templates can generate different configuration results. When the database viewed by the test stub server has a configuration corresponding to the calling domain name in the calling request, it will continue to check whether there is the same calling service type as the calling request in the database, that is, whether there is a configuration corresponding to the calling service type in the calling request in the database. Service configuration. If there is a corresponding service configuration, the test stub server obtains a preset template corresponding to the invocation service type, generates and outputs a corresponding configuration result to the invocation server according to the preset template, wherein the configuration result is a simulated response result. If there is no service configuration corresponding to the invocation service type in the configuration file of the invocation request in the database, the test stub server sends the invocation request to an external interface, and then sends the invocation request to the target network server through the external interface. The external interface is an interface for data transmission between the test stub server and other servers, preferably an interface for data transmission between the test stub server and the network server.

S325. If there is no domain name configuration corresponding to the calling domain name, the test stub server sends the calling request to the target network server.

Exemplarily, if the database viewed by the test stub server does not have a domain name configuration corresponding to the calling domain name in the calling request, the calling request is sent to the external interface, and then sent to the target network server by the external interface. After receiving the invocation request, the target network server feeds back the response result to the external interface, and sends it to the invocation server through the external interface, and the invocation server parses and generates a service result. Alternatively, the target network server may directly feed back the result to the invocation server after receiving the invocation request, and the invocation server parses and generates a service result.

In the method of configurable test stub service provided by Embodiment 3 of the present invention, the test stub server parses the received call request and checks whether there is a configuration corresponding to the call request in the database. type corresponding to the configuration, the test stub server will generate and output the corresponding configuration results to the invocation server according to the preset template, if there is no configuration corresponding to the invocation domain name or invocation service type in the configuration file of the invocation request in the database, then The test stub server sends the call request to the target network server. All the processing of call requests is carried out by the test stub server. Since the test stub server has nothing to do with the online environment, operation and maintenance accidents caused by configuration problems are avoided, and the test stub server performs shunt processing of call requests, which is convenient for management. It is easy to find the problem after the problem.

Embodiment Four

FIG. 5 is a flowchart of a method for configuring a test stub service provided by Embodiment 4 of the present invention. This embodiment is a preferred example. Referring to Figure 5, the method includes:

S510, xxxService initiates a request to call the api.yyy.com/service service.

Exemplarily, xxxService is a client, and api.yyy.com/service is a third-party service on a specific network server.

S520. Modify the hosts file of the calling server.

Exemplarily, the hosts file is a configuration file in the operating system of the calling server, and the hosts file of the calling server can be modified through a visualization window. The modification method is to add an instruction to obtain the IP address of the test stub server from the configuration server and add the IP address of the test stub server to the host file. For example, api.yyy.com192.168.6.66. That is, add 192.168.6.66 after the uniform resource locator (UniformResoureLocator, URL) api.yyy.com of api.yyy.com/service, where 192.168.6.66 is the IP address of the test stub server, where api.yyy.com is The URL of the third-party service pre-stored in the configuration file. It should be noted that this step can be placed before S510.

S530. The calling server receives a request from xxxService to call the api.yyy.com/service service, generates a corresponding calling request and forwards it to the test stub server.

Exemplarily, after the invocation server receives the request for invoking the api.yyy.com/service service initiated by xxxService, it parses and processes the service request and generates a corresponding invocation request. Since the IP address of the test stub server is added to the configuration file, the invocation server can send the invocation request to the test stub server according to the IP address.

S540. After receiving the invocation request, the test stub server compares the configuration in the database, and returns the configuration in the database as a result if there is a relevant configuration in the database, otherwise accesses the external system directly.

Exemplarily, if there is no configuration related to the call request in the database, the test stub server sends the call request to an external system through an external interface, and the external system may be a web server corresponding to api.yyy.com. With reference to Fig. 6, this step comprises:

S541. The test stub server receives the calling request.

S542. The test stub server queries the database according to the URL and the IP address.

Exemplarily, the corresponding configuration is queried in the database according to the URL and IP address in the call request. If there is no relevant configuration, execute S543, and if there is relevant configuration, execute S544.

S543. If there is no relevant configuration, the test stub server directly invokes the external interface.

Exemplarily, if there is no configuration corresponding to the URL and IP address of the invocation request in the database, the invocation request is sent to the external interface, and then sent to the external device through the external interface.

S544. If there is a relevant configuration, the test stub server judges whether it matches the calling service type.

Exemplarily, if there is a configuration corresponding to the URL and IP address of the invocation request in the database, the test stub server determines whether there is a configuration in the database that matches the invocation service type of the invocation request. If there is a configuration matching the calling service type in the database, execute S546, otherwise execute S545.

S545. If it does not match the calling service type, the test stub server directly calls the external interface.

Exemplarily, if they do not match, the test stub server sends the call request to the external interface, and sends it to the external device through the external interface.

S546. If the parameter matches the invocation service type, the test stub server parses the parameters to fill the template.

Exemplarily, if there is a configuration corresponding to the calling service type in the database, the test stub server parses the parameters corresponding to the configuration, and fills the parsed parameters in the template.

S547. Generate a configuration result according to the template.

Exemplarily, the test stub server generates configuration results according to the parameters in the template.

S548. The result is returned to the caller, and the process ends.

Exemplarily, the configuration result is fed back to the caller that sends the call request, that is, the call server, and the process ends.

In the method for configurable test stub service provided by Embodiment 4 of the present invention, the call request is sent to the test stub server by invoking the server to modify the configuration file. If there is a configuration corresponding to the call request in the database viewed by the test stub server, then Output the configuration result to the caller. If there is no configuration corresponding to the call request in the database viewed by the test stub server, the call request will be sent to the external device, so that the call server does not need to set an interceptor, and it is easy to manage and can avoid operation and maintenance ACCIDENT.

Embodiment five

FIG. 7 is a schematic structural diagram of a system for configuring test stub services provided by Embodiment 5 of the present invention. As shown in FIG. 7 , the system includes an invocation server 701 and a test stub server 702 .

Wherein, the invocation server 701 may include: a request acquisition module, configured to acquire a hypertext transfer protocol service request sent by the client, and generate a corresponding invocation request according to the service request; a modification module, configured to modify the configuration file, And according to the modified configuration file, the call request is sent to the test stub server 702; the receiving module is used to receive the configuration result corresponding to the call request fed back by the test stub server 702, and generate a configuration result according to the configuration result The corresponding service result is sent to the client.

Further, the modification module may include: an instruction acquisition unit, configured to acquire an IP address addition instruction; an address addition unit, configured to add an instruction according to the IP address, and add the IP address of the test stub server 702 in the configuration file a sending unit, configured to send the call request to the test stub server 702 according to the IP address.

Preferably, the test stub server 702 may include: an output module, configured to receive an invocation request sent by the invocation server 701 , and output a corresponding configuration result to the invocation server 701 according to the invocation request.

Further, the output module may include: a request receiving unit, configured to receive the invocation request sent by the invocation server 701; a configuration unit, configured to check whether there is a configuration related to the invocation request, and if so, follow the The above configuration outputs the corresponding configuration result to the calling server 701, otherwise, sends the calling request to the target network server.

Preferably, the configuration unit may include: a domain name confirmation subunit, configured to resolve the calling domain name in the calling request; a domain name matching subunit, used to check whether there is a domain name configuration corresponding to the calling domain name in the database; The confirmation subunit is used to analyze the calling service type in the calling request if there is a domain name configuration corresponding to the calling domain name in the database; the service matching subunit is used to check whether there is a configuration corresponding to the calling domain name in the database. The service configuration corresponding to the calling service type, if it exists, output the configuration result corresponding to the calling request to the calling server according to the preset template, otherwise, send the calling request to the target network server; send A subunit, configured to send the calling request to the target network server if there is no domain name configuration corresponding to the calling domain name in the database.

On the basis of the above embodiments, the configuration result is a preset simulation response result for different call requests.

The system for configurable test stub service provided by Embodiment 5 of the present invention can be used to execute the method for configurable test service provided by any of the above embodiments, and has corresponding functional modules and beneficial effects for executing the method.

Note that the above are only preferred embodiments of the present invention and applied technical principles. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present invention, and the present invention The scope is determined by the scope of the appended claims.

Claims (12)

1. A method for configurable test stub service, comprising: Invoking the server to obtain the service request of the hypertext transfer protocol sent by the client, and generating a corresponding invocation request according to the service request; The calling server modifies the configuration file, and sends the calling request to the test stub server according to the modified configuration file; The invocation server receives the configuration result corresponding to the invocation request fed back by the test stub server, generates a corresponding service result according to the configuration result, and transmits it to the client. 2. The method according to claim 1, wherein the calling server modifies the configuration file, and sending the calling request to the test stub server according to the modified configuration file comprises: The calling server obtains an IP address addition instruction; The calling server adds an instruction according to the IP address, and adds the IP address of the test stub server in the configuration file; The calling server sends the calling request to the test stub server according to the IP address. 3. The method according to claim 1, further comprising: The test stub server receives the invocation request sent by the invocation server, and outputs a corresponding configuration result to the invocation server according to the invocation request. 4. The method according to claim 3, wherein the test stub server receives the invocation request sent by the invocation server, and outputting a corresponding configuration result to the invocation server according to the invocation request comprises: The test stub server receives the invocation request sent by the invocation server; The test stub server checks whether there is a configuration related to the invocation request, and if so, outputs the corresponding configuration result to the invocation server according to the configuration, otherwise, sends the invocation request to the target network server. 5. The method according to claim 4, wherein the test stub server checks whether there is a configuration related to the invocation request, and if it exists, outputs a corresponding configuration result to the invocation server according to the configuration , otherwise, sending the call request to the target web server includes: The test stub server resolves the calling domain name in the calling request; The test stub server checks whether there is a domain name configuration corresponding to the calling domain name in the database; If there is a domain name configuration corresponding to the invocation domain name, the test stub server resolves the invocation service type in the invocation request; The test stub server checks whether there is a service configuration corresponding to the invocation service type in the database, and if it exists, outputs the configuration result corresponding to the invocation request to the invocation server according to a preset template, otherwise, sending the calling request to the target web server; If there is no domain name configuration corresponding to the calling domain name, the test stub server sends the calling request to the target network server. 6. The method according to any one of claims 1-5, wherein the configuration result is a preset simulated response result for different call requests. 7. A system for configurable test stub services, comprising: The request acquisition module is configured in the invocation server, and is used to acquire the service request of the hypertext transfer protocol sent by the client, and generate a corresponding invocation request according to the service request; A modification module, configured on the calling server, is used to modify the configuration file, and send the calling request to the test stub server according to the modified configuration file; The receiving module is configured on the invocation server, and is used for receiving the configuration result corresponding to the invocation request fed back by the test stub server, and generating a corresponding service result according to the configuration result and sending it to the client. 8. The system according to claim 7, wherein the modification module comprises: An instruction acquisition unit, configured to acquire an IP address to add an instruction; The address adding unit is used to add the IP address of the test stub server in the configuration file according to the IP address adding instruction; A sending unit, configured to send the call request to the test stub server according to the IP address. 9. The system according to claim 7, further comprising: The output module is configured on the test stub server, and is used for receiving the invocation request sent by the invocation server, and outputting corresponding configuration results to the invocation server according to the invocation request. 10. The system according to claim 9, wherein the output module comprises: a request receiving unit, configured to receive the invocation request sent by the invocation server; The configuration unit is configured to check whether there is a configuration related to the invocation request, and if so, output a corresponding configuration result to the invocation server according to the configuration, otherwise, send the invocation request to a target network server. 11. The system according to claim 10, wherein the configuration unit comprises: A domain name confirmation subunit, configured to resolve the calling domain name in the calling request; The domain name matching subunit is used to check whether there is a domain name configuration corresponding to the calling domain name in the database; A service confirmation subunit, configured to resolve the invocation service type in the invocation request if there is a domain name configuration corresponding to the invocation domain name in the database; The service matching subunit is used to check whether there is a service configuration corresponding to the invocation service type in the database, and if it exists, output the configuration result corresponding to the invocation request to the invocation server according to a preset template, Otherwise, send the call request to the target web server; The sending subunit is configured to send the calling request to the target network server if there is no domain name configuration corresponding to the calling domain name in the database. 12. The system according to any one of claims 7-11, wherein the configuration result is a preset simulated response result for different call requests.