CN116107791A

CN116107791A - Test environment fault node repairing method and device

Info

Publication number: CN116107791A
Application number: CN202310187258.6A
Authority: CN
Inventors: 侯文龙; 刘孟昕; 任瑜平; 杨洋
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-02-13
Filing date: 2023-02-13
Publication date: 2023-05-12

Abstract

The disclosure provides a test environment fault node repairing method, relates to the technical field of artificial intelligence, can be used in the field of software testing, and can be applied to the technical field of finance. The method comprises the following steps: responding to a fault repairing instruction, and acquiring fault node information; determining an access request link string of each automation test script according to the access request message and the test environment node information; calculating the recovery priority weights of the fault nodes in different periods according to the fault node information and the access request link strings; and repairing the fault node according to the recovery priority weight of the fault node, wherein the access request message is generated during the running of the automatic test script, and comprises node IP information and access request time. The present disclosure also provides a test environment fault node repairing apparatus, device, storage medium and program product.

Description

Test environment fault node repairing method and device

Technical Field

The present disclosure relates to the field of artificial intelligence technology, and in particular, to the field of software testing technology, and more particularly, to a method, apparatus, device, storage medium, and program product for repairing a failed node in a testing environment.

Background

In the process of software development, the operation and maintenance guarantee of the test environment is a very important work, and all version verification works depend on the test environment with high stability and good testability. However, when the enterprise scale is large and the number of tested systems is large, the operation team of the testing environment cannot have enough human resources to process the equipment with faults at the same time, when the testing environment is recovered, the environment with the largest influence on the testing efficiency at present cannot be effectively screened out for optimization recovery due to lack of supporting tools, and under the conditions of multiple testing tasks and short period, the testing progress and the testing efficiency of the version are greatly influenced.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

In view of the foregoing, the present disclosure provides a test environment fault node repairing method, apparatus, device, storage medium, and program product that improve test efficiency.

According to a first aspect of the present disclosure, there is provided a test environment fault node repair method, the method comprising:

Responding to a fault repairing instruction, and acquiring fault node information;

determining an access request link string of each automation test script according to the access request message and the test environment node information;

calculating the recovery priority weights of the fault nodes in different periods according to the fault node information and the access request link strings; and

repairing the fault node according to the recovery priority weight of the fault node,

the access request message is generated during the running of the automatic test script, and comprises node IP information and access request time.

According to an embodiment of the disclosure, the test environment node information includes a test environment node IP and a node corresponding service name, and determining an access request link string of each automation test script according to the access request message and the test environment node information includes:

determining an access node IP path of each automated test script according to the access request time and the script name; and

and determining an access request link string of each automation test script according to the IP path of the access node and the service name corresponding to the node.

According to an embodiment of the present disclosure, the calculating the recovery priority weights of the failed nodes in different periods according to the failed node information and the access request link string includes:

Determining the same group of node fault statistical information according to the test environment node information and the fault node information;

and determining the recovery priority weights of the fault nodes in different periods according to the fault statistical information of the same group of nodes and the access request link strings.

According to an embodiment of the disclosure, the determining the recovery priority weights of the failed nodes in different periods according to the same group of node failure statistics and the access request link string includes:

calculating first recovery priority weights of single fault nodes in different periods according to the fault statistical information of the same group of nodes;

calculating a second recovery priority weight related to the service combination of the fault node according to the access request link string; and

and determining the recovery priority weights of the fault nodes in different periods according to the first recovery priority weights and the second recovery priority weights.

According to an embodiment of the present disclosure, the peer group node failure statistics include a failure node IP, a node name, a peer group node total number, and a peer group node failure number, and calculating the first restoration priority weight of the single failure node according to the peer group node failure statistics includes:

determining the failure rate of the failure node according to the failure number of the nodes in the same group, the node names and the total number of the nodes in the same group;

Determining the number of automation scripts influenced by the fault nodes in different periods;

and determining first recovery priority weights in different periods according to the failure rate of the failure node and the quantity of the automatic scripts.

According to an embodiment of the disclosure, the calculating the second recovery priority weight of the failed node with respect to the service combination according to the access request link string includes:

determining that the fault node relates to service combination statistical information based on the knowledge graph;

determining service node combinations with failure node failure rates greater than a preset threshold;

calculating priority weights of the fault nodes in the service node combination; and

