CN113849361A

CN113849361A - Method, device, equipment and storage medium for testing service node

Info

Publication number: CN113849361A
Application number: CN202111147617.2A
Authority: CN
Inventors: 李鸿斌
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2021-09-28
Filing date: 2021-09-28
Publication date: 2021-12-28
Anticipated expiration: 2041-09-28
Also published as: CN113849361B

Abstract

The disclosure provides a method, a device, equipment and a storage medium for testing service nodes, and relates to the technical field of computers, in particular to the technical field of micro-services. The specific implementation scheme is as follows: deploying a plurality of original service nodes, wherein data are transmitted among the original service nodes through original links; deploying at least one test node in one-to-one correspondence with at least one target original service node in a plurality of original service nodes; generating at least one test link corresponding to the at least one test node by multiplexing the original link; and testing the test node using the at least one test link.

Description

Method, device, equipment and storage medium for testing service node

Technical Field

The present disclosure relates to the field of computer technology, and more particularly, to the field of micro-service technology.

Background

The microservice architecture is a variant of the Service Oriented Architecture (SOA) architectural style. In the micro-service architecture, a single service is split into a plurality of micro-services, the plurality of micro-services are independently maintained, and research and development work such as development, testing and the like is respectively carried out.

Disclosure of Invention

The present disclosure provides a method, apparatus, device, storage medium, and program product for testing a service node.

According to an aspect of the present disclosure, there is provided a method of testing a service node, including: deploying a plurality of original service nodes, wherein data is transmitted among the original service nodes through original links; deploying at least one test node in one-to-one correspondence with at least one target original service node in the plurality of original service nodes; generating at least one test link corresponding to the at least one test node by multiplexing the original link; and testing the test node using the at least one test link. .

According to another aspect of the present disclosure, there is provided an apparatus for testing a service node, including: the system comprises a first deployment module, a second deployment module and a third deployment module, wherein the first deployment module is used for deploying a plurality of original service nodes, and data are transmitted among the original service nodes through original links; the second deployment module is used for deploying at least one test node which corresponds to at least one target original service node in the plurality of original service nodes one by one; a generating module, configured to generate at least one test link corresponding to the at least one test node by multiplexing the original link; and the testing module is used for testing the testing node by utilizing the at least one testing link.

Another aspect of the present disclosure provides an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the embodiments of the present disclosure.

According to another aspect of the disclosed embodiments, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method shown in the disclosed embodiments.

According to another aspect of the embodiments of the present disclosure, there is provided a computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions, when executed by a processor, implement the steps of the method shown in the embodiments of the present disclosure.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 schematically shows a schematic diagram of a system to which a method of testing a service node may be applied, according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a schematic diagram of a method of testing a service node according to an embodiment of the present disclosure;

FIG. 3 schematically shows a schematic diagram of a method of testing a service node according to another embodiment of the present disclosure;

FIG. 4 schematically shows a flow chart of a method of testing a service node according to an embodiment of the present disclosure;

FIG. 5 schematically shows a flow diagram of a method of generating a test link according to an embodiment of the disclosure;

FIG. 6 schematically shows a schematic diagram of a method of configuring routing information of an originating node and a testing node, according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a method of testing a service node according to an embodiment of the disclosure;

FIG. 8 schematically illustrates a block diagram of an apparatus for testing a service node, in accordance with an embodiment of the present disclosure; and

FIG. 9 schematically shows a block diagram of an example electronic device that may be used to implement embodiments of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the related data all meet the regulations of related laws and regulations and do not violate the customs of the public order.

A system to which the method of testing a service node according to an embodiment of the present disclosure may be applied is described below with reference to fig. 1.

Fig. 1 schematically shows a schematic diagram of a system to which a method of testing a service node may be applied, according to an embodiment of the present disclosure.

The system 100 may include a client (client)110 and a server 120 according to embodiments of the present disclosure. Wherein the server 120 may include an entry module (gateway)121 and a plurality of microservice modules 122.

According to an embodiment of the present disclosure, the client 110 may send a request to the server 120, which may pass through the corresponding micro service modules 122 in sequence via the portal module 121.

As an optional embodiment, in the process of testing the micro service, a set of link test environment may be constructed, then the micro service module to be tested is replaced with the module of the corresponding test version, and after the test is completed, the micro service module of the original version is replaced.

