CN114640614A

CN114640614A - RPC interface automatic test method, system, electronic equipment, medium and product

Info

Publication number: CN114640614A
Application number: CN202210436452.9A
Authority: CN
Inventors: 王成义; 王禹; 左超; 刘曼
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-04-24
Filing date: 2022-04-24
Publication date: 2022-06-17
Anticipated expiration: 2042-04-24
Also published as: CN114640614B

Abstract

The utility model provides a RPC interface automated testing method, can be used to financial field or other fields, this method is executed by the sandbox, realizes RPC interface automated testing through sandbox control registration center cluster appointed route, includes: acquiring a test request from an automatic test platform; registering a simulation port and deactivating a downstream server to the registration center cluster according to the test request and the preset configuration rule; and simulating the test request according to the simulation port to generate a response piece message. The present disclosure also provides a sandbox, a registry cluster, an RPC interface automated testing system, an electronic device, a computer readable storage medium and a computer program product.

Description

RPC interface automatic test method, system, electronic equipment, medium and product

Technical Field

The disclosure relates to the technical field of automated testing, in particular to an RPC interface automated testing method, system, electronic device, storage medium and program product.

Background

With the gradual increase of the requirements of each technical company on the software quality of the company, each enterprise needs a powerful test platform to support the software quality test, however, the system complexity is gradually increased, the interaction between systems is more and more complex, and the dependence of each internal application test is forced to be strengthened. And a sandbox is used as a baffle to decouple the testing functions of the modules. However, for an internal call service of an RPC (remote procedure call service), in the prior art, unless the version number or the interface name of an application code is modified to realize the simulation of the service, the problem that the test result does not have authenticity and the sequencing efficiency is low due to the change of the tested code is involved.

Disclosure of Invention

In order to solve the problems in the prior art, embodiments of the present disclosure provide a method, a system, an electronic device, a storage medium, and a program product for RPC interface automated testing, so as to implement that a registry cluster is intelligently controlled through a sandbox without modifying application codes, and an automated testing process is completed by specifying a route.

The first aspect of the present disclosure provides an RPC interface automated testing method, which is executed by a sandbox, and implements RPC interface automated testing by controlling a registration center cluster to specify a route through the sandbox, including: acquiring a test request from an automatic test platform; registering a simulation port and deactivating a downstream server to the registration center cluster according to the test request and the preset configuration rule; and simulating the test request according to the simulation port to generate a response piece message.

Further, the test request includes a transaction serial number, wherein, registering a simulation port and deactivating a downstream server to the registry cluster according to the test request and a preset configuration rule, includes: registering a simulation port to a registration center cluster according to the transaction serial number and a preset number rule in a preset configuration rule; and updating the state identification of the downstream server to the deactivation state according to the test request.

Further, the simulating receipt of the test request according to the simulation port and generating a receipt message include: and generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule.

Further, generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule, including: intercepting a preset number in the transaction flow serial number according to the transaction flow serial number; acquiring service data and a receipt code of the test request according to the preset number; and generating a receipt message corresponding to the test request according to the service data, the receipt code and a receipt message configuration rule in the preset configuration rule.

Further, a preset bit number in the transaction flow number is used for updating the identification state of the downstream server.

A second aspect of the present disclosure provides an RPC interface automated testing method, which is performed by a registry cluster, where the registry cluster performs communication interaction with a sandbox, and the method includes: responding to a newly added simulation interface request initiated by the sandbox; and deactivating the downstream server to enable the sandbox to perform simulation receipt on the test request according to the simulation port to generate a receipt message.

Further, deactivating the downstream server comprises: the status of the downstream server is identified as inactive.

Further, the method further comprises: acquiring a test request message from an application server; searching the service ID number in the test request message according to the service ID management file; and according to the retrieval result, indicating the sandbox to respond to the test request message or outputting a response message to the application server.

Further, the retrieval result includes: the presence or absence of a service interface corresponding to the service ID number; when a service interface corresponding to the service ID number exists, the registration center cluster forwards the test request message to the sandbox through the simulation port so that the sandbox responds to the test request message; and when the service interface corresponding to the service ID number does not exist, the registration center cluster outputs a response message to the application server.

The third aspect of the disclosure provides an RPC interface automated testing method, where an automated testing platform performs data interaction with a sandbox, and the sandbox performs data interaction with a registry cluster, and the method includes: the automatic test platform initiates a test request; responding to the test request by the sandbox, registering a simulation port to the registration center cluster and deactivating the downstream server according to the test request and a preset configuration rule; the sandbox simulates a receipt according to the simulation port to generate a receipt message, and outputs the receipt message to the automatic test platform; and the automatic test platform receives the receipt message, analyzes the test result of the test request, and records and stores the test result.

