A production inspection method and related device for an online environment

Abstract

The present application discloses a production inspection method and related devices for an online environment, which relate to the field of software technology. The online faults of the online environment are determined by the running results of the target production inspection tasks. Business inspection alarm information, business processing in progress information, and processing completion information can be generated for the processing progress of the online fault. Business inspection alarm information, business processing in progress information, and processing completion information can be displayed in the same notification group, and the processing progress can be displayed. This allows other people in the same notification group to see the processing progress of the online fault. The present application standardizes and automates the alarm processing process. Online faults are assigned through the identification of responsible persons, making alarm processing efficient. The present application allows operation and maintenance personnel to be informed of the occurrence of faults in the first place, thereby reducing fault response time.

Description

Technical Field

[0001] The present application relates to the field of software technology, and in particular to a production inspection method and related devices for an online environment. Background Art

[0002] With the advancement of technology, enterprises' online environments are becoming increasingly complex. The online environment refers to the environment where applications actually run and provide services. These environments may be distributed across different physical locations and even across different cloud service providers, making monitoring and maintenance of these environments more difficult.

[0003] When a failure occurs in the online environment, due to the lack of an effective monitoring and alarm system, operation and maintenance personnel are often unable to learn about the failure in the first place, resulting in prolonged failure response time. Summary of the Invention

[0004] In view of the above problems, this application provides a production inspection method and related devices for an online environment to automatically monitor online faults in the online environment and automatically trigger alarms. The specific solution is as follows:

[0005] A first aspect of the present application provides a production inspection method for an online environment, comprising:

[0006] Determine online faults in the online environment based on the results of target production inspection tasks.

[0007] Searching for target notification information corresponding to the target production inspection task from the preset correspondence between production inspection tasks and notification information, wherein the target notification information includes a notification group address and a person-in-charge identifier; the notification number of the person-in-charge with the person-in-charge identifier is located in the notification group with the notification group address;

[0008] Generate business inspection alarm information, the business inspection alarm information including the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, and a first processing status indicating that the task is not processed;

[0009] Sending the service inspection alarm information to the notification group address;

[0010] Acquire a start processing message indicating that the online fault is being processed, wherein the start processing message is obtained by operating the first processing state;

[0011] Generate business processing progress information, the business processing progress information including the name of the test task, the test time, the online fault, the person in charge identifier, the person identifier of the person who handles the online fault, and a second processing state representing the processing in progress; the person identifier is at least one person identifier among the person in charge identifiers;

[0012] Sending the business processing progress information to the notification group address;

[0013] Obtaining a processing completion message indicating that the online fault has been processed;

[0014] Generate processing completion information, the processing completion information including the name of the test task, the test time, the online fault, the person in charge identifier, the processor identifier, and a third processing status indicating that the processing has been completed;

[0015] Send the processing completion information to the notification group address.

[0016] In a possible implementation, the target production inspection task includes multiple test cases; and the step of determining an online fault in the online environment based on the running result of the target production inspection task includes:

[0017] For each of the test cases, if the running result of the test case does not match the expected result of the test case, it is determined that the online fault exists.

[0018] In a possible implementation, if the responsible person identifiers corresponding to different test cases are not exactly the same, the step of searching for the target notification information corresponding to the target production inspection task from the preset correspondence between the production inspection task and the notification information includes:

[0019] From the preset correspondence between test cases and notification information, the target notification information corresponding to each of the plurality of test cases included in the target production inspection task is searched.

[0020] In one possible implementation, the processing completion message is obtained by operating the second processing state, or the processing completion message is obtained by executing the target production inspection task again and the operation result of the target production inspection task does not have an online fault.

[0021] In one possible implementation, the method for constructing the production inspection task includes:

[0022] In response to the operation of creating a production inspection task, the control displays the use case sources, which include infrastructure, APIFOX, Jenkins, and cloud testing platform;

[0023] Identify target sources from the stated use case sources;

[0024] Controlling the display of a first user interface corresponding to the target source;

[0025] Obtaining a production inspection task identifier through the first user interface;

[0026] Select one or more test cases from the test case set corresponding to the target source through the first user interface;

[0027] Obtaining a first execution order of the one or more test cases through the first user interface;

[0028] A correspondence between the production inspection task identifier, the first execution order, and the one or more test cases is constructed to obtain the production inspection task.

[0029] In one possible implementation, the method for constructing the test case includes:

[0030] In response to an operation of creating a test case, controlling display of a second user interface;

[0031] Obtaining a test case identifier and an operating environment through the second user interface;

[0032] obtaining, through the second user interface, a plurality of use case steps and a second execution order between the plurality of use case steps;

[0033] A correspondence between the test case identifier, the operating environment, the multiple use case steps, and the second execution order is constructed to obtain the test case.

[0034] A second aspect of the present application provides a production inspection device for an online environment, comprising:

[0035] The first determination module is used to determine the online fault of the online environment based on the running results of the target production inspection task;

[0036] The first search module is used to search for target notification information corresponding to the target production inspection task from the preset correspondence between production inspection tasks and notification information, wherein the target notification information includes a notification group address and a person-in-charge identifier; the notification number of the person-in-charge with the person-in-charge identifier is located in the notification group with the notification group address;

[0037] A first generating module is configured to generate business inspection alarm information, wherein the business inspection alarm information includes an identifier of the target production inspection task, a test time, the online fault, an identifier of the person in charge, and a first processing status indicating that the task is not processed;

[0038] A first sending module is used to send the service inspection alarm information to the notification group address;

[0039] A first acquisition module is configured to acquire a processing start message indicating that the online fault is being processed, wherein the processing start message is obtained by operating the first processing state;

[0040] A second generating module is configured to generate business processing progress information, wherein the business processing progress information includes the name of the test task, the test time, the online fault, the responsible person identifier, the handler identifier of the handler who handles the online fault, and a second processing state representing the processing progress; the handler identifier is at least one of the responsible person identifiers;

[0041] A second sending module is used to send the business processing progress information to the notification group address;

[0042] A second acquisition module is used to obtain a processing completion message indicating that the online fault has been processed;

[0043] A third generating module is configured to generate processing completion information, wherein the processing completion information includes the name of the test task, the test time, the online fault, the person in charge identifier, the processor identifier, and a third processing status indicating that the processing has been completed;

[0044] The third sending module is used to send the processing completion information to the notification group address.