and determining a second recovery priority weight of the fault node related to the service combination according to the priority weight.

According to an embodiment of the present disclosure, the fault node information includes a fault node IP, a fault time, and a fault discovery manner.

A second aspect of the present disclosure provides a test environment fault node repair apparatus, the apparatus comprising:

the acquisition module is used for responding to the fault repairing instruction and acquiring fault node information;

the access request link string determining module is used for determining an access request link string of each automation test script according to the access request message and the test environment node information;

The recovery priority weight determining module is used for calculating the recovery priority weights of the fault nodes in different periods according to the fault node information and the access request link strings; and

a fault repairing module for repairing the fault node according to the recovery priority weight of the fault node,

According to an embodiment of the present disclosure, the test environment node information includes a test environment node IP and a node corresponding service name, and the access request link string determining module includes: a first determination sub-module and a second determination sub-module.

The first determining submodule is used for determining an access node IP path of each automated test script according to the access request time and the script name; and

and the second determining submodule is used for determining the access request link string of each automation test script according to the IP path of the access node and the service name corresponding to the node.

According to an embodiment of the present disclosure, the restoration priority weight determination module includes a third determination sub-module and a fourth determination sub-module.

The third determining submodule is used for determining node fault statistical information in the same group according to the test environment node information and the fault node information;

and a fourth determining sub-module, configured to determine recovery priority weights of failed nodes in different periods according to the same group of node failure statistics information and the access request link string.

According to an embodiment of the present disclosure, the fourth determination submodule includes a first calculation unit, a second calculation unit, and a determination unit.

A first calculation unit, configured to calculate a first recovery priority weight of a single failure node in different periods according to the failure statistics information of the same group of nodes;

a second calculation unit for calculating a second recovery priority weight of the failed node related to the service combination according to the access request link string; and

and the determining unit is used for determining the recovery priority weights of the fault nodes in different periods according to the first recovery priority weights and the second recovery priority weights.

According to an embodiment of the present disclosure, the peer group node fault statistics include a fault node IP, a node name, a peer group node total number, and a peer group node fault number, and the first calculation unit includes a first determination subunit, a second determination subunit, and a third determination subunit.

A first determining subunit, configured to determine a failure rate of a failed node according to the same group node failure number, the node name, and the total number of the same group nodes;

the second determining subunit is used for determining the quantity of the automation scripts influenced by the fault nodes in different periods;

and the third determination subunit is used for determining the first recovery priority weights in different periods according to the failure rate of the failure node and the quantity of the automation scripts.

According to an embodiment of the present disclosure, the second calculation unit includes: a fourth determination subunit, a fifth determination subunit, a calculation subunit, and a sixth determination subunit.

A fourth determining subunit, configured to determine, based on the knowledge graph, that the fault node relates to service combination statistics;

a fifth determining subunit, configured to determine a service node combination with a failure node failure rate greater than a preset threshold;

a calculating subunit, configured to calculate a priority weight of the failure node in the service node combination; and

a sixth determining subunit, configured to determine, according to the priority weights, a second recovery priority weight related to the service combination for the failed node.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the test environment fault node repair method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described test environment fault node repair method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described test environment fault node repair method.

According to the test environment fault node repairing method provided by the embodiment of the disclosure, the access request link string is determined by collecting the access request forwarding messages generated during the running of the automatic test script. The influence degree of the fault node in the current test environment is evaluated according to the access request link string and the fault node information, the recovery priority is automatically formed according to the influence degree, the selection of test environment maintenance personnel is facilitated, under the condition that the number and the scale of the test environment nodes are large, the resources of the test environment maintenance personnel are limited, and the automatic test script execution tasks are more, the pre-evaluation of the test environment recovery effect by the test environment maintenance personnel is facilitated, the maintenance work of the test environment nodes is unfolded according to the evaluation result, and the test environment maintenance utility is improved.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a test environment failure node repair method, apparatus, device, storage medium, and program product according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a system architecture diagram of a test environment failure node repair device provided in accordance with an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a test environment failure node repair method provided in accordance with an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a method of determining an access request link string provided in accordance with an embodiment of the present disclosure;

FIG. 5a schematically illustrates one of the flowcharts of a method for determining recovery priority weights for failed nodes in different periods provided in accordance with an embodiment of the present disclosure;