Further, the test request includes a transaction serial number, wherein, registering a simulation port and deactivating a downstream server to the registry cluster according to the test request and a preset configuration rule, includes: registering a simulation port to a registration center cluster according to the transaction serial number and a preset number rule in a preset configuration rule;

and updating the state identification of the downstream server to the deactivation state according to the test request.

Further, the simulating receipt of the test request according to the simulation port to generate a receipt message includes: and generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule.

A fourth aspect of the present disclosure provides a sandbox for implementing RPC interface automation test by sandbox control registration center cluster designated routing, including: the request acquisition module is used for acquiring a test request from the automatic test platform; the first processing module is used for registering a simulation port to the registration center cluster and deactivating a downstream server according to the test request and the preset configuration rule; and the second processing module is used for simulating the receipt of the test request according to the simulation port and generating a receipt message.

A fifth aspect of the present disclosure provides a registry cluster, the registry cluster interacting with a sandbox in communication, comprising: the request acquisition module is used for acquiring a newly-added simulation interface request initiated by the sandbox; and the first processing module is used for deactivating the downstream server so that the sandbox can simulate the receipt of the test request according to the simulation port to generate a receipt message.

A sixth aspect of the present disclosure provides an RPC interface automated test system, including: the system comprises an automatic test platform, a sandbox and a registration center cluster; the automatic test platform initiates a test request; responding to the test request by the sandbox, registering a simulation port to the registration center cluster and deactivating the downstream server according to the test request and a preset configuration rule; the sandbox simulates a receipt according to the simulation port, generates a receipt message and outputs the receipt message to the automatic test platform; and the automatic test platform receives the receipt message, analyzes the test result of the test request, and records and stores the test result.

A seventh aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the RPC interface automated testing method provided by the first, second or third aspect.

An eighth aspect of the present disclosure provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements the RPC interface automated testing method provided by the first, second or third aspect of the present disclosure.

A ninth aspect of the present disclosure provides a computer program product comprising a computer program which, when executed by a processor, implements the RPC interface automated testing method provided by the first, second or third aspects of the present disclosure.

The method controls a registration center cluster to register RPC services to be simulated in a testing mode through a sandbox configuration mode, then based on uniqueness of a transaction flow serial number of a testing scene, sandbox receipt content is appointed through the transaction flow serial number, and sandbox intelligent response is completed through configuration of a receipt message corresponding to a flow serial number rule. In addition, the registration center cluster is intelligently controlled through the sandbox, the automatic testing process is completed by the specified route, and the purpose that no matter the sandbox simulates the receipt or requests the receipt of a downstream server, the application code does not need to be modified is achieved.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a diagram schematically illustrating an application scenario of an RPC interface automated testing method according to an embodiment of the present disclosure;

FIG. 2 schematically shows a flow chart of a RPC interface automated testing method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow diagram of a sandbox simulated receipt according to one embodiment of the present disclosure;

FIG. 4 schematically shows a flow chart of a RPC interface automated testing method according to another embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow diagram of a realistic test scenario according to an embodiment of the present disclosure;

FIG. 6 schematically shows a flow chart of a RPC interface automated testing method according to yet another embodiment of the present disclosure;

FIG. 7 schematically illustrates a block flow diagram of a sandbox simulation response piece according to an embodiment of the present disclosure;

FIG. 8 schematically illustrates a block flow diagram of a realistic test scenario, according to an embodiment of the present disclosure;

FIG. 9 schematically illustrates a block diagram of a sandbox according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a registry cluster according to an embodiment of the present disclosure;

FIG. 11 schematically illustrates a block diagram of an RPC interface automated test system according to an embodiment of the present disclosure;

fig. 12 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that these descriptions are illustrative only and are not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

Fig. 1 schematically shows an exemplary system architecture 100 that may be applied to the RPC interface automated testing method according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, a system architecture 100 according to this embodiment may include

end devices

101, 102, 103, a network 104, a sandbox 105, a registry cluster 106 and a downstream server 107. Network 104 is used to provide a medium for communication links between

terminal devices

101, 102, 103, sandbox 105, registry cluster 106 and downstream server 107. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user (e.g., a test engineer) may use

terminal devices

