Event labeling method and device in application program, equipment and storage medium

Abstract

The application discloses an event labeling method and device in an application program, an event labeling equipment and a storage medium, and belongs to the technical field of application programs. The method comprises the following steps: displaying a user interface of an event labeling tool in a browser; in response to a starting operation on an application program explorer, displaying a user interface of the application program explorer in the user interface of the event labeling tool; after the application program explorer enters an element selection mode, in response to a selection operation on a first element in the user interface of the application program explorer, displaying event labeling information related to the first element in the user interface of the event labeling tool; and in response to a confirmation operation on the event labeling information, labeling an operation event matched with the event labeling information in an application program corresponding to the application program explorer. The application helps analysts to independently complete event labeling, and data can be obtained for analysis without changing and publishing the application program, so that the event labeling efficiency and the object behavior analysis efficiency are improved.

Description

Technical Field

[0001] This application relates to the field of application technology, and in particular to an event annotation method, apparatus, device, and storage medium within an application. Background Technology

[0002] After an application is released and launched, analysts typically need to collect and analyze data on the application's user behavior to obtain information on user usage and provide data support for the application's subsequent operation and optimization.

[0003] In related technologies, data is collected through code-based event tracking. This involves embedding code within the application at the points where statistics are needed to track events, thereby recording metrics such as clicks, visitor counts, page dwell time, and video playback duration. The process for code-based event tracking begins with the analyst defining the tracking requirements, including the events to be collected and the specific behaviors to be tracked. The analyst then communicates these requirements with the application developers, who implement the tracking. Further testing may be required by the analyst, developer, or application testers to verify the accuracy and effectiveness of the tracking. Finally, the tracking takes effect after the application is redeployed, and the corresponding events are automatically collected and reported.

[0004] It is evident that using code-based event tracking requires extensive communication and coordination, resulting in high communication costs. Furthermore, event tracking only becomes effective after application updates and releases, making it impossible to obtain data for analysis immediately. Summary of the Invention

[0005] This application provides an event annotation method, apparatus, device, and storage medium within an application, which helps analysts independently complete event annotation and obtain relevant data for analysis without application changes or releases, effectively improving event annotation efficiency and application object behavior analysis efficiency. The technical solution is as follows:

[0006] According to one aspect of the embodiments of this application, an event annotation method within an application is provided, the method comprising:

[0007] Display the user interface of the event annotation tool in the browser;

[0008] In response to a launch operation for an application experiencer, the user interface of the application experiencer is displayed in the user interface of the event annotation tool, the application experiencer being an application runtime instance used by the analyst for interaction.

[0009] After the application experiencer enters the element selection mode, in response to the selection operation of the first element in the user interface of the application experiencer, the event annotation information related to the first element is displayed in the user interface of the event annotation tool.

[0010] In response to the confirmation operation for the event annotation information, the operation event within the application corresponding to the application experiencer that matches the event annotation information is annotated.

[0011] According to one aspect of the embodiments of this application, an in-application event labeling device is provided, the device comprising:

[0012] The tool interface display module is used to display the user interface of the event annotation tool in the browser;

[0013] The experiencer interface display module is used to display the user interface of the application experiencer in the user interface of the event annotation tool in response to the launch operation of the application experiencer. The application experiencer refers to the runtime instance of the application used by the analyst for interaction.

[0014] The annotation information display module is used to display event annotation information related to the first element in the user interface of the event annotation tool in response to the selection operation of the first element in the user interface of the application experiencer after the application experiencer enters the element selection mode.

[0015] The operation event labeling module is used to respond to the confirmation operation of the event labeling information and label the operation events within the application corresponding to the application experiencer that match the event labeling information.

[0016] In some embodiments, the annotation information display module includes: an element set acquisition unit, configured to acquire a first element set from the user interface of the application experiencer in response to a selection operation on the first element, the first element set including the first element and similar elements of the first element; and an element selector display unit, configured to display selectors for each element in the first element set and its parent element in the user interface of the event annotation tool; wherein the event annotation information includes a selector for at least one element, the selector being used to indicate the interaction type and display characteristics of the element.

[0017] In some embodiments, the element set acquisition unit is configured to: acquire the DOM tree corresponding to the user interface of the application experiencer, the DOM tree being used to indicate each element in the user interface of the application experiencer and the hierarchical relationship between each element; search for similar elements of the first element based on the DOM tree, and construct the first element set based on the search results.

[0018] In some embodiments, the element set acquisition unit is further configured to: acquire the sibling elements of the first element, wherein the nodes corresponding to the sibling elements of the first element and the nodes corresponding to the first element are at the same level in the DOM tree; search for similar elements of the first element from the sibling elements of the first element; the similar elements of the first element have the same interaction type as the first element and have at least one identical display feature; if there are similar elements of the first element among the sibling elements of the first element, combine the first element and the similar elements of the first element to obtain the first element set; if there are no similar elements of the first element among the sibling elements of the first element, recursively search upwards in the DOM tree; wherein the recursive upward search means replacing the first element with the parent element of the first element and re-executing from acquiring the sibling elements of the first element; if the recursive upward search reaches the recursion level threshold and no similar elements of the first element are found, construct the first element set with the first element.

[0019] In some embodiments, the apparatus further includes an element enhancement display module, configured to: enhance the display of each element in the first element set and its parent element in the user interface of the application experiencer; and, in response to a removal operation of the selector of the second element in the user interface of the event annotation tool, cancel the enhanced display of the second element in the user interface of the application experiencer; wherein the second element refers to any element in the first element set and its parent element.

[0020] In some embodiments, the annotation information display module further includes a supplementary condition display unit, configured to: display at least one supplementary annotation condition in the user interface of the event annotation tool, the supplementary annotation condition including page routing parameters and element text content, the page routing parameters being used to restrict the operation event from the current user interface of the application experiencer, and the element text content being used to restrict the operation event to specified text content; wherein, in response to a selection operation for a first supplementary annotation condition among the at least one supplementary annotation conditions, the event annotation information further includes the first supplementary annotation condition.

