Application test method and device, electronic equipment and storage medium

Abstract

The invention relates to an application test method and device, electronic equipment and a storage medium, and relates to the technical field of computers, and the method comprises the steps: obtaining an application service relation graph and test range indication information under the condition that an application test instruction is received; determining a plurality of to-be-tested services and service link diagrams based on the application service relation diagram; performing link weight analysis on each to-be-tested sub-link based on the edge weight information or the node weight information in each to-be-tested sub-link to obtain sub-link weight information; based on the sub-link weight information and the service link diagram, performing a flow distribution test on the plurality of to-be-tested sub-links to obtain a link calling test result; obtaining service test codes corresponding to a plurality of to-be-tested services; based on the service test code, performing a service execution test on each service to be tested in the plurality of services to be tested to obtain a service execution test result; and generating an application test result based on the link call test result and the service execution test result.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to an application testing method, apparatus, electronic device, and storage medium. Background Technology

[0002] An application may contain multiple services to be invoked and multiple service call chains. The detection of these call chains is typically a routine maintenance and troubleshooting process conducted by operations and maintenance (O&M) personnel based on their understanding of the application and their O&M experience. Specifically, applications may have corresponding application deployment documents, which record the software call chains of each function at a relatively abstract level. O&M personnel need to carefully read and understand these documents and, with the help of application developers, encounter problems in actual O&M environments to refine the specific objects and relationships of the software call chains for each function. O&M personnel need to communicate and cooperate with each other to accumulate O&M experience, but passing this experience on to the next O&M personnel is costly and the results are inconsistent. Furthermore, application call chains evolve with application versions. Relying solely on application documentation and O&M personnel mentoring to record these chains leads to high O&M and troubleshooting costs, inconsistent results, and significant manpower and time investment. The unpredictable effectiveness of application O&M support also impacts the efficiency of application development and delivery. Therefore, current application call chain testing methods are inefficient and have low accuracy. Summary of the Invention

[0003] In view of the aforementioned technical problems, this disclosure proposes an application testing method, apparatus, electronic device, and storage medium.

[0004] According to one aspect of the embodiments of this disclosure, an application testing method is provided, the method comprising:

[0005] Upon receiving an application test instruction for a target application, the system obtains the application service relationship graph corresponding to the target application and the test scope indication information corresponding to the application test instruction; the application service relationship graph is constructed with multiple application services corresponding to the target application as nodes and the call relationships between application service nodes as edges.

[0006] Based on the application service relationship graph, multiple services to be tested corresponding to the test scope indication information are determined from the multiple application services, and the service link graphs of each of the multiple sub-links to be tested corresponding to the test scope indication information are determined.

[0007] Based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link to be tested, a link weight analysis is performed on each sub-link to be tested to obtain the sub-link weight information corresponding to each sub-link to be tested; the sub-link weight information corresponding to each sub-link to be tested characterizes the importance of each sub-link to be tested in the multiple sub-links to be tested.

[0008] Based on the sub-link weight information corresponding to each of the multiple sub-links to be tested and the service link diagram, traffic allocation test is performed on the multiple sub-links to be tested to obtain the link call test results.

[0009] Obtain the service test code corresponding to the multiple services to be tested;

[0010] Based on the service test code, service execution tests are performed on each of the plurality of services to be tested to obtain the service execution test results corresponding to each service to be tested.

[0011] Based on the link call test results and the service execution test results, the application test results corresponding to the target application are generated.

[0012] According to another aspect of the embodiments of this disclosure, an application testing apparatus is provided, the apparatus comprising:

[0013] The first information acquisition module is used to acquire, upon receiving an application test instruction for a target application, an application service relationship graph corresponding to the target application and test scope indication information corresponding to the application test instruction; the application service relationship graph is constructed with multiple application services corresponding to the target application as nodes and the call relationship between application service nodes as edges;

[0014] The execution module is used to determine, based on the application service relationship diagram, multiple services to be tested corresponding to the test scope indication information from the multiple application services, and to determine the service link diagram of each of the multiple sub-links to be tested corresponding to the test scope indication information.

[0015] The first weight analysis module is used to perform link weight analysis on each sub-link under test based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test; the sub-link weight information corresponding to each sub-link under test represents the importance of each sub-link under test in the multiple sub-links under test.

[0016] The traffic allocation test module is used to perform traffic allocation tests on the multiple sub-links to be tested based on the sub-link weight information corresponding to each of the multiple sub-links to be tested and the service link diagram, and to obtain the link call test results.

[0017] The code acquisition module is used to acquire the service test code corresponding to the multiple services to be tested.

[0018] The service execution test module is used to perform service execution tests on each of the plurality of services to be tested based on the service test code, and obtain the service execution test results corresponding to each service to be tested;

[0019] The test result generation module is used to generate application test results corresponding to the target application based on the link call test results and the service execution test results.

[0020] Optionally, the device further includes:

[0021] The second weight analysis module is used to perform edge weight analysis on each edge in the target sub-link under test based on the associated node information of each edge in the multiple edges included in the target sub-link under test indicated by the application service relationship graph, and to obtain the edge weight information corresponding to each edge; the target sub-link under test is any one of the multiple sub-links under test, and the edge weight information corresponding to each edge represents the importance of each edge in the multiple sub-links under test.

[0022] Accordingly, the first weight analysis module includes:

[0023] The first fusion unit is used to fuse the edge weight information corresponding to each of the multiple edges in the target sub-link to be tested, so as to obtain the sub-link weight information corresponding to the target sub-link to be tested.

[0024] Optionally, the second weight analysis module includes:

[0025] The first node acquisition unit is used to determine multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are nodes in the target sub-link to be tested that are connected to the target edge.

[0026] The node weight analysis unit is used to perform node weight analysis on each of the plurality of adjacent nodes based on the associated node information of the target edge indicated by the application service relationship graph, so as to obtain the first node weight information corresponding to each adjacent node.

[0027] The second fusion unit is used to fuse the first node weight information corresponding to each of the multiple adjacent nodes to obtain the edge weight information corresponding to the target edge.

[0028] Optionally, the associated node information of the target edge includes the number of parent nodes of the adjacent nodes of the target edge and the number of child nodes of the adjacent nodes of the target edge; the node weight analysis unit includes:

[0029] The first duration acquisition unit is used to acquire the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node;

[0030] The third fusion unit is used to perform fusion processing on the preset timeout duration corresponding to each adjacent node, the number of parent nodes corresponding to each adjacent node, and the number of child nodes corresponding to each adjacent node to obtain the first node weight information corresponding to each adjacent node.

[0031] Optionally, the associated node information of each edge includes the number of parent nodes of each edge's adjacent nodes and the number of child nodes of each edge's adjacent nodes; the second weight analysis module includes:

[0032] The second node acquisition unit is used to determine multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are nodes in the target sub-link to be tested that are connected to the target edge.

[0033] The second duration acquisition unit is used to acquire the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node;

[0034] The first indicator acquisition unit is used to determine the first indicator data corresponding to the target edge based on the preset timeout duration corresponding to each of the multiple adjacent nodes; the first indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of timeout duration.

[0035] The second indicator acquisition unit is used to determine the second indicator data corresponding to the target edge based on the number of parent nodes corresponding to each of the multiple adjacent nodes; the second indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of the number of parent nodes.

[0036] The third indicator acquisition unit is used to determine the third indicator data corresponding to the target edge based on the number of child nodes corresponding to each of the multiple adjacent nodes; the third indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of the number of child nodes.

[0037] The fourth fusion unit is used to fuse the first indicator data, the second indicator data, and the third indicator data to obtain the edge weight information corresponding to the target edge.

[0038] Optionally, the device further includes:

[0039] The third weight analysis module is used to perform node weight analysis on each sub-link node based on the associated node information of each sub-link node among the multiple sub-link nodes included in the target sub-link to be tested indicated by the application service relationship diagram, and to obtain the second node weight information corresponding to each sub-link node; the target sub-link to be tested is any one of the multiple sub-links to be tested;

[0040] Accordingly, the first weight analysis module includes:

[0041] The fifth fusion unit is used to fuse the weight information of multiple second nodes corresponding to the target sub-link under test to obtain the sub-link weight information corresponding to the target sub-link under test.

[0042] Optionally, the traffic allocation test module includes:

[0043] The first instruction generation unit is used to determine the first allocation instruction information corresponding to the plurality of sub-links to be tested based on the sub-link weight information corresponding to the plurality of sub-links to be tested; the first allocation instruction information is used to indicate the allocation of test traffic for the plurality of sub-links to be tested.

[0044] The allocation test unit is used to test the multiple sub-links to be tested based on the first allocation instruction information and the service link diagram, and obtain the link call test results.

[0045] Optionally, the device further includes:

[0046] The sub-link acquisition module is used to determine multiple functional sub-links corresponding to each application function based on the service call relationship under each application function of the target application indicated by the application service relationship diagram.

[0047] The fourth weight analysis module is used to perform link weight analysis on each functional sub-link based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple nodes contained in each functional sub-link, so as to obtain the sub-link weight information of each functional sub-link.

[0048] The fusion module is used to fuse the sub-link weight information of each of the multiple functional sub-links corresponding to each application function to obtain the functional weight information corresponding to each application function; the functional weight information corresponding to each application function represents the importance of each application function in the target application.