101, 102, 103 to interact with sandbox 105, registry cluster 106, and downstream servers 107 over network 104 to initiate test requests or receive response piece messages, etc. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as an automation test platform, various language software programming systems, a web browser application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having display screens and supporting web browsing, and the

terminal devices

101, 102, 103 provide an operating platform for upstream users, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The sandbox 105 provides an application service virtual operating environment for intelligently controlling the registry cluster 106 and realizing the directional transmission of messages. The sandbox 105 includes a sandbox management module and an interface agent module, and the sandbox management module is configured to analyze the test request and perform intelligent control on the registry cluster 106, and specifically control the activation or deactivation of the service port of the registry cluster 106.

The registry cluster 106 serves as a management platform for the downstream servers 107, and intelligently controls the registry cluster 106 through the sandbox 105, so that the registry cluster 106 registers a new simulation port and outputs an applicable downstream server port in the downstream servers 107 to the sandbox 105, so that the sandbox 105 directionally outputs a request message to a downstream server in the downstream servers 107.

The downstream server 107 may be a server providing various services, including a plurality of downstream servers, such as a backend management server (for example only) providing support for applications that users follow with the

terminal devices

101, 102, 103. The backend management server may perform response to the received user request and the like, and feed back the response result to the sandbox 105 and then to the

terminal devices

101, 102, and 103.

It should be noted that the RPC interface automation test method provided by the embodiment of the present disclosure may be generally executed by the sandbox 105 or the registry cluster 106. The RPC interface automated testing method provided by the embodiments of the present disclosure may also be performed by a server or server cluster that is different from sandbox 105 or registry cluster 106 and that is capable of communicating with

terminal devices

101, 102, 103 and/or sandbox 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 2 schematically shows a flow chart of an RPC interface automation test method according to an embodiment of the present disclosure. As shown in fig. 2, the method is executed by a sandbox 105, and the RPC interface automation test is implemented by controlling the registration center cluster 106 to specify a route through the sandbox 105, and the flow of the method is suitable for a sandbox simulation scenario, and includes: steps S201 to S203.

In operation S201, a test request from an automated test platform is obtained.

In the embodiment of the present disclosure, the test engineer may generate test data and execute a test through an automated test platform installed in the

terminal devices

101, 102, and 103, and the automated test platform sends a test request to the sandbox 105. Wherein the test request at least comprises: test interface, service data and trade water serial number.

Specifically, the service data is used for performing interface automation test, and includes but is not limited to transaction type, transaction data, transaction interface, and the like. The transaction serial number in the test request has uniqueness, and is a serial number with preset digits. For example, the transaction serial number may be a 20-digit transaction serial number composed of numbers or a combination of letters and numbers, such as: l000 … 0001, the 20-bit character has a preset bit number for distinguishing the routing method, and the preset bit number can be the 5 th to 9 th bit numbers, the 6 th to 10 th bit numbers or the 7 th to 11 th bit numbers in the 20-bit transaction serial number.

It should be noted that, in the embodiments of the present disclosure, the transaction sequence number is merely an example, and does not constitute a limitation of the present disclosure.

In operation S202, a simulation port is registered with the registry cluster and a downstream server is deactivated according to the test request and the preset configuration rule.

In the embodiment of the present disclosure, the preset configuration rule includes a preset numbering rule and a receipt message configuration rule, the sandbox 105 registers a new simulation port to the registration center cluster 106 according to the transaction serial number and the preset numbering rule in the test request, and updates the state identifier of the downstream server 107 to a disabled state according to the preset number in the transaction serial number, and the registration center cluster 106 opens the simulation port to direct the test request response to the sandbox 105.

In the embodiment of the present disclosure, the registry cluster 106 is configured to manage multiple downstream servers, specifically, service ID number management, interface identifier state update or state registration storage, and the like, so as to implement sandbox simulated receipt and specified routing of a test request in a real test scene.

In operation S203, a simulation receipt is performed on the test request according to the simulation port, and a receipt message is generated.

In the embodiment of the present disclosure, the sandbox performs simulation receipt on the test request according to the simulation port, and generates a receipt message, which specifically includes: and generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule.

According to an embodiment of the present disclosure, as shown in fig. 3, step S203 specifically includes: step S301 to step S303.

In operation S301, a preset bit number in the transaction flow number is intercepted according to the transaction flow number.

In the embodiment of the present disclosure, the sandbox management module in the sandbox 105 intercepts the preset number in the transaction serial number according to the transaction serial number, where the preset number is used to obtain the service data and the response piece code in the test request.

In operation S302, the service data and the response piece code in the test request are obtained according to the preset bit number.