[0021] In some embodiments, the apparatus further includes a selection mode control module, configured to: control the application experiencer to enter the element selection mode in response to an operation of a mode selection control in the user interface of the event annotation tool; wherein, when the application experiencer is in the element selection mode, the application experiencer does not respond to interactive operations received by the user interface of the application experiencer.

[0022] In some embodiments, the selection mode control module is further configured to: in response to an operation on the element reset control in the user interface of the event annotation tool, clear the currently selected element and the current event annotation information in the event annotation tool; and control the application experiencer to exit the element selection mode.

[0023] In some embodiments, the experiencer interface display module is configured to: in response to scene parameters received by the user interface of the event labeling tool, load the online code package of the application in the delivery channel corresponding to the scene parameters; run the online code package to obtain the application experiencer; and display the user interface of the application experiencer in the user interface of the event labeling tool; wherein, the startup operation for the application experiencer includes the scene parameters received by the user interface of the event labeling tool.

[0024] In some embodiments, the experiencer interface display module is configured to: load the online code package of the application; run the online code package to obtain the application experiencer; and, in response to the path parameters received by the user interface of the event annotation tool, display the user interface of the application experiencer in the user interface of the event annotation tool, wherein the initial user interface of the application experiencer matches the path parameters; wherein the startup operation for the application experiencer includes the path parameters received by the user interface of the event annotation tool.

[0025] According to one aspect of the embodiments of this application, a computer device is provided, the computer device including a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the event annotation method within an application as described above.

[0026] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, the storage medium storing a computer program that is loaded and executed by a processor to implement the event annotation method within an application as described above.

[0027] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including a computer program stored in a computer-readable storage medium, wherein a processor reads from the computer-readable storage medium and executes the computer program to implement the event annotation method within the application as described above.

[0028] The technical solutions provided in this application have at least the following beneficial effects:

[0029] Event annotation tools enable visual annotation of events within the application, reducing the difficulty of event annotation compared to code tracking. Analysts can independently annotate events using these tools, eliminating the need for extensive communication and coordination with developers and testers, thus reducing communication costs and improving annotation efficiency. Furthermore, all user actions within the application are collected and stored in real-time. When annotating events, the event annotation tool can immediately extract and store the corresponding events. Analysts can access and analyze this data instantly without needing to re-release or modify the application, further enhancing the efficiency of object behavior analysis. Attached Figure Description

[0030] Figure 1 This is a schematic diagram of an event labeling system provided in one embodiment of this application;

[0031] Figure 2 This is a flowchart of an event annotation method within an application provided in one embodiment of this application;

[0032] Figure 3 This is a schematic diagram illustrating the startup of an application experiencer provided in one embodiment of this application;

[0033] Figure 4 This is a schematic diagram illustrating the entry and exit of an element selection mode provided in one embodiment of this application;

[0034] Figure 5 This is a schematic diagram showing the event annotation information provided in one embodiment of this application;

[0035] Figure 6 This is a flowchart of an event annotation method within an application provided in another embodiment of this application;

[0036] Figure 7 This is a block diagram of an event labeling device within an application provided in one embodiment of this application;

[0037] Figure 8 This is a block diagram of an event labeling device within an application provided in another embodiment of this application;

[0038] Figure 9 This is a schematic diagram of the structure of a computer device provided in one embodiment of this application. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0040] Please refer to Figure 1 This illustration shows a schematic diagram of an event annotation system provided in one embodiment of this application. This event annotation system is used to annotate and extract events within an application to obtain data in real time for object behavior analysis of the application. Figure 1 As shown, the event labeling system includes: application 10, event labeling tool 20, and application experiencer 30.

[0041] In this embodiment of the application, the analyst uses the event annotation tool 20 to annotate the events that need to be extracted from the application 10. For example... Figure 1 As shown, the event annotation tool 20 runs on a browser. After receiving relevant parameters of the application (such as scene parameters, path parameters, etc.) input by the analyst, the event annotation tool 20 loads and runs the online code package of the application 10 through the browser based on the relevant parameters to obtain the application experiencer 30. The user interface of the application experiencer 30 is displayed in the user interface of the event annotation tool 20.

[0042] After the application experiencer 30 enters the element selection mode, in response to the analyst's selection operation on any element in the user interface of the application experiencer 30, the event annotation tool 20 displays the event annotation information related to the element in the user interface; then, in response to the analyst's confirmation operation on the event annotation information, the event annotation tool 20 annotates the operation events in the application 10 that match the event annotation information. These operation events will also be extracted and stored for the analyst to analyze the object behavior of the application 10.

[0043] Optionally, application 10 is a sub-application that depends on the target application to run. This sub-application can be called a mini-program. While a mini-program cannot run independently, it can be used without downloading or installing. For example, the sub-application can be opened directly by scanning its QR code or searching for its name. In this implementation, application 10 is the sub-application, and the target application is its parent application. The parent application provides the environment for the implementation of the sub-application, allowing it to be easily obtained and distributed. The parent application is a native application, which is an application that can run directly on the operating system. For example, the parent application can be a social application, a food application, a dedicated application that supports sub-applications, a file management application, an email application, or a game application; social applications include, but are not limited to, instant messaging applications, SNS (Social Network Service) applications, or live streaming applications.

[0044] In addition, such as Figure 1 As shown, the event annotation tool 20 and the browser that hosts it both run on a physical computer device 40. This computer device 40 can access a network to obtain online code packages of the application 10, etc. This network can be a wide area network, a local area network, a metropolitan area network, a personal area network, or the Internet, etc. Optionally, the computer device 40 can be implemented as a server, or as a terminal such as a tablet computer, mobile phone, or PC (Personal Computer). When implemented as a server, the computer device 40 can be a single server, a server cluster composed of multiple servers, or a cloud computing center; this embodiment of the application does not limit this.

[0045] related Figure 1 For further descriptions of the application experiencer and its launch method, element selection mode and its entry and exit methods, event labeling information and its acquisition and display methods, etc. in the embodiments, please refer to the following method embodiments, which will not be repeated here.

[0046] Please refer to Figure 2 It illustrates a flowchart of an event annotation method within an application provided in one embodiment of this application. This method can be applied to event annotation tools, such as those used in... Figure 1 The event annotation tool 20 is shown. For example... Figure 2 As shown, the event annotation method includes at least one of the following steps (steps 210 to 240).

