Business transaction link test method, device and system

Abstract

This invention discloses a method, apparatus, device, and storage medium for testing business transaction links, relating to the field of software testing and applicable to the fintech field. The method includes: determining information about each node in the business transaction link; obtaining the monitoring method corresponding to each node; testing each node according to its corresponding monitoring method; and storing the test results of each node for each monitoring method in the business transaction link test results. The solution provided by this invention improves the testing efficiency of business transaction links.

Description

Technical Field

[0001] This invention relates to the field of software testing technology, and in particular to a method, apparatus, device, and storage medium for testing business transaction links. Background Technology

[0002] As the architecture of technological information systems becomes increasingly complex, business transaction chains increase significantly, and business logic rules become more intricate, current business testing work faces various transformations, including platform transformation under the host machine, canary releases, and product decoupling. Many of these transformations rely on various switches, circulation loops, and environmental controls, resulting in a lack of transparency regarding business information. Business testers are unaware of whether the business transactions they are testing are following the correct chain, and technical personnel are also spending more time locating and troubleshooting errors. Therefore, how to achieve real-time tracking and early warning of the business transaction chain status is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This invention provides a method, apparatus, device, and storage medium for testing business transaction links, thereby improving the testing efficiency of business transaction links.

[0004] According to one aspect of the present invention, a method for testing a business transaction chain is provided, comprising:

[0005] Determine the information of each node in the business transaction chain;

[0006] Obtain the monitoring method corresponding to each node;

[0007] Each node is tested according to the monitoring method corresponding to each node, and the test results of each monitoring method for each node are stored in the business transaction link test results.

[0008] In one embodiment, obtaining the monitoring method corresponding to each node includes:

[0009] Obtain the technical monitoring methods and / or business monitoring methods corresponding to each node.

[0010] In one embodiment, each node is tested according to the monitoring method corresponding to each node, including:

[0011] Technical testing was conducted on each node according to the corresponding technical monitoring method.

[0012] And / or perform business tests on each node according to the business monitoring method corresponding to each node.

[0013] In one embodiment, the technical monitoring method includes at least one of the following: address interface, service registration, and port;

[0014] Business monitoring methods include at least one of the following: database, server logs, and cloud platform logs.

[0015] In one embodiment, each node is tested according to the monitoring method corresponding to each node, and the test results of each monitoring method for each node are stored in the business transaction link test results, including:

[0016] Test each node according to the monitoring method corresponding to each node, and determine the test result status and test result information of each node for each monitoring method;

[0017] The test results and status of each monitoring method of each node are stored in the status parameter field corresponding to each monitoring method of each node in the business transaction link test results, and the test result information of each monitoring method of each node is stored in the result information field corresponding to each monitoring method of each node in the business transaction link test results.

[0018] In one embodiment, after testing each node according to the monitoring method corresponding to each node, the method further includes:

[0019] When the test result of any monitoring method for any node is abnormal, an abnormal status notification message is issued.

[0020] In one embodiment, when the test result status of any monitoring method for any node is abnormal, an abnormal status notification message is issued, including:

[0021] When the test result status of any node in any monitoring method is abnormal, an abnormal status notification email is sent to the management email address bound to the monitoring method. The abnormal status notification email includes the node information, monitoring method and test result information.

[0022] According to another aspect of the present invention, a business transaction link testing apparatus is provided, comprising:

[0023] The determination module is used to determine the information of each node in the business transaction chain;

[0024] The acquisition module is used to acquire the monitoring method corresponding to each node.

[0025] The monitoring module is used to test each node according to the monitoring method corresponding to each node and store the test results of each monitoring method of each node into the business transaction link test results.

[0026] According to another aspect of the present invention, an electronic device is provided, comprising: a processor, and a memory communicatively connected to the processor;

[0027] The memory stores the instructions that the computer executes;

[0028] The processor executes computer execution instructions stored in memory to implement the aforementioned business transaction link testing method.

[0029] According to another aspect of the present invention, a computer program product is provided, comprising a computer program stored in a computer-readable storage medium, wherein at least one processor can read the computer program from the computer-readable storage medium, and the at least one processor implements the above-described business transaction link testing method when executing the computer program.

[0030] The technical solution of this invention first determines the information of each node in the business transaction link, then obtains the monitoring method corresponding to each node, and finally tests each node according to the monitoring method corresponding to each node and stores the test results of each monitoring method of each node into the business transaction link test results. This greatly improves the testing efficiency of testers on the business transaction link and can be applied to various different business transaction links with a high environment availability.