In operation S303, a receipt message corresponding to the test request is generated according to the service data, the receipt code, and a receipt message configuration rule in the preset configuration rule.

In the embodiment of the present disclosure, the sandbox 105 generates a response piece packet corresponding to the test request according to the obtained service data, the response piece code, and the configuration rule of the response piece packet. The receipt message configuration rule represents the mapping relation between the receipt code and the receipt message, and the corresponding receipt message can be obtained according to the service data, the receipt code and the receipt message configuration rule. Sandbox 105 forwards the generated response piece packet to the application server.

According to the embodiment of the disclosure, the test request may be a plurality of test requests, the sandbox obtains the plurality of test requests from the automated test platform, and sequentially performs the test requests and preset configuration rules on the plurality of test requests to register corresponding simulation ports and disable downstream servers to the registry cluster.

In the embodiment of the disclosure, after receiving a test request from an automated test platform, a sandbox registers an analog port in a registration center cluster according to a transaction serial number and a preset configuration rule in the test request, where the preset configuration rule specifically includes an analog interface configuration rule and a receipt message format configuration rule. By presetting configuration rules, the sandbox simulates a uniform service among the services corresponding to registry cluster 106. Registry cluster 106 shuts down downstream server 107 and enables the pseudo-service when the emulation interface is invoked, so that the transaction is routed to the sandbox, enabling dynamic emulation of the transaction.

FIG. 4 schematically shows a flow chart of a RPC interface automated testing method according to another embodiment of the present disclosure.

As shown in fig. 4, the method is performed by a registry cluster 106, the registry cluster 106 communicatively interacting with a sandbox 105, comprising: steps S401 to S402.

In operation S401, a new simulation interface request initiated by a sandbox is responded.

In the embodiment of the present disclosure, the sandbox 105 obtains a test request from the automated testing platform, and registers a simulation port with the registry cluster 106 according to the test request and a preset configuration rule, and the registry cluster 106 registers a new simulation port in response to a request for a new simulation interface, and performs management and storage. For example, assuming that the registry cluster 106 stores service interface management files of 50 downstream servers, each time the registry cluster 106 responds to a new simulation interface request, a new simulation interface is added to the service interface management file, and at this time, the service interface management file in the registry cluster 106 stores the service interfaces of 50 downstream servers and 1 simulation interface. The service interfaces of the 50 downstream servers are respectively used for calling the corresponding 50 downstream servers, and the test request is forwarded to the sandbox through the simulation interface, so that the sandbox performs simulation receipt on the test request.

In operation S402, the downstream server is deactivated, so that the sandbox performs a simulation receipt on the test request according to the simulation port, and generates a receipt message.

In the embodiment of the present disclosure, the registry cluster 106 responds to the new interface request, and simultaneously identifies the states of 50 downstream servers in the service interface management file as the disabled states, so that the test request is directed to the sandbox 105 through the call simulation port to perform response receipt.

According to an embodiment of the present disclosure, in a real test scenario, as shown in fig. 5, the method further includes: steps 501 to 503.

In operation S501, the registry cluster 106 receives a test request message from an application server.

In the embodiment of the present disclosure, in a real test scenario, a test engineer initiates a test request message through an application server, where the test request message includes: test data, transaction stream numbers, service interfaces, service ID numbers, and the like.

In operation S502, the service ID number in the test request message is retrieved according to the service ID management file.

In the embodiment of the present disclosure, the registry cluster 106 stores a service ID management file, where the service ID management file is used to search for a service ID number in a test request message, find whether a service ID in the test request message exists in the registry cluster 106, and perform routing assignment on the test request message according to the search report.

In operation S503, the sandbox is instructed to respond to the test request message or output a response message to the application server according to the search result.

In the embodiment of the present disclosure, the retrieval result specifically includes two cases, one is that if the service ID number is not retrieved, and the corresponding service ID corresponds to the service ID number in the test request message, it indicates that the service interface corresponding to the service ID number does not exist in the service ID management file; if the service interface corresponding to the service ID number does not exist, the registration center cluster 106 outputs a response message to the application server, where the response message at least includes information such as "no response service interface exists, and test failure". And secondly, if the corresponding service ID corresponding to the service ID number in the test request message can be searched through the service ID number search, the service ID management file has a service interface corresponding to the service ID number. If a service interface corresponding to the service ID number exists, the registry cluster 106 forwards the test request packet to the sandbox 105 through the analog port, so that the sandbox responds to the test request packet. At this time, the sandbox management module in the sandbox 105 analyzes the transaction flow number in the test request message, obtains the corresponding preset number, and forwards the test request message to the corresponding downstream server for message receipt.