[0045] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the production inspection method in an online environment of the above-mentioned first aspect or any implementation method of the first aspect.

[0046] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0047] The memory is used to store computer programs;

[0048] The processor is used to execute the computer program so that the electronic device can implement the production inspection method in an online environment of the above-mentioned first aspect or any implementation method of the first aspect.

[0049] In a fifth aspect, the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the production inspection method of the online environment of the above-mentioned first aspect or any implementation method of the first aspect.

[0050] By means of the above technical solution, the present application provides a production inspection method for an online environment, which determines the online fault of the online environment through the running results of the target production inspection task. Business inspection alarm information, business processing in progress information, and processing completion information can be generated for the processing progress of the online fault respectively; wherein, the progress of the business inspection alarm information is unprocessed, the progress of the business processing in progress information is processing in progress, and the progress of the processing completion information is restored; the business inspection alarm information, business processing in progress information, and processing completion information can be displayed in the same notification group, and the processing progress can be displayed. This allows other people in the same notification group to see the processing progress of the online fault. The present application standardizes and automates the alarm processing process. Online faults are assigned through the identification of responsible persons, making alarm processing efficient. The present application allows operation and maintenance personnel to know the occurrence of the fault in the first time, thereby reducing the fault response time. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0052] Figure 1 A schematic diagram of the system architecture provided for this application;

[0053] Figure 2 This is a schematic diagram of an optional hardware structure of a first terminal 100 provided in this application;

[0054] Figure 3 A schematic diagram of the structure of a server 200 provided in this application;

[0055] Figure 4 A flowchart of a production inspection method for an online environment provided by this application;

[0056] Figure 5 A schematic diagram of a method of representing the service inspection alarm information provided by this application;

[0057] Figure 6 A schematic diagram of an implementation of the alarm processing interface provided by this application;

[0058] Figure 7 A schematic diagram of a method of representing information during business processing provided by this application;

[0059] Figure 8 A schematic diagram of another implementation of the alarm processing interface provided by this application;

[0060] Figure 9A schematic diagram showing a method of representing the processing completion information provided by this application;

[0061] Figure 10 A schematic diagram of the user interface for creating a production inspection task provided for this application;

[0062] Figure 11 A schematic diagram of an implementation of the first user interface provided in this application;

[0063] Figure 12 A schematic diagram of the third user interface provided by this application;

[0064] Figure 13 A schematic diagram of another implementation of the first user interface provided in this application;

[0065] Figure 14 A schematic diagram of the timing window provided for this application;

[0066] Figure 15 A schematic diagram of the user interface for creating test cases provided for this application;

[0067] Figure 16 A schematic diagram of the second user interface portion provided by this application;

[0068] Figure 17 A schematic diagram of the user interface for setting test steps provided for this application;

[0069] Figure 18 A schematic diagram of the user interface for setting up a notification group provided by this application;

[0070] Figure 19 A schematic diagram of the structure of an online production inspection device provided in this application;

[0071] Figure 20 Schematic diagram of the structure of the electronic device provided for this application DETAILED DESCRIPTION

[0072] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.

[0073] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0074] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0075] The online environment, also known as the production environment or deployment environment, is the environment where applications actually run and provide services. In this environment, applications face real user traffic and data and require key features such as high availability and scalability. The following are some of the main components of the online environment:

[0076] Servers and hardware resources: Online environments require servers to host applications. These servers can be physical servers or cloud servers. They need sufficient computing power, memory, and storage resources to handle user requests.

[0077] Network infrastructure: The online environment relies on stable network connections, including load balancers, DNS (Domain Name System) services, and CDNs (Content Delivery Networks), to ensure that users can quickly access applications and handle high traffic.

[0078] Database system: Most applications require a database to store and retrieve data. A production environment will include a database server, which could be a relational database like MySQL, PostgreSQL, or a non-relational database like MongoDB, Redis, etc.

[0079] Middleware and infrastructure: Online environments may use various middleware to support the operation of applications, such as message queues (such as Kafka), caching systems (such as Memcached), search engines (such as Elasticsearch), etc.

[0080] Application Service: The online environment includes the code for the actual running application, which is optimized and configured to ensure stability and performance under production conditions.

[0081] Monitoring and logging systems: To ensure the stability and performance of the online environment, it is necessary to integrate monitoring tools to track application status in real time, and a logging system to record events and error information to facilitate problem troubleshooting.

[0082] User Interface and Application Programming Interface (API): The online environment provides a user interface for end-user interaction and an API for integration with other systems and applications.

[0083] Building and managing an online environment is a complex process, involving multiple aspects, from code deployment and resource management to performance optimization and security assurance. Proper configuration and management of the online environment is crucial to ensuring application reliability and user experience.

[0084] In summary, online environments are extremely complex, potentially distributed across different physical locations and even across different cloud service providers. This complexity increases the difficulty of monitoring and maintenance, as any single point of failure can impact the stability and performance of the entire system.

[0085] In related technologies, alarm systems are decentralized, with each system or service having its own alarm mechanism. This fragmentation forces operations and maintenance personnel to monitor multiple alarm sources, increasing the risk of information overload and making it easy for important alarms to be overlooked. Furthermore, alarm formats may differ between systems, further complicating alarm processing.

[0086] To ensure service quality in online environments, enterprises typically use multiple use case sources. These sources often have different configuration requirements and user interfaces, requiring operations personnel to spend significant time learning and maintaining them. Furthermore, configuration complexity increases with the introduction of new use case sources.

[0087] In related technologies, the alarm handling process is imperfect and, in many cases, lacks standardization and automation, resulting in extended alarm response times. Alarm handling often relies on manual operations, which is not only inefficient but also prone to errors. The lack of a clear responsibility allocation mechanism makes alarm handling chaotic and inefficient.

[0088] Due to these factors, fault response and handling become complex and difficult. Operations personnel must switch between multiple systems and use-case sources to collect and analyze fault information. This manual and fragmented approach is not only time-consuming but also prone to missing the optimal time to address the fault, leading to a wider impact of the fault.

[0089] The efficiency of production inspections is directly related to how quickly an enterprise can identify and resolve problems, as well as restore service. Inefficient inspection processes mean that problems may be discovered late, impacting service continuity and customer satisfaction. Furthermore, inefficient inspections can lead to a waste of resources, including human resources, time, and financial resources.