[0047] Step 210: Display the user interface of the event annotation tool in the browser.

[0048] The event annotation tool runs in a browser. Once launched, its user interface will be displayed in the browser. Optionally, the event annotation tool can be launched by entering a URL, searching for a name, scanning a QR code, or entering voice commands in the browser.

[0049] This application embodiment does not limit the content displayed in the initial user interface after the event annotation tool is launched. Optionally, the initial user interface displays an input interface for authentication information such as account name, login password, and biometrics. In response to the corresponding information entered by the analyst, the event annotation tool jumps from the initial user interface to the user interface in the normal working state; or, the initial user interface directly displays the user interface in the normal working state. The user interface in the normal working state includes at least one of the following: a user interface for launching the application experiencer, a user interface for performing event annotation, and a user interface for setting event annotation attributes (such as name, event storage location, etc.).

[0050] Step 220: In response to the launch operation for the application experiencer, display the user interface of the application experiencer in the user interface of the event labeling tool.

[0051] An application experiencer is a runtime instance of an application used by analysts for interaction. It is generated by loading and running the online code package of the application in a browser. Upon launching the application experiencer, its user interface is displayed directly within the event annotation tool's user interface. Optionally, the display hierarchy of the application experiencer's user interface can be equal to that of the event annotation tool's user interface, allowing it to be displayed in a blank area of ​​the event annotation tool's user interface; alternatively, the application experiencer's user interface can be displayed above the event annotation tool's user interface via a floating window or similar means. Optionally, the display of the application experiencer's user interface within the event annotation tool's user interface can be fixed or flexibly movable. When the application experiencer's user interface is flexibly movable, the display positions of various elements within the event annotation tool's user interface can be adaptively moved to avoid obstruction; or, when the application experiencer's user interface is displayed as a floating window or similar means, the event annotation tool's user interface can remain unchanged.

[0052] This application does not limit the launch method of the application experiencer. Optionally, the application experiencer can be launched by entering a URL, searching for a name, scanning a QR code, entering a voice command, or entering authentication information. Several launch methods of the application experiencer are illustrated below.

[0053] In one example, the above-mentioned startup operation for the application experiencer includes scene parameters received by the user interface of the event labeling tool; based on this, step 220 includes: in response to the scene parameters received by the user interface of the event labeling tool, loading the online code package of the application in the delivery channel corresponding to the scene parameters; running the online code package to obtain the application experiencer; and displaying the user interface of the application experiencer in the user interface of the event labeling tool.

[0054] In another example, the above-described launch operation for the application experiencer includes path parameters received by the user interface of the event annotation tool; based on this, step 220 includes: loading the online code package of the application; running the online code package to obtain the application experiencer; and, in response to the path parameters received by the user interface of the event annotation tool, displaying the user interface of the application experiencer in the user interface of the event annotation tool, wherein the initial user interface of the application experiencer matches the path parameters.

[0055] The aforementioned scenario parameters are used to locate the source channel of the online code package, i.e., the distribution channel of the application corresponding to the application experiencer, such as the source of the application acquisition or the parent application that provides the environment for the application's operation. The aforementioned path parameters are used to locate the initial user interface of the application experiencer, such as the homepage, settings page, login page, or personal information page. In practical applications, the application experiencer can also be launched by combining scenario parameters and path parameters. Optionally, the user interface of the event annotation tool can also display an experiencer launch control. If the analyst does not input scenario parameters and / or path parameters but operates the experiencer launch control, the event annotation tool responds to the operation on the experiencer launch control and launches the application experiencer according to the default scenario parameters and / or default path parameters.

[0056] For example, such as Figure 3 As shown, the event annotation tool's user interface 310 displays an input interface 312 for scene parameters and an input interface 314 for path parameters. After the analyst inputs the corresponding parameters into input interfaces 312 and 314, the event annotation tool receives the scene parameters and path parameters. First, in response to the scene parameters, the online code package of the application in the delivery channel corresponding to the scene parameters is loaded; then, the online code package is run to obtain the application demo; then, in response to the path parameters, the user interface 320 of the application demo is displayed in the event annotation tool's user interface 310. The initial user interface of the application demo matches the path parameters.

[0057] In another example, the aforementioned launch operation for the application experiencer includes authentication information received by the user interface of the event annotation tool. Based on this, step 220 includes: responding to the authentication information received by the user interface of the event annotation tool, obtaining historical program parameters corresponding to the authentication information, including historical scenario parameters and historical path parameters; loading the online code package of the application in the delivery channel corresponding to the historical scenario parameters; running the online code package to obtain the application experiencer; and displaying the user interface of the application experiencer in the user interface of the event annotation tool, wherein the initial user interface of the application experiencer matches the historical path parameters. Optionally, the authentication information includes, but is not limited to, account name, login password, biometrics, etc.

[0058] The historical program parameters can be the scene parameters and path parameters entered by the analyst when they last annotated an event using the event annotation tool, or the scene parameters corresponding to the source channel of the loaded online code package and the path parameters corresponding to the source page of the annotated event. Alternatively, the historical program parameters can also be the scene parameters and path parameters entered most frequently by the analyst in the previous N (N is an integer greater than 2) instances of event annotation using the event annotation tool, or the scene parameters corresponding to the source channel of the most frequently loaded online code package and the path parameters corresponding to the source page of the most annotated events. This embodiment of the application does not limit this.

[0059] The event annotation tool can record and store the correspondence between authentication information and historical program parameters. Each time an analyst enters authentication information and program parameters, or after completing event annotation, the tool updates this correspondence, replacing some or all of the stored historical program parameters with the current program parameters. Optionally, the event annotation tool's user interface can display a parameter update control. After completing event annotation, the analyst can freely choose whether to replace historical program parameters with the current program parameters through the parameter update control, thereby updating the aforementioned correspondence.

[0060] Step 230: After the application experiencer enters the element selection mode, in response to the selection operation of the first element in the user interface of the application experiencer, the event annotation information related to the first element is displayed in the user interface of the event annotation tool.