Fig. 2 schematically shows a schematic diagram of a method of testing a service node according to an embodiment of the present disclosure.

For example, as shown in FIG. 2, the link test environment includes client, portal and microservice modules A, B, C, D and E. In this example, test versions of B and D need to be tested.

Based on this, the micro-service module B may be replaced with a test version B-DEV of B for testing. Wait for B to be tested and then restore the original version of B. And then replacing the micro-service module D with a test version D-DEV of D for testing, and recovering D to the original version after the test is finished.

However, the test process can only be performed in series, and thus the test efficiency is low.

Fig. 3 schematically shows a schematic diagram of a method of testing a service node according to another embodiment of the present disclosure.

For example, as shown in fig. 3, in the process of testing the micro service, a plurality of sets of link test environments can be constructed for different test requirements. For example, under the condition that test versions of B and D need to be tested, two sets of link test environments can be set up, wherein one set is used for testing the test version of B, and the other set is used for testing the test version of D. For example, as shown in fig. 3, the client, the portal module 1 and the micro service modules a1, B-DEV, C1, D1 and E1 constitute a set of link test environments for testing B test version B-DEV. The client, the portal module 2 and the micro service modules a2, B2, C2, D-DEV and E2 constitute another set of link test environment for testing the test version D-DEV of C.

Although the above test process can perform parallel tests, it needs to build multiple sets of test environments, which is relatively wasteful of resources on one hand, for example, suppose that there are N services on a link, where N is a positive integer. If each service needs to be tested, N test links need to be built, and N × N service resources are needed in total. On the other hand, time is consumed, a whole set of test links are built, N modules need to be deployed, a request route needs to be set besides the deployed modules and is used for forwarding the request to the corresponding links, and time is consumed for setting the request route.

Based on this, according to the embodiment of the present disclosure, the requests may be dyed, that is, each request is configured with a field for storing a feature identifier, where the feature identifier may be used to represent a link corresponding to the request. The feature identity may be communicated in the link by request.

According to the embodiment of the disclosure, the feature identifier and the corresponding routing information can be configured according to the test requirement information. And sending the characteristic identification and the corresponding routing information to each service node in the service grid. The service node may include, for example, an entry module, a micro-service module, and the like. The routing information may include, for example, one or more feature identifiers, and identification and address information of upstream nodes, identification and address information of downstream nodes corresponding to each feature identifier.

For each node (including the node to be tested), after receiving the request, the corresponding routing information can be queried according to the feature identifier included in the request, so as to determine the address information of the downstream node. The request may then be forwarded to the downstream node based on the address information.

When the micro service is tested, the nodes to be tested can be added on the basis of the original nodes, and the characteristic identification and the routing information are configured to the test link corresponding to the nodes to be tested. And sending the characteristic identification and the corresponding routing information to each node including the node to be tested. Thus, upon receiving a request, the request may be forwarded via the test link to test the node under test. The testing method can be used for testing in parallel, and the efficiency is higher. In addition, the modules can be multiplexed, so that the resource waste is reduced.

In this embodiment, for example, route matching and forwarding for the request may be implemented by the service grid. The service grid refers to a configurable infrastructure layer for microservice applications, and can be used for network calling, current limiting, fusing, monitoring and the like among microservices. In this embodiment, the service grid may be implemented by setting a proxy instance (sidecar) in each microservice. Among other things, the proxy instance may be used to handle communications between microservices, as well as perform monitoring, throttling, fusing, and the like.

Fig. 4 schematically shows a flow chart of a method of testing a service node according to an embodiment of the present disclosure.

As shown in fig. 4, the method 400 of testing a service node includes deploying a plurality of original service nodes, wherein data is transmitted between the plurality of original service nodes through original links in operation S410.

Then, at least one test node, which corresponds one-to-one to at least one target original service node among the plurality of original service nodes, is deployed in operation S420.

At operation S430, at least one test link corresponding to the at least one test node is generated by multiplexing the original links.

In operation S440, the test node is tested using the at least one test link.

According to an embodiment of the present disclosure, at least a portion of an original link may be multiplexed with a test node to generate a test link. By multiplexing the original link to generate at least one test link corresponding to at least one test node, waste of resources can be reduced.

According to the embodiment of the disclosure, a sandbox environment can be set up in advance, and then a plurality of original service nodes are deployed inside the sandbox environment. The service node may comprise, for example, the portal module and the microservice module shown above.