[0090] In light of the above issues, this application proposes an integrated solution that unifies alarm configuration, simplifies the management of use case sources, improves fault response speed, and ensures the timeliness and effectiveness of online fault handling. This solution should provide real-time monitoring, automated alarms, clear responsibility allocation, and effective fault handling tracking to improve the overall efficiency and effectiveness of production inspections.

[0091] The technical solution of this application is described in detail below.

[0092] See also Figure 1 , Figure 1 A schematic diagram of a system architecture is shown. The system may include a first terminal 100, a server 200, and a second terminal 300. The server 200 may include one or more servers ( Figure 1 (The example includes a server, and the server 200 is used as an example for explanation), and the server 200 can provide the method provided in the embodiment of the present application for one or more first terminals.

[0093] Exemplarily, the online environment includes one or more servers 200. The number of servers 200 can be one or more. The geographical locations of different servers 200 may be the same or different.

[0094] Illustratively, the operating environments of different servers 200 may be different or the same.

[0095] It is understandable that the production inspection task can be run in the server 200.

[0096] Among them, the first terminal 100 may be installed with an application or a web page, and the above application and web page may provide an interface. The first terminal 100 may receive relevant parameters entered by the user on the interface, for example, determine the instruction to execute the production inspection task, and send the above parameters to the server 200. In an optional implementation, the server 200 may obtain the running result of the production inspection task based on the received parameters, and return the running result to the first terminal 100, so that the first terminal 100 executes the production inspection method of the online environment provided in the embodiment of the present application. In an optional implementation, the server 200 may obtain the running result of the production inspection task based on the received parameters, and execute the production inspection method of the online environment provided in the embodiment of the present application, and feed back the final result to the first terminal 100.

[0097] Exemplarily, the first terminal 100 may send corresponding information to a notification group, thereby enabling operation and maintenance personnel in the notification group to perform online fault repair.

[0098] For example, the notification group can be a WeChat group, a QQ group, a Fetion group, a Feishu group, or a DingTalk group. The application corresponding to the notification group can be run on the second terminal 300. For example, there are multiple second terminals 300.

[0099] Next describe Figure 1 The product form of the first terminal 100;

[0100] The first terminal 100 in the embodiment of the present application can be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and the embodiment of the present application does not impose any restrictions on this.

[0101] Figure 2 A schematic diagram of an optional hardware structure of the first terminal 100 is shown.

[0102] refer to Figure 2 As shown, the first terminal 100 may include a radio frequency unit 110, a memory 120, an input unit 130, a display unit 140, a camera 150 (optional), an audio circuit 160 (optional), a speaker 161 (optional), a microphone 162 (optional), an earphone jack 163 (optional), a processor 170, an external interface 180, a power supply 190 and other components. Those skilled in the art will understand that Figure 2 This is merely an example of the first terminal and does not constitute a limitation on the first terminal. The first terminal may include more or fewer components than shown in the figure, or a combination of certain components, or different components.

[0103] The input unit 130 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the first terminal. Specifically, the input unit 130 may include a touch screen 131 (optional) and / or other input devices 132. The touch screen 131 can collect user touch operations on or near it (for example, operations performed on or near the touch screen using a finger, joint, stylus, or any other suitable object) and drive corresponding connected devices according to a pre-set program. The touch screen can detect user touch actions on the touch screen, convert the touch actions into touch signals and transmit them to the processor 170, and can receive and execute commands sent by the processor 170; the touch signals include at least touch point coordinate information. The touch screen 131 can provide an input interface and an output interface between the first terminal 100 and the user. In addition, touch screens can be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch screen 131, the input unit 130 may also include other input devices. Specifically, the other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, and the like.

[0104] Among them, the input device 132 can receive input data and the like.

[0105] The display unit 140 may be used to display information input by the user or provided to the user, various menus of the first terminal 100, interactive interfaces, file display, and / or playback of any multimedia file. In the embodiment of the present application, the display unit 140 may be used to display interfaces, processing results, etc.

[0106] Memory 120 can be used to store instructions and data. It primarily includes an instruction storage area and a data storage area. The data storage area can store various data, such as multimedia files and text. The instruction storage area can store software units such as the operating system, applications, and instructions required for at least one function, or subsets or extensions thereof. It may also include non-volatile random access memory (RAM). It provides processor 170 with management functions for the hardware, software, and data resources within the computing and processing device, supporting control software and applications. It is also used to store multimedia files and running programs and applications.

[0107] The processor 170 is the control center of the first terminal 100. It connects all components of the first terminal 100 using various interfaces and circuits. By executing instructions stored in the memory 120 and accessing data stored in the memory 120, it performs various functions of the first terminal 100 and processes data, thereby providing overall control of the first terminal device. Optionally, the processor 170 may include one or more processing units. Preferably, the processor 170 may integrate an application processor and a modem processor, with the application processor primarily processing the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into the processor 170. In some embodiments, the processor and memory may be implemented on a single chip; in some embodiments, they may be implemented on separate chips. The processor 170 may also be used to generate corresponding operational control signals and send them to corresponding components of the computing and processing device. It may also read and process data in the software, particularly the data and programs in the memory 120, to enable the various functional modules therein to perform their corresponding functions, thereby controlling the corresponding components to operate as instructed.

[0108] Among them, the memory 120 can be used to store software codes related to the production inspection method of the online environment, the processor 170 can execute the steps of the production inspection method of the online environment, and can also schedule other units (such as the above-mentioned input unit 130 and display unit 140) to implement corresponding functions.

[0109] The RF unit 110 (optional) can be used to send and receive information or receive and send signals during a call. For example, after receiving downlink information from the base station, it is passed to the processor 170 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF unit 110 can also communicate with network devices and other devices via wireless communication. This wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0110] In this embodiment of the present application, the radio frequency unit 110 can send data to the server 200 and receive processing results sent by the server 200.

[0111] It should be understood that the radio frequency unit 110 is optional and can be replaced by other communication interfaces, such as a network port.

[0112] The first terminal 100 also includes a power supply 190 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 170 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0113] The first terminal 100 further includes an external interface 180 , which may be a standard Micro USB interface or a multi-pin connector, and may be used to connect the first terminal 100 to other devices for communication, or to connect a charger to charge the first terminal 100 .