[0049] The second instruction generation module is used to determine the second allocation instruction information corresponding to the multiple application functions based on the function weight information corresponding to each of the multiple application functions; the second allocation instruction information is used to indicate the allocation of test traffic for the multiple application functions;

[0050] The call chain testing module is used to test the call chain corresponding to the multiple application functions based on the second allocation indication information, and obtain the function call test results corresponding to the multiple application functions.

[0051] Accordingly, the test result generation module includes:

[0052] The first result generation unit is used to generate the application test results based on the function call test results, the link call test results, and the service execution test results.

[0053] Optionally, the device further includes:

[0054] The link connectivity test module is used to perform network link connectivity tests on the multiple sub-links to be tested and obtain link connectivity test results; the link connectivity test results are used to indicate the network connectivity status of the multiple sub-links to be tested.

[0055] Accordingly, the test result generation module includes:

[0056] The second result generation unit is used to attach the link call test results, the service execution test results, and the link connectivity test results to the service link graph to obtain the application test results.

[0057] Optionally, the plurality of services to be tested includes services to be tested corresponding to business service types and services to be tested corresponding to support service types; the device further includes:

[0058] The backup service testing module is used to perform service execution testing on the backup application service of the second service under test based on the service test code corresponding to the second service under test, when both the service execution test results for the first service under test and the service execution test result for the second service under test are the first execution test result, to obtain the backup execution test result for the backup application service. The first service under test is the service under test corresponding to the business service type, and the second service under test is the service under test corresponding to the support service type. The first service under test and the second service under test are linked through a call chain. The first execution test result is used to indicate that the service execution result of the corresponding service under test does not meet the target execution result.

[0059] The service switching module is used to switch the second service to be tested to the backup application service when the backup execution test result indicates that the backup application service is in normal operation.

[0060] The service test retry module is used to perform service execution tests on the first service under test based on the service test code corresponding to the first service under test, and obtain the retry execution test results corresponding to the first service under test.

[0061] The running status determination module is used to determine the service running status corresponding to the first service to be tested based on the retry execution test results.

[0062] Optionally, the running status determination module includes:

[0063] The running status determination unit is used to determine the normal operating status as the service running status corresponding to the first service under test when the retry execution test result indicates that the service execution result of the first service under test meets the target execution result corresponding to the first service under test.

[0064] Optionally, the application testing instruction includes the current version information corresponding to the target application; the device further includes:

[0065] The historical version acquisition module is used to acquire the historical version information corresponding to the target application based on the current version information;

[0066] The second information acquisition module is used to acquire the historical service relationship diagram corresponding to the target application based on the historical version information.

[0067] The comparison processing module is used to compare the historical service relationship diagram and the application service relationship diagram to obtain relationship diagram difference information; the relationship diagram difference information is used to indicate the parts where there are differences between the historical service relationship diagram and the application service relationship diagram.

[0068] The indication information generation module is used to determine the test range indication information based on the relationship diagram difference information.

[0069] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the above-described application testing method.

[0070] According to another aspect of the present disclosure, a computer-readable storage medium is provided, which, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the above-described application testing method.

[0071] According to another aspect of the present disclosure, a computer program product containing instructions is provided that, when run on a computer, causes the computer to perform the application testing method described above.

[0072] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0073] Upon receiving an application test instruction for a target application, the system acquires the application service relationship graph corresponding to the target application and the test scope indication information corresponding to the application test instruction. The application service relationship graph is constructed with multiple application services corresponding to the target application as nodes and the call relationships between application service nodes as edges. This allows for the acquisition of the application service relationship graph describing the service call relationships within the target application, as well as the acquisition of the corresponding test scope indication information. Combining the application service relationship graph, the system identifies multiple services to be tested corresponding to the test scope indication information from among the multiple application services, and determines the service link graphs for each of the multiple sub-links to be tested corresponding to the test scope indication information. This enables rapid identification of the services to be tested and the sub-links to be tested. Furthermore, by combining the edge weight information or node weight information of the multiple edges or nodes within each sub-link to be tested, a link weight analysis is performed on each sub-link to be tested. By obtaining the sub-link weight information corresponding to each sub-link to be tested, link weight analysis of the sub-link to be tested can be realized. Then, by combining the sub-link weight information and service link graph corresponding to each of the multiple sub-links to be tested, traffic allocation tests are performed on the multiple sub-links to be tested, and link call test results are obtained. This can improve the accuracy of traffic tests on multiple sub-links to be tested, making the link traffic tests closer to and simulating real traffic conditions. Then, the service test code corresponding to multiple services to be tested is obtained. Based on the service test code, service execution tests are performed on each of the multiple services to be tested, and service execution test results are obtained for each service to be tested. This can realize the testing of the service execution of the services to be tested in the target application. Based on the link call test results and service execution test results, application test results corresponding to the target application are generated. This can realize the testing of services and call links in the target application, thereby improving the efficiency and accuracy of application testing.

[0074] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0075] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0076] Figure 1 This is a schematic diagram illustrating an application system according to an exemplary embodiment;

[0077] Figure 2 This is a flowchart illustrating an application testing method according to an exemplary embodiment;

[0078] Figure 3 This is a schematic diagram illustrating an application service relationship diagram according to an exemplary embodiment;

[0079] Figure 4 This is a block diagram illustrating an application testing apparatus according to an exemplary embodiment;

[0080] Figure 5 This is a block diagram illustrating an electronic device for implementing call chain testing of a target application according to an exemplary embodiment;

[0081] Figure 6 This is a block diagram illustrating another electronic device for implementing call chain testing of a target application, according to an exemplary embodiment. Detailed Implementation

[0082] Various exemplary embodiments, features, and aspects of this application will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0083] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0084] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, methods, means, components, and circuits well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0085] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating an application system according to an exemplary embodiment. The application system can be used in the application testing method of this application. The application system may include at least a server 01 and a terminal 02.

[0086] In this embodiment, server 01 can be used to perform testing on a target application. Specifically, server 01 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0087] In this embodiment, terminal 02 can be used to generate application testing instructions for a target application. Terminal 02 may include physical devices such as smartphones, desktop computers, tablets, laptops, smart speakers, in-vehicle terminals, digital assistants, augmented reality (AR) / virtual reality (VR) devices, and smart wearable devices, and may also include software running on the physical device, such as applications. The operating system running on terminal 02 in this embodiment may include, but is not limited to, Android, GNU / Linux, and Windows systems.

[0088] In the embodiments described in this specification, the terminal 02 and the server 01 can be directly or indirectly connected through wired or wireless communication, and this application does not limit this connection.

[0089] It should be noted that the following diagram shows one possible sequence of steps, and it is not strictly necessary to follow this order. Some steps can be executed in parallel without interdependence.

[0090] Specifically, Figure 2 This is a flowchart illustrating an application testing method according to an exemplary embodiment. For example... Figure 2 As shown, this application testing method can be used in electronic devices such as terminals or servers, and may specifically include the following steps:

[0091] S201: Upon receiving an application test instruction for the target application, obtain the application service relationship diagram corresponding to the target application and the test scope indication information corresponding to the application test instruction.

[0092] In one specific embodiment, the target application can refer to the application currently under test. Specifically, the target application may include shopping applications, social applications, or gaming applications, etc. The target application may include multiple application services. Further, the aforementioned multiple application services may include services under test corresponding to business service types, support service types, or gateway service types.

[0093] In one specific embodiment, the application testing instruction can be used to instruct the testing of the services and call chains of the target application. Specifically, the application testing instruction may include the application identification information corresponding to the target application.

[0094] In one specific embodiment, the application tester can perform an application test triggering operation on the target application through a test terminal, so that the test terminal generates application test instructions corresponding to the target application; accordingly, the test terminal can send the application test instructions to the server so that the server can test the target application.

[0095] In a specific embodiment, an application service relationship graph can be used to describe the calling relationships between multiple application services in a target application. The application service relationship graph can be constructed with multiple application services corresponding to the target application as nodes and the calling relationships between these application service nodes as edges. Specifically, Figure 3 This is a schematic diagram illustrating an application service relationship diagram according to an exemplary embodiment; such as Figure 3 As shown, the target application can contain three functions (i.e., function 1, function 2, and function 3). Further, taking function 2 as an example, in... Figure 3 The diagram illustrates the multiple application services included in Function 2 (i.e., application service "lb1", application service "pod1", application service "pod2", application service "pod3", application service "es1", application service "kafka1", and application service "mysql1"), as well as the calling relationships between these application services. Figure 3 The calling relationship between application service "lb1" and application service "pod1" is that application service "lb1" calls application service "pod1".

[0096] In one specific embodiment, application service configuration information corresponding to the target application can be obtained. Based on the application service configuration information, a relationship graph can be constructed using multiple application services corresponding to the target application as nodes and the call relationships between application service nodes as edges, thus obtaining the application service relationship graph corresponding to the target application. The application service configuration information can be used to describe the multiple application services contained in the target application and the call relationships between these multiple application services.