According to embodiments of the present disclosure, at least one test node may be deployed outside of a sandbox environment. According to other embodiments of the present disclosure, at least one test node may also be deployed inside the sandbox environment, or test nodes may be deployed inside and outside the sandbox environment, respectively.

According to an embodiment of the present disclosure, a link characteristic identification of each test request test link of at least one test link test request may be determined. And then configuring routing information of a plurality of original nodes and at least one testing node according to the characteristic identifier of each testing link of the characteristic identifier of each testing request to obtain at least one routing link as at least one testing link.

According to the embodiment of the disclosure, a corresponding test request may be sent to each test link in at least one test link, so that the test node in the test link processes the test request to obtain a test result.

According to the embodiment of the disclosure, the testing may include, for example, testing the operation information of each test node, and may also include testing a response result obtained after the request passes through the test link.

Fig. 5 schematically shows a flow chart of a method of generating a test link according to an embodiment of the present disclosure.

As shown in fig. 5, the method 530 of generating a test link includes determining a link characteristic identifier of each test link of at least one test link test request in operation S531.

In operation S532, the routing information of the plurality of original nodes and the at least one test node is configured according to the feature identifier of each test link of the feature identifier of each test request, and the at least one routing link is obtained as the at least one test link.

According to the embodiment of the disclosure, when configuring the routing information of the plurality of original nodes and the at least one test node, for each target original node corresponding to the test request, the routing information of the upstream node of the target original service node may be configured according to the feature identifier of the test request, so that the upstream node forwards the test request to the test node corresponding to the target original node when receiving the test request. In addition, the routing information of the test node corresponding to the target original service node can be configured according to the feature identifier of the test request, so that the test node forwards the test request to the downstream node of the target original node when receiving the test request.

According to an embodiment of the present disclosure, the routing information may include, for example, a feature identifier of the test request, and an address of a downstream node corresponding to the feature identifier. According to further embodiments of the present disclosure, the routing information may also include other information such as an identification of the upstream node and an identification of the downstream node corresponding to the characteristic identification.

According to the embodiment of the disclosure, for each node, after receiving a request of an upstream node, the node may search for routing information matching with a feature identifier in its own stored routing information according to the feature identifier in the request. And forwarding the request to the corresponding downstream node according to the address of the downstream node in the matched routing information.

According to the embodiment of the disclosure, by configuring the routing information of the original node and the test node, part of the original link can be multiplexed, thereby saving resources. In addition, different test requests correspond to different routing information, so that the different test requests are transmitted simultaneously and do not conflict, thereby supporting the parallel execution of a plurality of tests and improving the test efficiency.

The method for configuring routing information of the original node and the test node as described above is further described with reference to fig. 6. Those skilled in the art will appreciate that the following example embodiments are only for the understanding of the present disclosure, and the present disclosure is not limited thereto.

Fig. 6 schematically shows a schematic diagram of a method of configuring routing information of an originating node and a testing node according to an embodiment of the present disclosure.

As shown in fig. 6, in this embodiment, it is necessary to test the test versions a1 and C1 of the microservice module a, that is, the nodes corresponding to the test request are a and C. According to the embodiment of the present disclosure, the routing information of the entry module of the upstream node of a may be configured according to the feature identifier of the test request, so that the entry module forwards the test request to the test version a1 of a when receiving the test request, and the routing information of the upstream node B of C may be configured, so that B forwards the test request to the test version C1 of C when receiving the test request. In addition, routing information of a1 is configured such that a1 forwards a test request to a downstream node B of a upon receiving the test request, and routing information of C1 is configured such that C1 forwards the test request to C downstream node D upon receiving the test request.

The method for testing a service node shown above is further described with reference to fig. 7 in conjunction with the specific embodiments. Those skilled in the art will appreciate that the following example embodiments are only for the understanding of the present disclosure, and the present disclosure is not limited thereto.

Fig. 7 schematically shows a method of testing a service node according to an embodiment of the present disclosure.

As shown in fig. 7, in this embodiment, a sandbox environment is deployed, which may include a Client, an entry module Gateway, and microservice modules A, B, C, D and E, and the default traffic forwarding path is as follows:

Client->Gateway->A->B->C->D->E

for example, in this embodiment, the request may store the signature in a logid field, which represents the id of the entire link.