[0061] Once the application experiencer is launched, analysts can interact with it just like users of the application. For each interaction, the application experiencer provides corresponding feedback according to the application's operational logic. However, when the application experiencer is in element selection mode, it does not respond to interactions received by the user interface; instead, the event annotation tool responds to these interactions.

[0062] In the application experiencer's element selection mode, the analyst's interactive operations on the application experiencer's user interface include selecting any element within the user interface. This element refers to a visible element in the user interface, and its types include, but are not limited to, text, images, buttons, symbols, icons, sliders, videos, progress bars, audio, and labels. At this time, the event annotation tool responds to the selection operation and displays event annotation information related to that element in its user interface. For details regarding the content, acquisition method, and display method of the event annotation information, please refer to the following method embodiments.

[0063] This application embodiment does not limit the method of entering and exiting the element selection mode. Optionally, the element selection mode can be entered and exited by operating on a specific control, inputting voice commands, inputting gestures, etc. In one example, taking the operation of a specific control as an example of entering and exiting the element selection mode, after step 220 above, it further includes: responding to the operation of the mode selection control in the user interface of the event annotation tool, controlling the application experiencer to enter the element selection mode; after controlling the application experiencer to enter the element selection mode, it further includes: responding to the operation of the element reset control in the user interface of the event annotation tool, clearing the currently selected element and the current event annotation information in the event annotation tool, and controlling the application experiencer to exit the element selection mode. The mode selection control and the element reset control can be displayed in the form of buttons, icons, sliders, etc., and the operations on the mode selection control and the element reset control include, but are not limited to, click operations, double-click operations, press operations, and swipe operations.

[0064] For example, such as Figure 4 As shown, the user interface 410 of the event annotation tool displays a mode selection control 412 and an element reset control 414. After the analyst clicks the mode selection control 412, the application experiencer enters element selection mode and no longer responds to interactive operations on the user interface 420 of the application experiencer. When the application experiencer is in element selection mode, if the analyst clicks any element 422 in the user interface 420 of the application experiencer, the event annotation tool responds to the analyst's operation and displays the event annotation information 416 related to the element 422 in the user interface 410 of the event annotation tool. After the analyst clicks the element reset control 414, the currently selected element 422 and the current event annotation information 416 are cleared in the event annotation tool, and the application experiencer also exits element selection mode and resumes responding to the analyst's interactive operations on the user interface 420 of the application experiencer.

[0065] Step 240: In response to the confirmation operation for the event annotation information, annotate the operation event within the application corresponding to the application experiencer that matches the event annotation information.

[0066] Analysts can modify event annotation information; please refer to the following method embodiments for details on how to modify event annotation information. If the analyst has no need for modification or has already completed the modification, event annotation can be completed by confirming the event annotation information. This application embodiment does not limit the method of confirming event annotation information; optionally, event annotation information can be confirmed by operating a specific control, inputting voice commands, inputting gestures, etc. For example, ... Figure 4 As shown, the user interface 410 of the event annotation tool displays an information confirmation control 418. The analyst can confirm the event annotation information by clicking the information confirmation control 418.

[0067] In response to the analyst's confirmation of the event annotation information, the event annotation tool annotates all operation events within the application corresponding to the application experiencer that match the event annotation information. In this embodiment, the event type of the operation event annotated by the event annotation tool in step 240 may or may not be the same as the type of selection operation performed by the analyst in step 230. For example, if the selection operation performed by the analyst is a click operation, the operation events annotated by the event annotation tool may include only click events, or may include click events, press events, swipe events, double-click events, etc.

[0068] In this embodiment, all user actions on the application are collected and stored in real time, such as on the application's server. When performing event annotation, the event annotation tool can extract operation events matching the annotation information from the storage location of the operation events and export or store them in a default storage location or a storage location specified by the analyst, allowing the analyst to instantly obtain relevant data and conduct object behavior analysis of the application.

[0069] In summary, this application embodiment launches the application experiencer corresponding to the application through an event annotation tool. When the application experiencer is in element selection mode, in response to the analyst's selection operation on any element in the user interface of the application experiencer, it acquires and displays the event annotation information related to that element. Then, in response to the analyst's confirmation operation on the event annotation information, it annotates all operation events within the application that match the event annotation information. This application embodiment achieves visual annotation of events within the application through an event annotation tool, reducing the difficulty of event annotation compared to code tracking. Analysts can independently complete event annotation through the event annotation tool without needing to communicate and coordinate with developers and testers, reducing communication costs and improving event annotation efficiency. Furthermore, all operation events of the application by users are collected and stored in real time. Therefore, when the event annotation tool performs event annotation, it can immediately extract and store the corresponding operation events. Analysts can obtain relevant data and conduct analysis immediately without needing to change or release the application, which helps improve the efficiency of object behavior analysis of the application.

[0070] In addition, this application provides multiple ways to flexibly launch the application experiencer. Launching the application experiencer via scene parameters allows selection of the application's distribution channel, enabling targeted analysis of the application's object behavior under that channel. Launching the application experiencer via path parameters allows selection of the initial user interface displayed after launch, directly locating the source page of the event to be labeled by the analyst. Launching the application experiencer via historical program parameters corresponding to authentication information can match the analyst's labeling habits, allowing the analyst to quickly perform event labeling.

[0071] The following section explains how to obtain, display, and modify event annotation information.

[0072] In one example, step 230 above includes the following sub-steps (steps 232 to 234).

[0073] Step 232, in response to the selection operation for the first element, obtain the first element set from the user interface of the application experiencer.

[0074] The first element set includes the first element and its similar elements. Optionally, the similar elements of the first element have at least one of the following characteristics: having the same interaction type as the first element, having the same or partially the same display characteristics as the first element, having the same text content as the first element, or being located in the same display area as the first element.

[0075] Optionally, embodiments of this application obtain similar elements through a DOM (Document Object Model) tree. Based on this, step 232 includes: obtaining the DOM tree corresponding to the user interface of the application experiencer; searching for similar elements of the first element based on the DOM tree; and constructing a set of the first elements based on the search results. The DOM tree is used to indicate each element in the user interface of the application experiencer, and the hierarchical relationship between these elements. Each node in the DOM tree corresponds to an element in the user interface of the application experiencer, and each node includes information such as the element's identifier, hierarchy, instance, and child nodes. When obtaining similar elements through the DOM tree, the event annotation tool can reduce the search scope and improve search efficiency based on heuristic search.