[0097] In one specific embodiment, the test scope indication information can be used to indicate the service scope that needs to be tested. Specifically, the test scope indication information may include function identification information corresponding to the function to be tested, application identification information corresponding to the target application, or service identification information corresponding to multiple services to be tested, etc.

[0098] In one specific embodiment, at least one of the multiple application functions corresponding to the target application can be selected as the function to be tested; correspondingly, the function identification information corresponding to the function to be tested can be used as the test scope indication information. The multiple application functions corresponding to the target application can refer to multiple different application functions that the target application can implement. For example, application functions may include virtual resource interaction functions or chat functions, etc.

[0099] In one specific embodiment, the application identifier information corresponding to the target application can be used as the test scope indication information. Accordingly, when the test scope indication information is the application identifier information corresponding to the target application, all application functions under the target application can be tested.

[0100] In one specific embodiment, the service identifier information corresponding to multiple services to be tested can be used as the test scope indication information.

[0101] In one specific embodiment, the application testing instructions may include the current version information of the target application. This current version information can be used to indicate the version of the target application that the target application currently needs to be tested.

[0102] In one specific embodiment, the test range indication information may be obtained in the following ways:

[0103] Based on the current version information, obtain the historical version information corresponding to the target application;

[0104] Based on historical version information, obtain the historical service relationship diagram corresponding to the target application;

[0105] The historical service relationship diagram and the application service relationship diagram are compared and processed to obtain the difference information of the relationship diagram;

[0106] Based on the difference information in the relationship diagram, the test range indication information is determined.

[0107] In one specific embodiment, historical version information may refer to version information prior to the current version of the target application.

[0108] In a specific embodiment, the tested data corresponding to the target application can be obtained from a preset memory; correspondingly, the tested version information can be obtained from the tested data corresponding to the target application; the version information closest to the current version information in the tested version information can be used as historical version information.

[0109] In one specific embodiment, the historical service relationship diagram may refer to the application service relationship diagram generated during the testing process of the target application based on historical version information.

[0110] In a specific embodiment, the application service relationship diagram corresponding to the historical version information can be obtained from the above-mentioned tested data. Accordingly, the application service relationship diagram corresponding to the above-mentioned historical version information can be used as the above-mentioned historical service relationship diagram.

[0111] In one specific embodiment, relationship graph difference information can be used to indicate the parts where there are differences between the historical service relationship graph and the application service relationship graph.

[0112] In a specific embodiment, the functional identification information corresponding to the parts with differences indicated by the relationship diagram difference information in the application service relationship diagram corresponding to the current version information can be used as the test scope indication information.

[0113] In one specific embodiment, the service identifier information of the application service corresponding to the part of the application service relationship diagram with differences indicated by the relationship diagram difference information corresponding to the current version information can be used as the test scope indication information.

[0114] In the above embodiments, based on the current version information, the historical version information corresponding to the target application is obtained, and based on the historical version information, the historical service relationship diagram corresponding to the target application is obtained. The historical service relationship diagram and the application service relationship diagram are compared and processed to obtain relationship diagram difference information. This can enable rapid analysis of the improvements of the target application under the current version information compared to the historical version. Combined with the relationship diagram difference information, the test scope indication information is determined, thereby improving test efficiency while ensuring test accuracy.

[0115] S203: Based on the application service relationship diagram, determine the multiple services to be tested corresponding to the test scope indication information from multiple application services, and determine the service link diagram of each of the multiple sub-links to be tested corresponding to the test scope indication information.

[0116] In a specific embodiment, multiple services to be tested may refer to the services that need to be tested among the multiple application services mentioned above.

[0117] In a specific embodiment, when the test scope indication information is function identification information, the application function corresponding to the function identification information can be taken as the current function to be tested. Accordingly, the node belonging to the current function to be tested can be found in the application service relationship graph, and the application service corresponding to the node belonging to the current function to be tested can be taken as multiple services to be tested.

[0118] In a specific embodiment, the starting service node corresponding to the currently tested function can be determined in the application service relationship graph, and an initial link graph can be generated based on the starting service node. Based on the application service relationship graph, the next service node corresponding to the starting service node can be determined; the initial link graph can be updated based on the next service node corresponding to the starting service node to obtain an updated link graph; the next service node can be used as the starting service node, and based on the updated starting service node and the updated link graph, the link iteration generation step of determining the next service node corresponding to the starting service node based on the application service relationship graph is repeated until the updated starting service node satisfies a preset iteration convergence condition; the updated link graph obtained when the updated starting service node satisfies the preset iteration convergence condition can be used as the service link graph of the target sub-link to be tested. The target sub-link to be tested can be any one of the multiple sub-links to be tested. Specifically, the preset iteration convergence condition may include the updated starting service node being a leaf node.

[0119] In the above embodiments, by determining multiple services to be tested corresponding to the test scope indication information from multiple application services based on the application service relationship graph, and determining the service link graph of each of the multiple sub-links to be tested corresponding to the test scope indication information, it is possible to quickly obtain the services to be tested and the sub-links to be tested, thereby improving testing efficiency.

[0120] S205: Based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link to be tested, perform link weight analysis on each sub-link to be tested to obtain the sub-link weight information corresponding to each sub-link to be tested.

[0121] In one specific embodiment, the edge weight information of any one side can be used to characterize the importance of any of the aforementioned edges in the target application.

[0122] In one specific embodiment, the node weight information corresponding to any sub-link node can be used to characterize the importance of any of the aforementioned sub-link nodes in the target application.

[0123] In one specific embodiment, the sub-link weight information corresponding to each sub-link under test can characterize the importance of each sub-link under test among multiple sub-links under test. Correspondingly, the sub-link weight information corresponding to any sub-link under test can characterize the importance of any of the aforementioned sub-links under test in the target application. It is understood that the larger the weight information, the higher the corresponding importance.

[0124] In one specific embodiment, the above method may further include:

[0125] Based on the associated node information of each edge in the target sub-link to be tested, indicated by the application service relationship graph, edge weight analysis is performed on each edge in the target sub-link to be tested to obtain the edge weight information corresponding to each edge.

[0126] Accordingly, the link weight analysis performed on each sub-link under test, based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test, may include:

[0127] The edge weight information corresponding to each edge in the target sub-link to be tested is fused to obtain the sub-link weight information corresponding to the target sub-link to be tested.

[0128] In one specific embodiment, the target sub-link to be tested can be any one of the above-mentioned multiple sub-links to be tested.

[0129] In a specific embodiment, the edge weight information corresponding to each edge can characterize the importance of each edge in multiple sub-links to be tested.

[0130] In a specific embodiment, based on the associated node information of each edge among the multiple edges contained in the target sub-link under test indicated by the application service relationship graph, edge weight analysis is performed on each edge in the target sub-link under test to obtain the edge weight information corresponding to each edge, which may include:

[0131] From the target sub-link to be tested, determine multiple adjacent nodes corresponding to the target edge;

[0132] Based on the associated node information of the target edge indicated by the application service relationship graph, node weight analysis is performed on each of the multiple adjacent nodes to obtain the first node weight information corresponding to each adjacent node.

[0133] The weight information of the first node corresponding to each of the multiple adjacent nodes is fused to obtain the edge weight information corresponding to the target edge.

[0134] In one specific embodiment, the target edge can be any one of the multiple edges corresponding to the target sub-link under test. Here, the multiple edges corresponding to the target sub-link under test can refer to the multiple edges contained within the target sub-link under test.

[0135] In one specific embodiment, the aforementioned plurality of adjacent nodes can be nodes in the target sub-link to be tested that are connected to the target edge. Specifically, the number of the plurality of adjacent nodes of the target edge can be two. It is understood that the aforementioned plurality of adjacent nodes can be connected through the target edge.

[0136] In one specific embodiment, the nodes connected to the target edge among the multiple nodes contained in the target sub-link to be tested are regarded as the multiple adjacent nodes corresponding to the target edge.

[0137] In one specific embodiment, the associated node information of the target edge can be used to indicate the attribute information of the nodes associated with the target edge. Specifically, the associated node information of the target edge may include the number of parent nodes of the target edge's neighboring nodes and the number of child nodes of the target edge's neighboring nodes.

[0138] In one specific embodiment, the first node weight information corresponding to any adjacent node can be used to characterize the importance of any of the adjacent nodes in the target application.

[0139] In a specific embodiment, the number of parent nodes and the number of child nodes corresponding to any of the above-mentioned adjacent nodes can be fused to obtain the first node weight information corresponding to any of the above-mentioned adjacent nodes.

[0140] In a specific embodiment, when the associated node information of the target edge includes the number of parent nodes and the number of child nodes of the adjacent nodes of the target edge, the above-mentioned analysis of node weights for each of the multiple adjacent nodes based on the associated node information of the target edge indicated by the application service relationship graph, to obtain the first node weight information corresponding to each adjacent node, may include:

[0141] Obtain the preset timeout duration for each adjacent node from the node configuration information of each adjacent node;

[0142] The preset timeout duration, the number of parent nodes, and the number of child nodes for each adjacent node are fused together to obtain the first node weight information for each adjacent node.

[0143] In one specific embodiment, the node configuration information of any adjacent node can be used to indicate the service configuration of the application service corresponding to any adjacent node. Specifically, the node configuration information of any adjacent node may include a preset timeout duration or a load balancing strategy corresponding to any adjacent node.