[0114] Although not shown, the first terminal 100 may also include a flash, a wireless fidelity (WiFi) module, a Bluetooth module, sensors with different functions, etc., which will not be described in detail here. Some or all of the methods described below can be applied to Figure 2 In the first terminal 100 shown.

[0115] Next describe Figure 1 The product form of the server 200;

[0116] Figure 3 A structural diagram of a server 200 is provided, such as Figure 3 As shown, the server 200 includes a bus 201, a processor 202, a communication interface 203, and a memory 204. The processor 202, the memory 204, and the communication interface 203 communicate with each other via the bus 201.

[0117] The bus 201 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0118] The processor 202 may be any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0119] The memory 204 may include volatile memory, such as random access memory (RAM). The memory 204 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0120] The memory 204 may be used to store software codes related to the production inspection method of the online environment, and the processor 202 may execute the steps of the production inspection method of the online environment of the chip, and may also schedule other units to implement corresponding functions.

[0121] It should be understood that the above-mentioned first terminal 100 and server 200 can be centralized or distributed devices, and the processors in the above-mentioned first terminal 100 and server 200 (such as processor 170 and processor 202) can be hardware circuits (such as application specific integrated circuit (ASIC), field-programmable gate array (FPGA), general-purpose processor, digital signal processor (DSP), microprocessor or microcontroller, etc.), or a combination of these hardware circuits. For example, the processor can be a hardware system with an instruction execution function, such as a CPU, DSP, etc., or a hardware system without an instruction execution function, such as an ASIC, FPGA, etc., or a combination of the above-mentioned hardware systems without an instruction execution function and hardware systems with an instruction execution function.

[0122] In order to solve the above problems, the embodiment of the present application provides a production inspection method for an online environment. The production inspection method for an online environment of the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0123] Reference Figure 4 , Figure 4 A flowchart of a production inspection method for an online environment provided in an embodiment of the present application is shown as follows: Figure 4 As shown, a production inspection method for an online environment provided by an embodiment of the present application may include steps S401 to S410, and these steps are described in detail below.

[0124] Step S401: determining an online fault in the online environment based on the running result of the target production inspection task.

[0125] It is understandable that the target production inspection task can be executed on the server 200, and the operation result can be obtained through the server 200; it is understandable that the online fault can be determined based on the operation result.

[0126] It is understandable that corresponding production inspection tasks can be set based on the online faults that need to be detected.

[0127] Production inspections are a series of checks and tests performed regularly in the online environment to ensure its normal operation and performance. The purpose of production inspections is to proactively identify and resolve potential issues, minimizing the impact of online environment failures on the business.

[0128] Exemplary online fault types include but are not limited to the following:

[0129] Code Bug: There is a problem with the code logic of the online environment.

[0130] Resource configuration errors: Resource configuration errors in the online environment, such as unreasonable startup sequence, initialization script errors, etc.

[0131] System-level software bugs: Bugs in the operating system, third-party libraries, and software used in the technical architecture that are triggered in special scenarios lead to failures.

[0132] Network failures: These include public network congestion, packet loss, dedicated line problems, network equipment failures, IP (Internet Protocol Address) attacks (including DNS attacks), IP blocking, domain name blocking, and network software bugs.

[0133] Security issues: attacks, exploitation of vulnerabilities, etc.

[0134] Local failure: Problems caused by failures in external units such as the ISP (Internet Service Provider), root domain name service, electricity, air conditioning, and optical cables.

[0135] Failure of third-party partner companies or interfaces: Failure of third-party companies or interfaces that the project depends on.

[0136] CPU (Central Processing Unit) issues: These include business logic issues (dead loops), frequent garbage collection (GC), and excessive context switching.

[0137] Disk problem: Low disk space or disk performance issues.

[0138] Memory issues: including out of memory (OOM), Stack Overflow, memory leaks, etc.

[0139] Network issues: including timeouts, TCP queue overflows, RST (Reset Exception) exceptions, TIME_WAIT, and CLOSE_WAIT issues.

[0140] Exemplarily, the target production inspection task includes multiple test cases. The step of determining an online fault in the online environment based on the execution result of the target production inspection task includes: for each test case, if the execution result of the test case does not match the expected result of the test case, determining that the online fault exists. Accordingly, steps S402 to S410 may be executed for each test case.

[0141] Step S402: searching for target notification information corresponding to the target production inspection task from the preset correspondence between production inspection tasks and notification information.

[0142] The target notification information includes a notification group address and a person-in-charge identifier; the communication signal of the person-in-charge with the person-in-charge identifier is located in the notification group with the notification group address.

[0143] Exemplarily, the notification group may be a WeChat group, a QQ group, a Fetion group, a Feishu group, or a DingTalk group.

[0144] Exemplarily, the notification group address may be a URL (Uniform Resource Locator) of the notification group.

[0145] Exemplarily, the person-in-charge identification includes the name of the person-in-charge and / or the employee number of the person-in-charge.

[0146] For example, if the notification group is a WeChat group, the communication number is the WeChat number; if the notification group is a QQ group, the communication number is the QQ number; if the notification group is a Fetion group, the communication number is the Fetion number; if the notification group is a Feishu group, the communication number is the Feishu number; if the notification group is a DingTalk group, the communication number is the DingTalk number.

[0147] In an optional implementation, a production inspection task includes multiple test cases; if the notification information corresponding to the multiple test cases is the same, then the "correspondence between the production inspection task and the notification information" is the "correspondence between the production inspection task and the notification information".

[0148] In an optional implementation, a production inspection task includes multiple test cases; the notification information corresponding to each of the multiple test cases can be the same or different. The "correspondence between production inspection tasks and notification information" is then the "correspondence between test cases and notification information." In this case, step S402 searches for the target notification information corresponding to each of the multiple test cases included in the target production inspection task from the preset correspondence between test cases and notification information.

[0149] A test case is a set of conditions used in software testing, including test input, execution conditions, test environment, and expected results. It is used to verify whether specific functions or modules in the online environment work as expected.

[0150] Step S403: Generate business inspection alarm information, the business inspection alarm information includes the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, and a first processing status indicating that the task is not processed.

[0151] Step S404: Send the service inspection alarm information to the notification group address.

[0152] Exemplarily, for each test case, a business inspection alarm message may be generated; in this case, the identifier of the target production inspection task may be the test case name of the test case.