FIG. 5b schematically illustrates a second flowchart of a method for determining recovery priority weights for failed nodes in different periods provided in accordance with an embodiment of the present disclosure;

FIG. 6a schematically illustrates a flow chart of a method of determining a first recovery priority weight for a single failed node provided in accordance with an embodiment of the present disclosure;

FIG. 6b schematically illustrates a flow chart of a method of determining a second recovery priority weight for a failed node involving a combination of services provided in accordance with an embodiment of the present disclosure;

FIG. 7 schematically illustrates a block diagram of a test environment failure node repairing apparatus according to an embodiment of the present disclosure; and

fig. 8 schematically illustrates a block diagram of an electronic device adapted to implement a test environment fault node repair method according to an embodiment of the present disclosure.

Detailed Description

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

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

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Based on the technical problems described above, an embodiment of the present disclosure provides a test environment fault node repairing method, including: responding to a fault repairing instruction, and acquiring fault node information; determining an access request link string of each automation test script according to the access request message and the test environment node information; calculating the recovery priority weights of the fault nodes in different periods according to the fault node information and the access request link strings; and repairing the fault node according to the recovery priority weight of the fault node, wherein the access request message is generated during the running of the automatic test script, and comprises node IP information and access request time.

Fig. 1 schematically illustrates an application scenario diagram of a test environment failure node repairing method, apparatus, device, storage medium and program product according to an embodiment of the present disclosure. Fig. 2 schematically illustrates a system architecture diagram of a test environment fault node repair device provided in accordance with an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a test environment failure node automatic repair scenario. The network 104 is used as a medium to provide communication links between the

terminal devices

101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 via the network 104 using the

terminal devices

101, 102, 103 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the

terminal devices

101, 102, 103.

The

terminal devices

101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a test environment fault node influence analysis server, and the server performs intelligent analysis based on access link string information of an automatic test script and combines fault node information to calculate recovery priority weights of fault nodes in different periods. And the fault node with great influence on the service of the test environment is repaired preferentially, so that the test efficiency is improved.

It should be noted that, the test environment fault node repairing method provided by the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the test environment fault node repairing apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 105. The test environment failure node repairing method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the test environment fault node repairing apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

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

It should be noted that, the method and the device for repairing the fault node of the test environment determined by the embodiment of the present disclosure may be used in the technical field of automated testing, may also be used in the technical field of finance, and may also be used in any field other than the financial field.

As shown in fig. 2, the test environment fault node repairing device provided by the embodiment of the disclosure includes an access request bypass forwarding module, a test message centralized collection module, a test environment information registration module, a test environment node state monitoring module, an automatic test task scheduling module and a test influence analysis module, wherein the automatic test task scheduling module is used for scheduling normal automatic execution tasks and initialized registered automatic execution tasks; the access request bypass forwarding module is deployed on each server equipment node and is mainly used for forwarding all access request messages received by the current node and forwarding the request messages to the test message centralized gathering module; the test message collection module is used for bypassing the messages sent by the forwarding module from the access request received in the corresponding time, extracting node IP information through time sequence, and forming each automated test script test environment access request link string; the test environment information registration module is mainly used for registering the names of the service groups and the IP lists of the corresponding services and synchronizing with the configuration management system; the test environment node state monitoring module is mainly used for monitoring the states of all environment node devices, when a certain environment node is found to have a fault, the fault information of the node is recorded into the fault node monitoring registry, and when the service of the certain node in the fault node monitoring registry is found to be recovered to be normal, the node is automatically removed from the fault node monitoring registry. The test influence degree analysis module acquires all fault node lists of the current fault from the fault node monitoring module, acquires the service group name of the current IP node from the test environment information registration module, and the same group of service group IP lists to form fault statistical information of the same group of nodes, and analyzes the influence degree of the fault node so as to determine the recovery priority weight of the fault node.

The method for repairing the fault node of the test environment according to the embodiment of the present disclosure will be described in detail below with reference to the scenario described in fig. 1 and the system architecture described in fig. 2 by using fig. 3 to 6 b.

Fig. 3 schematically illustrates a flowchart of a test environment fault node repair method provided according to an embodiment of the present disclosure. As shown in fig. 3, the test environment fault node repairing method of this embodiment includes operations S210 to S240, which may be performed by a server or other computing device.