[0144] In one specific embodiment, the preset timeout duration for any adjacent node can refer to the maximum waiting time for a service request. It is understood that if the service processing for any node exceeds its corresponding preset timeout duration, the service of that node can be determined to have timed out.

[0145] In a specific embodiment, the preset timeout duration corresponding to any of the above adjacent nodes, the number of parent nodes corresponding to any of the above adjacent nodes, and the number of child nodes corresponding to any of the above adjacent nodes can be multiplied to obtain the first node weight information corresponding to any of the above adjacent nodes.

[0146] In a specific embodiment, the preset timeout duration corresponding to any of the above adjacent nodes, the number of parent nodes corresponding to any of the above adjacent nodes, and the number of child nodes corresponding to any of the above adjacent nodes can be added together to obtain the first node weight information corresponding to any of the above adjacent nodes.

[0147] In a specific embodiment, the preset timeout duration corresponding to any of the above adjacent nodes, the number of parent nodes corresponding to any of the above adjacent nodes, and the number of child nodes corresponding to any of the above adjacent nodes can be weighted and superimposed to obtain the first node weight information corresponding to any of the above adjacent nodes.

[0148] In a specific embodiment, the specific fusion process of the first node weight information corresponding to each of multiple adjacent nodes can refer to the fusion process of the preset timeout duration, number of parent nodes and number of child nodes corresponding to the adjacent nodes, which will not be repeated in this disclosure.

[0149] In the above embodiments, by obtaining the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node, and by fusing the preset timeout duration corresponding to each adjacent node, the number of parent nodes corresponding to each adjacent node, and the number of child nodes corresponding to each adjacent node, the first node weight information corresponding to each adjacent node can be obtained. This enables accurate analysis of the node weight of each adjacent node, thereby improving the accuracy of sub-link weight analysis.

[0150] In a specific embodiment, the fusion process of edge weight information of multiple edges can refer to the fusion process of the preset timeout duration, number of parent nodes and number of child nodes corresponding to adjacent nodes, as described above, and will not be repeated here.

[0151] In the above embodiments, by determining multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested, and performing node weight analysis on each of the multiple adjacent nodes based on the associated node information of the target edge indicated by the application service relationship graph, the first node weight information corresponding to each adjacent node is obtained. The first node weight information corresponding to each of the multiple adjacent nodes is fused to obtain the edge weight information corresponding to the target edge, which can realize edge weight analysis in the dimension of application service.

[0152] In one specific embodiment, the associated node information for each edge may include the number of parent nodes of each edge's adjacent nodes and the number of child nodes of each edge's adjacent nodes.

[0153] In a specific embodiment, the process of analyzing the associated node information of each edge in the target sub-link under test based on the application service relationship graph to obtain the edge weight information corresponding to each edge can include:

[0154] From the target sub-link to be tested, determine multiple adjacent nodes corresponding to the target edge;

[0155] Obtain the preset timeout duration for each adjacent node from the node configuration information of each adjacent node;

[0156] Based on the preset timeout duration of each of the multiple adjacent nodes, determine the first indicator data corresponding to the target edge;

[0157] Based on the number of parent nodes corresponding to each of the multiple adjacent nodes, determine the second indicator data corresponding to the target edge;

[0158] Based on the number of child nodes corresponding to each of multiple adjacent nodes, the third indicator data corresponding to the target edge is determined.

[0159] The first, second, and third indicator data are fused together to obtain the edge weight information corresponding to the target edge.

[0160] In a specific embodiment, the target edge can be any one of the multiple edges corresponding to the target sub-link to be tested.

[0161] In one specific embodiment, the aforementioned multiple adjacent nodes can be nodes in the target sub-link to be tested that are connected to the target edge.

[0162] In one specific embodiment, the first metric data can be used to characterize the importance of the target edge in multiple sub-links under test from the dimension of timeout duration.

[0163] In a specific embodiment, the preset timeout durations corresponding to the above-mentioned multiple adjacent nodes are fused to obtain the first index data corresponding to the above-mentioned target edge.

[0164] In one specific embodiment, the second metric data can be used to characterize the importance of the target edge in multiple sub-links to be tested from the dimension of the number of parent nodes.

[0165] In one specific embodiment, the number of parent nodes corresponding to each of the above-mentioned multiple adjacent nodes is fused to obtain the second index data corresponding to the above-mentioned target edge.

[0166] In one specific embodiment, the third metric data can be used to characterize the importance of the target edge in multiple sub-links under test from the dimension of the number of child nodes.

[0167] In a specific embodiment, the number of child nodes corresponding to each of the above-mentioned multiple adjacent nodes is fused to obtain the third indicator data corresponding to the target edge.

[0168] In a specific embodiment, the fusion processing of the first indicator data, the second indicator data, and the third indicator data can refer to the fusion processing of the preset timeout duration, the number of parent nodes, and the number of child nodes corresponding to the adjacent nodes, as described above, and will not be repeated here.

[0169] In a specific embodiment, the second indicator data and the third indicator data can be fused to obtain the edge weight information corresponding to the target edge.

[0170] In the above embodiments, by determining multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested, obtaining the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node, determining the first indicator data corresponding to the target edge based on the preset timeout duration corresponding to each of the multiple adjacent nodes, determining the second indicator data corresponding to the target edge based on the number of parent nodes corresponding to each of the multiple adjacent nodes, determining the third indicator data corresponding to the target edge based on the number of child nodes corresponding to each of the multiple adjacent nodes, and fusing the first indicator data, the second indicator data, and the third indicator data to obtain the edge weight information corresponding to the target edge, it is possible to perform edge weight analysis from the perspective of node attributes.

[0171] In a specific embodiment, the specific fusion process of the edge weight information of multiple edges of the target sub-link to be tested can refer to the fusion process of the preset timeout duration, number of parent nodes and number of child nodes corresponding to the adjacent nodes, which will not be repeated in this disclosure.

[0172] In the above embodiments, by analyzing the associated node information of each edge in the target sub-link under test based on the application service relationship graph, edge weight analysis is performed on each edge in the target sub-link under test to obtain the edge weight information corresponding to each edge. This can achieve edge weight analysis for each edge in the target sub-link under test. Then, the edge weight information corresponding to each edge in the target sub-link under test is fused to obtain the sub-link weight information corresponding to the target sub-link under test, which can improve the accuracy of link weight analysis for the target sub-link under test.

[0173] In one specific embodiment, the above method may further include:

[0174] Based on the associated node information of each sub-link node in the target sub-link under test indicated by the application service relationship graph, a node weight analysis is performed on each sub-link node to obtain the second node weight information corresponding to each sub-link node.

[0175] Accordingly, the link weight analysis performed on each sub-link under test, based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test, may include:

[0176] The weight information of multiple second nodes corresponding to the target sub-link under test is fused to obtain the sub-link weight information corresponding to the target sub-link under test.

[0177] In one specific embodiment, the target sub-link to be tested can be any one of a plurality of sub-links to be tested.

[0178] In one specific embodiment, the second node weight information corresponding to any sub-link node can be used to characterize the importance of any of the aforementioned sub-link nodes in the target application.

[0179] In a specific embodiment, the node weight analysis process for each sub-link node can refer to the node weight analysis process for adjacent nodes described above. That is, it can be determined by combining the preset timeout duration, the number of parent nodes, and the number of child nodes of any sub-link node, or it can be determined by combining the number of parent nodes and the number of child nodes of any sub-link node. This disclosure will not elaborate further.

[0180] In one specific embodiment, the second node weight information of each of the multiple sub-link nodes included in the target sub-link under test can be fused to obtain the sub-link weight information corresponding to the target sub-link under test. Specifically, the fusion process of multiple second node weight information can refer to the fusion process of the preset timeout duration, number of parent nodes and number of child nodes corresponding to adjacent nodes, which will not be repeated in this disclosure.

[0181] In the above embodiments, by fusing the weight information of multiple second nodes corresponding to the target sub-link under test, the sub-link weight information corresponding to the target sub-link under test can be obtained, which can improve the analysis efficiency of the link weight analysis of each sub-link under test, thereby improving the application testing efficiency.

[0182] S207: Based on the sub-link weight information and service link diagram corresponding to each of the multiple sub-links to be tested, traffic allocation test is performed on the multiple sub-links to be tested to obtain the link call test results.

[0183] In one specific embodiment, the link call test results can be used to indicate whether there are any abnormalities in the service link calls of the target application.

[0184] In a specific embodiment, the above-mentioned traffic allocation test on multiple sub-links under test based on their respective sub-link weight information and service link diagram, to obtain the link call test results, may include:

[0185] Based on the sub-link weight information corresponding to multiple sub-links to be tested, determine the first allocation indication information corresponding to multiple sub-links to be tested;

[0186] Based on the first allocation instruction information and service link diagram, multiple sub-links to be tested are tested to obtain link call test results.

[0187] In one specific embodiment, the first allocation indication information can be used to indicate the allocation of test traffic for multiple sub-links to be tested. Specifically, the first allocation indication information may include traffic allocation ratio data corresponding to each sub-link to be tested. The traffic allocation ratio data corresponding to any sub-link to be tested can be used to indicate the proportion of traffic required to be allocated for testing any given sub-link to be tested within the total test traffic for the multiple sub-links to be tested.