[0153] In order for those skilled in the art to better understand the service inspection alarm information provided by the embodiments of the present application, the following examples are given to illustrate.

[0154] like Figure 5 The figure shows a schematic diagram of a method of representing the service inspection alarm information provided in an embodiment of the present application.

[0155] Assume that the notification group is a DingTalk group, the second terminal 300 has a DingTalk application installed, and the DingTalk account logged in by the DingTalk application running on the second terminal is in the DingTalk group. Then, the service inspection alarm information displayed by the second terminal 300 is as follows: Figure 5 shown.

[0156] like Figure 5 As shown, the test case name is "Production Business Inspection Alarm: 739"; "Occurrence Time" is the test time of 2024-11-28 19:07:54; and the alarm content is "Online Failure". For example, Figure 5 The alarm content is in a collapsed state. If you click "Click to view details", the alarm content can be expanded, and the operation and maintenance personnel can see the detailed alarm content.

[0157] For example, Figure 5 "De-process" or "Silent processing" can be the first processing state.

[0158] For example, Figure 5 In the example, "Zhang San" is the person in charge. "@" is a special prompt symbol for Zhang San. For example, the special prompt symbols for different notification groups may be different or the same.

[0159] For example, the service inspection alarm information may also include the number of abnormalities and the inspection scenario. For example, the inspection scenario is a description of the target production inspection task, so that the operation and maintenance personnel can determine how to solve the online fault based on the inspection scenario.

[0160] Step S405: Acquire a start processing message indicating that the online fault is being processed, wherein the start processing message is obtained by operating the first processing state.

[0161] Exemplarily, in response to an operation in the first processing state, an alarm processing interface may be displayed. A start processing message may be obtained through the alarm processing interface. This will be described below with reference to examples.

[0162] like Figure 6, which is a schematic diagram of an implementation method of the alarm processing interface provided in an embodiment of the present application.

[0163] Exemplarily, after clicking the first processing state "Go to Process", the alarm processing interface can be displayed on the right; if the "Start Processing" button in the alarm processing interface is clicked, a start processing message is generated.

[0164] For example, detailed alarm information can also be viewed through the "Alarm Details" in the alarm processing interface to assist operation and maintenance personnel in determining solutions to resolve online failures.

[0165] Step S406: Generate business processing progress information, which includes the name of the test task, the test time, the online fault, the person in charge ID, the person in charge ID of the person who handles the online fault, and a second processing status representing the processing in progress; the person in charge ID is at least one person in charge ID among the person in charge IDs.

[0166] For example, there may be multiple responsible persons; different responsible persons may have different responsible persons. If a responsible person AA in the notification group manipulates a service inspection alarm, the person who handles it will be the responsible person AA. For example, multiple people may be allowed to manipulate service inspection alarms simultaneously or sequentially, meaning there may be multiple persons who handle the information. For example, only one person may be allowed to manipulate service inspection alarms, meaning there will be only one person who handles the information.

[0167] Step S407: Send the business processing progress information to the notification group address.

[0168] like Figure 7 , which is a schematic diagram of a method of representing information during business processing provided in an embodiment of the present application.

[0169] If the target production inspection task is identified by the test case name, Figure 7 This example uses the test case identified as "Production Business Inspection Alarm: 678" as an example. If "Production Business Inspection Alarm: 678" is unhandled, the business inspection alarm message is 71. If "Production Business Inspection Alarm: 678" is being handled, the business processing information is 72.

[0170] By comparing the service inspection alarm information 71 and the service processing ongoing information 72 , it can be seen that there is a difference between the service inspection alarm information and the service processing ongoing information.

[0171] Figure 7 "Processing" is the second processing status. Figure 7 The "Handler: Li Si" in the . Figure 7It can be seen that Li Si is one of the multiple responsible persons (Li Si and Zhang Jiu).

[0172] Step S408: Obtain a processing completion message indicating that the online fault has been processed.

[0173] In an optional implementation, the processing completion message is obtained by operating the second processing state.

[0174] For example, in response to the operation for the second processing state, an alarm processing interface may be displayed. A processing completion message may be obtained through the alarm processing interface. This will be described below with reference to examples.

[0175] like Figure 8 , which is a schematic diagram of another implementation method of the alarm processing interface provided in an embodiment of the present application.

[0176] For example, after clicking the second processing status "Processing", the alarm processing interface can be displayed on the right; if the "Restored" button in the alarm processing interface is clicked, a processing completion message is generated.

[0177] For example, the corresponding alarm cause can also be selected through the "Alarm Cause Assignment" in the alarm processing interface, so that when similar alarm causes occur, the operation and maintenance personnel can be assisted in determining the solution to solve the online fault.

[0178] In an optional implementation, the processing completion message is obtained by re-executing the target production inspection task and the running result of the target production inspection task does not contain an online fault. Exemplarily, the processing completion message is obtained by re-executing the target production inspection task and the running result of the target production inspection task matches the expected result.

[0179] It is understandable that the target production inspection task is to run once every preset time; if the operation and maintenance personnel have repaired the online fault and did not click Figure 8 Click the "Recovered" button in the alarm processing interface shown. After the target production inspection task is run again, if the running result of the test case matches the expected result of the test case, the online fault is considered to have been resolved, and the processing completion message is obtained.

[0180] Step S409: Generate processing completion information, which includes the name of the test task, the test time, the online fault, the person in charge identifier, the processor identifier, and a third processing status indicating that the processing has been completed.

[0181] Step S410: Send the processing completion information to the notification group address.

[0182] like Figure 9 , which is a schematic diagram of a method of representing the processing completion information provided in an embodiment of the present application.

[0183] If the target production inspection task is identified by the test case name, Figure 9 The test case identified as "production business inspection alarm: 678" is used as an example for description. After the online fault corresponding to "production business inspection alarm: 678" has been processed, the third processing status of the processing completion information 91 may be "recovered".

[0184] Exemplarily, the processing completion information also includes: recovery time.

[0185] Combine Figures 5 to 9 As can be seen, service inspection alarm information, ongoing service processing information, and completed service processing information can be displayed in the same notification group, and the processing progress can be displayed. This allows others in the same notification group to see the progress of the online fault handling. This application standardizes and automates the alarm handling process. Online faults are assigned by responsible person identification, making alarm handling more efficient.