FIG. 6 schematically shows a flowchart of an RPC interface automated testing method according to yet another embodiment of the present disclosure.

As shown in fig. 6, the automated testing platform performs data interaction with sandbox 105, and sandbox 105 performs data interaction with registry cluster 106, including: steps S601 to S604.

In operation S601, the automated test platform initiates a test request.

In the embodiment of the disclosure, a test engineer generates test data through an automatic test platform and executes a test, and the automatic test platform initiates a test request to a sandbox, wherein the test request includes a test interface, a transaction serial number, service data and the like.

In operation S602, the sandbox responds to the test request, and registers a simulation port with the registry cluster and deactivates the downstream server according to the test request and the preset configuration rule.

In the embodiment of the disclosure, the sandbox responds to the test request, registers the simulation port to the registration center cluster through the sandbox management module according to the transaction serial number and the preset number rule in the preset configuration rule, and updates the state identifier of the downstream server to the disabled state according to the test request.

In operation S603, the sandbox performs simulation receipt on the test request according to the simulation port to generate a receipt message, and outputs the receipt message to the automated test platform.

In the embodiment of the disclosure, the sandbox management module generates a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule. Specifically, the sandbox management module intercepts a preset number in the transaction serial number according to the transaction serial number, wherein the preset number is used for acquiring the service data and the receipt code in the test request. And acquiring the service data and the receipt code in the test request according to the preset bit number, generating a receipt message corresponding to the test request according to the service data, the receipt code and a receipt message configuration rule in the preset configuration rule, and outputting the receipt message to the automatic test platform.

In operation S604, the automated testing platform receives the receipt message, analyzes the test result of the test request, and records and stores the test result.

In the embodiment of the disclosure, the automated testing platform receives the receipt message returned by the sandbox, analyzes the test result of the test request, and records and stores the test result, and the test result can be used for comparative analysis of the test result when the same test request is initiated in a real scene.

Fig. 7 schematically shows a flowchart of an RPC interface automation testing method in a sandbox simulation scenario according to an embodiment of the present disclosure.

As shown in fig. 7, the method flow includes: steps S701 to S708.

In operation S701, a test engineer generates test data on an automated test platform and performs a test. The automated testing platform outputs the test request to the sandbox. The test request comprises service data, a test interface, a transaction serial number and the like.

In operation S702, the sandbox receives a test request from the automated testing platform, registers a simulation port with the registry cluster according to the test request and a preset configuration rule, and deactivates a downstream server.

In the embodiment of the disclosure, a sandbox management module in the sandbox judges and analyzes the transaction serial number in the test request, registers a simulation port to the registration center cluster according to the service data and the test interface type in the test request, judges whether the identifier of the simulation RPC interface is opened or closed according to the preset number in the transaction serial number with uniqueness, and starts or stops a downstream server according to the judgment result.

In operation S703, the registry cluster sends a registration success receipt to the automated testing platform.

In operation S704, the application server receives the test request, generates a request message according to the test request, and sends the request message to the registration center cluster, and invokes a new registered simulation port.

In operation S705, the registry cluster receives the request packet and forwards the request packet to the sandbox according to the new simulation port.

In operation S706, the sandbox receives the request packet, performs a response to the request packet according to the preset number and the preset configuration rule in the transaction flow number in the request packet, generates a corresponding response packet, and forwards the response packet to the application server.

In operation S707, the application server returns the test result to the automated testing platform according to the receipt message.

FIG. 8 is a flow chart of a method for automatically testing an RPC interface in a real test scenario according to an embodiment of the present disclosure.

As shown in fig. 8, the method flow includes: steps S801 to S807.

In operation S801, a test engineer initiates a test request on an application server, and the application server generates a corresponding test request message according to the test request.

In operation S802, the registry cluster receives a test request message from an application server.

In the embodiment of the disclosure, the registry cluster searches the service ID number in the test request message, specifically, compares the service ID number with the service ID stored in the service ID management file in the registry cluster, judges whether the service ID corresponding to the service ID number exists, and if the service ID exists, performs the next response; if the application server does not exist, the application server directly returns a receipt message, and the receipt message at least comprises information of 'no service ID number exists, test failure' and the like.

Specifically, if a service interface matching the service ID number exists in the service ID management file, the registry cluster calls the interface to perform response receipt on the test request packet, which is specifically divided into two cases, such as step S803 and step S804.

In operation S803, the registry cluster calls the service interface to perform response to the test request packet.