[0031] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 A flowchart illustrating a business transaction link testing method provided in an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram of the structure of a business transaction link testing device provided in an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present invention. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with the relevant provisions of national laws and regulations.

[0037] Figure 1 This is a flowchart illustrating a business transaction link testing method provided in an embodiment of the present invention, as shown below. Figure 1 As shown, the business transaction link testing method provided in this embodiment includes:

[0038] Step S110: Determine the information of each node in the business transaction chain.

[0039] The business transaction link testing method provided in this application embodiment can be applied to any computer or server with processing capabilities. This computer or server is used to monitor or test the business transaction link, and can establish connections with each node in the business transaction link for testing. Alternatively, the business transaction link testing method provided in this embodiment can be executed by a software module installed in the computer or server. This computer or server can be deployed locally or in the cloud. The business transaction link testing method provided in this application embodiment can be used in the fintech field.

[0040] The business transaction link testing method provided in this application tests any type of business transaction link. A business transaction link refers to the entire path process from when a user initiates a transaction request to when the transaction is completed and a business loop is achieved, covering all aspects of user operation, system processing, data flow, and business implementation. Nodes in a business transaction link refer to key links or steps in the entire transaction process. Each node undertakes a specific function and is connected through system interaction and data flow to complete the entire link. Nodes in a business transaction link are generally software nodes, or each node can also be a hardware node that implements a specific function of the business transaction link.

[0041] To test the business transaction chain, it is first necessary to determine the information of each node in the chain. This node information can be the node information of all nodes in the chain, allowing for a complete test of the entire chain. The node information includes basic node information such as node name and identifier, as well as related node information such as parent and child nodes. Based on this information, the target node for testing the business transaction chain can be determined.

[0042] Step S120: Obtain the monitoring method corresponding to each node.

[0043] After determining the information of each node in the business transaction chain, the monitoring method corresponding to each node is further obtained. The monitoring method for each node indicates the way to test each node. Because different nodes are located at different positions in the business transaction chain and perform different functions in the business transaction chain, they may need to be tested using different methods. Therefore, the monitoring method for each node indicates the different methods to test each node.

[0044] The monitoring methods for each node can be varied, categorized into technical monitoring and business monitoring. The monitoring methods configured for each node can include only technical monitoring, only business monitoring, or both. Technical monitoring involves performing technical-level tests on the node to determine whether it meets the usage requirements of the business transaction chain. Business monitoring involves performing business-level tests on the node to determine whether it meets the business requirements executed on the business chain. Both technical and business monitoring can have multiple different monitoring methods, tailored to the specific technical and business characteristics of each node. Each monitoring method can include the testing method and normal test reference results. If the test results obtained differ from the normal test reference results after testing using each method, test anomalies can be detected promptly.

[0045] The monitoring methods for each node in the business transaction chain can be configured by the maintenance personnel of the business transaction chain according to the actual situation of the node and the testing requirements. The monitoring methods for the same business transaction chain can also be different in different application scenarios.

[0046] Step S130: Test each node according to the monitoring method corresponding to each node and store the test results of each monitoring method of each node into the business transaction link test results.

[0047] After obtaining the monitoring methods corresponding to each node in the business transaction link, each node can be tested using those methods to obtain test results for each monitoring method. These test results can then be stored in the business transaction link test results file, thus completing a full test of the business transaction link. The business transaction link test results include the measurement results of all corresponding monitoring methods for all nodes in the link. The test results for a single business transaction link test can be stored in a test log file for easy viewing by relevant personnel.

[0048] Because corresponding monitoring methods are configured for each node in the business transaction chain, when performing a test on the business transaction chain, all nodes in the entire business transaction chain undergo the required complete testing.

[0049] Testing the business transaction chain can be done by testing each node according to its corresponding monitoring method, determining the test result status and information for each monitoring method. In other words, the testing of various monitoring methods includes not only the test result information but also the test result status indicating whether the test result matches the normal result. If the test result information is consistent with the preset normal test reference result, the test result status is normal; otherwise, the test result status is abnormal. After determining the test result status and information for each monitoring method at each node, the test result status of each node is stored in the status parameter field corresponding to each monitoring method in the business transaction chain test results, and the test result information of each node's monitoring method is stored in the result information field corresponding to each monitoring method in the business transaction chain test results. This allows relevant maintenance and management personnel of the business transaction chain to intuitively see the abnormal nodes and their corresponding monitoring methods from the test result status. Furthermore, by analyzing the test result information, they can quickly locate the abnormal nodes and their causes in the entire business transaction chain, thereby greatly improving the detection efficiency of the business transaction chain.