In operation S210, failure node information is acquired in response to the failure repair instruction.

In operation S220, an access request link string of each automation test script is determined according to the access request message and the test environment node information.

According to an embodiment of the present disclosure, the access request message is generated during the running of the automated test script, and the access request message includes node IP information and access request time.

In one example, in an automated test environment, different service groups are formed by different node devices to provide different services for the outside, such as an identity authentication service, a transfer service, a customer information inquiry service, an account information inquiry service, a balance inquiry service and the like, and since a plurality of nodes may be required to provide services together for successful execution of one automated test script, in order to analyze the influence degree of a fault node on the test environment, if the fault node with the largest influence degree is repaired preferentially under the premise of limited operation and maintenance resources, the influence of the fault on the test environment can be reduced to the greatest extent, and the smooth performance of a test task is ensured.

In one example, the discovery mode of the fault node may be automatically discovered by a test environment node status monitoring module, where the module is mainly configured to monitor the status of all environment node devices, record the fault information of the node into a fault node monitoring registry when a fault occurs in a certain environment node, and automatically remove the node from the fault node monitoring registry when a service of a certain node in the fault node monitoring registry is recovered to be normal; the fault node may be found by manually setting the test environment node to a fault or normal state by a test environment maintainer.

Therefore, firstly, an access request link string of each automation test script is required to be determined according to an access request message, namely, an access node IP path corresponding to each test script is determined, wherein the access request message comprises node IP information and access request time, the access request message is generated during the operation of the automation test script, for example, when a certain test script operates, an identity authentication service node and a transfer service node are required to provide services, the identity authentication service node and the transfer service node receive the corresponding access request message, and the access request link string of each automation test script is further obtained by collecting the messages through an access request bypass forwarding module deployed on each equipment node, for example, 5 nodes of the test script 1, namely, the identity authentication node, the transfer service node, a customer information query node, an account information query node and a balance query node; the test script 2 corresponds to 6 nodes of an accounting information registration node, a transfer detail query node service node, a deduction detail query node, a banking transaction query node and a balance query node. The specific process may be referred to as operation S221 and operation S222 shown in fig. 4.

In operation S230, a restoration priority weight of the failed node in different periods is calculated according to the failed node information and the access request link string.

In operation S240, the failed node is repaired according to the restoration priority weight of the failed node.

In one example, after the access request link string is acquired, acquiring all fault node lists of the current fault from the fault node monitoring module, determining fault statistics information of the same group of nodes according to the acquired fault node information and the test environment node information, and further calculating recovery priority weights of the fault nodes in different periods according to the access link request string, wherein the different periods refer to that the number of scripts executed in 30 minutes is different from the number of scripts executed in 60 minutes or 90 minutes because the test script tasks may be executed in batches, the number of test scripts influenced by the fault nodes in the different periods is also used as an influence factor of the recovery priority weights of the fault nodes, and after the recovery priority weights of all the fault nodes in the fault node lists in the different periods are determined, repairing the fault nodes with great influence on the test environment according to the recovery priority weights.

According to the test environment fault node repairing method provided by the embodiment of the disclosure, the influence degree of the fault node in the current test environment is evaluated through the access request link string and the fault node information of the obtained automatic test script, the recovered priority is automatically formed according to the influence degree, the test environment maintainer is convenient to select, under the condition that the number of the test environment nodes is large in scale, the test environment maintainer resources are limited, the test environment maintainer is convenient to pre-evaluate the test environment recovery effect under the condition that the automatic test script executes a plurality of tasks, and the test environment maintainer expands the maintenance work of the test environment node according to the evaluation result, so that the test environment maintenance utility is improved.

The determination of the access request link string in the embodiments of the present disclosure will be described below with reference to fig. 4. Fig. 4 schematically illustrates a flowchart of a method of determining an access request link string provided in accordance with an embodiment of the present disclosure. As shown in fig. 4, operation S220 includes operations S221 to S222.

In operation S221, an access node IP path of each automation test script is determined according to the access request time and script name.

According to an embodiment of the disclosure, the test environment node information includes a test environment node IP and a node corresponding service name.

In operation S222, an access request link string of each automation test script is determined according to the access node IP path and the node corresponding service name.

In one example, the test environment node information includes a test environment node IP and a service name corresponding to the node, as shown in table 1 below:

TABLE 1

Service name	Equipment node IP
		Identity authentication node	42.17.109.1
Identity authentication node	42.17.109.2
		Identity authentication node	42.17.109.3
Identity authentication node	42.17.114.4
		Transfer service node	42.17.23.1

Based on the automated test script names, node IP information (one node accesses only one node is counted) is refined through time sequence to form a link string of each automated test script test environment access request, as shown in table 2:

TABLE 2

Fig. 5a schematically illustrates one of the flowcharts of the method for determining the restoration priority weights of failed nodes in different periods provided according to an embodiment of the present disclosure. Fig. 5b schematically illustrates a second flowchart of a method for determining recovery priority weights of failed nodes in different periods provided according to an embodiment of the present disclosure. Fig. 6a schematically illustrates a flowchart of a method for determining a first recovery priority weight of a single failed node provided according to an embodiment of the disclosure. Fig. 6b schematically illustrates a flow chart of a method of determining a second recovery priority weight for a failed node involving a service portfolio, according to an embodiment of the disclosure.

As shown in fig. 5a, operation S230 includes operations S231 to S232.

In operation S231, the same group of node fault statistics are determined according to the test environment node information and the fault node information.

In operation S232, a restoration priority weight of the failed node in different periods is determined according to the same group of node failure statistics and the access request link string.

In one example, according to all fault node lists of the current fault obtained from the fault node monitoring module, the service group name to which the current IP node belongs and the service group IP list of the same group are obtained from the test environment information registration module, so as to form fault statistics information of the nodes of the same group, as shown in table 3:

TABLE 3 Table 3

As shown in fig. 5b, operation S232 includes operation S2321 and operation S2323.

In operation S2321, a first restoration priority weight of a single failed node in different periods is calculated according to the same set of node failure statistics.

As shown in fig. 6a, operation S2321 includes operations S310 to S330.

In operation S310, a failure rate of the failed node is determined according to the same group node failure number, the node name, and the total number of the same group nodes.

In operation S320, the number of automation scripts affected by the failed node in the different periods is determined.

In operation S330, a first restoration priority weight in different periods is determined according to the failure rate of the failed node and the number of automation scripts.

In one example, according to the current fault node situation, the fault rate of the service corresponding to each fault node is calculated, and the fault rate m=the number of fault nodes in the same group/the total number of fault nodes in the same group, so as to obtain the fault rates M1, M2, M3 and Mn corresponding to each fault node. And (5) ordering according to the failure rate from large to small to obtain ordered queues { M2, M3, M1}. When the fault rate values are consistent, calculating an automation script range influenced by the service corresponding to the current fault node, and respectively obtaining an automation script list of an execution plan in a corresponding time interval according to intervals of more than 30 minutes, 60 minutes, 90 minutes and 120 minutes, wherein the automation script list is shown in table 4:

counting the fault nodes and the corresponding automation scripts to obtain the quantity N of the automation test scripts influenced by each node in different time period intervals, for example, the influence in 30 minutes: n1=12, n2=5, n3=4, n4=30; effect within 120 min: n1=25, n2=23, n3=121, n4=56. Based on the failure rate of the service corresponding to the single failure node, calculating a first recovery priority weight F of the failure node: f1 M1=n1, f2=n2×m2, f3=n3×m3, f4=n4×m4.

In operation S2322, a second recovery priority weight for the failed node relating to the service combination is calculated from the access request link string.

As shown in fig. 6b, operation S2322 includes operations S410 to S440.

In operation S410, it is determined that the failed node relates to service composition statistics based on the knowledge-graph. In operation S420, it is determined that the failure node failure rate is greater than the service node combination of the preset threshold. In operation S430, a priority weight of the failed node in the service node combination is calculated. In operation S440, a second restoration priority weight of the failed node related to the service combination is determined according to the priority weight.

In one example, taking an automation script as a unit, corresponding the current fault node to a corresponding service node name, and obtaining a combination and a corresponding number D, D1= { P1, P2, P30, P43, 20} of services related to the current fault node based on a knowledge graph algorithm; d2 = { P1, P2, P3, P55, 15}; d3 = { P2, P5, P4, P64,3} … dm= { P2, P5, P14, P60, Y }. The service node combination with the equipment node failure rate larger than the preset threshold corresponding to the current service is obtained by associating with the failure statistical information of the nodes in the same group, wherein the preset threshold is 100% in the embodiment, namely, the service node combination E with the failure rate of 100%, E1= { P1, P2, 20}; e2 = { P1, P2, P3, 15}; e3 = { P2, P5, P4,3}; .. Em= { P2, P5, P14, P60, Y }.