[0188] In a specific embodiment, weight ratio analysis can be performed on the sub-link weight information corresponding to multiple sub-links under test to obtain the aforementioned first allocation indication information. Specifically, the first weight fusion data can be obtained by fusing the sub-link weight information corresponding to multiple sub-links under test; the traffic allocation ratio data corresponding to any sub-link under test can be obtained by dividing the sub-link weight information corresponding to any sub-link under test by the aforementioned first weight fusion data. The first weight fusion data can be used to characterize the sum of the weights of the sub-link weight information corresponding to multiple sub-links under test.

[0189] In a specific embodiment, the allocated traffic quantity for each sub-link to be tested can be determined based on the first allocation instruction information and the preset test traffic quantity. Based on the allocated traffic quantity for each sub-link to be tested, a corresponding amount of test traffic can be allocated to each sub-link to be tested, and the link service processing result of each sub-link to be tested for the allocated traffic can be obtained. The link service processing result of each sub-link to be tested for the allocated traffic can be matched with the corresponding expected processing result to obtain the traffic test result of each sub-link to be tested. Accordingly, a link call test result can be generated based on the traffic test results of each sub-link to be tested. The link service processing result of any sub-link to be tested can refer to the response of any sub-link to be tested after processing each allocated test traffic. The traffic test result of any sub-link to be tested can be used to indicate the matching status between the link service processing result of any sub-link to be tested and the corresponding expected processing result.

[0190] In the above embodiments, by determining the first allocation indication information corresponding to the multiple sub-links to be tested based on the sub-link weight information corresponding to the multiple sub-links to be tested, and testing the multiple sub-links to be tested based on the first allocation indication information and the service link diagram, the link call test results can be obtained. This can improve the accuracy of traffic testing of the multiple sub-links to be tested, make the link traffic test closer to and simulate the real traffic situation, improve the efficiency of link traffic testing, and thus improve the accuracy and efficiency of application testing.

[0191] S209: Obtain the service test code corresponding to multiple services to be tested.

[0192] In a specific embodiment, a preset test code corresponding to each service to be tested can be obtained from a preset memory based on the service identifier information corresponding to each service to be tested, and the preset test code corresponding to each service to be tested can be used as the service test code corresponding to each service to be tested.

[0193] In one specific embodiment, the preset test code corresponding to each service to be tested stored in the preset memory can be generated and stored in advance by the application developer.

[0194] In a specific embodiment, for any preset test code corresponding to a service to be tested, the application developer can select at least one alternative test type from a variety of alternative test types as needed, and perform code combination operations on the alternative test codes corresponding to each of the above at least one alternative test type to obtain the preset test code corresponding to any service to be tested.

[0195] S211: Based on the service test code, perform service execution tests on each of the multiple services to be tested, and obtain the service execution test results for each service to be tested.

[0196] In a specific embodiment, the service execution test result corresponding to any service under test can be used to indicate whether the service execution result of any service under test meets the target execution result. Here, the service execution result of any service under test can refer to the processing result obtained by the service under test from executing the business service operation corresponding to the service test code. The target execution result of any service under test can refer to the expected result obtained by executing any service under test.

[0197] In one specific embodiment, the service execution test result for any service under test may include a first execution test result or a second execution test result. The first execution test result can be used to indicate that the service execution result of the corresponding service under test does not meet the target execution result. The second execution test result can be used to indicate that the service execution result of the corresponding service under test meets the target execution result.

[0198] In one specific embodiment, the multiple services to be tested may include services to be tested corresponding to business service types and services to be tested corresponding to supporting service types. Specifically, the business service type may be a business service related to a specific business of the target application. For example, the application service corresponding to the supporting service type may include a database service.

[0199] In one specific embodiment, the above method may further include:

[0200] If, in the service execution test results, the service execution test result corresponding to the first service to be tested is the first execution test result, and the service execution test result corresponding to the second service to be tested is the first execution test result, then based on the service test code corresponding to the second service to be tested, the service execution test is performed on the backup application service of the second service to be tested, and the backup execution test result corresponding to the backup application service is obtained.

[0201] If the standby test results indicate that the standby application service is in normal operation, the second service to be tested will be switched to the standby application service.

[0202] Based on the service test code corresponding to the first service to be tested, perform service execution tests on the first service to be tested and obtain the retry execution test results corresponding to the first service to be tested.

[0203] Based on the test retry results, determine the service running status corresponding to the first service to be tested.

[0204] In a specific embodiment, the first service to be tested can be a service corresponding to a business service type. The second service to be tested can be a service corresponding to a supporting service type. The first and second services to be tested can be linked through a call chain. It is understood that the node corresponding to the first service to be tested and the node corresponding to the second service to be tested are connected by an edge.

[0205] In one specific embodiment, the backup application service of the second service to be tested may be a backup service that performs the same business operations as the second service to be tested described above.

[0206] In one specific embodiment, the standby execution test result can be used to indicate whether the service execution result of the standby application service of the second service to be tested meets the target execution result.

[0207] In a specific embodiment, the retry execution test result can refer to whether the service execution result of the first service to be tested meets the target execution result when the second service to be tested is switched to the backup application service.

[0208] In one specific embodiment, when the second service to be tested is switched to the backup application service, the service execution test of the first service to be tested is performed based on the service test code corresponding to the first service to be tested, and the retry execution test result corresponding to the first service to be tested is obtained.

[0209] In a specific embodiment, the service operation status corresponding to the first service to be tested can characterize whether there is an anomaly in the current service processing of the first service to be tested. The service operation status corresponding to the first service to be tested can include a normal operation status or an abnormal operation status.

[0210] In a specific embodiment, determining the service running status corresponding to the first service to be tested based on the retry execution test results may include:

[0211] If the test result of the retry execution indicates that the service execution result of the first service to be tested meets the target execution result corresponding to the first service to be tested, the normal operation state shall be taken as the service operation state corresponding to the first service to be tested.

[0212] In one specific embodiment, if the retry execution test result is the second execution test result, the normal operating state is taken as the service operating state corresponding to the first service to be tested. Accordingly, the service operating state corresponding to the second service to be tested can be determined as an abnormal operating state.

[0213] In a specific embodiment, if the retry execution test result is the first execution test result, the abnormal running state can be taken as the service running state corresponding to the first service to be tested.

[0214] In a specific embodiment, application test results corresponding to the target application can be generated based on the service running status, link call test results, and service execution test results of the first service to be tested.

[0215] In the above embodiments, when both the service execution test result for the first service under test and the service execution test result for the second service under test are the first execution test result, a service execution test is performed on the backup application service of the second service under test based on the service test code corresponding to the second service under test. A backup execution test result is obtained for the backup application service. If the backup execution test result indicates that the backup application service is in normal operating condition, the second service under test is switched to the backup application service. A service execution test is then performed on the first service under test based on the service test code corresponding to the first service under test, obtaining a retry execution test result for the first service under test. Based on the retry execution test result, the service operating status of the first service under test is determined. This allows for further judgment of abnormal services when an anomaly is detected, narrowing the scope of anomalies and avoiding inaccurate test results for the two types of services due to the correlation between supporting service types and business service types. This improves the accuracy of application test results.

[0216] S213: Based on the link call test results and service execution test results, generate the application test results corresponding to the target application.

[0217] In one specific embodiment, the application test results corresponding to the target application can be used to indicate whether there are any anomalies in the service calls within the target application. Specifically, the application test results may include link call test results and service execution test results.

[0218] In one specific embodiment, the results of link call tests and service execution tests can be used as the application test results of the target application. Correspondingly, these application test results can be returned to the test terminal of the application tester, allowing the test terminal to display the application test results.

[0219] In one specific embodiment, the above method may further include:

[0220] Based on the service call relationship under each application function in the target application indicated by the application service relationship diagram, determine the multiple functional sub-links corresponding to each application function.

[0221] Based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple nodes contained in each functional sub-link, link weight analysis is performed on each functional sub-link to obtain the sub-link weight information of each functional sub-link.

[0222] The sub-link weight information of each application function is fused to obtain the function weight information corresponding to each application function.

[0223] Based on the functional weight information corresponding to each of the multiple application functions, determine the second allocation instruction information corresponding to the multiple application functions.

[0224] Based on the second allocation instruction information, the call chain corresponding to multiple application functions is tested to obtain the function call test results corresponding to multiple application functions.

[0225] Accordingly, the application test results generated based on the link call test results and service execution test results for the target application may include:

[0226] Application test results are generated based on the function call test results, link call test results, and service execution test results.

[0227] In one specific embodiment, multiple functional sub-links corresponding to any application function can be used to indicate the calling relationship between multiple services in any application function.

[0228] In a specific embodiment, a functional node corresponding to any application function can be found in the application service relationship graph; the links connected to the functional node corresponding to any application function can be used as the functional call links corresponding to any application function. Accordingly, multiple functional sub-links corresponding to any application function can be obtained by traversing the functional call links corresponding to any application function. Specifically, the process of generating multiple functional sub-links corresponding to any application function can refer to the process of generating multiple sub-links to be tested corresponding to the test scope indication information, which will not be elaborated further in this disclosure.