In accordance with embodiments of the present disclosure, Gateway x, a1, B1, and C1 may be deployed in addition to Client, Gateway, a, B, C, D, and E. Where module a1 is a test version of module a, module B1 is a test version of module B, module C1 is a test version of module C, and Gateway x is a test version of Gateway. When any one or more of a1, B1, C1, and GatewayX requires testing, multiple test links may be constructed based on module multiplexing.

For example, in the case where module B1 requires testing, the routing information for each module may be configured to construct test link 1. The traffic forwarding path of the test link 1 is Client- > Gateway- > A- > B1- > C- > D- > E.

For example, in this embodiment, the feature identifier corresponding to the test request of B1 may be 12345678. The request address of B1 may be 10.10.10.10: 8888. routing information for each module is configured so that each module forwards requests containing signatures 12345678 along test link 1. For example, when a receives a request, if the value of the logid field in the request is 12345678, the request is forwarded to 10.10.10.10: 8888, i.e., to B1. If the signature in the request is not 12345678, the request is forwarded to the default backend, i.e., to B.

Also for example, similar to the above, when modules a1 and C1 simultaneously require testing, the routing information of each module may be configured to construct test link 2. The traffic forwarding path of the test link 2 is Client- > Gateway- > A1- > B- > C1- > D- > E. The routing information for each module may be configured so that each module forwards test requests for simultaneous tests a1 and C1 along test link 2.

For another example, similarly to the above, when the portal module Gateway1 needs to be tested, the routing information of each module may be configured to construct the test link 3. Wherein the flow forwarding path of the test link 3 is Client- > gateway X- > A- > B- > C- > D- > E. The routing information of each module may be configured so that each module forwards test requests for testing Gateway1 along test link 3.

According to the embodiment of the disclosure, the feature identifiers in different test requests can be different, so that the test links 1, 2 and 3 can be tested in parallel, and the efficiency is higher. In addition, the modules can be multiplexed, so that the resource waste is reduced.

Fig. 8 schematically shows a block diagram of an apparatus for testing a service node according to an embodiment of the present disclosure.

As shown in fig. 8, the apparatus 800 for testing a service node includes a first deployment module 810, a second deployment module 820, a generation module 830, and a testing module 840.

The first deployment module 810 can be configured to deploy a plurality of original service nodes, wherein the plurality of original service nodes transmit data therebetween via original links.

The second deployment module 820 may be configured to deploy at least one test node corresponding to at least one target original service node of the plurality of original service nodes.

The generating module 830 may be configured to generate at least one test link corresponding to at least one test node by multiplexing the original link.

The testing module 840 may be configured to test the test node using the at least one test link. According to an embodiment of the present disclosure, the first deployment module may include: and the first deployment submodule is used for deploying a plurality of original service nodes in the sandbox environment.

According to an embodiment of the present disclosure, the second deployment module may include: a second deployment submodule, operable to deploy at least one test node inside and/or outside of the sandbox environment.

According to an embodiment of the present disclosure, the generating module may include a determining submodule and a configuring submodule. The determining submodule may be configured to determine a feature identifier of each test request in the at least one test request. The configuration submodule may be configured to configure routing information of the plurality of original nodes and the at least one test node according to the feature identifier of each test request, and obtain at least one routing link as the at least one test link.

According to an embodiment of the present disclosure, the configuration submodule may include a first configuration unit and a second configuration unit. The first configuration unit may be configured to configure, for each target original node corresponding to the test request, routing information of an upstream node of the target original service node according to the feature identifier of the test request, so that the upstream node forwards the test request to the test node corresponding to the target original node when receiving the test request. The second configuration unit may be configured to configure, for each target original node corresponding to the test request, routing information of the test node corresponding to the target original service node according to the feature identifier of the test request, so that the test node forwards the test request to a downstream node of the target original node when receiving the test request.

According to an embodiment of the present disclosure, the test module may include a test sub-module, and may be configured to send a corresponding test request to each test link in at least one test link, so that the test node in the test link processes the test request to obtain a test result.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

FIG. 9 schematically shows a block diagram of an example electronic device 900 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 9, the apparatus 900 includes a computing unit 901, which can perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The calculation unit 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