Based on the combination of the related services of the fault nodes, a second recovery priority weight G of the automation script, which is commonly influenced by the fault nodes, is calculated, and is mainly used for adjusting the scene that the flow cannot be continued due to the fault of other nodes after single-point fault repair, the weight consideration for normally completing the flow test only by simultaneous recovery is increased, and the weight value of each IP node in the corresponding combination E takes a weight.

For example, the priority weight value of P1 in E1 is y11=20/(20+15+3+.+ y) x 100, and the priority weight value of P2 in E1 is equal to the priority weight value of P1 in E1, y21=20/(20+15+3+.+ y) x 100. G1=y11+y12+y13+y14+y19+), g2=y21+y22+y23+y24+), g3=y31+y32+y33+y34+y35+). Wherein, the y11/y12/y13 sub-table represents the priority weight value of P1 in the E1, E2 and E3 service combination, the y21/y22/y23 sub-table represents the priority weight value of P2 in the E1, E2 and E3 service combination, and the y31/y32/y33 sub-table represents the priority weight value of P3 in the E1, E2 and E3 service combination.

In operation S2323, a restoration priority weight of the failed node in different periods is determined according to the first restoration priority weight and the second restoration priority weight.

In one example, the restoration priority weight X of each IP node is finally determined according to the first restoration priority weight and the second restoration priority weight, x1=f1×50++g1×50%, x2=f2×50++g2×50%, and so on. Based on the time segments, node impact weights of 30 minutes, 60 minutes, 90 minutes and 120 minutes are obtained respectively and provided for test environment maintenance personnel to reference treatment. And when the version or maintenance is required to be carried out on the test nodes in the test environment, the test nodes to be maintained are manually set to be in a fault state, the priority of the maintenance of the test environment nodes is deduced according to the method provided by the embodiment of the disclosure, and the corresponding test environment version maintenance is carried out by testers from low to high according to the priority weight of the nodes, so that the influence of fault detection points on test tasks is reduced.

Based on the test environment fault node repairing method, the disclosure also provides a test environment fault node repairing device. The device will be described in detail below in connection with fig. 7.

Fig. 7 schematically illustrates a block diagram of a test environment fault node repair device according to an embodiment of the present disclosure.

As shown in fig. 7, the test environment failure node repairing apparatus 700 of this embodiment includes an acquisition module 710, an access request link string determination module 720, a restoration priority weight determination module 730, and a failure repairing module 740.

The obtaining module 710 is configured to obtain fault node information in response to a fault repair instruction. In an embodiment, the obtaining module 710 may be configured to perform the operation S210 described above, which is not described herein.

The access request link string determining module 720 is configured to determine an access request link string of each automation test script according to the access request message and the test environment node information. In an embodiment, the access request link string determining module 720 may be configured to perform the operation S220 described above, which is not described herein.

The recovery priority weight determining module 730 is configured to calculate the recovery priority weights of the failed nodes in different periods according to the failed node information and the access request link string. In an embodiment, the recovery priority weight determining module 730 may be configured to perform the operation S230 described above, which is not described herein.

The fault repairing module 740 is configured to repair the faulty node according to the recovery priority weight of the faulty node, where the access request message is generated during the running of the automated test script, and the access request message includes node IP information and access request time. In an embodiment, the fault modification module 740 may be configured to perform the operation S240 described above, which is not described herein.

According to an embodiment of the present disclosure, the access request link string determining module 710 includes: a first determination sub-module and a second determination sub-module.

And the first determining submodule is used for determining the IP path of the access node of each automation test script according to the access request time and the script name. In an embodiment, the first determining sub-module may be used to perform the operation S221 described above, which is not described herein.

And the second determining submodule is used for determining the access request link string of each automation test script according to the IP path of the access node and the service name corresponding to the node. In an embodiment, the second determining sub-module may be used to perform the operation S222 described above, which is not described herein.

The third determining submodule is used for determining node fault statistical information in the same group according to the test environment node information and the fault node information; the third determination sub-module may be used to perform operation S231 described above, and will not be described again.