In the embodiment of the disclosure, if a service interface matched with the service ID number exists in the service ID management file, and the service ID number is correspondingly matched with one of the service interfaces in the 50 downstream servers, the registration center cluster calls the matched service interface to forward the test request packet to the downstream server to perform a receipt response.

In operation S804, the registry cluster calls the simulation interface to perform response to the test request packet.

In the embodiment of the present disclosure, if the service ID number is correspondingly matched with the analog interface, the registration center cluster calls the analog interface to forward the test request packet to the sandbox. The sandbox management module analyzes the preset bit number of the transaction process number in the test request message, and forwards the test request message to a corresponding matched downstream server in 50 downstream servers according to the analysis result.

In operation S805, the downstream server responds to the test request packet with a response receipt, and forwards the response receipt packet to the sandbox.

In operation S806, the sandbox forwards the received response piece packet to the application server, and completes the real scene test.

In operation S807, the application server receives the receipt message and performs analysis and storage of the test result.

It should be noted that the above embodiment flows are only exemplary illustrations, and do not constitute a limitation of the embodiments of the present disclosure.

In the embodiment of the disclosure, the registry cluster is intelligently controlled through the sandbox, so that the registry cluster performs routing designation according to the test request.

Fig. 9 schematically illustrates a sandbox structure for performing the RPC interface automated testing method shown in fig. 2 according to an embodiment of the present disclosure.

As shown in fig. 9, the sandbox 900 includes: a request acquisition module 910, a first processing module 920, and a second processing module 930.

A request obtaining module 910, configured to obtain a test request from an automated testing platform. In the embodiment of the disclosure, the request obtaining module 910 may be configured to perform the step S201 described above with reference to fig. 2, for example, and is not described in detail here.

The first processing module 920 is configured to register a simulation port with the registry cluster and disable the downstream server according to the test request and the preset configuration rule. In the embodiment of the disclosure, the first processing module 920 may be configured to, for example, execute the step S202 described above with reference to fig. 2, and is not described in detail here.

The second processing module 930 is configured to perform simulation receipt on the test request according to the simulation port, and generate a receipt message. In the embodiment of the disclosure, the second processing module 930 may be configured to perform the step S203 described above with reference to fig. 2, for example, and is not described in detail here.

Fig. 10 is a schematic diagram illustrating a structure of a registry cluster used for executing the RPC interface automation test method shown in fig. 4 according to an embodiment of the present disclosure.

As shown in fig. 10, the registry cluster 10 includes: a request acquisition module 1010 and a first processing module 1020.

The request obtaining module 1010 is configured to obtain a new simulation interface request initiated by a sandbox. In the embodiment of the disclosure, the request obtaining module 1010 may be configured to perform the step S401 described above with reference to fig. 4, for example, and is not described in detail here.

The first processing module 1020 is configured to deactivate the downstream server, so that the sandbox performs simulation receipt on the test request according to the simulation port, and generates a receipt message. In the embodiment of the disclosure, the first processing module 1020 may be configured to execute the step S402 described above with reference to fig. 4, for example, and is not described in detail herein.

FIG. 11 schematically illustrates an RPC interface automated testing system to perform the RPC interface automated testing method shown in FIG. 6, according to an embodiment of the present disclosure.

As shown in fig. 11, the RPC interface automated test system 1100 includes: automated test platform 1110, sandbox 1120, and registry cluster 1130.

The automated testing platform 1110 is configured to initiate a test request. In the embodiment of the disclosure, the automated testing platform 1110, for example, can be used to perform the step S601 described above with reference to fig. 6, and is not described in detail herein.

Sandbox 1120, which is used to respond to the test request and register 1130 new simulation ports and deactivate downstream servers with the registry cluster according to the test request and the preset configuration rules; and simulating the test request according to the simulation port to generate a receipt message, and outputting the receipt message to the automatic test platform. In the embodiment of the disclosure, the sandbox 1120 may be used to perform the steps S602 to S603 described above with reference to fig. 6, and details are not repeated here.

The automated testing platform 1130 is further configured to receive the receipt message, analyze the testing result of the testing request, and record and store the testing result. In the embodiment of the disclosure, the automated test platform 1130, for example, may be used to perform the step S604 described above with reference to fig. 6, and details thereof are not repeated herein.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be implemented at least partly as a computer program module, which when executed, may perform a corresponding function.