[0076] Based on this, optionally, the above-mentioned method of searching for similar elements of the first element based on the DOM tree and constructing a set of the first element based on the search results includes: obtaining the sibling elements of the first element; searching for similar elements of the first element from the sibling elements of the first element; if there are similar elements of the first element among the sibling elements of the first element, then combining the first element and the similar elements of the first element to obtain a set of the first element; if there are no similar elements of the first element among the sibling elements of the first element, then recursively searching upwards in the DOM tree; if the recursive search upwards reaches the recursion level threshold and no similar elements of the first element are found, then constructing a set of the first element with the first element.

[0077] In this example, the nodes corresponding to the sibling elements of the first element are at the same level in the DOM tree as the node corresponding to the first element. By searching for similar elements among the sibling elements of the first element, the search scope is effectively reduced. Similar elements to the first element are defined to have the same interaction type (i.e., tag) and at least one identical display characteristic (i.e., class tag). Interaction types include, but are not limited to, click, press, and swipe; display characteristics include, but are not limited to, display color, display shape, display position, and display element.

[0078] If no similar element exists among the sibling elements of the first element, the event annotation tool recursively searches upwards in the DOM tree. This upward recursive search means replacing the first element with its parent element and re-executing the search starting from the first element's sibling elements; in other words, it re-executes the search for similar elements using the first element's parent element. This upward recursive search can account for nested elements in list rendering, improving the accuracy of similar element searches. However, considering the number of levels in list rendering and the efficiency of similar element searches, this example sets a recursion level threshold for the upward recursive search, such as two or three levels. If the upward recursive search does not reach the recursion level threshold and a similar element is found, a set of the first element is constructed using the first element and its similar elements. If the upward recursive search reaches the recursion level threshold and no similar element is found, the event annotation tool abandons the search for similar elements and directly constructs the set of the first element using the first element itself.

[0079] Step 234: In the user interface of the event annotation tool, display the selectors for each element in the first element set and its parent element.

[0080] Event annotation information includes a selector for at least one element, which indicates the element's interaction type and display characteristics. After acquiring the event annotation information, the event annotation tool can display it in its user interface for analysts to modify and confirm. Optionally, to reduce the difficulty of understanding the event annotation information and provide positive feedback to analysts, while the event annotation tool displays the event annotation information, the user interface of the application experiencer can also enhance the display of each element in the first element set and its parent element. Optionally, the enhancement display methods include, but are not limited to, highlighting text and images, bolding text and lines, and adding text and icons.

[0081] When analysts need to modify the event, they can precisely select the source element by manipulating the selector. Based on this, after the event annotation tool displays the event annotation information, in response to the removal of the selector for the second element in the event annotation tool's user interface, the enhanced display of the second element is canceled in the application experiencer's user interface. Here, the second element refers to any element in the first element set and its parent element. The removal operation for the second element's selector includes, but is not limited to, click, swipe, and press operations. When the analyst removes the selector for the second element, in addition to canceling the enhanced display of the second element in the application experiencer's user interface, the display style of the second element's selector can also be changed in the event annotation tool's user interface to remind the analyst whether the second element is selected. Optionally, the change in display style includes, but is not limited to, at least one of the following: change in display color, change in icon state, change in display content, etc.

[0082] For example, such as Figure 5 As shown, assuming the analyst clicks on element 522 in the user interface 520 of the application experiencer, the event annotation tool automatically infers similar elements of element 522 to construct a first element set, and displays event annotation information in the user interface 510 of the event annotation tool. This event annotation information includes selectors 512 for each element in the first element set and its parent element. At the same time, the user interface 520 of the application experiencer enhances the display of element 522 and its similar elements 524 by bolding the text, and enhances the display of the parent elements of these elements by highlighting the area.

[0083] In one example, to meet the analyst's need for richer and more accurate event annotation, after step 232 above, the method further includes: displaying at least one supplementary annotation condition in the user interface of the event annotation tool; wherein, in response to the selection operation of the first supplementary annotation condition among the at least one supplementary annotation condition, the event annotation information also includes the first supplementary annotation condition.

[0084] Optionally, supplementary annotation conditions include at least one of the following: page routing parameters, element text content, and operation event type. Page routing parameters restrict the operation event to originating from the current user interface of the application experiencer; element text content restricts the operation event to specific text content; and operation event type restricts the operation event to a specified event type. Optionally, event types include, but are not limited to, click events, press events, double-click events, and swipe events. It should be understood that when the analyst specifies the operation event type, the event type annotated and extracted by the event annotation tool may differ from the analyst's selection of the event source element. For example, if the analyst selects the event source element through a click operation, but subsequently adds swipe and press events as supplementary annotation conditions, the event annotation tool will annotate and extract swipe and press events for the event source element and its related elements.

[0085] For example, such as Figure 5 As shown, the user interface 510 of the event annotation tool also displays three types of supplementary annotation conditions: page routing parameters 514, element text content 516, and operation event type 518. Analysts can add restrictions to the event annotation information by clicking the content or control corresponding to page routing parameters 514, specifying that the operation event originates from the current user interface of the application experiencer; by clicking the content or control corresponding to element text content 516, analysts can add restrictions to the event annotation information by specifying that the operation event applies to the specified text content; and by clicking the content or control corresponding to operation event type 518, analysts can add restrictions to the event annotation information by specifying that the operation event is of the specified event type.

[0086] In summary, this application embodiment, after the analyst selects an event source element from the application experiencer's user interface, automatically infers similar elements of the event source element using an event annotation tool. Based on the event source element and its similar elements, it obtains and displays event annotation information, facilitating rapid annotation of events corresponding to a class of elements. Furthermore, when inferring similar elements, the event annotation tool considers the possibility of list rendering in the user interface, and recursively searches for similar elements upwards from the parent element of the event source element when necessary, improving the accuracy and comprehensiveness of similar element searches. Additionally, this application embodiment further restricts event annotation information by adding parameters such as page routing parameters, element text content, and operation event types, meeting the analyst's needs for richer and more precise event annotation.