[0186] The embodiment of the present application provides a production inspection method for an online environment, which determines the online fault of the online environment through the running results of the target production inspection task. Business inspection alarm information, business processing in progress information, and processing completion information can be generated for the processing progress of the online fault respectively; wherein, the progress of the business inspection alarm information is unprocessed, the progress of the business processing in progress information is processing in progress, and the progress of the processing completion information is restored; the business inspection alarm information, business processing in progress information, and processing completion information can be displayed in the same notification group, and the processing progress can be displayed. This allows other people in the same notification group to see the processing progress of the online fault. The present application standardizes and automates the alarm processing process. Online faults are assigned through the person in charge identification, making alarm processing efficient. The present application allows operation and maintenance personnel to know the occurrence of the fault in the first time, thereby reducing the fault response time.

[0187] The following describes a method for constructing a production inspection task. The method includes the following steps A1 to A7 during implementation.

[0188] Step A1: In response to the operation of creating a production inspection task, control the display of use case sources, which include infrastructure, APIFOX, Jenkins, and cloud testing platform.

[0189] Exemplarily, different sources of use cases correspond to different test case sets.

[0190] like Figure 10As shown, it is a schematic diagram of the user interface for creating a production inspection task provided in an embodiment of the present application.

[0191] Figure 10 The following table shows the identification of multiple production inspection tasks that have been created. Figure 10 In the example, the identifier of the production inspection task is used as the task name.

[0192] For example, the operation of creating a production inspection task is to click the "Add Task" button. After clicking the "Add Task" button, you can Figure 10 (a) becomes 10 Figure (b).

[0193] The following describes the sources of these four use cases.

[0194] Infrastructure in testing refers to the hardware and software environment that supports test execution, including servers, network equipment, databases, test frameworks, etc. These infrastructures provide the necessary operating environment and resources for testing, ensuring that the test can proceed smoothly.

[0195] APIFOX is a collaborative platform that integrates API documentation, debugging, mocking, and testing. It supports multiple protocol interfaces, including HTTP (HyperText Transfer Protocol), HTTPS (Hypertext Transfer Protocol Secure), WebSocket, and TCP (Transmission Control Protocol). It also automatically generates code and supports multiple languages ​​and frameworks. APIFOX can serve as a source of test cases, providing interface testing capabilities and test data management, allowing testers to design and execute API test cases based on APIFOX.

[0196] Jenkins is an open-source automation server that can be used to automate various tasks, including building, testing, and deploying software projects. Given a source of test cases, Jenkins can configure automated testing processes, execute test scripts, and generate test reports. Through the continuous integration / continuous deployment (CI / CD) process, Jenkins helps teams automate test case execution and improve testing efficiency.

[0197] Cloud testing platforms offer cloud-based services that support the execution and management of testing activities. These platforms typically provide capabilities such as instant deployment of test environments, test data management, and analysis of run results. Cloud testing platforms can serve as a source of test cases because they provide a test execution environment and tools, enabling testers to design, execute, and monitor test cases in a cloud environment.

[0198] These four sources provide different ways of generating and managing test cases, covering everything from infrastructure support to specific test execution tools, providing testers with a comprehensive testing solution.

[0199] Step A2: Identify target sources from the use case sources.

[0200] like Figure 10 As shown, it is assumed that the target source identified is the infrastructure.

[0201] Step A3: controlling the display of a first user interface corresponding to the target source.

[0202] like Figure 11 , which is a schematic diagram of an implementation method of the first user interface provided in an embodiment of the present application.

[0203] For example, if the production inspection task is identified as the task name, the operation and maintenance personnel can enter the "Task Name" in the first user interface and select the notification group through "DingTalk Notification".

[0204] Step A4: Obtain a production inspection task identifier through the first user interface.

[0205] Step A5: Select one or more test cases from the test case set corresponding to the target source through the first user interface.

[0206] Combine Figure 11 For example, click Figure 11 The "Add Use Case" button in the test case display 1101, thereby selecting the type of test case. Exemplarily, the types of test cases include but are not limited to: basic use cases and scenario use cases.

[0207] For example, if you click on the scenario use case, the third user interface can be displayed; Figure 12 , which is a schematic diagram of the third user interface provided in an embodiment of the present application.

[0208] pass Figure 12 It can be seen that Figure 12 The left side shows the storage path of the test case. Click the corresponding storage path to Figure 12 The test cases stored in the storage path can be displayed on the right. Figure 12 In the test case, "Use Case Name" is used to indicate the test case identifier of the test case. Operation and maintenance personnel can select one or more test cases from it.

[0209] Step A6: Obtain a first execution order of the one or more test cases through the first user interface.

[0210] pass Figure 12 After selecting one or more test cases, you can get Figure 13 The user interface shown in the figure can be Figure 13 The illustrated “execution order” determines the first execution order of the multiple test cases as concurrent execution or sequential execution.

[0211] For example, it can be achieved by Figure 13 The "Scheduled Time" determines the time interval and start time for executing production inspection tasks.

[0212] For example, you can start Figure 13 Click "Timer" to display the "Timer" Figure 14 The timing window shown. Figure 14 , which is a schematic diagram of the timing window provided in an embodiment of the present application.

[0213] Can be achieved through Figure 14 The timing window shown determines the time interval and start time for executing the production inspection task.

[0214] Step A7: Construct a correspondence between the production inspection task identifier, the first execution sequence, and the one or more test cases to obtain the production inspection task.

[0215] Combine Figure 10 It can be seen that in order to ensure the service quality of the online environment, this application uses multiple use case sources. The configuration requirements and user interfaces of different use case sources are the same, which eliminates the need for operation and maintenance personnel to spend a lot of time learning and maintaining use case sources, reducing the configuration complexity of introducing new use case sources.

[0216] This application brings together different alarm systems with the same alarm mechanism. For details, please refer to steps S401 to S410. Alarm information from different alarm systems (such as business inspection alarm information, business processing in progress information, and processing completion information) will be sent to the same notification group if the notification information is the same, and the alarm information will not be dispersed. Operation and maintenance personnel do not need to monitor multiple alarm sources, but only need to monitor the notification group, which reduces the risk of information overload and is not easy to ignore important alarms. The alarm format between different systems is the same, which can be seen in Figures 5 to 9 As shown, the complexity of alarm processing is reduced.

[0217] The following describes a method for constructing a test case. The method includes the following steps B1 to B4 during implementation.