[0050] Furthermore, after testing each node according to its corresponding monitoring method, and determining that the test results for each monitoring method include the test result status, if the test result status of any monitoring method for any node is abnormal, an abnormal status notification can be issued. This abnormal status notification can be sent to the maintenance or management personnel of the business transaction link, or to the personnel performing tests on the business transaction link, so that relevant personnel are aware of any anomalies in the tested business transaction link as soon as possible.

[0051] When the test result status of any monitoring method on any node is abnormal, an abnormal status notification can be sent via email, SMS, or any other method. For example, when the test result status of any monitoring method on any node is abnormal, an abnormal status notification email can be sent to the management email address bound to the monitoring method. The abnormal status notification email includes information about the node with the abnormal test result status, the monitoring method, and the test result information.

[0052] Since monitoring of each node in the business transaction chain includes both technical and / or business monitoring methods, testing each node can include technical testing based on the corresponding technical monitoring method and business testing based on the corresponding business monitoring method. Technical monitoring methods are entered into the user-inputted technical information, and each method includes corresponding technical parameters. Testing of the corresponding node can be performed based on these parameters, and each method can also include correct test results. Similarly, business monitoring methods are entered into the user-inputted business information, and each method includes corresponding business parameters. Testing of the corresponding node can be performed based on these parameters, and each business monitoring method can also include correct test results.

[0053] Optionally, technical monitoring methods may include at least one of the following: address interface, service registration, and port; business monitoring methods may include at least one of the following: database, server logs, and cloud platform logs.

[0054] In one specific implementation, the technical monitoring methods include three types: address interface, service registration, and port. When the technical monitoring method is a Hypertext Transfer Protocol (HTTP) address interface, this method can include the following information: the HTTP interface Uniform Resource Locator (URL) address, input parameters, calling method (GET, POST), and normal return value of the interface. When the technical monitoring method is a service registration method, this method can include the following information: service name, registered application name, etc. When the technical monitoring method is a port, this method can include the following information: server address and port number.

[0055] In one specific implementation, business monitoring methods include three types: database monitoring, server log monitoring, and cloud platform log monitoring. When the business monitoring method is database monitoring, it can include the following information: database type, connection string, username, password, business transaction query SQL, successful transaction return value, and transaction return information. When the business monitoring method is server logs (e.g., Infrastructure as a Service (IaaS) logs), it can include the following information: server network protocol (Internet Protocol, IP), username, password, log path (absolute path + filename), transaction code, and successful transaction return value. When the business monitoring method is cloud platform logs (e.g., Platform as a Service (PaaS) logs), it can include the following information: PaaS application name, log path (absolute path + filename), transaction code, and successful transaction return value.

[0056] In one embodiment, the node information in the business transaction link can be pre-configured. This node information includes at least one of the following: transaction scene identifier (sceneid), transaction scene name (scenename), node ID (nodeid), and node name (nodename). Each node's information may also include a parent node ID (pa_id) and a child node ID (ch_id). Using a depth-first search algorithm based on the nodeid, idpa_id, and idch_id fields of each node in the business transaction link, a complete business transaction link diagram for that transaction scene can be obtained and displayed. The node information in the business transaction link can also reserve monitoring status and monitoring information fields to store test results after testing the business transaction link. Storing the node information and test results together facilitates quick location of relevant nodes in the business transaction link for personnel reviewing test results later. As described above, monitoring methods for each node can include technical monitoring and business monitoring. The test results for each monitoring method can include test result status and test result information. Therefore, technical monitoring interface status (techstatus), technical monitoring interface information (techmessage), business monitoring status (bussstatus), and business monitoring information (bussmessage) fields can be specifically set to store various test results. When there are multiple monitoring methods for each node, corresponding status and information fields are set for each monitoring method to store the test results. The technical monitoring interface status and business monitoring status fields can be single-bit fields; for example, a value of 1 indicates normal operation, and a value of 0 indicates an error.

[0057] In one embodiment, for each node in the business transaction link, the monitoring method of each node can be pre-configured. The monitoring method can be divided into technical monitoring method and business monitoring method, or it can be referred to as technical information and business information. Technical information and business information are configured for each node (each nodeid) in the business transaction link information.

[0058] When the technical monitoring methods for each node in the business transaction chain are configured as address interface, service registration, and port, the specific methods for testing each node in the business transaction chain can be as follows:

[0059] For cases where the technical monitoring method is an HTTP address interface, for example, Python's REQUEST module can be used to deploy this technical monitoring method. Specifically, first, iterate through the technical monitoring methods (technical information) of all nodes in the business transaction chain, then use the REQUEST method of the corresponding calling method to call the interface URL address, and then compare the return value of the call with the preset correct test result. If they match, the test result status is confirmed as normal, and the techstatus field of the technical monitoring method in the business transaction chain's node information can be recorded as 1. If they do not match, the techstatus field of the technical monitoring method in the business transaction chain's node information can be recorded as 0, and the call return value (i.e., the interface error information) can be recorded in the techmessage field of the technical monitoring method in the business transaction chain's node information.

[0060] For cases where the technical monitoring method is service registration, the service name entered by each node can be directly retrieved in the service registry center. If the service name exists, the techstatus field of the node information in the business transaction link for that technical monitoring method is recorded as 1. If the service name does not exist, the techstatus field of the node information in the business transaction link for that technical monitoring method is recorded as 0.

[0061] For cases where the technical monitoring method is a port, the shell command `nerstat` can be used to check the port status. Specifically, first, iterate through the technical monitoring methods (technical information) of all nodes in the business transaction chain. Then, execute `netstat -an|grep port number` on the server IP. If a port is returned, record the `techstatus` field in the node information of that technical monitoring method in the business transaction chain as 1. If no port is returned, record the `techstatus` field in the node information of that technical monitoring method in the business transaction chain as 0, and record "Port startup abnormal" in the `techmessage` field of the node information of that technical monitoring method in the business transaction chain.

[0062] When the business transaction chain is configured with three monitoring methods—database, server logs, and cloud platform logs—the specific methods for testing each node in the business transaction chain can be as follows:

[0063] First, iterate through the business monitoring methods (business information) of all nodes in the business transaction chain. If the business monitoring method is a database, connect to the corresponding database using the database type, connection string, account, and password information, and execute the business transaction query SQL. If the SQL return result is equal to the transaction success return value, then the bussstatus field of the business monitoring method in the business transaction chain's node information can be recorded as 1. If the SQL return result is not equal to the transaction success return value, then the bussstatus field of the business monitoring method in the business transaction chain's node information can be recorded as 0, and the SQL return result can be recorded in the bussmessage field of the business monitoring method in the business transaction chain's node information. If the business monitoring method is server logs (IASS server logs), the log file is obtained through the server IP, account, password, and log path (absolute path + filename). The latest line of data containing the transaction code in the file is retrieved. If the line of data contains a successful transaction return value, the bussstatus field in the business transaction link information of this business monitoring method is recorded as 1. If it does not contain a successful transaction return value, the bussstatus field in the business transaction link information of this business monitoring method is recorded as 0. The subsequent data information matched by the transaction code is entered into the bussmessage field in the business transaction link information of this business monitoring method. If the business monitoring method is cloud platform logs (PASS logs), then the log file is obtained by using the PaaS application name and log path (absolute path + file name), and the latest line of data containing the transaction code is retrieved from the file. If the data in the file contains a successful transaction return value, then the bussstatus field in the business transaction link information of this business monitoring method can be recorded as 1. If it does not contain a return value, then the bussstatus field in the business transaction link information of this business monitoring method can be recorded as 0, and the subsequent data information matched by the transaction code is entered into the bussmessage field in the business transaction link information of this business monitoring method.

[0064] After testing each node according to the monitoring method corresponding to each node, when the test result of any monitoring method of any node is abnormal, the abnormal status notification information can be sent by email. Specifically, the information of each node in the business transaction system can be traversed. When the techstatus field corresponding to the technical monitoring method of a certain node is 1, the abnormal information of the technical monitoring method is sent to the preset email address of the relevant technical maintenance or management personnel of the business transaction link. When the bussstatus field corresponding to the business monitoring method of a certain node is 1, the abnormal information of the business monitoring method is sent to the preset email address of the relevant business maintenance or management personnel of the business transaction link.

[0065] Figure 2 This is a schematic diagram of the structure of a business transaction link testing device provided in an embodiment of the present invention, as shown below. Figure 2 As shown, the business transaction link testing device provided in this embodiment includes:

[0066] The determination module 21 is used to determine the information of each node in the business transaction link; the acquisition module 22 is used to acquire the monitoring method corresponding to each node; the monitoring module 23 is used to test each node according to the monitoring method corresponding to each node and store the test results of each monitoring method of each node into the business transaction link test results respectively.

[0067] The business transaction link testing device provided in this embodiment is used to implement... Figure 1 The business transaction link testing device and method provided in the illustrated embodiment have similar implementation principles and technical effects, and will not be described in detail here.

[0068] In one embodiment, the acquisition module 22 is specifically used to acquire the technical monitoring method and / or business monitoring method corresponding to each node.