[0087] The following describes the overall process of the event annotation method provided in this application using an embodiment. This method can be applied to event annotation tools, such as those used in... Figure 1The event annotation tool 20 is shown. In one example, the event annotation tool includes a runtime control layer, an event annotation editor, and an event definition manager. Figure 6 As shown, the event annotation method includes at least one of the following steps (steps 610 to 670).

[0088] Step 610, runtime initialization.

[0089] The runtime control layer performs runtime initialization, which includes loading the application's online codebase, running the online codebase, and displaying the application experiencer's user interface. After loading the application's online codebase, the event annotation tool can automatically inject custom scripts to wrap `addEventListener`, enabling the interception and recording of operation events. Additionally, `pauseInnerCaptureMouseListeners` and `resumeInnerCaptureMouseListeners` are used to dynamically close and resume interactive operations on the application experiencer's user interface, respectively. Furthermore, by registering lifecycle hooks such as closing the application experiencer and route changes, the normal operation of the application experiencer is ensured; methods such as entering element selection mode, exiting element selection mode, and enhancing display are wrapped, and custom logic is added by injecting scripts into the corresponding layers (native, webview) within the application experiencer's iframe (inline frame).

[0090] Step 620: Control the application experiencer to enter element selection mode.

[0091] The event definition manager responds to the analyst's actions by sending corresponding instructions to the runtime control layer, controlling the application experiencer to enter element selection mode, preventing the application experiencer from responding to interactive operations on its user interface, and adding overriding hover and click events.

[0092] Step 630: Calculate similar elements of the element that is the source of the event and display the event annotation information.

[0093] In response to the analyst's selection of the event source element, the event definition manager returns the event source element to the event annotation editor. The event annotation editor further infers similar elements of the event source element, determines the selector of at least one element in the event annotation information based on the event source element and its similar elements, and initializes the display of the event annotation information.

[0094] Step 640: Enhance the display of corresponding elements based on event annotation information.

[0095] The event definition manager coordinates the runtime control layer to enhance the display of corresponding elements in the application experiencer's user interface based on the selectors in the event annotation information and the selection operations of the supplementary annotation conditions set by the analyst for the event annotation editor.

[0096] Step 650: Determine whether the event annotation information has been modified.

[0097] The event definition manager responds to the analyst's actions by determining whether the event annotation information has been modified. If the event annotation information has been modified, step 640 above is re-executed with the modified event annotation information, meaning the event annotation editor needs to respond to element changes; if the event annotation information has not been modified, step 660 below is executed.

[0098] Step 660: Determine whether the application experiencer has exited element selection mode.

[0099] The event definition manager responds to the analyst's actions by determining whether the application experiencer has exited element selection mode, i.e., whether the event annotation information has been reset. If the application experiencer has exited element selection mode, the process will restart from step 620 above after the analyst restarts element selection mode; if the application experiencer has not exited element selection mode, the process will continue to step 670 below.

[0100] Step 670: Label the operation events that match the event labeling information.

[0101] The event definition manager responds to the analyst's confirmation of event annotation information, annotates all operation events within the application that match the event annotation information, and stores these operation events for the analyst to perform object behavior analysis, etc.

[0102] related Figure 6 For details regarding the entry and exit methods of element selection mode, the calculation method of similar elements, the startup method of the application experiencer, the specific content of event annotation information, the element enhancement display method, and other descriptions in the embodiments, please refer to the above method embodiments, which will not be elaborated here.

[0103] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0104] Please refer to Figure 7This diagram illustrates a block diagram of an event annotation apparatus within an application according to an embodiment of this application. The apparatus has the functionality to implement the aforementioned example of an event annotation method within an application; this functionality can be implemented in hardware or by hardware executing corresponding software. The apparatus 700 can be a computer device or can be installed within a computer device. The apparatus 700 may include a tool interface display module 710, an experience interface display module 720, an annotation information display module 730, and an operation event annotation module 740.

[0105] Tool interface display module 710 is used to display the user interface of the event annotation tool in a browser.

[0106] The experiencer interface display module 720 is used to display the user interface of the application experiencer in the user interface of the event annotation tool in response to the launch operation of the application experiencer, wherein the application experiencer refers to the runtime instance of the application used by the analyst for interaction.

[0107] The annotation information display module 730 is used to display event annotation information related to the first element in the user interface of the event annotation tool in response to the selection operation of the first element in the user interface of the application experiencer after the application experiencer enters the element selection mode.

[0108] The operation event labeling module 740 is used to respond to the confirmation operation of the event labeling information and label the operation events within the application corresponding to the application experiencer that match the event labeling information.

[0109] In one example, such as Figure 8 As shown, the annotation information display module 730 includes: an element set acquisition unit 732, configured to acquire a first element set from the user interface of the application experiencer in response to a selection operation on the first element, the first element set including the first element and similar elements of the first element; and an element selector display unit 734, configured to display selectors for each element in the first element set and its parent element in the user interface of the event annotation tool; wherein, the event annotation information includes a selector for at least one element, the selector being used to indicate the interaction type and display characteristics of the element.

[0110] In one example, such as Figure 8As shown, the element set acquisition unit 732 is used to: acquire the DOM tree corresponding to the user interface of the application experiencer, the DOM tree being used to indicate each element in the user interface of the application experiencer, and the hierarchical relationship between each element; search for similar elements of the first element based on the DOM tree, and construct the first element set based on the search results.

[0111] In one example, such as Figure 8 As shown, the element set acquisition unit 732 is further configured to: acquire the sibling elements of the first element, wherein the nodes corresponding to the sibling elements of the first element and the nodes corresponding to the first element are at the same level in the DOM tree; search for similar elements of the first element from the sibling elements of the first element; the similar elements of the first element have the same interaction type as the first element and have at least one identical display feature; if there are similar elements of the first element among the sibling elements of the first element, combine the first element and the similar elements of the first element to obtain the first element set; if there are no similar elements of the first element among the sibling elements of the first element, recursively search upwards in the DOM tree; wherein, the upward recursive search refers to replacing the first element with the parent element of the first element and re-executing from acquiring the sibling elements of the first element; if the upward recursive search reaches the recursion level threshold and no similar elements of the first element are found, construct the first element set with the first element.