[0218] Step B1: In response to the operation of creating a test case, controlling the display of a second user interface.

[0219] like Figure 15, which is a schematic diagram of a user interface for creating a test case provided in an embodiment of the present application.

[0220] For example, it can be achieved by Figure 15 Click the "Operation" button of an existing test case to modify the existing test case.

[0221] For example, clicking “Add Test Case” is an operation of creating a test case.

[0222] like Figure 16 , which is a schematic diagram of the second user interface part provided in an embodiment of the present application.

[0223] For example, by clicking Figure 16 The "Step" button in the test case can add a test step; a test case includes one or more test steps. Exemplarily, the second user interface can also include the URL of each test step and the waiting delay of each test step. Exemplarily, the second execution order of the multiple test steps is based on the step numbers corresponding to the multiple test steps (such as Figure 16 1, 2, 3) are sorted by smallest arrival.

[0224] For example, it can be achieved by Figure 17 Set the test steps. Figure 17 As shown, it is a schematic diagram of the user interface for setting test steps provided in an embodiment of the present application.

[0225] Step B2: Obtain the test case identifier and the operating environment through the second user interface.

[0226] Step B3: Obtain multiple use case steps and a second execution order between the multiple use case steps through the second user interface.

[0227] For example, the second execution order is Figure 16 The step numbers corresponding to multiple test steps in Figure 16 1, 2, 3) in the list are sorted by smallest order.

[0228] Step B4: Construct a correspondence between the test case identifier, the operating environment, the multiple use case steps, and the second execution order to obtain the test case.

[0229] In an optional implementation, a production inspection task includes multiple test cases; if the notification information corresponding to the multiple test cases is the same, then the "correspondence between the production inspection task and the notification information" is the "correspondence between the production inspection task and the notification information".

[0230] It is understandable that through Figure 11You can set the notification group corresponding to the production inspection task, that is, you can select the notification group ID in the "DingTalk Notification" selection box. Figure 18 , which is a schematic diagram of a user interface for setting a notification group provided in an embodiment of the present application.

[0231] For example, the notification group identifier can be represented by "notification name". Figure 18 Set the notification ID or URL of the notification group. Figure 18 In the input box corresponding to "Notify person (@)", you can enter the person in charge's ID. Figure 18 and Figure 11 A "correspondence between production inspection tasks and notification information" has been established.

[0232] In an optional implementation, a production inspection task includes multiple test cases; the notification information corresponding to each of the multiple test cases can be the same or different. The "correspondence between production inspection tasks and notification information" is then the "correspondence between test cases and notification information." In this case, step S402 searches for the target notification information corresponding to each of the multiple test cases included in the target production inspection task from the preset correspondence between test cases and notification information.

[0233] Exemplarily, notification information corresponding to the test case may be set during the process of creating the test case.

[0234] The above describes a production inspection method for an online environment provided by an embodiment of the present application. The following describes a device for executing the above-mentioned production inspection method for an online environment.

[0235] See also Figure 19 , Figure 19 This is a schematic diagram of the structure of an online production inspection device provided in an embodiment of the present application. Figure 19 As shown, the production inspection device of the online environment includes:

[0236] The first determining module 1901 is configured to determine an online fault in the online environment based on the running result of the target production inspection task;

[0237] The first search module 1902 is configured to search for target notification information corresponding to the target production inspection task from a preset correspondence between production inspection tasks and notification information, wherein the target notification information includes a notification group address and a person-in-charge identifier; the notification information of the person-in-charge having the person-in-charge identifier is located in the notification group having the notification group address;

[0238] The first generating module 1903 is configured to generate service inspection alarm information, wherein the service inspection alarm information includes the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, and a first processing status indicating that the task is not processed;

[0239] The first sending module 1904 is used to send the service inspection alarm information to the notification group address;

[0240] A first acquisition module 1905 is configured to acquire a processing start message indicating that the online fault is being processed, wherein the processing start message is acquired by operating the first processing state;

[0241] The second generating module 1906 is configured to generate business processing progress information, wherein the business processing progress information includes the name of the test task, the test time, the online fault, the responsible person identifier, the handler identifier of the handler who handles the online fault, and a second processing status representing the processing progress; the handler identifier is at least one of the responsible person identifiers;

[0242] The second sending module 1907 is used to send the business processing progress information to the notification group address;

[0243] The second acquisition module 1908 is configured to acquire a processing completion message indicating that the online fault has been processed;

[0244] The third generating module 1909 is configured to generate processing completion information, wherein the processing completion information includes the name of the test task, the test time, the online fault, the person in charge identifier, the processor identifier, and a third processing status indicating that the processing has been completed;

[0245] The third sending module 1910 is used to send the processing completion information to the notification group address.

[0246] In an optional implementation, the target production inspection task includes multiple test cases; the first determination module includes:

[0247] The determining unit is configured to determine, for each of the test cases, if the running result of the test case does not match the expected result of the test case, that the online fault exists.

[0248] In an optional implementation, if the responsible person identifiers corresponding to different test cases are not completely the same, the first search module includes:

[0249] The search unit is used to search for the target notification information corresponding to the multiple test cases included in the target production inspection task from the preset correspondence between the test cases and the notification information.

[0250] In an optional implementation, the processing completion message is obtained by operating the second processing state, or the processing completion message is obtained by executing the target production inspection task again and the operation result of the target production inspection task does not have an online fault.

[0251] In an optional implementation, the method further includes:

[0252] The first control module is used to respond to the operation of creating a production inspection task and control the display of use case sources, where the use case sources include infrastructure, APIFOX, Jenkins, and cloud testing platform;

[0253] A second determination module is used to determine a target source from the use case source;

[0254] a second control module, configured to control the display of a first user interface corresponding to the target source;

[0255] A third acquisition module is used to obtain a production inspection task identifier through the first user interface;

[0256] A selection module, configured to select one or more test cases from a test case set corresponding to the target source through the first user interface;

[0257] A fourth acquisition module, configured to acquire a first execution order of the one or more test cases through the first user interface;

[0258] The first construction module is used to construct a correspondence between the production inspection task identifier, the first execution order and the one or more test cases to obtain the production inspection task.

[0259] In an optional implementation, the method further includes:

[0260] A third control module is configured to control the display of a second user interface in response to an operation of creating a test case;