For example, any plurality of the request obtaining module 910, the first processing module 920 and the second processing module 930, or the request obtaining module 1010 and the first processing module 1020 may be combined and implemented in one module, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to the embodiment of the disclosure, at least one of the request obtaining module 910, the first processing module 920 and the second processing module 930, or the request obtaining module 1010 and the first processing module 1020 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementation manners of software, hardware and firmware, or implemented by a suitable combination of any several of them. Alternatively, at least one of the request obtaining module 910, the first processing module 920 and the second processing module 930, or the request obtaining module 1010 and the first processing module 1020 may be at least partially implemented as a computer program module, which may perform a corresponding function when executed.

The RPC interface automatic test method and system provided by the present disclosure can be used in the financial field or other fields, and it should be noted that the RPC interface automatic test method and system provided by the present disclosure can be used in the financial field, for example, in the financial field, the service process test of each service system, and can also be used in other fields except the financial field.

According to the method and the system for the automatic test of the RPC interface, the dynamic switching of the interface is simulated, and only the test engineer instruction is sent up according to the serial number rule of the transaction flow. After the simulation service is connected with the sandbox in a butt joint mode, normal interaction on a downstream server cannot be influenced, and the problem that the existing abnormal scene in a business process can only be tested by statically modifying codes or matching the downstream server is solved. The method can simultaneously and sequentially carry out receipt processing on the test requests or a plurality of test requests in the sandbox simulation scene and the real test scene, and the two scenes do not influence each other. In addition, the method does not need to modify application codes, tests the test module independently, shields the related dependence influence of an upstream and downstream duboo (Ali distributed service framework) interface, intelligently controls the registration center through the sandbox module, realizes the directional sending of messages, realizes the automatic execution drive, can automatically process according to the interface dimension, the project dimension, the function dimension, the automatic identification and the control concurrence when completing case execution, and simultaneously supports network request protocols such as Api, Rpc, HttpRest, database operation and the like.

Fig. 12 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present disclosure. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 12, the electronic apparatus 1200 described in this embodiment includes: a processor 1201 which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. The processor 1201 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1201 may also include on-board memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM1203, various programs and data necessary for the operation of the electronic apparatus 1200 are stored. The processor 1201, the ROM1202, and the RAM1203 are connected to each other by a bus 1204. The processor 1201 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM1202 and/or the RAM 1203. Note that the program may also be stored in one or more memories other than the ROM1202 and the RAM 203. The processor 1201 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1200 may also include input/output (I/O) interface 1205, according to an embodiment of the disclosure, input/output (I/O) interface 1205 also connected to bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I/O interface 1205: an input portion 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 1208 including a hard disk and the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. A driver 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is mounted on the drive 1210 as necessary, so that a computer program read out therefrom is mounted into the storage section 1208 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program, when executed by the processor 1201, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

An embodiment of the present invention further provides a computer-readable storage medium, which may be included in the apparatus/device/system described in the foregoing embodiment; or may exist separately and not be assembled into the device/apparatus/system. The computer readable storage medium carries one or more programs which, when executed, implement the RPC interface automated testing method according to an embodiment of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM1202 and/or the RAM1203 and/or one or more memories other than the ROM1202 and the RAM1203 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated by the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the RPC interface automatic testing method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 1201. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, and the like. In another embodiment, the computer program may also be transmitted in the form of a signal over a network medium, distributed, and downloaded and installed through the communication section 1209, and/or installed from the removable medium 1211. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program, when executed by the processor 1201, performs the above-described functions defined in the system of the embodiments of the present disclosure. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

It should be noted that each functional module in each embodiment of the present disclosure may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, or a part or all of the technical solution that substantially contributes to the prior art.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be appreciated by those skilled in the art that various combinations and/or combinations of the features recited in the various embodiments of the disclosure and/or the claims may be made even if such combinations or combinations are not explicitly recited in the disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

While the disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.

Claims

1. The RPC interface automatic test method is characterized in that the method is executed by a sandbox, and the RPC interface automatic test is realized by controlling the designated route of a registration center cluster through the sandbox, and comprises the following steps:

acquiring a test request from an automatic test platform;

registering a simulation port and deactivating a downstream server to the registration center cluster according to the test request and a preset configuration rule; and

and simulating the test request according to the simulation port to generate a response piece message.

2. The RPC interface automated testing method of claim 1, wherein the test request includes a transaction flow number, wherein registering a simulation port with the registry cluster and deactivating a downstream server according to the test request and preset configuration rules comprises:

registering the simulation port to the registration center cluster according to the transaction flow serial number and a preset serial number rule in the preset configuration rule; and

and updating the state identifier of the downstream server to be a deactivation state according to the test request.