[0069] In one embodiment, the monitoring module 23 is specifically used to perform technical testing on each node according to the technical monitoring method corresponding to each node; and / or to perform business testing on each node according to the business monitoring method corresponding to each node.

[0070] In one embodiment, the technical monitoring method includes at least one of the following: address interface, service registration, and port; the business monitoring method includes at least one of the following: database, server logs, and cloud platform logs.

[0071] In one embodiment, the monitoring module 23 is specifically used to test each node according to the monitoring method corresponding to each node, determine the test result status and test result information of each monitoring method of each node; store the test result status of each monitoring method of each node in the status parameter field corresponding to each monitoring method of each node in the business transaction link test result, and store the test result information of each monitoring method of each node in the result information field corresponding to each monitoring method of each node in the business transaction link test result.

[0072] In one embodiment, the business transaction link testing device further includes a notification module, which is used to issue an abnormal status notification message when the test result status of any node in any monitoring method is abnormal.

[0073] In one embodiment, the notification module is specifically used to send an abnormal status notification email to the management email address bound to the monitoring method when the test result status of any monitoring method of any node is abnormal. The abnormal status notification email includes information about the node with the abnormal test result status, the monitoring method, and the test result information.

[0074] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 3 As shown, the electronic device may include: a transceiver 31, a processor 32, and a memory 33.

[0075] Processor 32 executes computer execution instructions stored in memory, causing processor 32 to perform the scheme in the above embodiments. Processor 32 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0076] The memory 33 is connected to the processor 32 via the system bus and completes communication between them. The memory 33 is used to store computer program instructions.

[0077] Transceiver 31 can be used to obtain the task to be run and its configuration information.

[0078] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory.

[0079] The electronic device provided in this application embodiment can be a computer or server deployed by the business transaction link testing device in the above embodiments.

[0080] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer performs the technical solution of the business transaction link testing method described in the above embodiment.

[0081] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the business transaction link testing method in the above embodiments.

[0082] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0083] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for testing a business transaction chain, characterized in that, include: Determine the information of each node in the business transaction chain; Obtain the monitoring method corresponding to each node; Each node is tested according to the monitoring method corresponding to each node, and the test results of each monitoring method for each node are stored in the business transaction link test results.

2. The method of claim 1, wherein, The methods for obtaining the monitoring corresponding to each node include: Obtain the technical monitoring methods and / or business monitoring methods corresponding to each node.

3. The method of claim 2, wherein, The testing of each node according to the monitoring method corresponding to each node includes: Technical testing was conducted on each node according to the corresponding technical monitoring method. And / or perform business tests on each node according to the business monitoring method corresponding to each node.

4. The method of claim 3, wherein, The technical monitoring methods include at least one of the following: address interface, service registration, and port; The business monitoring methods include at least one of the following: database, server logs, and cloud platform logs.

5. The method according to any one of claims 1 to 4, characterized in that, The step of testing each node according to the monitoring method corresponding to each node and storing the test results of each monitoring method for each node into the business transaction link test results includes: Test each node according to the monitoring method corresponding to each node, and determine the test result status and test result information of each node for each monitoring method; The test results and status of each monitoring method of each node are stored in the status parameter field corresponding to each monitoring method of each node in the business transaction link test results, and the test result information of each monitoring method of each node is stored in the result information field corresponding to each monitoring method of each node in the business transaction link test results.

6. The method of claim 5, wherein, After testing each node according to the monitoring method corresponding to each node, the process also includes: When the test result of any monitoring method for any node is abnormal, an abnormal status notification message is issued.

7. The method of claim 6, wherein, When the test result of any monitoring method for any node is abnormal, an abnormal status notification message is issued, including: When the test result status of any node in any monitoring method is abnormal, an abnormal status notification email is sent to the management email address bound to the monitoring method. The abnormal status notification email includes the node information, monitoring method and test result information of the node with abnormal test result status.

8. A service transaction link testing apparatus characterized by comprising: include: The determination module is used to determine the information of each node in the business transaction chain; The acquisition module is used to acquire the monitoring method corresponding to each node. The monitoring module is used to test each node according to the monitoring method corresponding to each node and store the test results of each monitoring method of each node into the business transaction link test results.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the business transaction link testing method as described in any one of claims 1-7.

10. A computer program product, characterised in that, It includes a computer program stored in a computer-readable storage medium, at least one processor can read the computer program from the computer-readable storage medium, and the at least one processor can implement the business transaction link testing method as described in any one of claims 1 to 7 when executing the computer program.

Images