[0229] In one specific embodiment, the sub-link weight information of each functional sub-link can be used to characterize the importance of each functional sub-link in the target application.

[0230] In a specific embodiment, the link weight analysis process for each functional sub-link can refer to the link weight analysis process of the sub-link to be tested described above, and will not be repeated here.

[0231] In a specific embodiment, the function weight information corresponding to each application function can characterize the importance of each application function in the target application.

[0232] In one specific embodiment, the fusion process of the sub-link weight information of each of the multiple functional sub-links can refer to the aforementioned weight information fusion process, and will not be repeated here.

[0233] In one specific embodiment, the second allocation indication information can be used to indicate the allocation of test traffic for multiple application functions. The second allocation indication information may include traffic allocation ratio data corresponding to each application function. Specifically, the traffic allocation ratio data corresponding to any application function can be used to indicate the proportion of traffic required to be allocated for testing any given application function within the total test traffic for all the multiple application functions.

[0234] In a specific embodiment, the functional weight information corresponding to multiple application functions can be analyzed by weight ratio to obtain the aforementioned second allocation indication information. Specifically, the functional weight information corresponding to multiple application functions can be fused to obtain second weight fusion data; the functional weight information corresponding to any application function can be divided by the aforementioned second weight fusion data to obtain the traffic allocation ratio data corresponding to any application function. The second weight fusion data can be used to represent the sum of the weights of the functional weight information corresponding to multiple application functions.

[0235] In one specific embodiment, the function call test results can be used to indicate whether there are any abnormalities in the service chain call process of each application function in the target application.

[0236] In a specific embodiment, the allocated traffic quantity for each application function can be determined based on the second allocation instruction information and the preset test traffic quantity. Based on the allocated traffic quantity for each application function, a corresponding amount of test traffic can be allocated to the call chain corresponding to each application function, and the link service processing result of each application function's call chain for the allocated traffic can be obtained. The link service processing result of each application function's call chain for the allocated traffic can be matched with the corresponding expected processing result to obtain the traffic test result for each application function. Accordingly, a function call test result can be generated based on the traffic test results of each application function. The link service processing result of any application function can refer to the response of the call chain of any application function after processing each allocated test traffic. The traffic test result of any application function can be used to indicate the matching status of the link service processing result of any application function with the corresponding expected processing result.

[0237] In a specific embodiment, the function call test results, link call test results, and service execution test results can be used as the application test results mentioned above.

[0238] In the above embodiments, by combining the service call relationships under each application function in the target application corresponding to multiple application functions indicated by the application service relationship graph, multiple functional sub-links corresponding to each application function are determined. Based on the edge weight information or node weight information corresponding to multiple edges or multiple nodes contained in each functional sub-link, link weight analysis is performed on each functional sub-link to obtain the sub-link weight information of each functional sub-link. The sub-link weight information of each of the multiple functional sub-links corresponding to each application function is fused to obtain the functional weight information corresponding to each application function. This can realize the functional weight analysis of multiple application functions in the target application. Then, combined with the functional weight information corresponding to each of the multiple application functions, the second allocation indication information corresponding to the multiple application functions is determined. Based on the second allocation indication information, the call links corresponding to the multiple application functions are tested to obtain the functional call test results corresponding to the multiple application functions. This can realize accurate testing of service calls of multiple application functions in the target application, thereby improving the diversity, accuracy and efficiency of application testing.

[0239] In one specific embodiment, the above method may further include:

[0240] Perform network link connectivity tests on multiple sub-links to be tested, and obtain the link connectivity test results;

[0241] Accordingly, the application test results generated based on the link call test results and service execution test results for the target application may include:

[0242] The results of link call tests, service execution tests, and link connectivity tests are attached to the service link graph to obtain the application test results.

[0243] In one specific embodiment, the link connectivity test result can be used to indicate the network connectivity status of multiple sub-links under test. The link connectivity test result may include data reception indication information for at least one data transmission port corresponding to any of the sub-links under test. Each of the at least one data transmission port corresponding to any of the sub-links under test can be used to implement data transmission within that sub-link. The data reception indication information for any data transmission port can be used to indicate the reception status of data packets sent by the data transmission node in the corresponding link.

[0244] In one specific embodiment, at least one second sub-link to be tested may include a first service node corresponding to a third service to be tested and a second service node corresponding to a fourth service to be tested. The fourth service to be tested may be a service to be invoked by the third service to be tested. The third service to be tested and the fourth service to be tested are linked based on at least one data transmission port. It is understood that, for the aforementioned third service to be tested and the fourth service to be tested, the third service node may be a data sending node, and the fourth service node may be a data receiving node.

[0245] In one specific embodiment, a preset data packet can be sent to the second service node based on the first service node and each data transmission port; data reception indication information corresponding to each data transmission port can be obtained; wherein, the data reception indication information corresponding to each data transmission port can be used to indicate the reception status of the preset data packet by the second service node based on each data transmission port. Accordingly, the above-mentioned link connectivity test result can be generated based on the data reception indication information corresponding to at least one data transmission port.

[0246] In the above embodiments, by performing network link connectivity tests on multiple sub-links to be tested and obtaining the link connectivity test results, the network link connectivity test of the sub-links in the target application can be realized. Then, the link call test results, service execution test results, and link connectivity test results are mounted to the service link graph to obtain the application test results. This can improve the readability of the application test results of the target application, making it easier for the application tester to more quickly and accurately locate abnormal links or nodes in the target application, thereby improving the optimization efficiency of the application tester for the target application with anomalies.

[0247] In the above embodiments, upon receiving an application test instruction for a target application, the system obtains the application service relationship graph corresponding to the target application and the test scope indication information corresponding to the application test instruction. The application service relationship graph is constructed using multiple application services corresponding to the target application as nodes and the call relationships between application service nodes as edges. This allows for the acquisition of the application service relationship graph describing the service call relationships within the target application, as well as the acquisition of the corresponding test scope indication information indicating the required test scope. Combined with the application service relationship graph, multiple services to be tested corresponding to the test scope indication information are determined from the multiple application services, and the service link graphs of each of the multiple sub-links to be tested corresponding to the test scope indication information are determined. This enables the rapid determination of the services to be tested and the sub-links to be tested. Furthermore, by combining the edge weight information corresponding to the multiple edges or the node weight information corresponding to the multiple sub-link nodes contained in each sub-link to be tested, the link weights of each sub-link to be tested are adjusted. The process involves reanalysis to obtain the sub-link weight information for each sub-link under test, enabling link weight analysis of the sub-links under test. Then, combining the sub-link weight information and service link graph of multiple sub-links under test, traffic allocation tests are performed on these sub-links to obtain link call test results. This improves the accuracy of traffic testing for multiple sub-links under test, allowing the link traffic test to more closely resemble and simulate real traffic conditions. Next, service test code is obtained for multiple services under test. Based on this service test code, service execution tests are performed on each of the multiple services under test, obtaining service execution test results for each service under test. This enables testing of the service execution of the services under test within the target application. Based on the link call test results and service execution test results, application test results for the target application are generated. This allows for testing of services and call links within the target application, thereby improving the efficiency and accuracy of application testing.

[0248] Figure 4 This is a block diagram illustrating an application testing apparatus according to an exemplary embodiment. Specifically, as shown below... Figure 4 As shown, the device may include:

[0249] The first information acquisition module 410 can be used to acquire, upon receiving an application test instruction for the target application, the application service relationship diagram corresponding to the target application and the test scope indication information corresponding to the application test instruction; the application service relationship diagram is constructed with multiple application services corresponding to the target application as nodes and the call relationship between application service nodes as edges;

[0250] The execution module 420 can be used to determine, based on the application service relationship diagram, multiple services to be tested corresponding to the test scope indication information from multiple application services, and to determine the service link diagram of each of the multiple sub-links to be tested corresponding to the test scope indication information.

[0251] The first weight analysis module 430 can be used to perform link weight analysis on each sub-link under test based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, and obtain the sub-link weight information corresponding to each sub-link under test; the sub-link weight information corresponding to each sub-link under test represents the importance of each sub-link under test in multiple sub-links under test.

[0252] The traffic allocation test module 440 can be used to perform traffic allocation tests on multiple sub-links under test based on the sub-link weight information and service link diagram corresponding to each of the multiple sub-links under test, and obtain the link call test results.

[0253] The code acquisition module 450 can be used to acquire the service test code corresponding to multiple services to be tested.

[0254] The service execution test module 460 can be used to perform service execution tests on each of multiple services under test based on service test code, and obtain the service execution test results for each service under test.

[0255] The test result generation module 470 can be used to generate application test results corresponding to the target application based on the link call test results and service execution test results.

[0256] In one specific embodiment, the above-described apparatus may further include:

[0257] The second weight analysis module can be used to perform edge weight analysis on each edge in the target sub-link under test based on the associated node information of each edge in the multiple edges contained in the target sub-link under test indicated by the application service relationship graph, and obtain the edge weight information corresponding to each edge; the target sub-link under test is any one of the multiple sub-links under test, and the edge weight information corresponding to each edge represents the importance of each edge in the multiple sub-links under test.

[0258] Accordingly, the first weight analysis module 430 mentioned above may include:

