Distributed system test method and related device
By combining Trace ID with B3 link tracing protocol, the problem of testing effectiveness and stability of distributed architecture application systems is solved, and full-link tracing and automated testing is realized, which improves testing efficiency and reduces costs.
Patent Information
- Application Number
- CN202411383616.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2024-12-31
AI Technical Summary
Traditional precision testing methods are difficult to fully capture the cross-service request path and context information of distributed architecture application systems, which makes it difficult to guarantee the effectiveness of tests and system stability, and there are potential risks.
By obtaining the Trace ID and corresponding it to the test request one by one, modifying the request header based on the B3 link tracing protocol, the full link tracing and testing of the distributed system is realized.
It ensures correct simulation and verification of code behavior and external system interaction, improves the effectiveness of test results of distributed architecture application systems, and implements automated testing, shortens test cycles and reduces test costs.
Smart Images
Figure CN119226171A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of system testing, and in particular to a distributed system testing method and related devices. Background Art
[0002] With the rapid advancement of information technology, the architecture of financial industry application systems is gradually shifting towards a distributed architecture.
[0003] Among them, the distributed architecture can improve the scalability and flexibility of the system, so as to adapt to the increasingly complex business needs. Traditional precision testing methods perform well when dealing with single-host application systems, but when facing distributed architecture application systems, it is difficult to fully capture the request path and context information across services, the effectiveness of the test cannot be guaranteed, and the stability and performance of the system are difficult to be fully guaranteed, which brings potential risks to the business development of the financial industry.
[0004] Therefore, how to improve the effectiveness of test results of distributed architecture application systems has become a problem that needs to be solved. Summary of the invention
[0005] Based on the above problems, the present application provides a distributed system testing method and related devices, which can improve the effectiveness of the test results of the distributed architecture application system.
[0006] The embodiments of the present application disclose the following technical solutions:
[0007] In a first aspect, an embodiment of the present application provides a distributed system testing method, the method comprising:
[0008] Obtain a test request and a Trace ID; the Trace ID corresponds to the test request one by one;
[0009] Modify the test request based on the Trace ID to obtain a target request including the Trace ID;
[0010] Based on the target request and the B3 link tracking protocol, the distributed system is tested.
[0011] Optionally, obtaining the Trace ID includes:
[0012] Obtain a unique identifier for the client's mobile device;
[0013] Extracting a preset number of characters from a preset position of the unique identifier to obtain a first character segment;
[0014] The preset character string, the first character fragment and the random character string are concatenated to obtain a Trace ID.
[0015] Optionally, after extracting a preset number of characters from the tail of the unique identifier to obtain the first character segment, the method further includes:
[0016] The first character segment is uploaded to the test platform.
[0017] Optionally, the modifying the test request based on the Trace ID to obtain a target request including the Trace ID includes:
[0018] In response to the message object sent by the event listener, a request header is added to the test request based on the Trace ID to obtain a target request containing the Trace ID.
[0019] Optionally, the event listeners include checkHeaderEditorInstalled, changeHeaderEditorTraceId, and toggleSwitchHeaderEditor.
[0020] Optionally, the modifying the test request based on the Trace ID to obtain a target request including the Trace ID includes:
[0021] The message injection of Trace ID is performed through a customized tool pre-deployed in the mobile application, and the test request is modified to obtain a target request containing Trace ID.
[0022] Optionally, it is characterized in that, after testing the distributed system based on the target request and the B3 link tracking protocol, the method further includes:
[0023] Based on the Trace ID, coverage data is uploaded to the test platform; the coverage data includes the ratio of executed code lines to the total number of code lines.
[0024] In a second aspect, an embodiment of the present application provides a distributed system testing device, the device comprising: an acquisition module, a modification module and a testing module;
[0025] The acquisition module is used to acquire the test request and the Trace ID; the Trace ID corresponds to the test request one by one;
[0026] The modification module is used to modify the test request based on the Trace ID to obtain a target request including the Trace ID;
[0027] The test module is used to test the distributed system based on the target request and the B3 link tracking protocol.
[0028] In a third aspect, an embodiment of the present application provides a distributed system testing device, the device comprising: a memory and a processor;
[0029] The memory is used to store program code and transmit the program code to the processor;
[0030] The processor is used to execute the steps of the distributed system testing method described in any implementation manner of the first aspect according to the program code.
[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a distributed system testing device, the distributed system testing device executes the steps of the distributed system testing method described in any implementation manner in the first aspect.
[0032] Compared with the prior art, this application has the following beneficial effects:
[0033] The present application provides a distributed system testing method, in which, first, a test request and a Trace ID are obtained; the Trace ID corresponds to the test request one by one; then, the test request is modified based on the Trace ID to obtain a target request containing the Trace ID; finally, the distributed system is tested based on the target request and the B3 link tracing protocol. Therefore, in the embodiment of the present application, the test request is modified based on the Trace ID, and a unique identifier in the distributed system is provided for each test request, and then the B3 link tracing protocol can be used to track the entire link of the test with the target request containing the Trace ID as the identifier, thereby ensuring that during the test process, the behavior of the code itself and the interaction between the code and the external system, service or library are correctly simulated, monitored and verified, thereby improving the effectiveness of the test results of the distributed architecture application system. In addition, the method adopted by the embodiment of the present application can also realize automated testing of distributed systems, which can improve test efficiency, shorten test cycles, and reduce test costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0035] Figure 1 A flow chart of a distributed system testing method provided in an embodiment of the present application;
[0036] Figure 2 A flow chart of another distributed system testing method provided in an embodiment of the present application;
[0037] Figure 3 A flow chart of another distributed system testing method provided in an embodiment of the present application;
[0038] Figure 4 A flow chart of another distributed system testing method provided in an embodiment of the present application;
[0039] Figure 5 A schematic diagram of a distributed system testing device provided in an embodiment of the present application;
[0040] Figure 6 A structural diagram of a distributed system testing device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0041] A distributed system testing method and related devices provided in the present application can be used in the field of system testing. The above is only an example and does not limit the application field of a distributed system testing method and related devices provided in the present application.
[0042] The terms "first", "second", "third" and "fourth" etc. in the specification, claims and drawings of this application are used to distinguish different objects rather than to limit a specific order.
[0043] In the embodiments of the present application, the words "as an example" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "as an example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the words "as an example" or "for example" is intended to present the relevant concepts in a specific way.
[0044] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.
[0045] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0046] See also Figure 1 , which is a flow chart of a distributed system testing method provided in an embodiment of the present application, the method comprising:
[0047] S101: Obtain a test request and a Trace ID.
[0048] Among them, Trace ID is a unique identifier used to trace requests in a distributed system, and corresponds to a test request one by one. Trace ID is usually 16 bytes (128 bits) or 8 bytes (64 bits), and is 32 characters long (128 bits) or 16 characters long (64 bits) in hexadecimal.
[0049] Specifically, a test request for a distributed system can be obtained from the outside or inside, and a Trace ID corresponding to the request can be obtained at the same time. Trace ID is used to uniquely identify the flow path of a test request in a distributed system, and is the key to achieving link tracking.
[0050] As an implementation method of the present application, for a client mobile device that initiates a request, such as a mobile device equipped with an Android system, a unique identifier of the client mobile device, such as an Android ID, can be obtained; then, a preset number of characters is extracted from the end of the unique identifier to obtain a first character fragment, such as an Android ID is a 16-character hexadecimal string, and if the preset number of characters is 6, the last 6 characters of the Android ID can be extracted; finally, the preset string, the first character fragment, and the random string are concatenated to obtain a Trace ID, such as a 6-character fixed string such as "7ac001", and a random string can be a randomly generated 4-character hexadecimal string, thereby concatenating a 6-character preset string, a 6-character first character fragment, and a 4-character random string to obtain a 16-character Trace ID. Among them, the length of the preset string, the first character fragment, and the random string can be flexibly set based on actual needs, and the total length of the three can be 16 characters or 32 characters.
[0051] As another implementation method provided in the embodiment of the present application, the Node.js library can also be used to generate a UUID (universally unique identifier), and the UUID can be used as the Trace ID, or a random number generator can be used to generate a string of the required length as the Trace ID, etc.
[0052] Optionally, a timestamp or a random number may be added to the Trace ID to ensure that each generated Trace ID is unique in the entire distributed system.
[0053] As an example, you can intercept test requests using the _modifyHeaders method to get the test request.
[0054] S102: Modify the test request based on the Trace ID to obtain a target request including the Trace ID.
[0055] As an example, after obtaining the Trace ID, you can add a request header to the test request based on the Trace ID to generate a target request. In this way, when the target request flows in the distributed system, each service node can track the flow path of the request by parsing the Trace ID in the request header.
[0056] As an example, you can use the _modifyHeaders method to intercept and modify the test request. For example, add a request header containing the Trace ID using the following code:
[0057]
[0058]
[0059] Among them, x-b3-traceid is a globally unique identifier, namely Trace ID, which is used to identify a complete trace link; x-b3-spanid is the identifier of a single span, indicating a logical trace unit in the trace link; x-b3-sample is a sampling flag, indicating whether to sample this request, where 1 indicates that sampling is required and 0 indicates that sampling is not required; x-b3-flags is an optional field used to pass additional control flags, such as passing debugging requests.
[0060] In this embodiment, k may be a Trace ID obtained by any implementation method provided in step S101. A random number is generated by Math.random(), and the random number is combined with the Trace ID to obtain an id.
[0061] Optionally, the values of x-b3-traceid and x-b3-spanid may both be set to id, or the value of x-b3-traceid may be set to k, and the value of x-b3-spanid may be set to id.
[0062] S103: Testing the distributed system based on the target request and the B3 link tracking protocol.
[0063] Specifically, the B3 link tracing protocol is a link tracing standard, in which B3 is an HTTP header format for distributed tracing, which is designed to propagate tracing context in a microservice architecture. The request header is a general term for multiple headers, and x-b3-traceid, x-b3-spanid, x-b3-sample, and x-b3-flags are all HTTP (Hypertext Transfer Protocol) headers defined by the B3 link tracing protocol. They can be passed between services to maintain the consistency of tracing information.
[0064] Therefore, in the embodiment of the present application, the test request is modified based on the Trace ID, and a unique identifier in the distributed system is provided for each test request. Then, the B3 link tracking protocol can be used to track the entire link of the test with the target request containing the Trace ID as the identifier, thereby ensuring that during the test process, the behavior of the code itself and the interaction between the code and the external system, service or library are correctly simulated, monitored and verified, thereby improving the effectiveness of the test results of the distributed architecture application system. In addition, the method adopted by the embodiment of the present application can also realize automated testing of distributed systems, which can improve test efficiency, shorten test cycles, and reduce test costs.
[0065] join Figure 2 , which is a flow chart of another distributed system testing method provided by an embodiment of the present application, the method comprising:
[0066] S201: Obtain a unique identifier of a client mobile device and a test request.
[0067] Specifically, for a mobile device equipped with an Android system, a unique identifier of the client mobile device such as an Android ID can be obtained. The Android ID is usually a 64-bit (16 characters in hexadecimal) unique identifier generated when the device is first started and is unique for each device and user combination.
[0068] As an example, you can intercept test requests using the _modifyHeaders method to get the test request.
[0069] S202: Extracting a preset number of characters from a preset position of the unique identifier to obtain a first character segment.
[0070] The preset position and the preset number of characters can be flexibly set based on actual needs, wherein the preset position can be the beginning, the end, or the Xth to Yth characters, and the preset number of characters can be set to any positive integer not greater than 16. For example, if the preset position is the beginning and the preset number of characters is 6, the first 6 characters in the Android ID are extracted as the first character segment.
[0071] S203: Upload the first character segment to the test platform.
[0072] Specifically, the first character fragment can be used as device information and uploaded to the test platform through the interface to establish a mapping relationship between the device and the test, thereby facilitating tracking of specific devices and related behaviors during precise testing and facilitating quick location of specific devices when problems are discovered.
[0073] Optionally, information such as device model and Android version can also be uploaded to the test platform.
[0074] S204: Concatenate the preset character string, the first character segment, and the random character string to obtain a Trace ID.
[0075] As an example, the preset string can be a fixed string of 6 characters such as "7ac001", and the random string can be a 4-character hexadecimal string randomly generated by Math.random(). Thus, by splicing the 6-character preset string, the 6-character first character segment and the 4-character random string, a 16-character Trace ID can be obtained. Among them, the length of the preset string, the first character segment and the random string can be flexibly set based on actual needs, and the total length of the three can be 16 characters or 32 characters.
[0076] S205: Add a request header to the test request based on the Trace ID to obtain a target request including the Trace ID.
[0077] As an example, a request header containing a Trace ID can be added to a test request, i.e., a request of the HTTP or HTTPS (Hypertext Transfer Protocol Secure) protocol, to obtain a target request containing a Trace ID, so that each service node can track the flow path of the request by parsing the Trace ID in the request header. For example, the values of the HTTP headers x-b3-traceid and x-b3-spanid in the request header can be set to Trace ID, and such a request header can be added to the test request to obtain a target request containing a Trace ID.
[0078] S206: Testing the distributed system based on the target request and the B3 link tracking protocol.
[0079] As an example, test case recording, functional testing, and automated testing can be performed in parallel.
[0080] S207: Upload coverage data to the test platform based on the Trace ID.
[0081] The coverage data includes the ratio of executed code lines to the total number of code lines, and can also show which code is executed and which code is not executed. The coverage data with Trace ID is uploaded to the test platform, which can associate the coverage data with the test case to more accurately evaluate the coverage of the code by the test case, so as to improve the test case and enhance the comprehensiveness and accuracy of the test.
[0082] In addition, when a test case fails or the system has an exception, you can view log information based on the Trace ID and quickly trace the specific request path, which makes it easier to locate the problem and gain an in-depth understanding of the cause of the problem. You can also promptly discover and fix potential problems in the system, ensuring the stability and performance of the system in complex environments.
[0083] See also Figure 3 , which is a flow chart of another distributed system testing method provided by an embodiment of the present application, the method comprising:
[0084] S301: Obtain a test request and a Trace ID.
[0085] As an example, for applications running in a web browser environment, such as single-page applications, static websites, and other browsers, you can use tools such as the Node.js library or a random number generator to get a Trace ID. You can also get a Trace ID based on a preset Trace ID format by concatenating random numbers with fixed fields.
[0086] For example, you can use the Node.js library to generate a UUID (universally unique identifier) and use the UUID as the Trace ID. You can also use a random number generator to generate a string of the required length and use the generated string as the Trace ID. You can also set the format of the Trace ID to: a 6-character fixed field, a 2-character special processing type identifier, and an 8-character random number for avoiding test case recording conflicts, where the fixed field is a special processing link identifier, so that the Trace ID is obtained by concatenating the special processing link identifier, the special processing type identifier, and the generated random number.
[0087] As an example, you can intercept test requests using the _modifyHeaders method to get the test request.
[0088] S302: In response to the message object sent by the event listener, add the Trace ID to the request header of the test request to obtain a target request containing the Trace ID.
[0089] As an example, you can implement event monitoring with the following code:
[0090]
[0091]
[0092] Among them, there are three event listeners, namely: checkHeaderEditorInstalled, changeHeaderEditorTraceId and toggleSwitchHeaderEditor.
[0093] Among them, checkHeaderEditorInstalled is used to check whether the request header already exists in the test request. When the event listener is triggered, event.preventDefault() is called to prevent the default behavior.
[0094] changeHeaderEditorTraceId is used to receive a message containing a Trace ID and add the Trace ID to the request header. When the event listener is triggered, if the event.detail is not empty and event.detail.traceId exists, an xb3 object containing the request header information to be modified is created, and chrome.runtime.sendMessage is used to send the xb3 object to the background script background.js to update the x-b3-traceid field in the request header. The message object sent by changeHeaderEditorTraceId includes method: "putRule", type: "sendHeader" and specific request header information content, which is used to update the x-b3-traceid field in the request header.
[0095] toggleSwitchHeaderEditor is used to switch the switch state of HeaderEditor. When the event listener is triggered, it can decide whether to disable HeaderEditor according to the value of event.detail. The message object sent by toggleSwitchHeaderEditor contains method:"toggleSwitch" or method:"toggleSwitch" and disableAll, which are used to instruct the background script to enable or disable HeaderEditor, and a disableAll parameter can be passed to decide whether to disable all rules.
[0096] Therefore, through the set event listener, the test request without a request header can be identified and modified based on the Trace ID, that is, a request header containing the Trace ID is added, thereby ensuring that a unique Trace ID is added to all network requests.
[0097] S303: Testing the distributed system based on the target request and the B3 link tracking protocol.
[0098] S304: Upload coverage data to the test platform based on the Trace ID.
[0099] The coverage data includes the ratio of executed code lines to the total number of code lines.
[0100] See also Figure 4 , which is a flow chart of another distributed system testing method provided by an embodiment of the present application, the method comprising:
[0101] S401: Obtain a test request and a Trace ID.
[0102] As an example, you can use a UUID or a random number as the Trace ID, and you can use the _modifyHeaders method to intercept the test request to obtain the test request.
[0103] S402: Execute the message injection of the Trace ID through the customized tool pre-deployed in the mobile application, and modify the test request to obtain the target request containing the Trace ID.
[0104] As an example, for applications running on mobile devices, such as Android applications, customized tools can be developed in advance to implement Trace ID message injection for test requests. For example, the TraceID generation and injection functions can be added to the existing Buginsight SDK, and / or new APIs or configuration options can be provided to allow custom TraceID generation and injection in the application, thereby implementing Trace ID message injection for test requests and ensuring that all test requests carry unique Trace IDs.
[0105] S403: Testing the distributed system based on the target request and the B3 link tracking protocol.
[0106] S404: Upload coverage data to the test platform based on the Trace ID.
[0107] The coverage data includes the ratio of executed code lines to the total number of code lines.
[0108] See also Figure 5 , this figure is a schematic diagram of a distributed system testing device provided in an embodiment of the present application, and the device includes: an acquisition module 501, a modification module 502 and a testing module 503.
[0109] The acquisition module 501 is used to acquire the test request and the Trace ID; the Trace ID corresponds to the test request one by one;
[0110] A modification module 502, used to modify the test request based on the Trace ID to obtain a target request including the Trace ID;
[0111] The testing module 503 is used to test the distributed system based on the target request and the B3 link tracking protocol.
[0112] Therefore, in the embodiment of the present application, the test request is modified based on the Trace ID, and a unique identifier in the distributed system is provided for each test request. Then, the B3 link tracking protocol can be used to track the entire link of the test with the target request containing the Trace ID as the identifier, thereby ensuring that during the test process, the behavior of the code itself and the interaction between the code and the external system, service or library are correctly simulated, monitored and verified, thereby improving the effectiveness of the test results of the distributed architecture application system. In addition, the method adopted by the embodiment of the present application can also realize automated testing of distributed systems, which can improve test efficiency, shorten test cycles, and reduce test costs.
[0113] Optionally, the acquisition module 501 is specifically used to: obtain a unique identifier of the client mobile device; extract a preset number of characters from a preset position of the unique identifier to obtain a first character segment; and concatenate a preset character string, the first character segment and a random character string to obtain a Trace ID.
[0114] Optionally, the modification module 502 is specifically configured to: in response to the message object sent by the event listener, add a request header to the test request based on the TraceID to obtain a target request containing the Trace ID.
[0115] Optionally, the modification module 502 is specifically used to: perform message injection of the Trace ID through a customized tool pre-deployed in the mobile application, and modify the test request to obtain a target request containing the Trace ID.
[0116] Optionally, another distributed system testing device provided by an embodiment of the present application also includes: a first uploading module, used to upload the first character segment to the testing platform.
[0117] Optionally, another distributed system testing device provided by an embodiment of the present application also includes: a second uploading module, used to upload coverage data to the test platform based on the Trace ID; the coverage data includes the ratio of executed code lines to the total number of code lines.
[0118] See also Figure 6 , this figure is a structural diagram of a distributed system testing device provided in an embodiment of the present application, and the device includes: a memory 601 and a processor 602.
[0119] Memory 601: used to store program codes and transmit the program codes to the processor.
[0120] Processor 602: used to execute the steps of the above-mentioned distributed system testing method according to the instructions in the program code.
[0121] In addition, the present application also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a distributed system testing device, the distributed system testing device executes the steps of the above-mentioned distributed system testing method.
[0122] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0123] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A distributed system testing method, characterized in that: The method comprises: Obtain a test request and a TraceID; the TraceID corresponds to the test request one by one; Modify the test request based on the TraceID to obtain a target request including the TraceID; Based on the target request and the B3 link tracking protocol, the distributed system is tested.
2. The method according to claim 1, characterized in that: The step of obtaining the Trace ID includes: Obtain a unique identifier for the client's mobile device; Extracting a preset number of characters from a preset position of the unique identifier to obtain a first character segment; The preset character string, the first character fragment and the random character string are concatenated to obtain a Trace ID.
3. The method according to claim 2, characterized in that After extracting a preset number of characters from the tail of the unique identifier to obtain the first character segment, the method further includes: The first character segment is uploaded to the test platform.
4. The method according to claim 1, characterized in that: The step of modifying the test request based on the Trace ID to obtain a target request including the TraceID includes: In response to the message object sent by the event listener, a request header is added to the test request based on the Trace ID to obtain a target request containing the TraceID.
5. The method according to claim 4, characterized in that The event listeners include checkHeaderEditorInstalled, changeHeaderEditorTraceId, and toggleSwitchHeaderEditor.
6. The method according to claim 1, characterized in that The step of modifying the test request based on the Trace ID to obtain a target request including the TraceID includes: The message injection of Trace ID is performed through a customized tool pre-deployed in the mobile application, and the test request is modified to obtain a target request containing TraceID.
7. The method according to any one of claims 1 to 6, characterized in that: After testing the distributed system based on the target request and the B3 link tracking protocol, the method further includes: Based on the TraceID, coverage data is uploaded to the test platform; the coverage data includes the ratio of executed code lines to the total number of code lines.
8. A distributed system testing device, characterized in that: The device comprises: an acquisition module, a modification module and a test module; The acquisition module is used to acquire the test request and the TraceID; the TraceID corresponds to the test request one by one; The modification module is used to modify the test request based on the Trace ID to obtain a target request containing the TraceID; The test module is used to test the distributed system based on the target request and the B3 link tracking protocol.
9. A distributed system testing device, characterized in that: The device comprises: a memory and a processor; The memory is used to store program codes and transmit the program codes to the processor; The processor is used to execute the steps of the distributed system testing method according to any one of claims 1 to 7 according to the program code.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program. When the computer program runs on a distributed system testing device, the distributed system testing device executes the steps of the distributed system testing method according to any one of claims 1 to 7.