Fault test request processing method and device, electronic equipment and storage medium
By receiving test requests in the fault detection device and converting them into test task objects, and processing test requests in multi-terminal parallel detection scenarios, the problems of waste of resources and low response rates in the prior art are solved, and fast response and high resource utilization are achieved.
Patent Information
- Application Number
- CN202311309318.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-10
- Publication Date
- 2025-04-11
AI Technical Summary
In the multi-end parallel detection scenario, the prior art parallel test request processing method results in waste of resources and low response rates, and cannot respond quickly to test requests from the test request end, and the resource utilization rate is not high.
By receiving the test request and converting it into a test task object, it is determined whether there is a task object containing the same test items in the test task queue. If it exists, add a requesting identification code. If it does not exist, add a new task object to the queue. Perform a fault test operation based on the task object in the queue to obtain the test results.
This method can avoid repeated execution of the same test item, quickly respond to test requests on the test request side, and improve resource utilization.
Smart Images
Figure CN119806920A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of equipment testing, and in particular to a method, device, electronic device and storage medium for processing a fault test request. Background Art
[0002] Medical equipment, servers, engines and other equipment will have built-in fault detection devices, through which users can perform fault detection; if the equipment is connected to the network, some fault detection devices also support remote access to provide remote fault detection.
[0003] In actual applications, a multi-terminal parallel detection scenario may occur in which a fault detection device on a device receives multiple test requests at the same time. Due to the limitation of resource access conflicts, in the above multi-terminal parallel detection scenario, the conventional parallel test request processing method in the related art is: when the fault detection device of the device receives a test request, if the fault detection device is working at this time, the newly received test request will be inserted at the end of the task queue. However, the above test request processing method will result in repeated execution of the same fault test operation, resulting in resource waste and a low response rate for test requests.
[0004] Therefore, how to quickly respond to the test request from the test request end and improve resource utilization is a technical problem that those skilled in the art currently need to solve. Summary of the invention
[0005] The purpose of this application is to provide a method, device, electronic device and storage medium for processing fault test requests, which can quickly respond to test requests from a test request end and improve resource utilization.
[0006] In order to solve the above technical problems, the present application provides a method for processing a fault test request, and the method for processing a fault test request includes:
[0007] Receive a test request sent by a test request end, and convert the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item;
[0008] Determine whether there is a second test task object that includes the first test item in the test task queue;
[0009] If yes, adding the first request end identification code to the second test task object;
[0010] If not, adding the first test task object to the test task queue;
[0011] A corresponding fault test operation is performed according to the test task object in the test task queue to obtain a fault test result corresponding to the test request.
[0012] Optionally, converting the test request into a first test task object includes:
[0013] Extracting the first request end identification code and the test item combination from the test request;
[0014] Splitting the test item combination into N first test items;
[0015] Generate a corresponding first test task object for each first test item; wherein the first test task object includes the first request end identification code and a single first test item.
[0016] Optionally, after adding the first test task object to the test task queue, the method further includes:
[0017] Creating a first test result object corresponding to the first test task object in a test result queue, and adding the first request end identification code and the first test item in the first test task object to the first test result object;
[0018] Correspondingly, after obtaining the fault test result corresponding to the test request, the method further includes:
[0019] Add the fault test result to the first test result object.
[0020] Optionally, also include:
[0021] Receiving a result query request sent by the test request end;
[0022] If the result query request includes the first request end identification code and the first test item, querying the corresponding fault test result from the first test result object according to the first request end identification code and the first test item;
[0023] The fault test result is sent to the test request end.
[0024] Optionally, after sending the fault test result to the test request end, the method further includes:
[0025] Deleting the first request end identification code in the first test result object;
[0026] If the request end identification code does not exist in the first test result object, the first test result object is deleted.
[0027] Optionally, after adding the first request end identification code to the second test task object, the method further includes:
[0028] Query the test result queue for a second test result object corresponding to the second test task object, and add the first request end identification code to the second test result object; wherein the second test result object is used to store the execution result of the second test task object.
[0029] Optionally, adding the first test task object to the test task queue includes:
[0030] Adding the first test task object to the tail of the test task queue;
[0031] Correspondingly, executing corresponding fault test operations according to the test task objects in the test task queue includes:
[0032] The test task objects to be executed currently are selected from the test task queue in sequence according to a preset order, and the fault test operations corresponding to the test task objects to be executed currently are executed.
[0033] The present application also provides a device for processing a fault test request, the device comprising:
[0034] A connection management module, configured to receive a test request sent by a test request end, and convert the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item;
[0035] A test task management module, used to determine whether there is a second test task object containing the first test item in the test task queue; if so, add the first request end identification code to the second test task object; if not, add the first test task object to the test task queue;
[0036] The test processing module is used to execute the corresponding fault test operation according to the test task object in the test task queue, so as to obtain the fault test result corresponding to the test request.
[0037] The present application also provides a storage medium on which a computer program is stored. When the computer program is executed, the steps of the method for processing the fault test request are implemented.
[0038] The present application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, the steps of executing the above-mentioned method for processing fault test requests are implemented.
[0039] The present application provides a method for processing a fault test request, including: receiving a test request sent by a test request end, and converting the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item; determining whether there is a second test task object in a test task queue that already includes the first test item; if so, adding the first request end identification code to the second test task object; if not, adding the first test task object to the test task queue; performing corresponding fault test operations according to the test task objects in the test task queue, so as to obtain a fault test result corresponding to the test request.
[0040] After receiving the test request sent by the test request end, the present application converts the test request into a first test task object including a first request end identification code and a first test item. When there is a second test task object that already includes the first test item in the test task queue, the present application directly adds the first request end identification code to the second test task object, so that after executing the second test task object in the test task queue, a fault test result corresponding to the test request is generated. The present application also adds the first test task object to the test task queue when there is no second test task object that already includes the first test item in the test task queue, so that after executing the first test task object in the test task queue, a fault test result corresponding to the test request is generated. The above method can avoid repeated execution of the same test item, so the present application can quickly respond to the test request of the test request end and improve resource utilization. The present application also provides a processing device for a fault test request, a storage medium and an electronic device, which have the above-mentioned beneficial effects and are not repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0042] Figure 1 A flowchart of a method for processing a fault test request provided in an embodiment of the present application;
[0043] Figure 2 A schematic diagram of a first method for processing a parallel fault test request in the related art;
[0044] Figure 3 A schematic diagram of a second method for processing a parallel fault test request in the related art;
[0045] Figure 4A schematic diagram of a test request processing solution for a fault detection program provided in an embodiment of the present application;
[0046] Figure 5 A schematic diagram of the structure of a test task queue in a test task management module provided in an embodiment of the present application. DETAILED DESCRIPTION
[0047] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0048] See below Figure 1 , Figure 1 A flowchart of a method for processing a fault test request provided in an embodiment of the present application.
[0049] Specific steps may include:
[0050] S101: receiving a test request sent by a test request end, and converting the test request into a first test task object;
[0051] This embodiment can be applied to a fault detection device, which can be built into medical equipment, servers, engines and other equipment; the test request end is a terminal that requests the fault detection device to perform a fault test, specifically, the test request end sends a test request to enable the fault detection device to perform a corresponding test operation. The test request sent by the test request end is a fault detection request.
[0052] The fault detection device can receive test requests from multiple test request ends. A test task queue is set in the fault detection device, and the test task queue can be updated after receiving the test request; a fault detection program is also running in the fault detection device, and the fault detection program can perform corresponding test operations according to the test task queue.
[0053] The test request sent by the test request end may include a first request end identification code and a first test item of the test request end; the first request end identification code is used to describe the identity of the test request end, that is, the unique identifier of the test request end; the first test item is used to describe the content of the fault test that the test request end needs to perform. After receiving the test request, the test request may be converted into a first test task object including the first request end identification code and the first test item.
[0054] S102: Determine whether there is a second test task object that includes the first test item in the test task queue; if so, proceed to S103; if not, proceed to S104;
[0055] Among them, there may be an operation of constructing a test task queue before this step, and the above-mentioned test task queue is used to store test task objects. After the first test task object is generated, it can be determined whether the first test item in the first test task object already exists in other test task objects that have been added to the test task queue. Specifically, this embodiment can determine whether there is a second test task object that already contains the first test item in the test task queue, and the above-mentioned second test task object is a test task object that has been added to the test task queue.
[0056] S103: Adding the first request end identification code to the second test task object;
[0057] Among them, this step is based on the existence of a second test task object in the test task queue that already contains the first test item, that is, the first test task object and the second test task object both contain the first test item. At this time, a new test task object (that is, the first test task object) does not need to be added to the test task queue, but the first request end identification code is directly added to the second test task object, so that after executing the second test task object, a fault test result corresponding to the test request is generated.
[0058] S104: Adding the first test task object to the test task queue;
[0059] This step is based on the fact that there is no second test task object containing the first test item in the test task queue. The first test task object can be added to the test task queue so that after executing the first test task object, a fault test result corresponding to the test request is generated.
[0060] S105: Execute a corresponding fault test operation according to the test task object in the test task queue to obtain a fault test result corresponding to the test request.
[0061] Among them, this embodiment can execute the corresponding fault test operation according to the test task object in the test task queue, and after executing the test task object where the first request end identification code is located, the fault test result corresponding to the test request can be obtained.
[0062] Specifically, the present embodiment can add the first test task object to the tail of the test task queue, that is, add the first test task object to the last position of the test task queue. The present embodiment can select the test task object to be executed from the test task queue in sequence according to a preset order (e.g., from the head to the tail), and execute the fault test operation corresponding to the test task object to be executed.
[0063] After receiving the test request sent by the test request end, the present embodiment converts the test request into a first test task object including a first request end identification code and a first test item. When there is a second test task object including the first test item in the test task queue, the present embodiment directly adds the first request end identification code to the second test task object, so that after executing the second test task object in the test task queue, a fault test result corresponding to the test request is generated. The present embodiment also adds the first test task object to the test task queue when there is no second test task object including the first test item in the test task queue, so that after executing the first test task object in the test task queue, a fault test result corresponding to the test request is generated. The above method can avoid repeated execution of the same test item, so that the present embodiment can quickly respond to the test request of the test request end and improve resource utilization.
[0064] As for Figure 1 Further introduction to the corresponding embodiment, the test request sent by the test request end may contain a first request end identification code and a test item combination, and the test item combination is a combination of multiple first test items. This embodiment can generate a first test task object for the test request, that is: a first test task object includes a first request end identification code and multiple first test items.
[0065] This embodiment can also generate multiple first test task objects for the test request, that is, one first test task object includes a first request end identification code and a single first test item. Specifically, this embodiment can extract the first request end identification code and the test item combination from the test request; split the test item combination into N first test items; generate a corresponding first test task object for each first test item; wherein the first test task object includes the first request end identification code and a single first test item.
[0066] As for Figure 1 As further introduction to the corresponding embodiment, the present embodiment can also pre-build a test result queue, which includes multiple test result objects for storing test results. For easy query, the test result object can also include a request end identification code and a test item.
[0067] Specifically, after adding the first test task object to the test task queue, a first test result object corresponding to the first test task object can also be created in the test result queue, and the first request end identification code and the first test item in the first test task object are added to the first test result object. The above-mentioned first test result object is used to store the execution result of the first test task object, that is, the fault test result corresponding to the test request. Therefore, after obtaining the fault test result corresponding to the test request, the fault test result can also be added to the first test result object.
[0068] After adding the fault test result to the first test result object, the first test result object and the first test item can be sent to the test request end according to the first request end identification code in the first test result object, or the first test result object and the first test item can be sent to the test request end after receiving the result query request sent by the test request end.
[0069] As a feasible implementation method, after adding the fault test result to the first test result object, a result query request sent by the test request end can also be received; if the result query request includes the first request end identification code and the first test item, the corresponding fault test result is queried from the first test result object according to the first request end identification code and the first test item; the fault test result is sent to the test request end, or the fault test result and the first test item can be sent to the test request end.
[0070] As for Figure 1 Further introduction to the corresponding embodiment, after the fault test result is sent to the test request end, the first request end identification code can also be deleted in the first test result object; if no other request end identification code exists in the first test result object, the first test result object is deleted.
[0071] As for Figure 1 Further introduction to the corresponding embodiment, after adding the first request end identification code to the second test task object, the second test result object corresponding to the second test task object can also be queried in the test result queue, and the first request end identification code is added to the second test result object to update the request end identification code in the second test result object. The above-mentioned second test result object is used to store the execution result of the second test task object.
[0072] The process described in the above embodiment is explained below through an embodiment in actual application.
[0073] In the related art, the fault detection device usually Figure 2 and Figure 3 The method shown implements parallel fault testing. The fault detection device is a device used to detect whether there is a fault in the device. The fault detection device uses its own hardware detection resources to perform operations corresponding to the test request to perform fault detection. The specific implementation process is as follows:
[0074] See also Figure 2 , Figure 2 The first parallel fault test request processing method in the related art is shown in FIG. 1 . When the fault detection device is in an idle state, the test request end 1 sends the test request 1 to the fault detection device, and the fault detection device accepts and processes the test request 1. During the process of processing the test request 1, the fault detection device is in a busy state. At this time, if the test request end sends the test request 2 to the fault detection device, the fault detection device rejects the test request 2. After the fault detection device resumes the idle state, the test request end 2 sends the test request 3 to the fault detection device, and the fault detection device accepts and processes the test request 3 and enters a busy state. In the above scheme, when the fault detection device of the device receives multiple test requests in the idle state, only the first test request is processed. Before the first test request is completed, the subsequent test requests are rejected until the fault detection device enters the idle state again. The above scheme requires the test request end to regularly query whether the fault detection device is in an idle state. If the request frequency of a test request end is very high, it may cause other test request ends to fail to obtain the hardware detection resources of the fault detection device and fail to perform fault detection.
[0075] See also Figure 3 , Figure 3 This is a schematic diagram of the second processing method of parallel fault test requests in the related technology. Test request terminals 1 to n send their respective test requests to the test task queue of the fault detection device, and detect the test task that needs to be executed currently by traversing the test task queue. In the above scheme, when the fault detection device of the device receives the test request, if the fault detection device is working at this time, the newly received test request will be inserted at the end of the test task queue. If the same test request initiated by multiple test request terminals enters the test task queue, it will cause a waste of detection resources, and the response rate of the test request terminal that enters the test task queue later will be reduced.
[0076] In order to solve the technical problems existing in the above-mentioned related technologies, the present application provides a hardware detection resource management solution for a fault detection device. The solution can simultaneously accept test requests from multiple test request terminals and maximize the response speed of the same test request, thereby improving the efficiency of fault detection. This embodiment can be implemented based on the fault detection program of the fault detection device. Figure 4 , Figure 4A schematic diagram of a test request processing scheme of a fault detection program provided in an embodiment of the present application. The fault detection program includes a connection management module, a test task management module and a test processing module. The test request end 1 to n sends a test request to the connection management module. The connection management module converts the test request into a test task object and transmits it to the test task management module. The test task management module transmits the test task object to the test processing module to perform the corresponding test operation.
[0077] The connection management module supports multiple test request terminals through socket communication. The test request terminal sends its request terminal identification code (client id) and test item (item) to the connection management module in the form of a data packet through socket. The connection management module converts the data packet into a test task object and sends it to the test task management module.
[0078] The test task management module maintains a test task queue internally. When a new test task object is received, it is not simply added to the tail of the test task queue. Instead, the existing test task objects in the current test task queue are traversed first. If the test item is the same as the test item of the existing test task object in the test task queue, a request end identification code (client id) is added to the test task object. If there is no test task object containing the same test item in the test task queue, the newly created test task object is inserted at the tail of the test task queue.
[0079] See also Figure 5 , Figure 5 A structural diagram of a test task queue in a test task management module provided in an embodiment of the present application, wherein there are test task objects 1, 2, ... n in the test task queue, each test task object includes a test item and a requester identification code, the requester identification code corresponding to test item item1 is client id 1, the requester identification codes corresponding to test item item2 are client id 1 and client id 2, and the requester identification code corresponding to test item item n is client id 2.
[0080] The test processing module maintains a test result queue internally. Each time a test task object is obtained from the test task management module, a test result object is first created in the test result queue, and the test items and request end identification code in the test task object are copied to the test result object. After the test operation corresponding to the test task object is completed, the test result is filled into the test result object. When the test request end queries the test result, the test item and the request end identification code are matched in the test result queue. If a test result object is matched, the fault test result is sent to the test request end and the corresponding request end identification code in the test result object is deleted. When the request end identification code in the test result object is empty, the test result object is deleted.
[0081] The above implementation can ensure that the same test requests from different test request ends can be processed together, which not only saves the hardware detection resources of the fault detection device, but also ensures that the test request end obtains the fault test result as soon as possible.
[0082] An embodiment of the present application provides a device for processing a fault test request, which may include:
[0083] A connection management module, configured to receive a test request sent by a test request end, and convert the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item;
[0084] A test task management module, used to determine whether there is a second test task object containing the first test item in the test task queue; if so, add the first request end identification code to the second test task object; if not, add the first test task object to the test task queue;
[0085] The test processing module is used to execute the corresponding fault test operation according to the test task object in the test task queue, so as to obtain the fault test result corresponding to the test request.
[0086] After receiving the test request sent by the test request end, the present embodiment converts the test request into a first test task object including a first request end identification code and a first test item. When there is a second test task object including the first test item in the test task queue, the present embodiment directly adds the first request end identification code to the second test task object, so that after executing the second test task object in the test task queue, a fault test result corresponding to the test request is generated. The present embodiment also adds the first test task object to the test task queue when there is no second test task object including the first test item in the test task queue, so that after executing the first test task object in the test task queue, a fault test result corresponding to the test request is generated. The above method can avoid repeated execution of the same test item, so that the present embodiment can quickly respond to the test request of the test request end and improve resource utilization.
[0087] Furthermore, the connection management module includes:
[0088] An information extraction unit, used to extract the first request end identification code and a test item combination from the test request;
[0089] A test item splitting unit, used for splitting the test item combination into N first test items;
[0090] A test task object generating unit is used to generate a corresponding first test task object for each first test item; wherein the first test task object includes the first request end identification code and a single first test item.
[0091] Furthermore, the test processing module includes:
[0092] A test result object creation unit, configured to create a first test result object corresponding to the first test task object in a test result queue, and add the first request end identification code and the first test item in the first test task object to the first test result object;
[0093] The test result object adding unit is used to add the fault test result to the first test result object after obtaining the fault test result corresponding to the test request.
[0094] Furthermore, the test processing module includes:
[0095] A query request receiving unit, used to receive a result query request sent by the test request end;
[0096] A result query unit, configured to query the corresponding fault test result from the first test result object according to the first request end identification code and the first test item if the result query request includes the first request end identification code and the first test item;
[0097] The query result feedback unit is used to send the fault test result to the test request end.
[0098] Furthermore, the test processing module includes:
[0099] The request end identification code management unit is used to delete the first request end identification code in the first test result object; and is also used to delete the first test result object if the request end identification code does not exist in the first test result object.
[0100] Furthermore, the test processing module includes:
[0101] A test result object updating unit is used to query the second test result object corresponding to the second test task object in the test result queue, and add the first request end identification code to the second test result object; wherein, the second test result object is used to store the execution result of the second test task object.
[0102] Furthermore, the test task management module includes:
[0103] A queue management unit, used for adding the first test task object to the tail of the test task queue;
[0104] Accordingly, the test processing module includes:
[0105] The test execution unit is used to select the test task objects to be executed currently from the test task queue in sequence according to a preset order, and execute the fault test operation corresponding to the test task objects to be executed currently.
[0106] Since the embodiments of the apparatus part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the apparatus part, which will not be repeated here.
[0107] The present application also provides a storage medium on which a computer program is stored, and when the computer program is executed, the steps provided in the above embodiment can be implemented. The storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.
[0108] The present application also provides an electronic device, which may include a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps provided in the above embodiment may be implemented. Of course, the electronic device may also include various network interfaces, power supplies and other components. It should be noted that the above electronic device may be a medical device such as an ultrasonic diagnostic device and an endoscope.
[0109] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of this application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of this application.
[0110] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises", "comprising" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.
Claims
1. A method for processing a fault test request, characterized in that: include: Receive a test request sent by a test request end, and convert the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item; Determine whether there is a second test task object that includes the first test item in the test task queue; If yes, adding the first request end identification code to the second test task object; If not, adding the first test task object to the test task queue; A corresponding fault test operation is performed according to the test task object in the test task queue to obtain a fault test result corresponding to the test request.
2. The method for processing a fault test request according to claim 1, characterized in that: Converting the test request into a first test task object includes: Extracting the first request end identification code and the test item combination from the test request; Splitting the test item combination into N first test items; Generate a corresponding first test task object for each first test item; wherein the first test task object includes the first request end identification code and a single first test item.
3. The method for processing a fault test request according to claim 1, characterized in that: After adding the first test task object to the test task queue, the method further includes: Creating a first test result object corresponding to the first test task object in a test result queue, and adding the first request end identification code and the first test item in the first test task object to the first test result object; Correspondingly, after obtaining the fault test result corresponding to the test request, the method further includes: Add the fault test result to the first test result object.
4. The method for processing a fault test request according to claim 3, characterized in that: Also includes: Receiving a result query request sent by the test request end; If the result query request includes the first request end identification code and the first test item, querying the corresponding fault test result from the first test result object according to the first request end identification code and the first test item; The fault test result is sent to the test request end.
5. The method for processing a fault test request according to claim 4, characterized in that: After sending the fault test result to the test request end, the method further includes: Deleting the first request end identification code in the first test result object; If the request end identification code does not exist in the first test result object, the first test result object is deleted.
6. The method for processing a fault test request according to claim 1, characterized in that: After adding the first request end identification code to the second test task object, the method further includes: Query the test result queue for a second test result object corresponding to the second test task object, and add the first request end identification code to the second test result object; wherein the second test result object is used to store the execution result of the second test task object.
7. The method for processing a fault test request according to claim 1, characterized in that: Adding the first test task object to the test task queue includes: Adding the first test task object to the tail of the test task queue; Correspondingly, executing corresponding fault test operations according to the test task objects in the test task queue includes: The test task objects to be executed currently are selected from the test task queue in sequence according to a preset order, and the fault test operations corresponding to the test task objects to be executed currently are executed.
8. A device for processing a fault test request, characterized in that: include: A connection management module, configured to receive a test request sent by a test request end, and convert the test request into a first test task object; wherein the first test task object includes a first request end identification code and a first test item; A test task management module, used to determine whether there is a second test task object containing the first test item in the test task queue; if so, add the first request end identification code to the second test task object; if not, add the first test task object to the test task queue; The test processing module is used to execute the corresponding fault test operation according to the test task object in the test task queue, so as to obtain the fault test result corresponding to the test request.
9. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it implements the steps of the method for processing a fault test request as claimed in any one of claims 1 to 7.
10. A storage medium, characterized in that: The storage medium stores computer executable instructions, and when the computer executable instructions are loaded and executed by the processor, the steps of the method for processing a fault test request as claimed in any one of claims 1 to 7 are implemented.