[0112] In one example, such as Figure 8 As shown, the device 700 further includes an element enhancement display module 750, configured to: enhance the display of each element in the first element set and its parent element in the user interface of the application experiencer; and, in response to a removal operation of the selector of the second element in the user interface of the event annotation tool, cancel the enhanced display of the second element in the user interface of the application experiencer; the second element refers to any element in the first element set and its parent element.

[0113] In one example, such as Figure 8As shown, the annotation information display module 730 further includes a supplementary condition display unit 736, used to: display at least one supplementary annotation condition in the user interface of the event annotation tool, the supplementary annotation condition including page routing parameters and element text content, the page routing parameters being used to restrict the operation event from the current user interface of the application experiencer, and the element text content being used to restrict the operation event to specified text content; wherein, in response to the selection operation of the first supplementary annotation condition among the at least one supplementary annotation conditions, the event annotation information also includes the first supplementary annotation condition.

[0114] In one example, such as Figure 8 As shown, the device 700 further includes a selection mode control module 760, configured to: control the application experiencer to enter the element selection mode in response to an operation of the mode selection control in the user interface of the event annotation tool; wherein, when the application experiencer is in the element selection mode, the application experiencer does not respond to interactive operations received by the user interface of the application experiencer.

[0115] In one example, such as Figure 8 As shown, the selection mode control module 760 is further configured to: in response to an operation on the element reset control in the user interface of the event annotation tool, clear the currently selected element and the current event annotation information in the event annotation tool; and control the application experiencer to exit the element selection mode.

[0116] In one example, the experiencer interface display module 720 is configured to: in response to scene parameters received by the user interface of the event labeling tool, load the online code package of the application in the delivery channel corresponding to the scene parameters; run the online code package to obtain the application experiencer; and display the user interface of the application experiencer in the user interface of the event labeling tool; wherein, the startup operation for the application experiencer includes the scene parameters received by the user interface of the event labeling tool.

[0117] In one example, the experiencer interface display module 720 is configured to: load the online code package of the application; run the online code package to obtain the application experiencer; and, in response to the path parameters received by the user interface of the event annotation tool, display the user interface of the application experiencer in the user interface of the event annotation tool, wherein the initial user interface of the application experiencer matches the path parameters; wherein the startup operation for the application experiencer includes the path parameters received by the user interface of the event annotation tool.

[0118] In summary, this application embodiment launches the application experiencer corresponding to the application through an event annotation tool. When the application experiencer is in element selection mode, in response to the analyst's selection operation on any element in the user interface of the application experiencer, it acquires and displays the event annotation information related to that element. Then, in response to the analyst's confirmation operation on the event annotation information, it annotates all operation events within the application that match the event annotation information. This application embodiment achieves visual annotation of events within the application through an event annotation tool, reducing the difficulty of event annotation compared to code tracking. Analysts can independently complete event annotation through the event annotation tool without needing to communicate and coordinate with developers and testers, reducing communication costs and improving event annotation efficiency. Furthermore, all operation events of the application by users are collected and stored in real time. Therefore, when the event annotation tool performs event annotation, it can immediately extract and store the corresponding operation events. Analysts can obtain relevant data and conduct analysis immediately without needing to change or release the application, which helps improve the efficiency of object behavior analysis of the application.

[0119] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0120] Please refer to Figure 9 This illustration shows a schematic diagram of the structure of a computer device provided in an embodiment of this application. This computer device can be used to implement the functionality of the event annotation method example within the aforementioned application. Specifically:

[0121] The computer device 900 includes a processing unit (such as a CPU (Central Processing Unit), GPU (Graphics Processing Unit), and FPGA (Field Programmable Gate Array)) 901, a system memory 904 including RAM (Random-Access Memory) 902 and ROM (Read-Only Memory) 903, and a system bus 905 connecting the system memory 904 and the central processing unit 901. The computer device 900 also includes an I / O system 906 that facilitates information transfer between various devices within the computer device, and a mass storage device 907 for storing the operating system 913, application programs 914, and other program modules 915.

[0122] The basic input / output system 906 includes a display 908 for displaying information and an input device 909 for user input, such as a mouse or keyboard. Both the display 908 and the input device 909 are connected to the central processing unit 901 via an input / output controller 910 connected to the system bus 905. The basic input / output system 906 may also include the input / output controller 910 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 910 also provides output to a display screen, printer, or other types of output devices.

[0123] The mass storage device 907 is connected to the central processing unit 901 via a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer-readable media provide non-volatile storage for the computer device 900. That is, the mass storage device 907 may include computer-readable media (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.

[0124] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage medium is not limited to the above-mentioned types. The system memory 904 and mass storage device 907 described above can be collectively referred to as memory.

[0125] According to an embodiment of this application, the computer device 900 can also be connected to a remote computer on a network, such as the Internet, for operation. That is, the computer device 900 can be connected to a network 912 via a network interface unit 911 connected to the system bus 905, or the network interface unit 911 can be used to connect to other types of networks or remote computer systems (not shown).

[0126] The memory also includes a computer program stored in the memory and configured to be executed by one or more processors to implement the event labeling method within the application described above.

[0127] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein a computer program is stored therein, the computer program being loaded and executed by a processor to implement the event annotation method within the application described above.

[0128] Optionally, the computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), solid-state drives (SSDs), or optical discs, etc. The random access memory may include resistive random access memory (ReRAM) and dynamic random access memory (DRAM).

[0129] In an exemplary embodiment, a computer program product is also provided, comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to implement the event annotation method within the application described above.

[0130] It should be understood that "multiple" as used herein refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0131] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

[0132] In this application, the relevant data and event processing (such as collection, recording, storage, etc.) should be strictly carried out in accordance with the requirements of relevant national laws and regulations, obtaining the informed consent or separate consent of the personal information subject (or having other legal basis), and subsequent data use and processing (such as extraction, statistics, analysis, etc.) should be carried out within the scope of laws and regulations and the authorization of the personal information subject.