[0259] The first fusion unit can be used to fuse the edge weight information corresponding to multiple edges in the target sub-link under test to obtain the sub-link weight information corresponding to the target sub-link under test.

[0260] In one specific embodiment, the second weight analysis module described above may include:

[0261] The first node acquisition unit can be used to determine multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are the nodes in the target sub-link to be tested that are connected to the target edge.

[0262] The node weight analysis unit can be used to perform node weight analysis on each of multiple adjacent nodes based on the associated node information of the target edge indicated by the application service relationship graph, and obtain the first node weight information corresponding to each adjacent node.

[0263] The second fusion unit can be used to fuse the weight information of the first node corresponding to each of multiple adjacent nodes to obtain the edge weight information corresponding to the target edge.

[0264] In one specific embodiment, the node weight analysis unit described above may include:

[0265] The first duration acquisition unit can be used to obtain the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node;

[0266] The third fusion unit can be used to fuse the preset timeout duration, the number of parent nodes, and the number of child nodes corresponding to each adjacent node to obtain the first node weight information corresponding to each adjacent node.

[0267] In one specific embodiment, the second weight analysis module described above may include:

[0268] The second node acquisition unit can be used to determine multiple adjacent nodes corresponding to the target edge from the target sub-link to be tested; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are nodes in the target sub-link to be tested that are connected to the target edge.

[0269] The second duration acquisition unit can be used to obtain the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node;

[0270] The first indicator acquisition unit can be used to determine the first indicator data corresponding to the target edge based on the preset timeout duration of each of multiple adjacent nodes; the first indicator data is used to characterize the importance of the target edge in multiple sub-links to be tested from the dimension of timeout duration.

[0271] The second indicator acquisition unit can be used to determine the second indicator data corresponding to the target edge based on the number of parent nodes corresponding to each of multiple adjacent nodes; the second indicator data is used to characterize the importance of the target edge in multiple sub-links to be tested from the dimension of the number of parent nodes.

[0272] The third indicator acquisition unit can be used to determine the third indicator data corresponding to the target edge based on the number of child nodes corresponding to each of multiple adjacent nodes; the third indicator data is used to characterize the importance of the target edge in multiple sub-links to be tested from the dimension of the number of child nodes.

[0273] The fourth fusion unit can be used to fuse the first indicator data, the second indicator data, and the third indicator data to obtain the edge weight information corresponding to the target edge.

[0274] In one specific embodiment, the above-described apparatus may further include:

[0275] The third weight analysis module can be used to perform node weight analysis on each sub-link node based on the associated node information of each sub-link node in the target sub-link to be tested indicated by the application service relationship graph, and obtain the second node weight information corresponding to each sub-link node; the target sub-link to be tested is any one of the multiple sub-links to be tested;

[0276] Accordingly, the first weight analysis module 430 mentioned above may include:

[0277] The fifth fusion unit can be used to fuse the weight information of multiple second nodes corresponding to the target sub-link under test to obtain the sub-link weight information corresponding to the target sub-link under test.

[0278] In one specific embodiment, the traffic allocation test module 440 described above may include:

[0279] The first instruction generation unit can be used to determine the first allocation instruction information corresponding to the multiple sub-links to be tested based on the sub-link weight information corresponding to the multiple sub-links to be tested; the first allocation instruction information is used to indicate the allocation of test traffic for the multiple sub-links to be tested.

[0280] The allocation test unit can be used to test multiple sub-links to be tested based on the first allocation instruction information and service link diagram, and obtain the link call test results.

[0281] In one specific embodiment, the above-described apparatus may further include:

[0282] The sub-link acquisition module can be used to determine multiple functional sub-links corresponding to each application function based on the service call relationship under each application function in the multiple application functions corresponding to the target application indicated by the application service relationship diagram.

[0283] The fourth weight analysis module can be used to perform link weight analysis on each functional sub-link based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple nodes contained in each functional sub-link, and obtain the sub-link weight information of each functional sub-link.

[0284] The fusion module can be used to fuse the sub-link weight information of multiple functional sub-links corresponding to each application function to obtain the functional weight information corresponding to each application function; the functional weight information corresponding to each application function represents the importance of each application function in the target application;

[0285] The second instruction generation module can be used to determine the second allocation instruction information corresponding to multiple application functions based on the function weight information corresponding to each of the multiple application functions; the second allocation instruction information is used to indicate the allocation of test traffic for multiple application functions.

[0286] The call chain testing module can be used to test the call chain corresponding to multiple application functions based on the second allocation instruction information, and obtain the function call test results corresponding to multiple application functions.

[0287] Accordingly, the test result generation module 470 mentioned above may include:

[0288] The first result generation unit can be used to generate application test results based on function call test results, link call test results, and service execution test results.

[0289] In one specific embodiment, the above-described apparatus may further include:

[0290] The link connectivity test module can be used to perform network link connectivity tests on multiple sub-links under test and obtain the link connectivity test results; the link connectivity test results are used to indicate the network connectivity status of multiple sub-links under test.

[0291] Accordingly, the test result generation module 470 mentioned above may include:

[0292] The second result generation unit can be used to attach the link call test results, service execution test results, and link connectivity test results to the service link graph to obtain application test results.

[0293] In one specific embodiment, the above-described apparatus may further include:

[0294] The backup service testing module can be used to perform service execution tests on the backup application service of the second service under test, based on the service test code corresponding to the second service under test, when both the first and second service under test have the same service execution test result. The first service under test is a service corresponding to a business service type, and the second service under test is a service corresponding to a support service type. The first and second services are linked through a call chain, and the first execution test result indicates that the service execution result of the corresponding service under test does not meet the target execution result.

[0295] The service switching module can be used to switch the second service to be tested to the backup application service when the backup execution test results indicate that the backup application service is in normal operation.

[0296] The service test retry module can be used to perform service execution tests on the first service to be tested based on the service test code corresponding to the first service to be tested, and obtain the retry execution test results corresponding to the first service to be tested.

[0297] The runtime status determination module can be used to determine the runtime status of the first service to be tested based on the results of retry execution tests.

[0298] In one specific embodiment, the above-mentioned operating status determination module may include:

[0299] The running status determination unit can be used to take the normal operation status as the service running status corresponding to the first service under test when the test result of the retry execution indicates that the service execution result of the first service under test meets the target execution result corresponding to the first service under test.

[0300] In one specific embodiment, the above-described apparatus may further include:

[0301] The historical version acquisition module can be used to obtain the historical version information of a target application based on the current version information;

[0302] The second information acquisition module can be used to obtain the historical service relationship diagram corresponding to the target application based on historical version information;

[0303] The comparison processing module can be used to compare the historical service relationship diagram and the application service relationship diagram to obtain relationship diagram difference information; the relationship diagram difference information is used to indicate the parts where there are differences between the historical service relationship diagram and the application service relationship diagram.

[0304] The indication information generation module can be used to determine test range indication information based on the relationship diagram difference information.

[0305] Regarding the apparatus in the above embodiments, the specific manner in which each module and unit performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0306] Figure 5 This is a block diagram illustrating an electronic device for implementing call chain testing of a target application according to an exemplary embodiment. The electronic device may be a server, and its internal structure diagram may be as follows: Figure 5 As shown, this electronic device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements an application testing method.

[0307] Figure 6 This is a block diagram illustrating another electronic device for implementing call chain testing of a target application according to an exemplary embodiment. The electronic device may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown, the electronic device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements an application testing method. The display screen can be a liquid crystal display (LCD) or an e-ink display. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the device's casing, or an external keyboard, touchpad, or mouse.

[0308] Those skilled in the art will understand that Figure 5 or Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the electronic device to which the present disclosure is applied. A specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0309] In an exemplary embodiment, an electronic device is also provided, including: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the application testing method as described in the embodiments of this disclosure.

[0310] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein when the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the application testing method of the present disclosure embodiments.

[0311] In an exemplary embodiment, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to perform the application testing method of the present disclosure embodiments.

[0312] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0313] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0314] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0315] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0316] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. An application testing method, characterized in that, The method includes: Upon receiving an application test instruction for a target application, the system obtains the application service relationship graph corresponding to the target application and the test scope indication information corresponding to the application test instruction; the application service relationship graph is constructed with multiple application services corresponding to the target application as nodes and the call relationships between application service nodes as edges. Based on the application service relationship graph, multiple services to be tested corresponding to the test scope indication information are determined from the multiple application services, and the service link graphs of each of the multiple sub-links to be tested corresponding to the test scope indication information are determined. Based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link to be tested, a link weight analysis is performed on each sub-link to be tested to obtain the sub-link weight information corresponding to each sub-link to be tested; the sub-link weight information corresponding to each sub-link to be tested characterizes the importance of each sub-link to be tested in the multiple sub-links to be tested. Based on the sub-link weight information corresponding to each of the multiple sub-links to be tested and the service link diagram, traffic allocation test is performed on the multiple sub-links to be tested to obtain the link call test results. Obtain the service test code corresponding to the multiple services to be tested; Based on the service test code, service execution tests are performed on each of the plurality of services to be tested to obtain the service execution test results corresponding to each service to be tested. Based on the link call test results and the service execution test results, the application test results corresponding to the target application are generated.