[0261] A fifth acquisition module, configured to acquire a test case identifier and an operating environment through the second user interface;

[0262] a sixth acquisition module, configured to obtain, through the second user interface, a plurality of use case steps and a second execution order between the plurality of use case steps;

[0263] The second construction module is used to construct a correspondence between the test case identifier, the operating environment, the multiple use case steps and the second execution order to obtain the test case.

[0264] An electronic device is also provided in an embodiment of the present application. Figure 20, which shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic device in the embodiments of the present application may include, but is not limited to, fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 20 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0265] like Figure 20 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 2001, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 2002 or programs loaded from a storage device 2008 into a random access memory (RAM) 2003. When the electronic device is powered on, the RAM 2003 also stores various programs and data required for the operation of the electronic device. The processing device 2001, ROM 2002, and RAM 2003 are interconnected via a bus 2004. An input / output (I / O) interface 2005 is also connected to the bus 2004.

[0266] Typically, the following devices may be connected to the I / O interface 2005: an input device 2006 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 2007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 2008 including, for example, a memory card, a hard disk, etc.; and a communication device 2009. The communication device 2009 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Figure 20 The electronic device is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0267] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any one of the online production inspection methods provided in the embodiments of the present application.

[0268] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When one or more computer programs are executed by an electronic device, the electronic device can implement any online environment production inspection method provided in an embodiment of the present application.

[0269] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0270] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0271] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0272] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. A production inspection method for an online environment, characterized in that: include: Determine online faults in the online environment based on the results of target production inspection tasks. From the preset correspondence between production inspection tasks and notification information, search for target notification information corresponding to the target production inspection task, wherein the target notification information includes a notification group address and a person in charge identifier; The communication number of the person in charge having the person in charge identification is located in the notification group having the notification group address; Generate business inspection alarm information, the business inspection alarm information including the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, and a first processing status indicating that the task is not processed; Sending the service inspection alarm information to the notification group address; Acquire a start processing message indicating that the online fault is being processed, wherein the start processing message is obtained by operating the first processing state; Generate business processing progress information, the business processing progress information including the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, the identifier of the person who handles the online fault, and a second processing status representing the processing in progress; The processor identifier is at least one of the person-in-charge identifiers; Sending the business processing progress information to the notification group address; Obtaining a processing completion message indicating that the online fault has been processed; Generate processing completion information, the processing completion information including the identifier of the target production inspection task, the test time, the online fault, the identifier of the person in charge, the identifier of the processor, and a third processing status indicating that the processing has been completed; Send the processing completion information to the notification group address.

2. The production inspection method for an online environment according to claim 1, characterized in that: The target production inspection task includes multiple test cases; the step of determining the online fault of the online environment based on the running result of the target production inspection task includes: For each of the test cases, if the running result of the test case does not match the expected result of the test case, it is determined that the online fault exists.

3. The production inspection method for an online environment according to claim 2, characterized in that: If the responsible person identifiers corresponding to different test cases are not exactly the same, the step of searching for the target notification information corresponding to the target production inspection task from the preset correspondence between the production inspection task and the notification information includes: From the preset correspondence between test cases and notification information, the target notification information corresponding to each of the plurality of test cases included in the target production inspection task is searched.

4. The production inspection method for an online environment according to any one of claims 1 to 3, characterized in that: The processing completion message is obtained by operating the second processing state, or the processing completion message is obtained by executing the target production inspection task again and the running result of the target production inspection task does not contain any online fault.

5. The production inspection method for an online environment according to claim 1, characterized in that: The method for constructing the production inspection task includes: In response to the operation of creating a production inspection task, the control displays the use case sources, which include infrastructure, APIFOX, Jenkins, and cloud testing platform; Identify target sources from the stated use case sources; Controlling the display of a first user interface corresponding to the target source; Obtaining a production inspection task identifier through the first user interface; Select one or more test cases from the test case set corresponding to the target source through the first user interface; Obtaining a first execution order of the one or more test cases through the first user interface; A correspondence between the production inspection task identifier, the first execution order, and the one or more test cases is constructed to obtain the production inspection task.

6. The production inspection method for an online environment according to any one of claims 2 or 3, characterized in that: The method of constructing the test case includes: In response to an operation of creating a test case, controlling display of a second user interface; Obtaining a test case identifier and an operating environment through the second user interface; obtaining, through the second user interface, a plurality of use case steps and a second execution order between the plurality of use case steps; A correspondence between the test case identifier, the operating environment, the multiple use case steps, and the second execution order is constructed to obtain the test case.

7. A production inspection device for an online environment, characterized in that: include: The first determination module is used to determine the online fault of the online environment based on the running results of the target production inspection task; A first search module is used to search for target notification information corresponding to the target production inspection task from the preset correspondence between production inspection tasks and notification information, wherein the target notification information includes a notification group address and a person in charge identifier; The communication number of the person in charge having the person in charge identification is located in the notification group having the notification group address; A first generating module is configured to generate business inspection alarm information, wherein the business inspection alarm information includes an identifier of the target production inspection task, a test time, the online fault, an identifier of the person in charge, and a first processing status indicating that the task is not processed; A first sending module is used to send the service inspection alarm information to the notification group address; A first acquisition module is configured to acquire a processing start message indicating that the online fault is being processed, wherein the processing start message is obtained by operating the first processing state; A second generating module is configured to generate business processing ongoing information, wherein the business processing ongoing information includes an identifier of the target production inspection task, the test time, the online fault, an identifier of the person in charge, an identifier of a person who handles the online fault, and a second processing status representing the ongoing processing; The processor identifier is at least one of the person-in-charge identifiers; A second sending module is used to send the business processing progress information to the notification group address; A second acquisition module is used to obtain a processing completion message indicating that the online fault has been processed; A third generating module is configured to generate processing completion information, wherein the processing completion information includes an identifier of the target production inspection task, the test time, the online fault, an identifier of the person in charge, an identifier of the processor, and a third processing status indicating that the processing has been completed; The third sending module is used to send the processing completion information to the notification group address.

8. A computer program product, characterized in that The method comprises computer-readable instructions, which, when executed on an electronic device, enable the electronic device to implement the production inspection method for an online environment as claimed in any one of claims 1 to 6.

9. An electronic device, characterized in that: comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the production inspection method for an online environment as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the production inspection method for an online environment as described in any one of claims 1 to 6.

Images