An interface diagnosis method, device, terminal and computer readable storage medium
By displaying screenshots of the application interface on the terminal screen and performing anomaly diagnosis, the problem of cumbersome application interface diagnosis process and high labor costs in the existing technology is solved, and efficient automated diagnosis is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- TENCENT TECHNOLOGY (SHENZHEN) CO LTD
- Filing Date
- 2020-09-22
- Publication Date
- 2026-06-23
AI Technical Summary
The diagnostic process in existing technologies is cumbersome, inefficient, and labor-intensive, requiring the cooperation of multiple users.
By displaying a screenshot of the application interface on the terminal screen and responding to user triggers, the system uses the screenshot to diagnose anomalies and outputs the diagnostic results.
It simplifies the diagnostic process, improves diagnostic efficiency, reduces labor costs, and enables automated diagnosis without the need for assistance from other users.
Smart Images

Figure CN112100074B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, specifically to the field of computer technology, and in particular to an interface diagnostic method, apparatus, terminal, and computer-readable storage medium. Background Technology
[0002] Currently, when a user suspects a problem with an application interface (such as the interface of an instant messaging application), the user typically needs to manually inform the distributor of the issue in the form of an operational document. The distributor then uses this document to diagnose the problem. If the distributor is unable to diagnose the issue, the document is forwarded to testers or developers for further diagnosis. This process is cumbersome, inefficient, and requires collaboration from distributors, testers, and developers, resulting in high labor costs. Summary of the Invention
[0003] This application provides an interface diagnostic method, apparatus, terminal, and computer-readable storage medium, which can effectively improve the diagnostic efficiency of application interfaces and reduce labor costs.
[0004] On one hand, embodiments of the present invention provide an interface diagnostic method, the method comprising:
[0005] Display the application interface of the target application on the terminal screen;
[0006] If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen.
[0007] In response to a trigger operation on the screenshot image, perform anomaly diagnosis on the application interface based on the screenshot image;
[0008] Feedback information is output to the terminal screen based on the diagnostic results.
[0009] On the other hand, embodiments of this application provide an interface diagnostic device, the device comprising:
[0010] The display unit is used to display the application interface of the target application on the terminal screen.
[0011] The display unit is further configured to display a screenshot image of the application interface on the terminal screen if a screenshot operation targeting the application interface is detected.
[0012] A diagnostic unit is configured to respond to a trigger operation on the screenshot image and perform anomaly diagnosis on the application interface based on the screenshot image.
[0013] The output unit is used to output feedback information on the terminal screen based on the diagnostic results.
[0014] Furthermore, embodiments of this application provide a terminal, which includes an input device and an output device, and further includes:
[0015] A processor, adapted to implement one or more instructions; and,
[0016] A computer storage medium storing one or more instructions adapted for loading by the processor and executing the following steps:
[0017] Display the application interface of the target application on the terminal screen;
[0018] If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen.
[0019] In response to a trigger operation on the screenshot image, perform anomaly diagnosis on the application interface based on the screenshot image;
[0020] Feedback information is output to the terminal screen based on the diagnostic results.
[0021] In another aspect, embodiments of this application provide a computer storage medium storing one or more instructions, which are adapted to be loaded by the processor and executed as follows:
[0022] Display the application interface of the target application on the terminal screen;
[0023] If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen.
[0024] In response to a trigger operation on the screenshot image, perform anomaly diagnosis on the application interface based on the screenshot image;
[0025] Feedback information is output to the terminal screen based on the diagnostic results.
[0026] In this embodiment, the application interface of the target application is displayed on the terminal screen. If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen. Then, in response to the trigger operation on the screenshot image, the terminal performs anomaly diagnosis on the application interface based on the screenshot image and outputs feedback information on the terminal screen based on the diagnosis results. It is evident that this interface diagnosis method simplifies the diagnostic process and effectively improves diagnostic efficiency; moreover, since anomaly diagnosis of the application interface can be achieved through screenshot images, the entire diagnostic process does not require assistance from distributors or other users, effectively reducing labor costs. Attached Figure Description
[0027] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0028] Figure 1 This is a schematic diagram of the structure of an interface diagnostic system provided in an embodiment of this application;
[0029] Figure 2 This is a flowchart illustrating an interface diagnosis method provided in an embodiment of this application;
[0030] Figure 3a This is a schematic diagram of a screenshot operation provided in an embodiment of this application;
[0031] Figure 3b This is a schematic diagram of a process for generating a screenshot image provided in an embodiment of this application;
[0032] Figure 3c This is a schematic diagram of a click diagnostic component and its output diagnostic prompt information provided in an embodiment of this application;
[0033] Figure 3d This is a schematic diagram of an output feedback information provided in an embodiment of this application;
[0034] Figure 3e This is a schematic diagram of another output feedback information provided in an embodiment of this application;
[0035] Figure 3f This is a schematic diagram of another type of output feedback information provided in an embodiment of this application;
[0036] Figure 4 This is a flowchart illustrating another interface diagnostic method provided in an embodiment of this application;
[0037] Figure 5This is a schematic diagram of another interface diagnostic system provided in an embodiment of this application;
[0038] Figure 6 This is a schematic diagram of the structure of an interface diagnostic device provided in an embodiment of this application;
[0039] Figure 7 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation
[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0041] To better diagnose application interface anomalies, this application proposes an interface diagnosis scheme and a corresponding interface diagnosis system. For example... Figure 1 As shown, the interface diagnostic system may include at least: at least one terminal (or client) 101 and a server (or server) 102. Each terminal 101 may be a smartphone, tablet, laptop, desktop computer, etc.; various applications may be installed and run on the terminal, such as social applications (e.g., instant messaging (IM) applications, content sharing applications), multimedia playback applications, browser applications, etc. Furthermore, for any application's interface, the terminal or an application within the terminal may provide a corresponding screenshot function to capture the application interface. The terminal 101 and the server 102 may be directly or indirectly connected via wired or wireless communication, which is not limited herein. Communication from the server (server 102) to the client (i.e., terminal 101) may be called SC communication; communication from the client (i.e., terminal 101) to the client (i.e., terminal 101) may be called CC communication; and communication from the client (i.e., terminal 101) to the server (server 102) may be called CS communication.
[0042] The service device 102 here may include one or more servers capable of providing various services to the terminal. For example, an application server that can provide application services (such as social services, multimedia playback services, etc.) for any application running on the terminal; a data storage server that can provide data storage services (such as storage services for abnormal problems in the application interface, storage services for solutions to abnormal problems, etc.) for the terminal; a file server for providing file storage services to the terminal, and so on. It should be noted that any server mentioned in the embodiments of this application can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.
[0043] Cloud computing refers to a delivery and usage model for information technology (IT) infrastructure, specifically, obtaining necessary resources through a network in an on-demand and easily scalable manner. More broadly, cloud computing refers to a service delivery and usage model, meaning obtaining necessary services through a network in an on-demand and easily scalable manner. These services can be IT and software-related, internet-related, or other services. Cloud computing is a product of the convergence and development of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing.
[0044] In its specific implementation, the interface diagnostic scheme proposed in this application embodiment can be executed by any terminal in the aforementioned interface diagnostic system. Its general principle is as follows: While running any application, the terminal can display the application interface of that application on its screen. When a user believes there is a problematic area in the application interface and wants to diagnose it, they can use the screenshot function of the terminal or an application running on the terminal to capture the problematic area, thereby triggering the terminal to obtain the corresponding screenshot image. Correspondingly, after obtaining the screenshot image, the terminal can perform anomaly diagnosis on the application interface based on the screenshot image. It is evident that this diagnostic method effectively simplifies the diagnostic process and improves diagnostic efficiency; moreover, the ability to diagnose application interface anomalies through screenshot images eliminates the need for assistance from distributors or other users, effectively reducing labor costs.
[0045] Based on the above interface diagnostic scheme, this application proposes an interface diagnostic method. This interface diagnostic method can be executed by any terminal in the above interface diagnostic system, or by any application running on any terminal; and the application can be the same as or different from the target application mentioned below, without limitation. For ease of explanation, the following description will use the execution of this interface diagnostic method by any terminal as an example; please refer to... Figure 2 The interface diagnostic method may include the following steps S201-S204:
[0046] S201. Display the application interface of the target application on the terminal screen.
[0047] The target application can be any application installed and running on the terminal, such as a social networking application, a multimedia playback application, a browser application, etc.; the application interface can be any interface provided to the user by the target application during its operation. For example, if the target application is a social networking application, the application interface can be the social conversation interface, user search interface, web page link interface (such as an H5 interface), etc. provided by the social networking application; as another example, if the target application is a browser application, the application interface can be the web page browsing interface, data download interface, etc. provided by the browser application; and as yet another example, if the target application is a multimedia playback application, the application interface can be the audio / video playback interface, audio / video selection interface, etc. provided by the multimedia playback application.
[0048] In the specific implementation, when a user wants to open the application interface of a target application, they can input a display trigger operation for that application interface. Correspondingly, if the terminal detects this display trigger operation, it can display the application interface of the target application on the terminal screen. After displaying the application interface, if the user wants to perform anomaly diagnosis on the application interface, they can perform a screenshot operation on the application interface to trigger the terminal to perform anomaly diagnosis on the application interface based on the screenshot image through subsequent steps S202-S204, and output corresponding feedback information.
[0049] S202. If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen.
[0050] In one specific implementation, the screenshot operation can be a standalone operation; specifically, the screenshot operation can be a touch operation on the terminal screen (such as double-tapping the screen, long-pressing the screen, squeezing the screen with two fingers, etc.), or a touch operation on the terminal's physical buttons (such as pressing the power button and volume button simultaneously), and so on.
[0051] In this specific implementation, if the terminal detects a screenshot operation targeting the application interface, the terminal can activate the screenshot function based on the screenshot operation and take a screenshot of the entire application interface to generate a screenshot image of the application interface; then, the screenshot image of the application interface is displayed on the terminal screen. See, for example... Figure 3a As shown, if the screenshot operation is to squeeze the terminal screen with two fingers, then after the terminal detects the squeezing operation of two fingers on the terminal screen, it can activate the screenshot function to take a screenshot of the entire application interface of the target application, thereby generating a screenshot image of the application interface.
[0052] In another specific implementation, the screenshot operation can be a combination of operations; specifically, this screenshot operation includes a screenshot trigger operation and a screenshot drawing operation. The screenshot trigger operation refers to the operation used to initiate the screenshot; it can be a touch operation on a pre-set shortcut function key, or a trigger operation on a screenshot component built into the application interface (such as a click operation, a press operation, etc.). The shortcut function key mentioned here can be one or more keys in a keyboard device connected to the terminal; that is, the shortcut function key can be a single key specified in the keyboard device, or a combination of keys specified in the keyboard device (such as "Ctrl + Alt + X"). It should be noted that the keyboard device mentioned here can be a regular physical keyboard or a virtual keyboard, without limitation. The screenshot drawing operation refers to the operation used to draw the screenshot area. This can be an operation that triggers the terminal to output a rectangle by pressing the input focus (such as the cursor) and adjusting the display size of the rectangle, or an operation that controls the input focus to draw any shape (such as a circle, rectangle, etc.), and so on.
[0053] In its implementation, if the terminal detects a screenshot trigger operation targeting the application interface, it can first display an overlay interface on the terminal screen, allowing the user to input the corresponding screenshot drawing operation within the overlay interface. The overlay interface refers to an interface that overlays the application interface and has a certain degree of transparency. Correspondingly, the terminal can draw the screenshot area within the overlay interface based on the screenshot drawing operation; and during the drawing process, it continuously detects whether a region drawing completion event exists. If such a region drawing completion event is detected, the terminal displays a screenshot image of the application interface in response to the event. The screenshot image is generated based on the interface content contained within the screenshot area, and the size of the screenshot image obtained through the screenshot operation is the same as the size of the drawn screenshot area. For example, suppose the screenshot drawing operation is triggered by pressing the input focus to output a rectangle and adjusting the display size of the rectangle; a schematic diagram of the terminal displaying the screenshot image can be found in [reference needed]. Figure 3b As shown.
[0054] S203. In response to a trigger operation on a screenshot image, perform anomaly diagnosis on the application interface based on the screenshot image.
[0055] In its implementation, after displaying a screenshot, the terminal can detect triggering operations on the screenshot in real time. These triggering operations can be: operations on diagnostic components displayed on the terminal screen simultaneously with the screenshot; for example, a click or press on a diagnostic component displayed simultaneously with the screenshot. Alternatively, triggering operations can be: inputting diagnostic gestures on the terminal screen; for example, inputting a swipe gesture or a specific "M" gesture. Or, triggering operations can also be: operations on the screenshot itself; such as clicking or long-pressing the screenshot, etc.
[0056] If a trigger operation targeting a screenshot image is detected, the terminal can respond to the trigger operation by performing anomaly diagnosis on the application interface based on the screenshot image. In one embodiment, the terminal can respond to the trigger operation targeting a screenshot image by performing image recognition on the screenshot image to obtain the target features included in the screenshot image. If the target features include anomaly problem features, it is determined that the application interface is abnormal, thus obtaining a diagnostic result indicating that the application interface is abnormal; if the target features do not include anomaly problem features, it is determined that the application interface is not abnormal, thus obtaining a diagnostic result indicating that the application interface is not abnormal. In another embodiment, an image resource set containing at least one abnormal image can be prepared in advance, with each abnormal image corresponding to an abnormal problem; accordingly, the terminal can respond to the trigger operation targeting a screenshot image by matching the screenshot image and the image resource set using a matching algorithm to determine whether the application interface is abnormal, and thus obtain a diagnostic result.
[0057] In one feasible embodiment, to allow users to intuitively perceive that the terminal is performing anomaly diagnosis on the application interface based on the screenshot image, the terminal can also output diagnostic prompt information during the anomaly diagnosis process. This diagnostic prompt information indicates that the application interface is in an anomaly diagnosis state. For example, suppose the trigger operation for the screenshot image is clicking the diagnostic component on the terminal screen, and the diagnostic prompt information is "Problem analysis in progress, please wait." A schematic diagram illustrating the terminal's response to the screenshot image trigger operation and the synchronous output of diagnostic prompt information during the anomaly diagnosis process can be found in [reference needed]. Figure 3c As shown.
[0058] S204. Output feedback information on the terminal screen based on the diagnostic results.
[0059] In a specific implementation, after the terminal performs anomaly diagnosis on the application interface in step S203, it can obtain a diagnosis result and output feedback information on the terminal screen based on the diagnosis result. In one feasible implementation, feedback information can be directly output on the current interface displayed on the terminal screen based on the diagnosis result. In another feasible implementation, as mentioned above, the terminal may output a masked interface and display a screenshot image in the masked interface when executing step S202; in this case, the current interface displayed on the terminal screen is the masked interface. Based on this, the terminal can also switch from the masked interface to the application interface and display feedback information in the application interface based on the diagnosis result. For ease of explanation, the following description will use the terminal displaying feedback information in the application interface as an example.
[0060] As mentioned above, the diagnostic results can indicate whether the application interface has an anomaly or not. Accordingly, the terminal can output different feedback information on the terminal screen based on different diagnostic results. Specifically, if the diagnostic result indicates that the application interface has no anomalies, the terminal can directly generate feedback information; in this case, the feedback information may include a notification message indicating that the application interface has no anomalies. For example, if the notification message is "The current interface has no anomalies, please use it with confidence," a schematic diagram of the output feedback information can be found in [reference needed]. Figure 3d As shown in the diagram. If the diagnostic results indicate an anomaly in the application interface, the terminal can identify the target anomaly and search for the corresponding target solution in the local storage space; and generate feedback information using the target anomaly and the target solution. In this case, the feedback information may include the target anomaly and the target solution for resolving the target anomaly; wherein, the target anomaly is: the anomaly in the application interface identified based on the screenshot image. For example, if the target anomaly is “××××××” and the target solution is “××××××××××××××××”, a schematic diagram of the output feedback information can be found in [reference needed]. Figure 3e As shown.
[0061] In one feasible embodiment, if the diagnostic result indicates an anomaly in the application interface, but the terminal fails to identify the target anomaly or find a corresponding target solution in the local storage, the terminal can also request relevant technical personnel to return the corresponding target solution after identifying the target anomaly in the application interface. In this case, the feedback information may also include a waiting prompt; this waiting prompt can be used to indicate that the technical personnel have been requested to diagnose the anomaly in the application interface based on the screenshot image, and to wait for the technical personnel's response. For example, if the waiting prompt is "Relevant information has been collected and reported to the backend; please wait for the technical response," the terminal can first output this waiting prompt; and after obtaining the target solution from the technical personnel, it can then output the target anomaly and the target solution, such as... Figure 3f As shown. It should be noted that, Figure 3f This is merely an illustrative diagram representing the output of feedback information and is not intended to limit the scope of the application. For example, in other embodiments, the terminal may first output the waiting prompt message; and after obtaining the target solution from the technician, output a solution resolution notification to inform the user that the target solution has been found; and after detecting the user's solution viewing operation, output the target abnormal problem and the corresponding target solution, and so on.
[0062] In this embodiment, the application interface of the target application is displayed on the terminal screen. If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen. In response to a trigger operation targeting the screenshot image, anomaly diagnosis of the application interface is performed based on the screenshot image, and feedback information is output on the terminal screen based on the diagnosis results. It is evident that this interface diagnosis method simplifies the diagnostic process and effectively improves diagnostic efficiency. Furthermore, since anomaly diagnosis of the application interface can be achieved through screenshot images, the entire diagnostic process does not require assistance from distributors or other users, effectively reducing labor costs.
[0063] Please see Figure 4 , Figure 4 This is a flowchart illustrating an interface diagnosis method provided in an embodiment of this application. This interface diagnosis method can be executed by any terminal in the aforementioned interface diagnosis system, or by any application running on any terminal; and this application may be the same as or different from the target application mentioned later, without limitation. For ease of explanation, the following description will use the execution of this interface diagnosis method by any terminal as an example; and, in this embodiment, the description mainly uses the method of diagnosing the application interface based on a screenshot image using a matching algorithm. See also... Figure 4 As shown, the interface diagnostic method includes the following steps:
[0064] S401. Display the application interface of the target application on the terminal screen.
[0065] S402. If a screenshot operation targeting the application interface is detected, display the screenshot image of the application interface on the terminal screen.
[0066] Steps S401-S402 can be referred to in the embodiment. Figure 2 The implementation methods in steps S201-S202 will not be described in detail here.
[0067] S403, In response to a trigger operation on a screenshot image, obtain a set of image resources.
[0068] In one specific implementation, the terminal can respond to a trigger operation on a screenshot image by directly retrieving a pre-saved set of image resources from its local storage. In another specific implementation, the terminal can respond to a trigger operation on a screenshot image by first detecting whether the screenshot image is blank. If the screenshot image is not blank, the terminal can determine that the application interface is normal based on the screenshot image; in this case, the terminal can directly execute step S407. If the screenshot image is blank, the terminal can determine that the application interface may be abnormal based on the screenshot image; in this case, the terminal can retrieve the set of image resources and further detect whether the application interface is abnormal through step S404. For example, if the screenshot image is generated based on the user's friend list interface included in the screenshot area, the terminal can detect whether the screenshot image is blank. If the screenshot image is blank, the terminal determines that the user's friend list interface is abnormal; otherwise, the terminal determines that the user's friend list interface is not abnormal.
[0069] The image resource set includes at least one abnormal image, with each abnormal image corresponding to an abnormal issue. The abnormal images can be set based on experience; for example, the image resource set can include images such as error pop-up windows and error notification images on the interface. If the abnormal image is an error pop-up window image, the corresponding abnormal issue is an error pop-up window; if the abnormal image is an error notification image on the interface, the corresponding abnormal issue is an error message.
[0070] S404. Calculate the matching degree between the screenshot image and each abnormal image, and find the target abnormal image from at least one abnormal image based on the calculated matching degree.
[0071] In this context, the target abnormal image refers to an abnormal image with a matching degree greater than a threshold. In the specific implementation, the terminal first calculates the matching degree between the screenshot image and each abnormal image; then, it determines whether the calculated matching degree between the screenshot image and each abnormal image is greater than the threshold. If a target matching degree is greater than the threshold, the abnormal image corresponding to the target matching degree is taken as the target abnormal image; at this point, it can be determined that the target abnormal image has been successfully found, and step S405 is executed. If no target matching degree is greater than the threshold, it indicates that at least one abnormal image does not contain the target abnormal image; at this point, it can be determined that the search for the target abnormal image has failed, and step S406 is executed. It can be understood that the matching degree is used to indicate the similarity between the screenshot image and the abnormal image, and the threshold can be set according to requirements, for example, the threshold can be set to 80%, 90%, etc.
[0072] S405. If the target abnormal image is successfully found, it is determined that there is an abnormality in the application interface.
[0073] S406. If the search for the target abnormal image fails, it is determined that there is no abnormality in the application interface.
[0074] S407. Output feedback information on the terminal screen based on the diagnostic results.
[0075] If the diagnostic results indicate that the application interface is normal, the terminal can directly generate and output feedback information. In this case, the feedback information may include a notification message indicating that the application interface is normal. If the diagnostic results indicate that the application interface is abnormal, the terminal can first determine the target abnormality. After determining the target abnormality, the terminal obtains the target solution to resolve the target abnormality and outputs the target abnormality and the target solution as feedback information.
[0076] The specific implementation methods for determining the target anomaly in the application interface can include the following: In one implementation, as mentioned above, a target anomaly image corresponds to an anomaly; therefore, after finding the target anomaly image, the terminal can also determine the target anomaly in the application interface based on the target anomaly image. Specifically, the terminal can use the anomaly corresponding to the target anomaly image as the anomaly in the screenshot image; since the screenshot image is generated based on the interface content contained in the screenshot area, the anomaly in the screenshot image must also exist in the application interface, so the anomaly in the screenshot image (i.e., the anomaly corresponding to the target anomaly image) can be used as the target anomaly in the target interface. In another implementation, the terminal can also perform image recognition on the screenshot image to obtain the text information in the screenshot image; and determine the anomaly in the application interface based on the text information. For example, if the terminal recognizes the text information "software upgrade failed" from the screenshot image, then the terminal can determine the target anomaly in the application interface of the target application as "software upgrade failed" based on the text information.
[0077] The method for obtaining the target solution may include the following steps s11-s13:
[0078] s11 retrieves the solution set from the terminal's local space.
[0079] s12, find solutions from the solution set to resolve the target anomaly.
[0080] In a specific implementation, the target application may include multiple functional modules; for example, when the target application is a social application, the multiple functional modules may be a conversational functional module, a search functional module, etc. Each functional module corresponds to one interface. Correspondingly, the solution set may include a subset of solutions for each functional module, and each functional module's solution subset includes at least one solution corresponding to an exception. Therefore, when the terminal executes step s12, it may include the following steps:
[0081] First, the target functional module corresponding to the application interface can be determined from multiple functional modules based on the screenshot image. Research shows that any functional module is usually associated with various operational components in the interface corresponding to that functional module; therefore, the target functional module can be determined based on the operational components included in the application interface. Since the screenshot image is obtained by capturing the application interface, the target operational components included in the screenshot image usually belong to the operational components included in the application interface. Therefore, the target functional module can be determined by identifying the target operational components in the screenshot image. For example, if the target operational components in the screenshot image include a close button and a send button, then the target functional module can be determined to be the functional module associated with the close button and the send button (such as the conversation functional module); similarly, if the target operational components in the screenshot image include a search component, then the target functional module can be determined to be the functional module associated with the search component (such as the search functional module).
[0082] Based on this, at least one component image can be added to the image resource set in advance, so that the image resource set obtained by the terminal in step S403 can also include at least one component image, which refers to an image containing an operation component. Then, the terminal can first determine the target component image contained in the screenshot image from the at least one component image; specifically, the terminal can match the components in the screenshot image with each component image to determine the target component image contained in the screenshot image. Then, it can search for functional modules associated with the target operation component in the target component image from multiple functional modules, and then determine the found functional module as the target functional module corresponding to the application interface. Multiple functional modules include, but are not limited to, the aforementioned session functional module and search functional module.
[0083] After identifying the target functional module, the terminal can search for a subset of target solutions for the target functional module from the solution set, and further search for solutions to resolve the target anomaly from the subset of target solutions. Specifically, the subset of target solutions includes solutions corresponding to at least one anomaly; correspondingly, the terminal can match the target anomaly with each anomaly in the subset of target solutions, and use the solution corresponding to the matched anomaly as the solution to resolve the target anomaly. In this embodiment, the terminal first performs a preliminary search based on the functional module, which can effectively narrow the scope of subsequent solution searches, thereby effectively improving search efficiency during the secondary search based on the target anomaly. It should be understood that the hierarchical search method mentioned above is a two-level search method, but in actual applications, more levels of search methods can be set to improve the accuracy of solution searches.
[0084] For example, in one feasible embodiment, before searching for a solution to a target anomaly from the solution set, the terminal can set a first-level index, a second-level index, and a third-level index in the solution set to quickly find the target solution corresponding to the target anomaly. The first-level index is a functional module index, the second-level index is an anomaly index, and the third-level index is a text information index. Correspondingly, the solution set includes a subset of solutions for each functional module and an index for each functional module. Each subset of solutions for a functional module includes at least one solution corresponding to an anomaly and an index for each anomaly. Therefore, the terminal can first determine the index corresponding to the target functional module from multiple functional modules based on the screenshot image, and then search for the target solution subset of the target functional module from the solution set based on that index. Further, it searches for a solution to the target anomaly from the target solution subset based on the target anomaly index and the target functional module index. Optionally, if the terminal cannot find a solution to the target anomaly from the solution set based on the target anomaly index and the target functional module index, it can also search based on the third-level index (i.e., the text information index) to find a solution to the target anomaly.
[0085] s13, If a solution to the target anomaly is successfully found from the solution set, the target solution is obtained based on the found solution.
[0086] In one implementation, the found solution can be directly used as the target solution. In another implementation, since the initially found solution may not be directly displayed on the target application's interface, the terminal can also combine the input BasicInfo to synchronously analyze the found solutions, extracting effective solutions that can be displayed to the user, and then displaying the extracted effective solutions so that the user can perform relevant operations. Based on this, when the terminal obtains the target solution from the found solutions, it can first acquire basic information; this basic information may include, but is not limited to, log information of the target functional module and machine information of the operating system, etc.
[0087] The log information of the target functional module can be obtained from the terminal's local storage; it can include operation records generated by the target application during the user's use of the target functional module. Machine information can be obtained through publicly available Application Programming Interface (API) methods, and may include, but is not limited to: network type, network connectivity, outgoing Internet Protocol (IP), list of open ports, central processing unit (CPU) at runtime, memory, hard disk size, etc. After obtaining the basic information, the terminal can use keyword matching to extract valid solutions associated with the basic information from the found solutions, and then use the extracted valid solutions as the target solutions. This processing method eliminates the need for manual intervention by technical personnel, intelligently and efficiently resolving operational issues of the target application's interface, and shortening the handling time for application interface anomalies.
[0088] It should be noted that the solution set may not contain a solution for the target anomaly, which will cause the terminal to fail to find a solution for the target anomaly from the solution set. Accordingly, if the terminal fails to find a solution for the target anomaly from the solution set, it requests the technician to return the target solution. In a specific implementation, after the terminal fails to find a solution for the target anomaly from the solution set, it can add the aforementioned screenshot, the target application's log information (i.e., including log information from each functional module), and the operating system's machine information to the diagnostic information, and then package and compress the diagnostic information. The compressed information is then uploaded to the service device, allowing technicians to periodically or in real-time retrieve the compressed information from the service device, decompress it to obtain the diagnostic information, and then analyze the target anomaly in the application interface based on the diagnostic information and provide the corresponding target solution. In another feasible embodiment, the terminal can send a prompt message within a certain period of time, indicating to the technician that there is an anomaly in the application interface of the target application. Once the terminal receives the feedback information from the technician, it can output the feedback information, which includes the target anomaly and the target solution. The target anomaly and the target solution are uploaded to the file server, saved to the data storage server, and synchronized to all terminals where the target application is located. This ensures that if similar problems occur in the future, the corresponding solutions can be found in a timely manner, ensuring that the application interface is resolved promptly and efficiently.
[0089] In this embodiment, the application interface of the target application is displayed on the terminal screen. If a screenshot operation on the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen. In response to the trigger operation on the screenshot image, an image resource set is obtained. The image resource set includes at least one abnormal image, and each abnormal image corresponds to an abnormal problem. The matching degree between the screenshot image and each abnormal image is further calculated, and a target abnormal image is searched from at least one abnormal image based on the calculated matching degree. If the target abnormal image is successfully found, it is determined that the application interface has an abnormality. If the search for the target abnormal image fails, it is determined that the application interface does not have an abnormality. Feedback information is output on the terminal screen based on the diagnostic results, thereby improving the efficiency of solving application interface problems.
[0090] Based on the above Figure 2 and Figure 4 The embodiments of the interface diagnostic method shown are described above. Further embodiments of this application may be implemented in addition to the above. Figure 1The interface diagnostic system mentioned above deploys servers such as a World Wide Web (WWW) server, a file server, and a data storage server in its service equipment. A problem analysis and diagnostic module is also deployed in the terminal to better diagnose application interface anomalies. This analysis and diagnostic module may include, but is not limited to, the following processing modules: an image matching module, a basic information analysis module, a knowledge base query module, and a knowledge base update module. Furthermore, the terminal's local knowledge base stores a pre-prepared set of image resources, including at least one abnormal image and at least one component image. The abnormal image can be an error pop-up image, an error message image on the interface, or images of various online statuses. The component image can be a button control image, a search component image, etc. The following will combine... Figure 5 The flowchart shown illustrates the working principle of each processing module in the terminal and the interaction process between them:
[0091] The image matching module can detect whether screenshots in the image resource set include the operation components indicated by various component images, thereby determining the target functional module corresponding to the application interface. For example, the target functional module can be identified as the session window module based on the close and send buttons, and the target functional module can be identified as the search module based on the search image on the main product panel. Additionally, it can detect whether each abnormal image in the image resource set matches the screenshot image, thereby determining whether there are any anomalies in the application interface; and if an anomaly is found, it can analyze the target anomaly problem in the application interface. Optionally, it can also identify Chinese characters, English text, and other text information from the screenshot image. Furthermore, the image matching module can define a module function identification field for the target functional module, the target anomaly problem, and the text information in the screenshot image: a module ID field, an error type field, and a content field. The target functional modules, target anomalies, and text information mentioned above can be written into machine language that the terminal can recognize. The written machine language is then filled into the following recognition fields: module ID_error Type_Content. The values of each field of module ID_error Type_Content are then used as input to the basic information analysis module.
[0092] The basic information analysis module can obtain machine information of the current operating system and log information of the target functional module. Specifically, when a target user uses the target application, it triggers the application to generate log information. This log information includes log information from various functional modules. Each functional module's log information stores the operation records generated by the program during user operations, and each functional module's log information is indexed based on its module identifier. Therefore, the target functional module's log information can be obtained based on its module ID. The obtained machine information of the current operating system and the target functional module's log information are defined as basic information (BasicInfo), and this basic information (BasicInfo) is returned to the image matching module. Upon receiving the basic information (BasicInfo) from the basic information analysis module, the image matching module can then pass the moduleID_errorType_Content_BasicInfo to the knowledge base lookup module.
[0093] The knowledge base search module can retrieve existing solutions for the target anomaly based on the four types of information provided by the image matching module, and then integrate the information. Specifically, moduleID, errorType, and Content can be divided into first-level, second-level, and third-level indexes, and each index and solution can be stored in a table in the knowledge base. The terminal can then search for the solution corresponding to the target anomaly from the knowledge base using each level of index.
[0094] It should be noted that if the terminal fails to find a solution to the target anomaly when calling the knowledge base search module, or if the image matching module fails to identify an anomaly in the application interface, the terminal can package the screenshot image, moduleID_errorType_Content_BasicInfo, the target application's log information, and the operating system's machine information into a zip file (a file compression format), and upload it to a web server via Hypertext Transfer Protocol over Secure Socket Layer (HTTPS). Technical personnel will periodically check the web server for anomalies in the target application's interface. By analyzing the screenshot images, the target application's operation information, and the operating system's machine information, they can identify the target anomaly in the application interface and find the corresponding solution. After finding the solution, the target functional module, the target anomaly, the text information, and the corresponding solution are uploaded to a file server and saved to a data storage server, and also synchronized to all terminals with the target application installed. After receiving the target functional module, the target abnormal problem, the text information, and the corresponding solution for the target abnormal problem, each terminal can call the knowledge base update module to store the received information into the knowledge base in its local space, so that it can quickly identify and find solutions for similar problems in the future.
[0095] The interface diagnostic method proposed in this application allows users to quickly identify the target solution for a specific anomaly, enabling timely problem resolution and saving communication costs with distributors. Furthermore, technical personnel can save significant time and manpower costs, focusing on resolving only one type of problem at a time. The knowledge base distribution ensures that every user receives problem solutions, greatly improving developer efficiency and preventing frequent operational incidents.
[0096] Based on the description of the above-described interface diagnostic method embodiments, this application also discloses an interface diagnostic device, which can be a computer program (including program code) running on the aforementioned terminal. This interface diagnostic device can execute... Figure 2 or Figure 4 The method shown. Please refer to [link / reference]. Figure 6 The interface diagnostic device can operate the following units:
[0097] Display unit 601 is used to display the application interface of the target application on the terminal screen;
[0098] The display unit 601 is further configured to display a screenshot image of the application interface on the terminal screen if a screenshot operation for the application interface is detected.
[0099] The diagnostic unit 602 is configured to perform anomaly diagnosis on the application interface based on the screenshot image in response to a trigger operation on the screenshot image.
[0100] The output unit 603 is used to output feedback information on the terminal screen based on the diagnostic results.
[0101] In one feasible embodiment, the output unit 603 can be specifically used to: output diagnostic prompt information on the terminal screen during the process of performing anomaly diagnosis on the application interface based on the screenshot image;
[0102] The diagnostic prompt information is used to indicate that the application interface is in an abnormal diagnostic state.
[0103] In another feasible embodiment, the triggering operation for the screenshot image includes: a triggering operation for a diagnostic component on the terminal screen, an operation to input a diagnostic gesture on the terminal screen, or a triggering operation for the screenshot image.
[0104] The diagnostic component is displayed synchronously on the terminal screen when the screenshot image is displayed.
[0105] In another feasible embodiment, the screenshot operation includes a screenshot trigger operation and a screenshot drawing operation; the device further includes: a drawing unit 604, wherein:
[0106] The display unit 601 is further configured to display a mask interface on the terminal screen if a screenshot trigger operation for the application interface is detected.
[0107] The drawing unit 604 is used to draw a screenshot area in the mask interface according to the screenshot drawing operation.
[0108] The display unit 601 is also configured to display a screenshot of the application interface on the terminal screen in response to a region drawing end event, wherein the screenshot image is generated based on the interface content contained in the screenshot area.
[0109] In another feasible embodiment, the display unit can be specifically used to: switch from the overlay interface to the application interface;
[0110] Feedback information is displayed in the application interface based on the diagnostic results.
[0111] In another feasible embodiment, if the diagnostic result indicates that there is no abnormality in the application interface, the feedback information includes a notification prompt, which is used to indicate that there is no abnormality in the application interface.
[0112] If the diagnostic results indicate that the application interface has an anomaly, the feedback information includes the target anomaly problem and the target solution for resolving the target anomaly problem; wherein, the target anomaly problem is: the anomaly problem of the application interface determined based on the screenshot image.
[0113] In another feasible embodiment, the diagnostic unit 602 can be specifically used to: obtain an image resource set, the image resource set including at least one abnormal image, each abnormal image corresponding to an abnormal problem;
[0114] Calculate the matching degree between the screenshot image and each abnormal image, and find the target abnormal image from at least one abnormal image based on the calculated matching degree. The target abnormal image refers to an abnormal image with a matching degree greater than a threshold.
[0115] If the target abnormal image is successfully found, it is determined that the application interface is abnormal;
[0116] If the search for the target abnormal image fails, it is determined that the application interface does not have any abnormalities.
[0117] In another feasible embodiment, the feedback information includes a target solution, which is obtained in the following way:
[0118] Retrieve the solution set in the terminal's local space;
[0119] Find a solution from the set of solutions to resolve the target anomaly.
[0120] If a solution for resolving the target anomaly is successfully found from the solution set, the target solution is obtained based on the found solution; otherwise, a technical staff member is requested to return the target solution.
[0121] In another feasible embodiment, the target application includes multiple functional modules, with each functional module corresponding to an interface; the solution set includes a subset of solutions from each functional module, and each functional module's solution subset includes at least one solution corresponding to an anomaly; the diagnostic module 602 can specifically be used for:
[0122] The step of searching for a solution to the target anomaly from the solution set includes:
[0123] Based on the screenshot image, determine the target functional module corresponding to the application interface from the plurality of functional modules;
[0124] Find a subset of target solutions for the target functional module from the set of solutions, and find a solution for resolving the target anomaly from the subset of target solutions.
[0125] In another feasible embodiment, the image resource set further includes: at least one component image, wherein the component image refers to an image including an operation component; each functional module is associated with various operation components in the interface corresponding to the functional module; the diagnostic module 602 is specifically used for:
[0126] From the at least one component image, determine the target component image contained in the screenshot image;
[0127] From the plurality of functional modules, find the functional module associated with the target operation component in the target component image;
[0128] The found functional modules are identified as the target functional modules corresponding to the application interface.
[0129] According to one embodiment of this application, Figure 2 or Figure 4 Each step involved in the method shown can be performed by... Figure 6 The individual units in the interface diagnostic device shown perform this operation. For example, Figure 2 Steps S201 and S202 shown are by Figure 6 The display unit 601 shown is used to perform step S203. Figure 6 The diagnostic unit 602 shown is used to perform step S204. Figure 6 The output unit 603 shown is used to execute this. For example, Figure 4 Steps S401 and S402 shown are by Figure 6 The display unit 601 shown is used to perform the steps S403-S406. Figure 6 The diagnostic unit 602 shown is used to perform step S407. Figure 6 The output unit 603 shown is used to perform this.
[0130] According to another embodiment of this application, Figure 6The various units in the interface diagnostic device shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the interface diagnostic device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.
[0131] According to another embodiment of this application, processing elements and storage elements, such as a central processing unit (CPU), random access storage medium (RAM), and read-only storage medium (ROM), can be used. For example, a general-purpose computing device such as a computer can run on a device capable of performing tasks such as... Figure 2 or Figure 4 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 6 The interface diagnostic apparatus shown herein, and the interface diagnostic method for implementing the embodiments of this application, are described. The computer program may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned terminal via the computer-readable recording medium, and run therein.
[0132] In this embodiment, the application interface of the target application is displayed on the terminal screen. If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen. In response to a trigger operation targeting the screenshot image, anomaly diagnosis of the application interface is performed based on the screenshot image, and feedback information is output on the terminal screen based on the diagnosis results. It is evident that this interface diagnosis method simplifies the diagnostic process and effectively improves diagnostic efficiency. Furthermore, since anomaly diagnosis of the application interface can be achieved through screenshot images, the entire diagnostic process does not require assistance from distributors or other users, effectively reducing labor costs.
[0133] Based on the description of the above-described interface diagnosis method embodiments, this application also discloses a terminal. Please refer to... Figure 7 The terminal includes at least a processor 701, an input device 702, an output device 703, and a computer storage medium 704. The processor 701, input device 702, output device 703, and computer storage medium 704 within the terminal can be connected via a bus or other means.
[0134] The computer storage medium 704 is a memory device in the terminal used to store programs and data. It is understood that the computer storage medium 704 can include the terminal's built-in storage medium, or it can include extended storage media supported by the terminal. The computer storage medium 704 provides storage space, which stores the terminal's operating system. Furthermore, this storage space also stores one or more instructions suitable for loading and execution by the processor 701. These instructions can be one or more computer programs (including program code). It should be noted that the computer storage medium can be a high-speed RAM memory; optionally, it can also be at least one computer storage medium located remotely from the aforementioned processor. The processor can be called a Central Processing Unit (CPU), which is the core and control center of the terminal, suitable for implementing one or more instructions, specifically loading and executing one or more instructions to achieve the corresponding method flow or function.
[0135] In one feasible embodiment, a processor 701 may load and execute one or more first instructions stored in a computer storage medium to implement the corresponding steps of the method in the above-described embodiment of the interface diagnosis method; specifically, one or more first instructions in the computer storage medium are loaded by the processor 701 and executed as follows:
[0136] Display the application interface of the target application on the terminal screen;
[0137] If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen.
[0138] In response to a trigger operation on the screenshot image, perform anomaly diagnosis on the application interface based on the screenshot image;
[0139] Feedback information is output to the terminal screen based on the diagnostic results.
[0140] In another feasible embodiment, the processor 701 is further configured to perform:
[0141] During the process of diagnosing anomalies in the application interface based on the screenshot image, diagnostic prompts are output on the terminal screen.
[0142] The diagnostic prompt information is used to indicate that the application interface is in an abnormal diagnostic state.
[0143] In another feasible embodiment, the triggering operation for the screenshot image includes: a triggering operation for a diagnostic component on the terminal screen, an operation to input a diagnostic gesture on the terminal screen, or a triggering operation for the screenshot image.
[0144] The diagnostic component is displayed synchronously on the terminal screen when the screenshot image is displayed.
[0145] In another feasible embodiment, the screenshot operation includes a screenshot trigger operation and a screenshot drawing operation; the processor 701 is specifically used for:
[0146] If a screenshot trigger operation is detected for the application interface, a mask interface is displayed on the terminal screen.
[0147] In the overlay interface, a screenshot area is drawn according to the screenshot drawing operation;
[0148] In response to a region drawing end event, a screenshot of the application interface is displayed on the terminal screen, the screenshot being generated based on the interface content contained in the screenshot area.
[0149] In another feasible embodiment, the processor 701 is specifically used for:
[0150] Switch from the overlay interface to the application interface;
[0151] Feedback information is displayed in the application interface based on the diagnostic results.
[0152] In another feasible embodiment, if the diagnostic result indicates that there is no abnormality in the application interface, the feedback information includes a notification prompt, which is used to indicate that there is no abnormality in the application interface.
[0153] If the diagnostic results indicate that the application interface has an anomaly, the feedback information includes the target anomaly problem and the target solution for resolving the target anomaly problem; wherein, the target anomaly problem is: the anomaly problem of the application interface determined based on the screenshot image.
[0154] In another feasible embodiment, the processor 701 is specifically used for:
[0155] Obtain an image resource set, wherein the image resource set includes at least one abnormal image, and each abnormal image corresponds to an abnormal issue;
[0156] Calculate the matching degree between the screenshot image and each abnormal image, and find the target abnormal image from at least one abnormal image based on the calculated matching degree. The target abnormal image refers to an abnormal image with a matching degree greater than a threshold.
[0157] If the target abnormal image is successfully found, it is determined that the application interface is abnormal;
[0158] If the search for the target abnormal image fails, it is determined that the application interface does not have any abnormalities.
[0159] In another feasible embodiment, the feedback information includes a target solution, which is obtained in the following way:
[0160] Retrieve the solution set in the terminal's local space;
[0161] Find a solution from the set of solutions to resolve the target anomaly.
[0162] If a solution for resolving the target anomaly is successfully found from the solution set, the target solution is obtained based on the found solution; otherwise, a technical staff member is requested to return the target solution.
[0163] In another feasible embodiment, the target application includes multiple functional modules, each functional module corresponding to an interface; the solution set includes a subset of solutions from each functional module, and each subset of solutions from each functional module includes at least one solution corresponding to an anomaly; the processor 701 is specifically used for:
[0164] Based on the screenshot image, determine the target functional module corresponding to the application interface from the plurality of functional modules;
[0165] Find a subset of target solutions for the target functional module from the set of solutions, and find a solution for resolving the target anomaly from the subset of target solutions.
[0166] In another feasible embodiment, the image resource set further includes: at least one component image, wherein the component image refers to an image including an operation component; each functional module is associated with various operation components in the interface corresponding to the functional module; the processor 701 is specifically used for:
[0167] From the at least one component image, determine the target component image contained in the screenshot image;
[0168] From the plurality of functional modules, find the functional module associated with the target operation component in the target component image;
[0169] The found functional modules are identified as the target functional modules corresponding to the application interface.
[0170] In this embodiment, the application interface of the target application is displayed on the terminal screen. If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen. In response to a trigger operation targeting the screenshot image, anomaly diagnosis of the application interface is performed based on the screenshot image, and feedback information is output on the terminal screen based on the diagnosis results. It is evident that this interface diagnosis method simplifies the diagnostic process and effectively improves diagnostic efficiency. Furthermore, since anomaly diagnosis of the application interface can be achieved through screenshot images, the entire diagnostic process does not require assistance from distributors or other users, effectively reducing labor costs.
[0171] It should be noted that the embodiments of the present invention also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The terminal's processor reads the computer instructions from the computer-readable storage medium, executes the computer instructions, and causes the terminal to perform the interface diagnosis method embodiments described above. Figure 2 or Figure 4 The steps performed in the process.
[0172] Furthermore, it should be understood that the above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Those skilled in the art can understand that implementing all or part of the processes of the above embodiments and making equivalent changes in accordance with the claims of this application are still within the scope of the invention.
Claims
1. An interface diagnostic method, characterized in that, include: Display the application interface of the target application on the terminal screen; If a screenshot operation targeting the application interface is detected, a screenshot image of the application interface is displayed on the terminal screen, and diagnostic components are displayed simultaneously. In response to a trigger operation on the diagnostic component, an anomaly diagnosis is performed on the application interface based on the screenshot image; wherein, the screenshot image is matched with each abnormal image in the image resource set, and the presence of an anomaly in the application interface is determined based on the matching degree between the screenshot image and each abnormal image; Based on the diagnostic results, feedback information is output on the terminal screen. If the diagnostic results indicate that there is an anomaly in the application interface, the feedback information includes a target solution, which is obtained by searching for a solution to resolve the target anomaly from a set of solutions. The target application includes multiple functional modules, with each functional module corresponding to an interface; the solution set includes a subset of solutions for each functional module, and each subset of solutions for a functional module includes at least one solution for an anomaly; the image resource set also includes at least one component image, which is an image that includes an operational component; any functional module is associated with each operational component in the interface corresponding to that functional module. The method of finding a solution for resolving the target anomaly from the solution set includes: determining the target component image contained in the screenshot image from the at least one component image; finding the functional module associated with the target operation component in the target component image from the plurality of functional modules; determining the found functional module as the target functional module corresponding to the application interface; finding a subset of target solutions for the target functional module from the solution set, and finding a solution for resolving the target anomaly from the subset of target solutions.
2. The method as described in claim 1, characterized in that, The method further includes: During the process of diagnosing anomalies in the application interface based on the screenshot image, diagnostic prompts are output on the terminal screen. The diagnostic prompt information is used to indicate that the application interface is in an abnormal diagnostic state.
3. The method as described in claim 1 or 2, characterized in that, The screenshot operation includes a screenshot trigger operation and a screenshot drawing operation; If a screenshot operation targeting the application interface is detected, displaying a screenshot image of the application interface on the terminal screen includes: If a screenshot trigger operation is detected for the application interface, a mask interface is displayed on the terminal screen. In the overlay interface, a screenshot area is drawn according to the screenshot drawing operation; In response to a region drawing end event, a screenshot of the application interface is displayed on the terminal screen, the screenshot being generated based on the interface content contained in the screenshot area.
4. The method as described in claim 3, characterized in that, The step of outputting feedback information on the terminal screen based on the diagnostic results includes: Switch from the overlay interface to the application interface; Feedback information is displayed in the application interface based on the diagnostic results.
5. The method as described in claim 1 or 2, characterized in that, If the diagnostic result indicates that there is no abnormality in the application interface, the feedback information includes a notification message, which is used to indicate that there is no abnormality in the application interface. If the diagnostic results indicate that the application interface is abnormal, the feedback information includes the target abnormality problem; wherein, the target abnormality problem is: the abnormality problem of the application interface determined based on the screenshot image.
6. The method as described in claim 1, characterized in that, The step of diagnosing anomalies in the application interface based on the screenshot image includes: Obtain an image resource set, wherein the image resource set includes at least one abnormal image, and each abnormal image corresponds to an abnormal issue; Calculate the matching degree between the screenshot image and each abnormal image, and find the target abnormal image from at least one abnormal image based on the calculated matching degree. The target abnormal image refers to an abnormal image with a matching degree greater than a threshold. If the target abnormal image is successfully found, it is determined that the application interface is abnormal; If the search for the target abnormal image fails, it is determined that the application interface does not have any abnormalities.
7. The method as described in claim 6, characterized in that, The target solution is obtained in the following way: Retrieve the solution set in the terminal's local space; Find a solution from the set of solutions to resolve the target anomaly. If a solution for resolving the target anomaly is successfully found from the set of solutions, the target solution is obtained based on the found solution. Otherwise, request the technical staff to return the target solution.
8. An interface diagnostic device, characterized in that, The device includes: The display unit is used to display the application interface of the target application on the terminal screen. The display unit is further configured to, if a screenshot operation targeting the application interface is detected, display a screenshot image of the application interface on the terminal screen and simultaneously display diagnostic components. A diagnostic unit is configured to respond to a trigger operation on the diagnostic component and perform anomaly diagnosis on the application interface based on the screenshot image; wherein, the screenshot image is matched with each abnormal image in the image resource set, and the application interface is determined to have an anomaly based on the matching degree between the screenshot image and each abnormal image; The output unit is used to output feedback information on the terminal screen according to the diagnostic results. If the diagnostic results indicate that there is an abnormality in the application interface, the feedback information includes a target solution, which is obtained after searching for a solution to solve the target abnormal problem from the solution set. The target application includes multiple functional modules, with each functional module corresponding to an interface; the solution set includes a subset of solutions for each functional module, and each subset of solutions for a functional module includes at least one solution for an anomaly; the image resource set also includes at least one component image, which is an image that includes an operational component; any functional module is associated with each operational component in the interface corresponding to that functional module. The method of finding a solution for resolving the target anomaly from the solution set includes: determining the target component image contained in the screenshot image from the at least one component image; finding the functional module associated with the target operation component in the target component image from the plurality of functional modules; determining the found functional module as the target functional module corresponding to the application interface; finding a subset of target solutions for the target functional module from the solution set, and finding a solution for resolving the target anomaly from the subset of target solutions.
9. A terminal, the terminal comprising an input device and an output device, characterized in that, The terminal also includes: A processor, adapted to implement one or more instructions; and computer storage media; The computer storage medium stores one or more instructions, which are adapted to be loaded by the processor and executed as described in any one of claims 1-7.
10. A computer storage medium, characterized in that, The computer storage medium stores one or more instructions, which are adapted to be loaded by a processor and executed as described in any one of claims 1-7.
11. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed by a processor, implement the method as described in any one of claims 1-7.