2. The method according to claim 1, characterized in that, The method further includes: Based on the associated node information of each edge in the multiple edges of the target sub-link to be tested indicated by the application service relationship graph, edge weight analysis is performed on each edge in the target sub-link to be tested to obtain the edge weight information corresponding to each edge; the target sub-link to be tested is any one of the multiple sub-links to be tested, and the edge weight information corresponding to each edge represents the importance of each edge in the multiple sub-links to be tested. The step involves performing link weight analysis on each sub-link under test based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test, including: The edge weight information corresponding to each of the multiple edges in the target sub-link to be tested is fused to obtain the sub-link weight information corresponding to the target sub-link to be tested.

3. The method according to claim 2, characterized in that, The method involves analyzing the associated node information of each edge in the target sub-link under test, based on the application service relationship graph, to obtain the edge weight information corresponding to each edge, including: From the target sub-link to be tested, determine multiple adjacent nodes corresponding to the target edge; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are nodes in the target sub-link to be tested that are connected to the target edge. Based on the associated node information of the target edge indicated by the application service relationship graph, a node weight analysis is performed on each of the multiple adjacent nodes to obtain the first node weight information corresponding to each adjacent node. The weight information of the first node corresponding to each of the multiple adjacent nodes is fused to obtain the edge weight information corresponding to the target edge.

4. The method according to claim 3, characterized in that, The associated node information of the target edge includes the number of parent nodes and the number of child nodes of the adjacent nodes of the target edge; based on the associated node information of the target edge indicated by the application service relationship graph, node weight analysis is performed on each of the multiple adjacent nodes to obtain the first node weight information corresponding to each adjacent node, including: Obtain the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node; The preset timeout duration, the number of parent nodes, and the number of child nodes corresponding to each adjacent node are fused to obtain the first node weight information corresponding to each adjacent node.

5. The method according to claim 2, characterized in that, The associated node information of each edge includes the number of parent nodes of each edge's neighboring nodes and the number of child nodes of each edge's neighboring nodes; based on the associated node information of each edge in the target sub-link under test indicated by the application service relationship graph, edge weight analysis is performed on each edge in the target sub-link under test to obtain the edge weight information corresponding to each edge, including: From the target sub-link to be tested, determine multiple adjacent nodes corresponding to the target edge; the target edge is any one of the multiple edges corresponding to the target sub-link to be tested; the multiple adjacent nodes are nodes in the target sub-link to be tested that are connected to the target edge. Obtain the preset timeout duration corresponding to each adjacent node from the node configuration information of each adjacent node; Based on the preset timeout duration corresponding to each of the multiple adjacent nodes, the first indicator data corresponding to the target edge is determined; the first indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of timeout duration. Based on the number of parent nodes corresponding to each of the multiple adjacent nodes, the second indicator data corresponding to the target edge is determined; the second indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of the number of parent nodes. Based on the number of child nodes corresponding to each of the multiple adjacent nodes, a third indicator data corresponding to the target edge is determined; the third indicator data is used to characterize the importance of the target edge in the multiple sub-links to be tested from the dimension of the number of child nodes. The first indicator data, the second indicator data, and the third indicator data are fused to obtain the edge weight information corresponding to the target edge.

6. The method according to claim 1, characterized in that, The method further includes: Based on the associated node information of each sub-link node among the multiple sub-link nodes included in the target sub-link to be tested indicated by the application service relationship graph, a node weight analysis is performed on each sub-link node to obtain the second node weight information corresponding to each sub-link node; the target sub-link to be tested is any one of the multiple sub-links to be tested; The step involves performing link weight analysis on each sub-link under test based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test, including: The weight information of multiple second nodes corresponding to the target sub-link to be tested is fused to obtain the sub-link weight information corresponding to the target sub-link to be tested.

7. The method according to claim 1, characterized in that, Based on the sub-link weight information corresponding to each of the multiple sub-links to be tested and the service link graph, traffic allocation tests are performed on the multiple sub-links to be tested to obtain link call test results, including: Based on the sub-link weight information corresponding to the plurality of sub-links to be tested, first allocation indication information corresponding to the plurality of sub-links to be tested is determined; the first allocation indication information is used to indicate the allocation of test traffic for the plurality of sub-links to be tested. Based on the first allocation instruction information and the service link diagram, the multiple sub-links to be tested are tested to obtain the link call test results.

8. The method according to claim 1, characterized in that, The method further includes: Based on the service call relationship under each application function of the target application indicated by the application service relationship diagram, determine the multiple functional sub-links corresponding to each application function. Based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple nodes contained in each functional sub-link, link weight analysis is performed on each functional sub-link to obtain the sub-link weight information of each functional sub-link. The sub-link weight information of each of the multiple functional sub-links corresponding to each application function is fused to obtain the functional weight information corresponding to each application function; the functional weight information corresponding to each application function represents the importance of each application function in the target application. Based on the functional weight information corresponding to each of the multiple application functions, second allocation indication information corresponding to the multiple application functions is determined; the second allocation indication information is used to indicate the allocation of test traffic for the multiple application functions. Based on the second allocation instruction information, the call chain corresponding to the multiple application functions is tested to obtain the function call test results corresponding to the multiple application functions. The step of generating application test results corresponding to the target application based on the link call test results and the service execution test results includes: The application test results are generated based on the function call test results, the link call test results, and the service execution test results.

9. The method according to claim 1, characterized in that, The method further includes: Network connectivity tests are performed on the plurality of sub-links to be tested to obtain the link connectivity test results; the link connectivity test results are used to indicate the network connectivity status of the plurality of sub-links to be tested. The step of generating application test results corresponding to the target application based on the link call test results and the service execution test results includes: The link call test results, the service execution test results, and the link connectivity test results are attached to the service link graph to obtain the application test results.

10. The method according to claim 1, characterized in that, The plurality of services to be tested includes services to be tested corresponding to business service types and services to be tested corresponding to support service types; the method further includes: If, in the service execution test results, the service execution test result corresponding to the first service under test is the first execution test result, and the service execution test result corresponding to the second service under test is the first execution test result, then based on the service test code corresponding to the second service under test, a service execution test is performed on the backup application service of the second service under test to obtain the backup execution test result corresponding to the backup application service; the first service under test is the service under test corresponding to the business service type, the second service under test is the service under test corresponding to the support service type, the first service under test and the second service under test are linked through a call chain, and the first execution test result is used to indicate that the service execution result of the corresponding service under test does not meet the target execution result; If the backup execution test result indicates that the backup application service is in normal operating condition, the second service to be tested will be switched to the backup application service; Based on the service test code corresponding to the first service to be tested, a service execution test is performed on the first service to be tested to obtain the retry execution test result corresponding to the first service to be tested. Based on the results of the retry test, the service running status corresponding to the first service to be tested is determined.

11. The method according to claim 10, characterized in that, The step of determining the service running status corresponding to the first service under test based on the retry test results includes: If the retry test result indicates that the service execution result of the first service under test meets the target execution result corresponding to the first service under test, the normal operation state shall be taken as the service operation state corresponding to the first service under test.

12. The method according to any one of claims 1-11, characterized in that, The application testing instructions include the current version information of the target application; the test scope indication information is obtained in the following ways: Based on the current version information, obtain the historical version information corresponding to the target application; Based on the historical version information, obtain the historical service relationship diagram corresponding to the target application; The historical service relationship diagram and the application service relationship diagram are compared to obtain relationship diagram difference information; the relationship diagram difference information is used to indicate the parts where there are differences between the historical service relationship diagram and the application service relationship diagram. Based on the difference information in the relationship diagram, the test range indication information is determined.

13. An application testing device, characterized in that, The device includes: The first information acquisition module is used to acquire, upon receiving an application test instruction for a target application, an application service relationship graph corresponding to the target application and test scope indication information corresponding to the application test instruction; the application service relationship graph is constructed with multiple application services corresponding to the target application as nodes and the call relationship between application service nodes as edges; The execution module is used to determine, based on the application service relationship diagram, multiple services to be tested corresponding to the test scope indication information from the multiple application services, and to determine the service link diagram of each of the multiple sub-links to be tested corresponding to the test scope indication information. The first weight analysis module is used to perform link weight analysis on each sub-link under test based on the edge weight information corresponding to multiple edges or the node weight information corresponding to multiple sub-link nodes contained in each sub-link under test, to obtain the sub-link weight information corresponding to each sub-link under test; the sub-link weight information corresponding to each sub-link under test represents the importance of each sub-link under test in the multiple sub-links under test. The traffic allocation test module is used to perform traffic allocation tests on the multiple sub-links to be tested based on the sub-link weight information corresponding to each of the multiple sub-links to be tested and the service link diagram, and to obtain the link call test results. The code acquisition module is used to acquire the service test code corresponding to the multiple services to be tested. The service execution test module is used to perform service execution tests on each of the plurality of services to be tested based on the service test code, and obtain the service execution test results corresponding to each service to be tested; The test result generation module is used to generate application test results corresponding to the target application based on the link call test results and the service execution test results.

14. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the application testing method according to any one of claims 1 to 12.

15. A non-volatile computer-readable storage medium storing computer program instructions thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the application testing method according to any one of claims 1 to 12.

Images