A number of components in the device 900 are connected to the I/O interface 905, including: an input unit 906 such as a keyboard, a mouse, and the like; an output unit 907 such as various types of displays, speakers, and the like; a storage unit 908 such as a magnetic disk, optical disk, or the like; and a communication unit 909 such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 901 performs the respective methods and processes described above, such as the method of testing the service node. For example, in some embodiments, the method of testing a service node may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 900 via ROM 902 and/or communications unit 909. When the computer program is loaded into RAM 903 and executed by the computing unit 901, one or more steps of the method of testing a service node described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured by any other suitable means (e.g. by means of firmware) to perform the method of testing the service node.

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in a traditional physical host and a VPS service (Virtual Private Server, or VPS for short). The server may also be a server of a distributed system, or a server incorporating a blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A method of testing a service node, comprising:

deploying a plurality of original service nodes, wherein data is transmitted among the original service nodes through original links;

deploying at least one test node in one-to-one correspondence with at least one target original service node in the plurality of original service nodes;

generating at least one test link corresponding to the at least one test node by multiplexing the original link; and

and testing the test node by using the at least one test link.

2. The method of claim 1, wherein the deploying a plurality of origin service nodes comprises:

deploying the plurality of original service nodes inside the sandbox environment.

3. The method of claim 2, wherein said deploying at least one test node in one-to-one correspondence with at least one target original service node of the plurality of original service nodes comprises:

deploying the at least one test node inside and/or outside of the sandbox environment.

4. The method of claim 1, wherein the generating at least one test link corresponding to the at least one test node by multiplexing the original link comprises:

determining a feature identifier of each test request in at least one test request; and

and configuring routing information of the plurality of original nodes and the at least one testing node according to the feature identifier of each testing request to obtain at least one routing link as the at least one testing link.

5. The method of claim 4, wherein said configuring routing information for said plurality of original nodes and said at least one test node comprises:

for each target primary node corresponding to the test request,

configuring routing information of an upstream node of the target original service node according to the feature identifier of the test request, so that the upstream node forwards the test request to the test node corresponding to the target original node when receiving the test request; and

and configuring routing information of the test node corresponding to the target original service node according to the feature identifier of the test request, so that the test node forwards the test request to a downstream node of the target original node when receiving the test request.

6. The method of claim 1, wherein said testing the test node using the at least one test link comprises:

and sending a corresponding test request to each test link in at least one test link so that the test node in the test link processes the test request to obtain a test result.

7. An apparatus for testing a service node, comprising:

the system comprises a first deployment module, a second deployment module and a third deployment module, wherein the first deployment module is used for deploying a plurality of original service nodes, and data are transmitted among the original service nodes through original links;

the second deployment module is used for deploying at least one test node which corresponds to at least one target original service node in the plurality of original service nodes one by one;

a generating module, configured to generate at least one test link corresponding to the at least one test node by multiplexing the original link; and

and the testing module is used for testing the testing node by utilizing the at least one testing link.

8. The apparatus of claim 7, wherein the first deployment module comprises:

and the first deployment submodule is used for deploying the plurality of original service nodes in the sandbox environment.

9. The apparatus of claim 8, wherein the second deployment module comprises:

a second deployment submodule to deploy the at least one test node inside and/or outside the sandbox environment.

10. The apparatus of claim 7, wherein the generating means comprises:

the determining submodule is used for determining the characteristic identification of each test request in at least one test request; and

and the configuration submodule is used for configuring the routing information of the plurality of original nodes and the at least one test node according to the feature identifier of each test request to obtain at least one routing link as the at least one test link.

11. The apparatus of claim 10, wherein the configuration submodule comprises:

a first configuration unit, configured to configure, according to a feature identifier of the test request, routing information of an upstream node of the target original service node for each target original node corresponding to the test request, so that the upstream node forwards the test request to a test node corresponding to the target original node when receiving the test request; and

and a second configuration unit, configured to configure, for each target original node corresponding to the test request, routing information of the test node corresponding to the target original service node according to the feature identifier of the test request, so that the test node forwards the test request to a downstream node of the target original node when receiving the test request.

12. The apparatus of claim 7, wherein the test module comprises:

and the test submodule is used for sending a corresponding test request to each test link in at least one test link so as to enable the test node in the test link to process the test request to obtain a test result.

13. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.

14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-6.

15. A computer program product comprising computer program/instructions, characterized in that the computer program/instructions, when executed by a processor, implement the steps of the method according to any of claims 1-6.