3. The RPC interface automated testing method of claim 2, wherein the simulating receipt of the test request according to the simulation port and generating a receipt message comprises:

and generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule.

4. The RPC interface automation test method of claim 3, wherein the generating a response piece packet corresponding to the test request according to the simulation port, the test request and a response piece packet configuration rule in the preset configuration rule comprises:

intercepting preset position numbers in the transaction serial numbers according to the transaction serial numbers;

acquiring the service data and the receipt code of the test request according to the preset bit number;

and generating a receipt message corresponding to the test request according to the service data, the receipt code and a receipt message configuration rule in the preset configuration rule.

5. The RPC interface automated testing method of claim 2, wherein a predetermined bit number in the transaction stream number is used to update the identification status of the downstream server.

6. An RPC interface automated testing method, which is performed by a registry cluster that performs communication interaction with a sandbox, comprises:

responding to a newly added simulation interface request initiated by the sandbox; and the number of the first and second groups,

and deactivating a downstream server to enable the sandbox to simulate receipt of the test request according to the simulation port to generate a receipt message.

7. The RPC interface automated testing method of claim 6, wherein deactivating the downstream server comprises:

identifying a state of the downstream server as a deactivated state.

8. The RPC interface automated testing method of claim 6, further comprising:

acquiring a test request message from an application server;

searching the service ID number in the test request message according to the service ID management file;

and indicating the sandbox to respond to the test request message or outputting a receipt message to the application server according to the retrieval result.

9. The RPC interface automated testing method of claim 8, wherein the search results include: the presence or absence of a service interface corresponding to the service ID number;

when a service interface corresponding to the service ID number exists, the registration center cluster forwards the test request message to the sandbox through an analog port so that the sandbox responds to the test request message;

and when the service interface corresponding to the service ID number does not exist, the registration center cluster outputs a response piece message to the application server.

10. An RPC interface automatic test method is characterized in that an automatic test platform performs data interaction with a sandbox, the sandbox performs data interaction with a registry cluster, and the method comprises the following steps:

the automatic test platform initiates a test request;

the sandbox responds to the test request, and registers a simulation port and disables a downstream server to the registry cluster according to the test request and a preset configuration rule;

the sandbox carries out simulation receipt on the test request according to the simulation port to generate a receipt message, and the receipt message is output to the automatic test platform;

and the automatic test platform receives the receipt message, analyzes the test result of the test request, and records and stores the test result.

11. The RPC interface automated testing method of claim 10, wherein the test request includes a transaction flow number, wherein registering a simulation port with the registry cluster and deactivating a downstream server according to the test request and preset configuration rules comprises:

registering the simulation port to the registration center cluster according to the transaction serial number and a preset number rule in the preset configuration rule;

12. The RPC interface automated testing method of claim 11, wherein the generating a receipt message by performing a simulation receipt on the test request according to the simulation port comprises:

13. The RPC interface automation test method of claim 12, wherein the generating a receipt message corresponding to the test request according to the simulation port, the test request and a receipt message configuration rule in the preset configuration rule comprises:

14. A sandbox for realizing automated testing of RPC interfaces by sandbox control registration center cluster designated routing, comprising:

the request acquisition module is used for acquiring a test request from the automatic test platform;

the first processing module is used for registering a simulation port and deactivating a downstream server to the registration center cluster according to the test request and a preset configuration rule;

and the second processing module is used for simulating the receipt of the test request according to the simulation port and generating a receipt message.

15. A registry cluster, wherein the registry cluster communicatively interacts with a sandbox, comprising:

the request acquisition module is used for acquiring a newly added analog interface request initiated by the sandbox;

and the first processing module is used for deactivating a downstream server so that the sandbox can simulate receipt of the test request according to the simulation port to generate a receipt message.

16. An RPC interface automated testing system, comprising: the system comprises an automatic test platform, a sandbox and a registration center cluster; wherein the content of the first and second substances,

the automatic test platform initiates a test request;

the sandbox responds to the test request, and registers a simulation port and deactivates a downstream server to the registry cluster according to the test request and a preset configuration rule; the sandbox simulates receipt according to the simulation port, generates a receipt message and outputs the receipt message to the automatic test platform;

17. An electronic device, comprising:

one or more processors;

a storage device to store one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the RPC interface automated testing method of any of claims 1-13.

18. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the RPC interface automated testing method of any of claims 1 to 13.

19. A computer program product comprising a computer program which, when executed by a processor, implements the RPC interface automated testing method of any of claims 1-13.