Multi-mode inspection system, device and storage medium
The multi-mode inspection system solves the problems of poor interoperability and insufficient scenario coverage of inspection tools, realizes unified access and aggregation of inspection tools, reduces costs and improves inspection efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-04
- Publication Date
- 2026-03-20
Smart Images

Figure CN116028742B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer software, in particular to a multi-mode inspection system, device and storage medium. BACKGROUND
[0002] In the scenario of payment business, the relationship on which the service depends is complex, one order placement process may involve more than ten self systems and other external third-party interfaces, and there are hundreds or even thousands of calls; in the production environment, long-time online failure caused by the failure of third-party services and the failure of the monitoring system to timely alarm, resulting in poor user experience and repair cost; at the same time, because there is no visual platform to show the availability of external third-party services and the usage state of external or third-party services, when an exception occurs, the actual business call monitoring needs to be alarmed passively and manually intervened, and at this time the actual user call failure has occurred, which has a large time lag. Therefore, in the related business scenario, the inspection platform needs to be used to actively find such problems, and the visual tool needs to be used to optimize the software and hardware configuration of each service.
[0003] In the usual website stability maintenance work, a single tool and type are generally used to test the system inspection scheme, or a user logs in the system manually to check whether the page is normal. For the usual inspection scheme, when the running system is relatively single and the number is small, the labor cost is not high. However, for the distributed system used at present, the system includes multiple functional modules, and the relationship between the functional modules is complex, so when the two methods are implemented, time consumption is large, use cases need to be rewritten because the tools cannot be converted, and the scene coverage is insufficient because of the single point inspection mode, which finally leads to high inspection cost. SUMMARY
[0004] In view of the defects in the prior art, the present disclosure provides a multi-mode inspection system, device and storage medium. Specifically, the first aspect of the present disclosure provides a multi-mode inspection system, which comprises a server and a plurality of front-end consoles in communication connection with the server, the server performs scheduling and execution of the corresponding inspection task according to one or more combinations of interface inspection tasks, man-machine interface inspection tasks and log inspection tasks, and feeds back the inspection result to the front-end console for presentation;
[0005] The server comprises:
[0006] The scheduler is configured to initiate and schedule the inspection task according to the preset inspection strategy or the user triggered instruction;
[0007] an execution engine configured to invoke a corresponding task executor to perform an operation according to the inspection task;
[0008] a result parser configured to parse the inspection report content of each task executor to obtain an inspection result that can be fed back to the front-end console;
[0009] The front-end console comprises:
[0010] an inspection scenario manager configured to configure a use case set and an inspection method for the interface inspection task, the human-computer interaction interface inspection task, and the log inspection task according to a user instruction;
[0011] an inspection result viewer configured to present the inspection result.
[0012] In a possible implementation of the first aspect, the service end is built based on a springboot framework, and is compatible with a POSTMAN test tool, an APIFOX test tool, and a Jmeter test tool.
[0013] The service end executes a background execution action in the form of a command string, and realizes concurrent execution of one or more of the POSTMAN test tool, the APIFOX test tool, and the Jmeter test tool in the background through a preset start command.
[0014] In a possible implementation of the first aspect, the command string comprises a business line parameter to which a use case belongs, an execution environment parameter, a use case set name parameter, and an executor type parameter.
[0015] In a possible implementation of the first aspect, the service end further comprises a notification module configured to feed back relevant execution information to a third-party user end prepared in advance according to the execution operation progress of the execution engine.
[0016] In a possible implementation of the first aspect, the result parser simultaneously uses a page analysis tool and an HTML parser to realize the parsing of the inspection report content, wherein:
[0017] The page analysis tool is configured to load the inspection report content and obtain corresponding page elements, and the page elements comprise a URL address and HTML text content.
[0018] The HTML parser is configured to parse the page elements.
[0019] The inspection result that can be fed back to the front-end console comprises one or more of a use case number corresponding to each inspection process, an execution success condition, an execution failure condition, and execution time information.
[0020] In a possible implementation of the first aspect, the front-end console further includes a debugging module, configured to initiate a debugging inspection task for any one of the scenes with the inspection requirement according to a user instruction.
[0021] The scheduler initiates and schedules the corresponding inspection task according to the debugging inspection task.
[0022] In a possible implementation of the first aspect, the inspection scene manager, in the process of configuring the inspection mode, includes:
[0023] The number of retries and the retry interval corresponding to a single inspection process are set to exclude abnormal jitter of the single inspection process caused by environmental system abnormalities.
[0024] In a possible implementation of the first aspect, the multi-mode inspection system further includes a plurality of reserved interfaces.
[0025] Other inspection test platforms and process automation robots allow access to the multi-mode inspection system through the reserved interfaces with access authorization.
[0026] The second aspect of the present disclosure provides a multi-mode inspection device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the multi-mode inspection system provided by the first aspect when executing the computer program.
[0027] The third aspect of the present disclosure provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the multi-mode inspection system provided by the first aspect.
[0028] Compared with the prior art, the present application has the following beneficial effects:
[0029] Through the technical solutions provided by the present disclosure, mainstream test automation tools can be applied to the unified access and aggregation of inspection scenes, and the inspection trend obtained from each inspection result and adjacent multiple inspection results can be analyzed and presented, so that the inspection test scene coverage is wider, and changes that are not easy to detect can be perceived in advance, the multi-mode system batch execution inspection is realized, the overall cost of the inspection is reduced, and the present application has promotional value. BRIEF DESCRIPTION OF DRAWINGS
[0030] Other features, objects and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments, with reference to the accompanying drawings:
[0031] Figure 1 According to the embodiments of the present disclosure, a schematic diagram of a multi-mode inspection system is shown;
[0032] Figures 2a to 2c According to the embodiments of the present disclosure, a schematic diagram of use case set configuration of the POSTMAN test tool in the front-end console is shown;
[0033] Figures 3a to 3b According to the embodiments of the present disclosure, a schematic diagram of use case set configuration of the APIFOX test tool and the Jmeter test tool in the front-end console is shown respectively;
[0034] Figure 4 According to the embodiments of the present disclosure, a schematic diagram of manual initiation of inspection calling for any scene in the scene management page of the front-end is shown;
[0035] Figures 5a to 5c According to the embodiments of the present disclosure, a schematic diagram of the inspection data table page, a schematic diagram of the inspection result viewing page and a schematic diagram of the inspection report page are shown respectively;
[0036] Figure 6 According to the embodiments of the present disclosure, a structural schematic diagram of a multi-mode inspection device is shown;
[0037] Figure 7 According to the embodiments of the present disclosure, a structural schematic diagram of a computer readable storage medium is shown. DETAILED DESCRIPTION
[0038] The present application will be described in detail below with specific embodiments. The following embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any form. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of changes and improvements can be made. These all belong to the protection scope of the present application.
[0039] In order to solve the problems of the existing technology that the inspection tool cannot be interchanged, the scene coverage is insufficient, and the inspection cost is high, the technical scheme provided by the present disclosure gives a multi-mode inspection system to realize the unified access and aggregation of mainstream inspection tools, and analyzes and presents the inspection trend obtained by the inspection result of each time and the inspection result of adjacent multiple times. The multi-mode inspection system provided by the technical scheme of the present disclosure will be explained and described in detail as follows:
[0040] Specifically, in some embodiments of the present disclosure, Figure 1 A structural schematic diagram of a multi-mode inspection system is shown. As shown in Figure 1 The multi-mode inspection system includes a server 100 and a plurality of front-end consoles 200 in communication connection with the server 100, wherein: the server 100 performs corresponding inspection task execution according to one or more combinations of interface inspection task, man-machine interface inspection task and log inspection task, and feeds back the inspection result to the front-end console 200 for presentation.
[0041] It can be understood that, in order to solve the problem of inflexible use and poor coverage of single tool interface inspection, in the process of building the server 100 in the above embodiment, a springboot framework can be used for building, and it is compatible with the existing public commonly used test tools such as POSTMAN test tool, APIFOX test tool and Jmeter test tool. In a specific implementation of the above embodiment, the server 100 uses the Runtime.exec(String command) method to perform background concurrent execution on the test tools such as POSTMAN test tool, APIFOX test tool and Jmeter test tool. The Runtime.exec(String command) is a command string that separately opens a thread to execute a specified command. The server 100 allows the background execution of the above test tools to be called by presetting the start commands of different test tools. For example, when the POSTMAN test tool needs to be executed in the background, the typed Runtime.exec can be as follows:
[0042] “command header middle platform and workflow test unified user daily inspection POSTMAN”
[0043] Among them, the parameter type corresponding to “middle platform and workflow” is the business line parameter of the test case, “test” is the corresponding execution environment parameter, “unified user daily inspection” is the case set parameter to which the test case belongs, and “POSTMAN” is the corresponding test tool executor type parameter. Through the above command parameters, accurate calling of background execution can be realized. Those skilled in the art can also adaptively increase the above command parameters according to actual needs, which is not limited here.
[0044] Further, the following shows part of the example code of Runtime.exec:
[0045]
[0046] It can be understood that, in the process of actually running the POSTMAN test tool, the cmd parameter in the above code will be replaced by the command string “command header middle platform and workflow test unified user daily inspection POSTMAN”. When those skilled in the art need to use other test tools, they only need to edit the corresponding command string and replace the cmd parameter in the above code to achieve it, which is not limited here.
[0047] In the multi-end inspection system shown in Figure 1 It can be seen that the main functional components of the server 100 can include:
[0048] Scheduler 101 is used to initiate and schedule inspection tasks according to preset inspection strategies or user-triggered commands. It can be understood that scheduler 101 may include executing corresponding scheduled tasks according to preset inspection configurations, or it may include executing inspection call debugging commands provided by the user through the front-end console 200; this is not limited here.
[0049] The execution engine 102 is used to call the corresponding task executor to perform operations according to the inspection task. In the above embodiment, the executor corresponding to the execution engine 102 includes the test executors corresponding to the POSTMAN test tool, APIFOX test tool, and Jmeter test tool; if other test tools required by actual applications are connected in addition to the test tools provided in the above embodiment, the execution engine 102 will integrate and control the corresponding test executor, which is not limited here.
[0050] The result parser 103 is used to parse the inspection report content of each task executor to obtain inspection results that can be fed back to the front-end console. In the above embodiment, specifically, the result parser 103 can perform parsing simultaneously through HtmlUnit and Jsoup: HtmlUnit, as an open-source Java page analysis tool, is used to load the inspection report and can effectively analyze the page content after reading the page; Jsoup, as a Java HTML parser, can directly parse inspection information such as a URL address or HTML text content. In the technical solution provided in this disclosure, the number of test cases corresponding to each inspection process, the success or failure of inspection execution, execution time, and other information can be obtained through the above two modules. This parsed information can be presented and displayed through the front-end console 200 for reference in system stability hardware configuration; at the same time, for inspection failure scenarios, timely alarm prompts will be sent to technical personnel through convenient third-party notifications such as email and DingTalk groups to enable rapid response by technical personnel and enhance system stability. In the above embodiments, the corresponding front-end display page can be quickly built using the antdpro scaffolding, and the display charts can be developed using the v2 chart framework.
[0051] Furthermore, the following is a sample code snippet for parsing the report:
[0052]
[0053] As can be seen from the above code implementation, in the specific inspection and analysis process, it is possible to...
[0054] At Figure 1 In the multi-terminal inspection system shown, the server 100 may further include:
[0055] The Websocket communication module 104 is configured to realize the bidirectional communication between the server 100 and the front-end console 200.
[0056] The notification module 105 is configured to feed back the relevant execution information to the third-party user terminal according to the execution operation progress of the execution engine. It can be understood that in the case of completing a single or scheduled inspection task, the completion of the inspection task can be fed back to the technical personnel in time through the user's pre-set notification mode such as email and Dingding.
[0057] It can be understood that the multi-terminal inspection system provided in the above embodiment can also include several reserved interfaces. Other custom inspection test platforms, inspection test tools, and process automation robots can access the multi-mode inspection system provided in the above embodiment through these reserved interfaces after obtaining access authorization.
[0058] In the multi-terminal inspection system shown in Figure 1 It can be seen that the front-end console 200 can specifically include:
[0059] The inspection scene manager 201 is configured to configure the use case set and the inspection method of the interface inspection task, the human-computer interaction interface inspection task, and the log inspection task according to the user instruction. The specific configuration process of the use case set and the inspection method will be specifically explained in the following.
[0060] The inspection result viewer 202 is configured to present the inspection result. The specific presentation method of the inspection result will be specifically explained in the following.
[0061] The specific function and use of the front-end console 200 provided in the above embodiment will be explained and described in the following by combining with the specific operation schematic diagram:
[0062] In a possible implementation of the above embodiment, Figures 2a to 2c A schematic diagram of configuring the use case set of the POSTMAN test tool in the front-end console 200 is shown, wherein: Figure 2a If the POSTMAN test tool is used as the executor of the inspection use case, the.json format use case set can be exported in the POSTMAN test tool first, and then the "add" button on the scene management page of the inspection platform is clicked to perform the add scene operation. After selecting the corresponding business line, running environment, timing task expression, and scene name, etc. in the add scene pop-up window, the "next" button is clicked to jump to the use case configuration interface as shown in Figure 2b The use case configuration interface as shown in Figure 2bIn the illustrated page, the use case source can be selected as "Postman", and then the previously exported.json format use case set can be uploaded. In the Figure 2c In the illustrated result notification page, the test result notification email can be set, and the retry number and retry interval corresponding to a single inspection process can be set to exclude the abnormal jitter of a single inspection process caused by environmental system abnormalities.
[0063] In another possible implementation of the above embodiment, Figures 3a to 3b The schematic diagrams of configuring the use case set for the APIFOX test tool and the Jmeter test tool in the front-end console 200 are respectively shown. Different from the use case set configuration for the POSTMAN test tool, the use case configuration interface needs to upload use case sets in different formats and check the corresponding test tool names, and the rest of the operations are the same as those for the POSTMAN test tool. Figures 2a to 2c The disclosed content can be kept consistent.
[0064] In the above embodiment, the inspection scene manager 201 can further include a debugging module, which is configured to initiate a debugging inspection task for any scene with an inspection requirement according to a user instruction; and the corresponding scheduler initiates and schedules the corresponding inspection task according to the debugging inspection task. In a specific implementation of the above embodiment, Figure 4 The schematic diagram of manually initiating an inspection call for any scene in the scene management page of the front-end is shown, as shown in Figure 4 As shown, the "debug" button in the operation bar corresponding to each scene can be clicked to manually trigger, and other triggering modes can also be selected by those skilled in the art according to actual needs, which are not limited herein. In addition, technical management personnel are also allowed to manage and maintain the use case set through the "download", "delete" and other buttons in the operation bar.
[0065] In the above embodiment, Figures 5a to 5c The schematic diagrams of the inspection data table page, the inspection result viewing page and the inspection report page are respectively shown. As shown in Figure 5a As shown, the running trend of the inspection scene can be viewed by the technical personnel according to the icon by counting the inspection running conditions of the last preset times (10 times are shown in the figure). As shown in Figures 5b to 5c As shown, the inspection result execution report can be presented in the form of a list, allowing the technical personnel to perform corresponding traversal operations or search operations, and clicking the specific execution ID number can jump to the inspection report viewing interface as shown in Figure 5c
[0066] It can be understood that each aspect of the technical solution of the present disclosure can be implemented as a system, a method or a program product. Therefore, each aspect of the technical solution of the present disclosure can be specifically implemented as a complete hardware implementation method, a complete software implementation method (including firmware, microcode, etc.), or an implementation method combining hardware and software aspects, which can be collectively referred to as "circuitry", "module" or "platform" here.
[0067] Those skilled in the art should understand that each unit or each module or each step of the present disclosure described above can be realized by a general computing device, which can be concentrated on a single computing device or distributed on a network composed of multiple computing devices, and can be realized by program code executable by a computing device, so that it can be stored in a storage medium and executed by a computing device, and in some cases, the steps shown or described can be executed in an order different from that described here, or they can be manufactured into individual integrated circuit modules, or multiple modules or steps among them can be manufactured into a single integrated circuit module.
[0068] Figure 6 According to some embodiments of the present disclosure, a structural diagram of a multi-mode inspection device is shown, which is used to implement the multi-mode inspection system provided in the foregoing embodiments. The electronic device 600 implemented according to the implementation method in the present embodiment will be described in detail below with reference to Figure 6 The electronic device 600 shown is only an example and should not limit the function and use range of any embodiment of the present disclosure. Figure 6
[0069] As shown in Figure 6 The electronic device 600 is in the form of a general computing device. The components of the electronic device 600 can include but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different platform components (including the storage unit 620 and the processing unit 610), a display unit 640, etc.
[0070] The storage unit stores program code, which can be executed by the processing unit 610, so that the processing unit 610 executes the implementation of each functional module in the multi-mode inspection system described above in the present embodiment.
[0071] The storage unit 620 can include a readable medium in the form of a volatile storage unit, such as a random access unit (RAM) 6201 and / or a cache storage unit 6202, and can further include a read-only storage unit (ROM) 6203.
[0072] The storage unit 620 can also include a program / utility 6204 having a set of programs / modules 6205, each of which performs one or more of the processes to be executed on the electronic device 600, such as one or more of the processes described in the above disclosure. The programs / utility 6204 can also include program modules that cause the electronic device 600 to perform various processes and other
[0073] The bus 630 can represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, an electronic device 600 local bus using any of a variety of bus architectures, etc.
[0074] The electronic device 600 can also communicate with one or more external devices 700 such as a keyboard or pointing device, a Bluetooth device, etc., one or more devices that enable a user to interact with the electronic device 600 and / or one or more devices (e.g., a router, a modem, a server, etc.) that enable the electronic device 600 to communicate with one or more other electronic devices. Such communication can occur via an input / output (I / O) interface 650. Still yet, the electronic device 600 can communicate with one or more networks, such as one or more local area networks (LANs), one or more wide area networks (WANs), and / or one or more public networks, such as the Internet, via the network adapter 660. The network adapter 660 can communicate with the other components of the electronic device 600 via the bus 630. It should be understood that although not shown, other hardware and / or software components could be used in conjunction with the electronic device 600. Such components can include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc. Figure 6
[0075] In some embodiments of the present disclosure, a computer readable storage medium is also provided, and the computer program is stored on the computer readable storage medium, and the computer program is executed by a processor to realize the implementation of each functional module in the multi-mode inspection system disclosed in the present disclosure.
[0076] Although the present embodiment does not enumerate other specific embodiments in detail, in some possible embodiments, each aspect of the technical solution of the present disclosure can also be implemented in the form of a program product, which includes program code for causing the terminal device to execute the steps of the embodiments according to the technical solution of the present disclosure described in the multi-mode inspection system of the present disclosure when the program product is run on the terminal device.
[0077] Figure 7 According to some embodiments of the present disclosure, a structural schematic diagram of a computer readable storage medium is shown. As shown in FIG. 8, the computer readable storage medium includes a computer program 801, and the computer program 801 is used to realize the implementation of each functional module in the multi-mode inspection system disclosed in the present disclosure. Figure 7 As shown in FIG. 8, a program product 800 for implementing the multi-mode inspection system described above according to an embodiment of the present disclosure is described, which can adopt a portable compact disc read-only memory (CD-ROM) and include program codes, and can run on a terminal device, such as a personal computer. Of course, the program product generated according to the present embodiment is not limited to this, and in the present disclosure, the readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, device or apparatus.
[0078] The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples (non-exhaustive list) of the readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0079] The computer readable storage medium can include a data signal carried in the baseband or as a carrier wave propagating through a propagation medium, where the readable program codes are carried. Such a propagating data signal can adopt various forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination thereof. The readable storage medium can also be any readable medium other than the readable storage medium, which can send, propagate or transmit a program for use by or in combination with an instruction execution system, device or apparatus. The program codes contained on the readable storage medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.
[0080] The program code for carrying out operations of the disclosed techniques can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider (ISP).
[0081] In summary, through the technical solution provided by the present disclosure, the unified access and aggregation of mainstream inspection tools can be realized, and the inspection trend obtained from each inspection result and adjacent multiple inspection results can be analyzed and presented, so that the inspection test scene coverage is wider, the changes that are not easy to detect can be perceived in advance, the multi-mode system batch execution inspection is realized, the overall cost of the inspection is reduced, and the technical solution has popularization value.
[0082] The above description is only a description of the preferred embodiments of the technical solution of the present disclosure, and does not limit the scope of the technical solution of the present disclosure. Any modification or change made by a person skilled in the art according to the above disclosure is within the protection scope of the claims.
Claims
1. A multi-mode inspection system, characterized in that, It includes a server and several front-end consoles that communicate with the server. The server schedules and executes corresponding inspection tasks according to one or more combinations of interface inspection tasks, human-computer interaction interface inspection tasks and log inspection tasks, and feeds back the inspection results to the front-end consoles for presentation. The server includes: The scheduler is used to initiate and schedule inspection tasks according to preset inspection strategies or user-triggered commands. The execution engine is used to call the corresponding task executor to perform the operation according to the inspection task. The server executes the background execution action in the form of a command string. The preset start command enables one or more of the POSTMAN test tool, APIFOX test tool and Jmeter test tool to be executed concurrently in the background. The result parser is used to parse the inspection report content of each task executor to obtain the inspection results that can be fed back to the front-end console. The result parser uses both a page analysis tool and an HTML parser to parse the inspection report content. The page analysis tool is used to load the inspection report content and obtain the corresponding page elements, which include URL addresses and HTML text content. The HTML parser is used to parse the page elements; The front-end console includes: The inspection scenario manager is used to configure the test case set and inspection method for the interface inspection task, the human-computer interaction interface inspection task, and the log inspection task according to user instructions. The inspection results viewer is used to present the inspection results.
2. The multi-mode inspection system according to claim 1, characterized in that, The command string includes parameters for the business line to which the test case belongs, execution environment parameters, test case set name parameters, and executor type parameters.
3. The multi-mode inspection system according to claim 1, characterized in that, The server also includes a notification module, which feeds back relevant execution information to pre-defined third-party clients based on the execution progress of the execution engine.
4. The multi-mode inspection system according to claim 1, characterized in that, In the result parser, the inspection results that can be fed back to the front-end console include one or more of the following: the number of test cases corresponding to each inspection process, the success status, the failure status, and the execution time information.
5. The multi-mode inspection system according to claim 1, characterized in that, The front-end console also includes a debugging module, which is used to initiate a debugging and inspection task for any scenario with inspection requirements based on user instructions. The scheduler initiates and schedules corresponding inspection tasks based on the debugging and inspection tasks.
6. The multi-mode inspection system according to claim 1, characterized in that, The inspection scene manager, in configuring the inspection method, includes: Set the number of retries and the retry interval for a single inspection process to eliminate abnormal fluctuations in a single inspection process caused by environmental system anomalies.
7. The multi-mode inspection system according to claim 1, characterized in that, The multi-mode inspection system also includes several reserved interfaces; Other inspection testing platforms and process automation robots are allowed to access the multi-mode inspection system through the reserved interface, provided they have the necessary access authorization.
8. A computer device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the multi-mode inspection system as described in any one of claims 1 to 7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the multi-mode inspection system as described in any one of claims 1 to 7.
Citation Information
Patent Citations
Control system applied to intelligent inspection robot
CN110587601A
Inspection method, device, electronic equipment and medium
CN112463612A