And a fourth determining sub-module, configured to determine recovery priority weights of failed nodes in different periods according to the same group of node failure statistics information and the access request link string. The fourth determination submodule may be used to perform operation S232 described above, and is not described here again.

And the first calculation unit is used for calculating the first recovery priority weight of the single fault node in different periods according to the fault statistical information of the same group of nodes. The first calculation unit may be used to perform the operation S2321 described above, which is not described herein.

And the second calculation unit is used for calculating a second recovery priority weight of the fault node related to the service combination according to the access request link string. The second calculation unit may be used to perform the operation S2322 described above, which is not described herein.

And the determining unit is used for determining the recovery priority weights of the fault nodes in different periods according to the first recovery priority weights and the second recovery priority weights. The determining unit may be used to perform the operation S2323 described above, which is not described herein.

According to an embodiment of the present disclosure, the first computing unit includes a first determining subunit, a second determining subunit, and a third determining subunit.

And the first determination subunit is used for determining the failure rate of the failed node according to the same group node failure number, the node name and the total number of the same group nodes. In an embodiment, the first determining subunit may be configured to perform the operation S310 described above, which is not described herein.

And the second determination subunit is used for determining the quantity of the automation scripts influenced by the fault nodes in different periods. In an embodiment, the second determining subunit may be configured to perform the operation S320 described above, which is not described herein.

And the third determination subunit is used for determining the first recovery priority weights in different periods according to the failure rate of the failure node and the quantity of the automation scripts. In an embodiment, the third determining subunit may be configured to perform the operation S330 described above, which is not described herein.

and a fifth determining subunit, configured to determine a service node combination with a failure node failure rate greater than a preset threshold. In an embodiment, the fifth determining subunit may be configured to perform the operation S410 described above, which is not described herein.

And the calculating subunit is used for calculating the priority weight of the fault node in the service node combination. In an embodiment, the computing subunit may be configured to perform the operation S420 described above, which is not described herein.

A sixth determining subunit, configured to determine, according to the priority weights, a second recovery priority weight related to the service combination for the failed node. In an embodiment, the sixth determining subunit may be configured to perform the operation S430 described above, which is not described herein.

Any of the acquisition module 710, the access request link string determination module 720, the restoration priority weight determination module 730, and the failover module 740 may be combined in one module to be implemented, or any of them may be split into a plurality of modules, according to embodiments of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the acquisition module 710, the access request link string determination module 720, the restoration priority weight determination module 730, and the failover module 740 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or in any one of or a suitable combination of any of the three. Alternatively, at least one of the acquisition module 710, the access request link string determination module 720, the restoration priority weight determination module 730, and the failover module 740 may be at least partially implemented as a computer program module that, when executed, performs the corresponding functions.

As shown in fig. 8, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 900 may also include an input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904. The electronic device 900 may also include one or more of the following components connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs that, when executed, implement a test environment failure node repairing method according to an embodiment of the present disclosure.

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

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, is configured to cause the computer system to implement a test environment failure node repair method provided by embodiments of the present disclosure.

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

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, via communication portion 909, and/or installed from removable medium 911. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

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

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

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A method for repairing a test environment failure node, the method comprising:

2. The method of claim 1, wherein the test environment node information includes a test environment node IP and a node corresponding service name, and wherein determining an access request link string for each automation test script based on the access request message and the test environment node information includes:

3. The method of claim 1, wherein said calculating recovery priority weights for failed nodes in different periods based on said failed node information and said access request link string comprises:

4. The method of claim 3, wherein said determining recovery priority weights for failed nodes in different periods based on said peer group node failure statistics and said access request link string comprises:

5. The method of claim 4, wherein the peer group node fault statistics include a fault node IP, a node name, a total number of peer group nodes, and a number of peer group node faults, and wherein calculating the first recovery priority weight for an individual fault node based on the peer group node fault statistics comprises:

6. The method of claim 4, wherein calculating a second recovery priority weight for the failed node related to the service portfolio based upon the access request link string comprises:

7. The method according to any one of claims 1 to 6, wherein the failure node information includes a failure node IP, a failure time, and a failure discovery mode.

8. A test environment fault node repair apparatus, the apparatus comprising:

9. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-7.

10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-7.

11. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 7.