[0133] In this application, when the facial (or other biometric) recognition technology is applied to specific products or technologies, the collection, use and processing of related data should comply with the requirements of national laws and regulations. Before collecting facial information, the information processing rules should be communicated and the informed consent or separate consent of the personal information subject should be obtained (or there should be other legal basis). Facial information should be processed in strict accordance with the requirements of laws and regulations and personal information processing rules, and technical measures should be taken to ensure the security of related data.

Claims

1. An event annotation method within an application, characterized in that, The method includes: Display the user interface of the event annotation tool in the browser; In response to a launch operation for an application experiencer, the user interface of the application experiencer is displayed in the user interface of the event annotation tool, the application experiencer being an application runtime instance used by the analyst for interaction. After the application experiencer enters the element selection mode, in response to the selection operation of the first element in the user interface of the application experiencer, a first element set is obtained from the user interface of the application experiencer. The first element set includes the first element and similar elements of the first element. In the user interface of the event annotation tool, selectors for each element in the first element set and its parent element are displayed; wherein, the event annotation information includes a selector for at least one element, the selector being used to indicate the interaction type and display characteristics of the element; In response to the confirmation operation for the event annotation information, the operation event within the application corresponding to the application experiencer that matches the event annotation information is annotated.

2. The method according to claim 1, characterized in that, The step of obtaining the first set of elements from the user interface of the application experiencer includes: Obtain the Document Object Model (DOM) tree corresponding to the user interface of the application experiencer. The DOM tree is used to indicate each element in the user interface of the application experiencer and the hierarchical relationship between the elements. Search for similar elements of the first element based on the DOM tree, and construct the set of the first element based on the search results.

3. The method according to claim 2, characterized in that, The step of searching for similar elements of the first element based on the DOM tree and constructing the first element set based on the search results includes: Get the sibling elements of the first element, where the node corresponding to the sibling element of the first element is at the same level as the node corresponding to the first element in the DOM tree; Search for similar elements of the first element from its sibling elements; the similar elements of the first element have the same interaction type as the first element and have at least one identical display feature. If there are similar elements to the first element among the sibling elements of the first element, then combine the first element and the similar elements of the first element to obtain the set of the first element; If there is no similar element among the sibling elements of the first element, then the search is performed recursively upwards in the DOM tree; wherein, the recursive upward search means replacing the first element with the parent element of the first element and starting again from obtaining the sibling elements of the first element; If the upward recursive search reaches the recursion level threshold and no similar elements to the first element are found, the first element set is constructed using the first element.

4. The method according to claim 1, characterized in that, After obtaining the first set of elements from the user interface of the application experiencer, the process further includes: In the user interface of the application experiencer, the individual elements in the first element set and their parent elements are displayed in an enhanced manner; In response to the removal operation of the selector of the second element in the user interface of the event annotation tool, the enhanced display of the second element is canceled in the user interface of the application experiencer; the second element refers to any element in the first element set and its parent element.

5. The method according to claim 1, characterized in that, After obtaining the first set of elements from the user interface of the application experiencer, the process further includes: At least one supplementary annotation condition is displayed in the user interface of the event annotation tool. The supplementary annotation condition includes page routing parameters and element text content. The page routing parameters are used to restrict the operation event from the current user interface of the application experiencer, and the element text content is used to restrict the operation event to specified text content. In response to the selection operation of the first supplementary annotation condition among the at least one supplementary annotation conditions, the event annotation information further includes the first supplementary annotation condition.

6. The method according to claim 1, characterized in that, After displaying the user interface of the application experiencer in the user interface of the event labeling tool, the method further includes: In response to an operation on the mode selection control in the user interface of the event annotation tool, the application experiencer is controlled to enter the element selection mode; Specifically, when the application experiencer is in the element selection mode, the application experiencer does not respond to interactive operations received by the user interface of the application experiencer.

7. The method according to claim 6, characterized in that, After the application experiencer is controlled to enter the element selection mode, the method further includes: In response to an operation that resets the element control in the user interface of the event annotation tool, the currently selected element and the current event annotation information are cleared in the event annotation tool; Control the application experiencer to exit the element selection mode.

8. The method according to any one of claims 1 to 7, characterized in that, The step of displaying the application experience's user interface in the event annotation tool's user interface in response to a launch operation for the application experience includes: In response to the scene parameters received by the user interface of the event annotation tool, the application loads the online code package in the delivery channel corresponding to the scene parameters; Running the online code package yields the application demo; The user interface of the application experiencer is displayed in the user interface of the event labeling tool; The startup operation for the application experiencer includes the scene parameters received by the user interface of the event annotation tool.

9. The method according to any one of claims 1 to 7, characterized in that, The step of displaying the application experience's user interface in the event annotation tool's user interface in response to a launch operation for the application experience includes: Load the online code package of the application; Running the online code package yields the application demo; In response to the path parameters received by the user interface of the event annotation tool, the user interface of the application experiencer is displayed in the user interface of the event annotation tool, and the initial user interface of the application experiencer is matched with the path parameters; The startup operation for the application experiencer includes the path parameters received by the user interface of the event annotation tool.

10. An event labeling device within an application, characterized in that, The device includes: The tool interface display module is used to display the user interface of the event annotation tool in the browser; The experiencer interface display module is used to display the user interface of the application experiencer in the user interface of the event annotation tool in response to the launch operation of the application experiencer. The application experiencer refers to the runtime instance of the application used by the analyst for interaction. The annotation information display module is used to, after the application experiencer enters the element selection mode, in response to the selection operation of the first element in the user interface of the application experiencer, obtain the first element set from the user interface of the application experiencer, wherein the first element set includes the first element and similar elements of the first element; The annotation information display module is further configured to display selectors for each element in the first element set and its parent element in the user interface of the event annotation tool; wherein, the event annotation information includes a selector for at least one element, the selector being used to indicate the interaction type and display characteristics of the element; The operation event labeling module is used to respond to the confirmation operation of the event labeling information and label the operation events within the application corresponding to the application experiencer that match the event labeling information.

11. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing a computer program that is loaded and executed by the processor to implement the event labeling method within an application as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which is loaded and executed by a processor to implement the event annotation method within an application as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes a computer program stored in a computer-readable storage medium, which a processor reads from and executes to implement the event annotation method within an application as described in any one of claims 1 to 9.

Images