Method for reporting BUG information

Abstract

The invention relates to the field of software engineering, and discloses a method for reporting BUG information, which comprises the following steps of: S1, starting to record user operation data when a specific condition is triggered in a user operation process; s2, capturing a key operation of a user, and generating a corresponding event object; s3, buffering the recorded operation data, and when a preset condition is met, sending the data to a back-end server in batches for storage; s4, the back-end server receives and stores the operation data, and analyzes the operation data to generate a readable reproduction step; and S5, displaying the generated reproduction step in a BUG report interface. According to the method, by automatically recording the user operation data, capturing key operations such as click, input and navigation, detailed reproduction steps are generated, and errors and omissions of manual description are avoided. The user does not need to memorize and describe a complex operation process, the accuracy and integrity of the BUG report are remarkably improved, and a development team is helped to understand and reproduce problems more quickly.

Description

Technical Field

[0001] The present invention relates to the technical field of software engineering, and in particular to a method for reporting BUG information. Background Art

[0002] With the rapid development and widespread application of software technology, the assurance and improvement of software quality have become increasingly important. In the process of software development, bug reporting and handling is one of the important links in quality assurance. The traditional bug reporting method mainly relies on users to manually describe the problem, including operation steps, error messages, operating environment, etc. However, when reporting a bug, users often need to recall and describe in detail the operation process in which the problem was encountered. This is not only time-consuming and laborious, but also prone to inaccurate descriptions or omissions of key operations, making it difficult for developers to reproduce the problem, which in turn affects the efficiency of bug location and resolution. And for complex software operation processes, it is a cumbersome and error-prone task for users to manually describe each step of the operation. Many users give up reporting bugs due to the cumbersome description process, which makes some potential problems unable to be discovered and handled in time, affecting the overall quality of the software.

[0003] In order to solve the above problems, current technology has developed some automated bug reporting tools and methods, such as automatically recording operation logs and taking screenshots. However, some automated tools only record part of the operation logs and cannot fully capture all user operations, resulting in incomplete information. At the same time, most existing tools remain at the level of simple data recording and display, lacking intelligent data analysis and language optimization, resulting in the generated bug report descriptions being not natural and easy to read.

[0004] To sum up, the existing bug reporting methods and tools have many shortcomings in terms of accuracy, completeness, security and user experience. There is an urgent need for a method that can record and report bugs in an automated, intelligent, efficient and secure manner to improve the quality and efficiency of software development and maintenance. Summary of the invention

[0005] In view of the deficiencies in the prior art, the present invention provides a method for reporting BUG information, aiming to solve the above problems and provide a comprehensive, reliable and user-friendly BUG reporting solution.

[0006] To achieve the above objectives, the present invention is implemented through the following technical solutions: A method for reporting BUG information, comprising the following steps: During the user operation process, the user operation data is recorded when a specific condition is triggered, and the specific condition includes an uncaught error thrown by the application, a specific operation performed by the user, or a manual trigger by the user; Capture key user operations, including click events, input events, navigation events, mouse and keyboard events, and generate corresponding event objects, which include operation type, target element identifier, operation timestamp and operation details; Buffering recorded operational data and sending the data in batches to a backend server for storage when preset conditions are met, such as reaching a certain number or time interval; The backend server receives and stores the operation data, and parses the operation data to generate readable reproduction steps, wherein the reproduction steps include template description and step optimization; The generated reproduction steps are displayed in the bug report interface, and users can view and edit these steps to complete the bug report.

[0007] Preferably, the user operation data includes user ID, session ID, operation type, target element identifier, operation timestamp and operation details.

[0008] Preferably, the operation data is transmitted using the HTTPS protocol for encrypted transmission to ensure data security.

[0009] Preferably, the method further comprises the step of encrypting sensitive data at the client to prevent sensitive information from being recorded and transmitted in plain text.

[0010] Preferably, the operation data of the buffer record uses local storage technology, including LocalStorage and IndexedDB, to prevent data loss caused by page refresh or closing.

[0011] Preferably, when the back-end server parses the operation data, it uses regular expressions and a template engine to generate a descriptive language, and the template engine includes Mustache and Handlebars.

[0012] Preferably, the method further comprises the step of optimizing the generated descriptive language using natural language processing technology to make it more natural and readable.

[0013] Preferably, the reproduction step display component includes a user interface, allowing a user to view and edit the automatically generated reproduction steps and add supplementary information.

[0014] Preferably, the user operation recording plug-in is integrated into the front-end application, captures user operations through an event listener, and is loaded when the application is started.

[0015] The present invention also provides a BUG information reporting device for implementing the method, comprising: The front-end user operation recording module is used to record user operation data when specific conditions are triggered during the user operation process; Operation data transmission module, used to buffer recorded operation data and send the data in batches to the backend server when the preset conditions are met; The backend data processing module is used to receive and store operation data, parse and generate readable reproduction steps; The bug report display module is used to display the generated reproduction steps in the bug report interface, and users can view and edit these steps.

[0016] The present invention provides a method for reporting BUG information, which has the following beneficial effects: 1. The present invention automatically records user operation data, captures key operations such as clicks, inputs, and navigation, and generates detailed reproduction steps, thus avoiding errors and omissions in manual descriptions. Users do not need to remember and describe complex operation processes, which significantly improves the accuracy and completeness of BUG reports and helps development teams understand and reproduce problems more quickly.

[0017] 2. The present invention reduces the time and effort of users to manually fill in bug reports by integrating user operation record plug-ins and automatically generating reproduction steps. Users only need to make simple supplements and edits to generate detailed bug reports, which improves user experience and satisfaction and encourages more users to actively report bugs.

[0018] 3. The present invention provides detailed and accurate user operation data and natural language description of the reproduction steps to help the development team quickly understand the problems encountered by users. Combined with the descriptive language optimized by NLP technology, the reproduction steps are more natural and easy to read, further improving the efficiency of problem location and resolution and shortening the time for problem resolution. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of the method flow of the present invention; Figure 2 It is a schematic diagram of the device structure of the present invention.

[0020] Among them, 100, front-end user operation recording module; 200, operation data transmission module; 300, back-end data processing module; 400, BUG report display module. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the specification of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] Please see attached Figure 1The embodiment of the present invention provides a method for reporting BUG information, comprising the following steps: S1. Record user operation data During the user operation process, the user operation data is recorded when specific conditions are triggered. Specific conditions include uncaught errors thrown by the application, specific operations performed by the user, or manual triggering by the user.

[0023] Uncaught Error: When an uncaught error (such as a JavaScript exception) occurs in the application, the user's operation data will be recorded immediately. This error usually causes the application to not work properly, so it is necessary to record the operation data before and after the error occurs for debugging.

[0024] Specific operations: Recording is triggered when users perform certain specific operations (such as clicking a key button or submitting a form). These operations are usually closely related to the occurrence of bugs, so user operation data is recorded when these operations occur.

[0025] Manual trigger: Recording starts when the user actively clicks the "Report Bug" button. This method allows users to decide to start recording when they encounter a problem, ensuring the accuracy of bug reports.

[0026] This step uses an intelligent trigger mechanism to ensure accurate timing of recording user operation data, which helps capture key operations where bugs occur and improves the accuracy of problem reproduction.

[0027] S2. Capture the user’s key operations Capture key user operations, including click events, input events, navigation events, mouse and keyboard events, and generate corresponding event objects. Event objects include operation type, target element identifier, operation timestamp and operation details.

[0028] Click event: records the user's click operation on each element on the page, and captures the unique identifier, click location and time of the target element.

[0029] Input events: Record what users input into input boxes and text fields to ensure that important input information is captured while filtering sensitive information such as passwords.

[0030] Navigation events: record the user's page navigation operations, such as page jumps, refreshes, etc., to ensure the integrity of the entire operation process.

[0031] Mouse and keyboard events: capture mouse clicks, double clicks, right-click menus, and keyboard key presses, and record detailed user interaction information.

[0032] This step ensures that important user operations in the application are captured and detailed event objects are generated, so that the BUG report can cover the complete operation chain and provide sufficient information for subsequent problem location and reproduction.

[0033] S3: Buffer recorded operation data and transmit Buffer recorded operational data and send the data in batches to the backend server for storage when preset conditions are met, such as reaching a certain number or time interval.

[0034] Data buffering: Implement a data buffer on the front end to temporarily store user operation data to avoid frequent data transmission affecting performance.

[0035] Batch transmission: Set transmission conditions, such as sending operation data to the server in batches after the buffer reaches a certain amount or a set time interval. Reliable data transmission is achieved through AJAX or WebSocket.

[0036] Local storage: Use LocalStorage or IndexedDB to temporarily store operation data to prevent data loss caused by page refresh or closing and ensure data integrity.

[0037] This step optimizes system performance through data buffering and batch transmission, ensures the timeliness and reliability of data transmission, prevents data loss, and ensures the integrity and accuracy of operation data.

[0038] S4. Analyze the operation data to generate the recurrence steps The backend server receives and stores the operation data, parses the operation data to generate readable reproduction steps, and the reproduction steps include templated description and step optimization.

[0039] Data parsing: After receiving the operation data, the backend server parses each operation event and extracts information such as the operation type, target element, and timestamp.

[0040] Templated description: Use template engines (such as Mustache and Handlebars) to fill the operation data into a preset template to generate an easy-to-read operation description. For example, describe the "click a button" operation as "click the 'Submit' button."

[0041] Step optimization: Merge consecutive similar operations, filter out invalid or repeated operations, and make the generated reproducible steps concise and clear. For example, merge the operation of clicking the same button multiple times in a row into one operation.

[0042] This step parses and optimizes the operation data to generate clear and easy-to-read reproduction steps, helping the development team to quickly understand and reproduce the problems encountered by users and improve the efficiency of problem location and resolution.

[0043] S5. Display and edit the steps to reproduce The generated reproduction steps are displayed in the bug report interface, and users can view and edit these steps to complete the bug report.

[0044] Display component: Integrate the operation step display component on the bug report page to display automatically generated reproduction steps, so that users can intuitively view the operation process.

[0045] User editing: Provides editing functions to allow users to modify and supplement the automatically generated reproduction steps, such as adding comments, correcting descriptions, etc.

[0046] Interaction design: Design a friendly user interface to ensure the user experience when editing operation steps, provide save and submit functions, and ensure that the user's modified steps can be fully recorded in the BUG report.

[0047] This step provides an editing function, allowing users to correct and supplement the reproduction steps, ensuring the accuracy and completeness of the bug report, enhancing user participation and satisfaction, and providing the development team with more detailed reference information.

[0048] The bug information reporting method provided by the present invention realizes the automation and accuracy of bug reports through a comprehensive mechanism of intelligent triggering, key operation capture, data buffering and transmission, reproduction step generation and optimization, and user participation. Compared with the prior art, the present invention automatically records user operation data to avoid human omissions and erroneous descriptions, reduces the burden of users manually filling out bug reports, improves user participation enthusiasm, and provides detailed and easy-to-read reproduction steps to help the development team quickly locate and solve problems.

[0049] In general, the implementation of the present invention not only improves the quality and efficiency of BUG reports, but also significantly improves the overall efficiency of software development and maintenance, and has broad application prospects.

[0050] In a preferred embodiment of the present invention, the user operation data includes user ID, session ID, operation type, target element identifier, operation timestamp and operation details. The preferred embodiment aims to provide a method for recording and managing user operation data in detail to improve the quality and efficiency of BUG reports. The following is a detailed description of the preferred embodiment.

[0051] User operation data structure User operation data includes the following key fields: User ID (userId): used to uniquely identify a user.

[0052] This can be an application-assigned user identifier or a user login name.

[0053] For example, a user ID might be "user123".

[0054] Session ID (sessionId): used to uniquely identify a user session.

[0055] A new session ID is generated each time a user logs in or accesses the application.

[0056] For example, a session ID might be "session_20230530123456".

[0057] Action Type (actionType): describes the specific action type of the user.

[0058] Common operation types include click, input, navigate, scroll, keyPress, etc.

[0059] For example, the action type might be "click".

[0060] Target element identifier (targetElement): used to uniquely identify the target element of the user operation.

[0061] This can be a CSS selector, an XPath, or a custom attribute of the element (such as data-id).

[0062] For example, the target element ID could be "#submitButton" or " / / div[@id='loginForm'] / input[@name='username']".

[0063] Operation timestamp: records the specific time when the operation occurs.

[0064] Use a standard time format such as Unix timestamp or ISO 8601 format.

[0065] For example, the operation timestamp can be "2023-05-30T12:34:56Z" or "1622381696000".

[0066] Operation details: Provides additional information about the operation. The specific content depends on the operation type.

[0067] For click operations, the click position (x, y coordinates) can be recorded.

[0068] For input operations, the input text content can be recorded (make sure sensitive information is filtered).

[0069] For example, for an input operation, the operation details might be "username: 'john_doe'".

[0070] Data recording and transmission process 1. Trigger recording conditions: Start recording user operation data when specific conditions are met (such as an uncaught error thrown by the application, a specific user operation, or a manual trigger by the user).

[0071] Trigger conditions ensure that data is recorded only when important operations or errors occur, avoiding unnecessary data redundancy.

[0072] 2. Capture key user operations: Capture key user operations such as clicks, input, navigation, etc. through front-end event listeners.

[0073] Each operation generates an event object, which contains all fields of user operation data.

[0074] 3. Data buffering and batch transfer: Implement a data buffer on the front end to temporarily store user operation data.

[0075] Set transmission conditions, such as sending data in batches to the backend server after the buffer reaches a certain number or time interval.

[0076] Data transmission is encrypted using the HTTPS protocol to ensure data security.

[0077] 4. Back-end data reception and storage: The backend server receives the operation data and stores it in the database.

[0078] The database structure design takes into account the needs of fast query and data analysis to ensure the integrity and consistency of operation data.

[0079] 5. Parse and generate the steps to reproduce: The backend server parses the operation data and generates detailed reproduction steps.

[0080] Use the template engine to fill the operation data into the preset template to generate an easy-to-read operation description.

[0081] Optimize the reproduction steps, merge similar operations, filter invalid operations, and ensure that the steps are concise and clear.

[0082] 6. Display and edit the steps to reproduce: Display the generated reproduction steps on the BUG report interface.

[0083] Users can review and edit these steps and add additional information to complete the bug report.

[0084] Provide a friendly user interface to ensure a good user operating experience.

[0085] This preferred embodiment significantly improves the accuracy and completeness of bug reports by recording and managing user operation data in detail. By recording information such as user ID and session ID, the uniqueness and consistency of operation data are ensured. At the same time, detailed operation data and optimized reproduction steps help the development team to quickly locate and reproduce bugs. Automatically record and generate operation steps to reduce the burden of manual filling by users, while providing editing functions to enhance user participation and satisfaction.

[0086] In summary, the preferred embodiment of the present invention has comprehensively optimized the recording, transmission, storage and analysis of user operation data, and provides an efficient, accurate and user-friendly BUG information reporting method, which has broad application prospects and significant practical value.

[0087] In a preferred embodiment of the present invention, the transmission of operation data adopts HTTPS protocol for encrypted transmission to ensure the security of data. This preferred embodiment provides a safe and efficient method for user operation data transmission by using HTTPS protocol. The following is a detailed description of this preferred embodiment.

[0088] 1. Configure HTTPS server: Obtain and install an SSL certificate: Obtain a trusted SSL certificate on the server side and install it on the Web server (such as Apache, Nginx).

[0089] Configure the web server: Configure the web server to communicate using the HTTPS protocol, ensuring that all incoming and outgoing requests are encrypted via HTTPS.

[0090] 2. Client configuration: In the client application, ensure that all communications with the server use the HTTPS protocol.

[0091] Update the client code to replace all HTTP requests with HTTPS requests.

[0092] 3. Testing and verification: Verify HTTPS connection: Ensure that the client can successfully establish an HTTPS connection and perform encrypted communication through the SSL / TLS protocol.

[0093] Data transmission test: Perform data transmission test to ensure that the operation data can be correctly transmitted and decrypted, and the integrity and security of the data are guaranteed.

[0094] This preferred embodiment uses the HTTPS protocol for encrypted transmission. The data is encrypted during the transmission process through the SSL / TLS protocol to prevent the data from being stolen or tampered with, thereby protecting the user's privacy and sensitive information. The identity of the server is verified through a digital certificate to ensure that the client communicates with the legitimate server and prevent man-in-the-middle attacks. Through the above implementation, the preferred embodiment of the present invention ensures the security of user operation data during transmission, provides an efficient and secure data transmission method, and significantly improves the reliability and user trust of the BUG information reporting system.

[0095] In a preferred embodiment of the present invention, the method further includes the step of: encrypting the sensitive data at the client to prevent the sensitive information from being recorded and transmitted in plain text. This preferred embodiment further enhances the security of the data by encrypting the sensitive data at the client. The following is a detailed description of this preferred embodiment.

[0096] Client encryption refers to encrypting sensitive data on the client before data transmission to prevent sensitive information from being intercepted and leaked during transmission. Even if the transmission channel is breached, the attacker cannot directly read the sensitive information because the data has been encrypted. Common encryption algorithms include symmetric encryption (such as AES) and asymmetric encryption (such as RSA).

[0097] 1. Data encryption algorithm selection and implementation: Select an appropriate encryption algorithm, such as AES (symmetric encryption) or RSA (asymmetric encryption).

[0098] Implement the encryption algorithm on the client side and use existing encryption libraries (such as CryptoJS) for encryption processing.

[0099] 2. Identify sensitive data and encrypt it: When capturing user action data, identify and label sensitive data fields.

[0100] Use encryption algorithms to encrypt sensitive data.

[0101] 3. Data encryption transmission: The encrypted data object is transmitted to the server via the HTTPS protocol.

[0102] Ensure the security of data during transmission.

[0103] 4. Server-side decryption processing: Implement the corresponding decryption algorithm on the server side.

[0104] After receiving the encrypted data, the data is decrypted to restore the original sensitive information.

[0105] By encrypting sensitive data on the client side, even if the transmission channel is breached, attackers cannot directly read sensitive information because the data has been encrypted, thus preventing sensitive information (such as passwords, credit card numbers) from being leaked during transmission and protecting user privacy. Combined with encrypted transmission of the HTTPS protocol, double encryption protection is provided to further enhance the security of data transmission.

[0106] In summary, the preferred embodiment of the present invention provides a more secure data transmission method by encrypting sensitive data on the client, further protects the user's sensitive information, and significantly improves the security and reliability of the BUG information reporting system.

[0107] In a preferred embodiment of the present invention, the operation data of the buffer record uses local storage technology, including LocalStorage and IndexedDB, to prevent data loss caused by page refresh or closing. This preferred embodiment ensures the reliability and persistence of the operation data by using local storage technology on the client. The following is a detailed description of this preferred embodiment.

[0108] 1. Configure local storage technology: Choose the appropriate local storage technology (LocalStorage or IndexedDB) based on the amount of data and storage requirements.

[0109] Implement storage and reading operations of LocalStorage and IndexedDB on the client.

[0110] 2. Buffer data persistence: Periodically persist the operation data in the memory buffer to local storage.

[0111] Implement buffer management logic to ensure data persistence when the buffer is full or the time interval is reached.

[0112] 3. Page refresh or close event processing: Listen to the beforeunload event and persist the data in the memory buffer to local storage before the page is refreshed or closed.

[0113] 4.Data recovery mechanism: When the page is reloaded, the operation data is read from the local storage and loaded into the memory buffer.

[0114] Ensure data continuity and integrity.

[0115] By using LocalStorage and IndexedDB on the client to cache and store operation data, local storage technology is used to ensure that the operation data will not be lost when the page is refreshed or closed, thereby improving the persistence and reliability of data. When the page is reloaded, the operation data can be restored from the local storage to ensure the continuity and integrity of the data. In addition, cached records and periodic persistence reduce frequent data transmission and storage operations, thereby improving the performance and response speed of the system.

[0116] In summary, the preferred embodiment of the present invention provides an efficient and reliable operation data buffer recording and storage method by using LocalStorage and IndexedDB technology, which significantly improves the stability and data security of the BUG information reporting system.

[0117] In a preferred embodiment of the present invention, when the backend server parses the operation data, regular expressions and template engines are used to generate descriptive language, and the template engines include Mustache and Handlebars. By using regular expressions to parse data and template engines to generate descriptive language, the user's operation records can be converted into easy-to-read and easy-to-understand descriptions of the recurrence steps. The following is a detailed description of the preferred embodiment.

[0118] 1. Data reception and storage: The backend server receives the operation data transmitted from the client and stores it in the database. The operation data includes user ID, session ID, operation type, target element ID, operation timestamp and operation details.

[0119] 2. Data analysis: Use regular expressions to parse each field in the operation data and extract key information.

[0120] Clean and standardize operational data through regular expression matching and replacement to ensure data consistency and integrity.

[0121] 3. The template engine generates descriptive language: Use a template engine (such as Mustache, Handlebars) to fill the parsed data into the preset template and generate descriptive language.

[0122] The template engine converts operation data into reproduction steps described in natural language through placeholders and template syntax.

[0123] By using regular expressions and template engines to generate descriptive language when parsing operation data on the backend server, regular expressions are used to accurately match and extract key information in the operation data to ensure the accuracy of data parsing, and the template engine is used to convert the operation data into natural language descriptions to make the reproduction steps clear and easy to understand. The generated descriptive language helps the development team quickly understand and reproduce the problems encountered by users, improving the efficiency of problem location and resolution.

[0124] In summary, the preferred embodiment of the present invention provides an efficient and accurate operation data parsing and description generation method by using regular expressions and template engines to generate descriptive languages, which significantly improves the readability and user experience of the BUG information reporting system.

[0125] In a preferred embodiment of the present invention, the method further comprises the step of optimizing the generated descriptive language using natural language processing technology to make it more natural and readable. By combining NLP technology, the quality of the generated descriptive language can be further improved, making the description of the BUG reproduction steps closer to human natural language, making it easier for developers to understand and reproduce the problem. The following is a detailed description of the preferred embodiment.

[0126] 1. Data reception and storage: The backend server receives the operation data transmitted from the client and stores it in the database. The operation data includes user ID, session ID, operation type, target element ID, operation timestamp and operation details.

[0127] 2. Data analysis: Use regular expressions to parse each field in the operation data and extract key information.

[0128] Clean and standardize operational data through regular expression matching and replacement to ensure data consistency and integrity.

[0129] 3. The template engine generates preliminary descriptive language: Use a template engine (such as Mustache, Handlebars) to fill the parsed data into the preset template to generate preliminary descriptive language.

[0130] The template engine converts operation data into reproduction steps described in natural language through placeholders and template syntax.

[0131] 4. Use Natural Language Processing (NLP) technology to optimize descriptive language: Use NLP technology to optimize the initially generated descriptive language to ensure that the description is more natural and easy to read.

[0132] NLP technologies can include language models (such as GPT-3), text simplification, spelling and grammar correction, etc.

[0133] By using natural language processing technology to optimize the generated descriptive language when parsing operation data on the back-end server, and using NLP technology to optimize the initially generated descriptive language to make it more in line with natural language habits and easier for developers to understand, the optimized descriptive language is clearer and more intuitive, which improves the user experience when reporting bugs. The optimized descriptive language helps the development team understand and reproduce the problems encountered by users more quickly, improving the efficiency of problem location and resolution.

[0134] In summary, the preferred embodiment of the present invention provides an efficient and intelligent operation data parsing and description generation method by combining NLP technology, which significantly improves the readability and user experience of the BUG information reporting system.

[0135] In a preferred embodiment of the present invention, the reproduction step display component includes a user interface, allowing users to view, edit the automatically generated reproduction steps, and add supplementary information. By providing an intuitive and friendly user interface, users can view and edit the automatically generated reproduction steps to ensure the completeness and accuracy of the BUG report. The following is a detailed description of the preferred embodiment.

[0136] 1. Generate and display the steps to reproduce: The system generates preliminary reproduction steps based on the captured user operation data.

[0137] The generated reproduction steps are displayed in the user interface for users to view and edit.

[0138] 2. User interface design and implementation: Design and implement user interfaces using front-end frameworks such as React, Vue.js, Angular.

[0139] Ensure that the interface layout is reasonable and easy to operate.

[0140] 3. Edit and supplement information function: Provides editing function to allow users to modify the reproduction steps.

[0141] Provides a supplementary information input area to allow users to add information such as operating environment and abnormal phenomena.

[0142] 4. Data storage and submission: Implement the save and submit functions to ensure that the user's modifications and supplementary information can be recorded by the system.

[0143] The edited reproduction steps and supplementary information are packaged and sent to the backend server.

[0144] User interface display and interaction process: 1. The user opens the Bug Report interface and sees automatically generated reproduction steps.

[0145] 2. Users can click on each step to edit and modify inaccurate descriptions.

[0146] 3. Users can enter other relevant information in the supplementary information area, such as operating environment, abnormal phenomena, etc.

[0147] 4. After the user completes editing, click the "Submit Bug Report" button to save and submit the complete report.

[0148] By providing a reproduction steps display component with a user interface, users can view and edit the automatically generated reproduction steps to ensure the accuracy of the description. At the same time, a user interface is provided to allow users to add supplementary information, improve user participation and report quality, and developers can obtain more detailed and accurate bug report information to speed up problem location and resolution.

[0149] In summary, the preferred embodiment of the present invention provides an efficient and accurate bug reporting method by designing and implementing a user-friendly reproduction step display component, which significantly improves the user experience and the quality of bug reports.

[0150] In a preferred embodiment of the present invention, the user operation record plug-in is integrated into the front-end application, and the user operation is captured through the event listener and loaded when the application is started. This embodiment captures the user's operation behavior in real time by integrating the operation record plug-in into the front-end application, and provides detailed operation records for subsequent BUG reporting and problem reproduction. The following is a detailed description of the preferred embodiment.

[0151] 1.Integrate user operation record plug-in: Introduce the operation record plug-in into the front-end application and load the plug-in when the application starts.

[0152] Make sure the plugin can be seamlessly integrated with other parts of the application and does not affect the normal operation of the application.

[0153] 2. Implement event listener: Use JavaScript event listeners to capture various user operation events.

[0154] Implement the corresponding event processing function for each operation type (such as click, input, scroll) and generate an operation event object.

[0155] 3. Operation data buffering and storage: Implement a data buffer in the memory to temporarily store the captured operation data.

[0156] Periodically persist the data in the buffer to LocalStorage or IndexedDB to ensure data persistence.

[0157] 4. Data Transmission and Security: The buffered data is regularly uploaded to the backend server via the HTTPS protocol to ensure the security of data transmission.

[0158] The backend server receives and stores the operation data for subsequent analysis and use.

[0159] By integrating the user operation record plug-in into the front-end application, various user operations can be captured in real time through event listeners to ensure the comprehensiveness and accuracy of operation data. Use LocalStorage or IndexedDB technology to save operation data to prevent data loss caused by page refresh or closure. The plug-in is designed as an independent module, which is easy to integrate into the front-end application and easy to maintain and expand.

[0160] In summary, the preferred embodiment of the present invention provides an efficient and reliable method for user operation recording and data transmission by integrating a user operation recording plug-in, which significantly improves the stability and data security of the BUG information reporting system.

[0161] Please refer to the attached Figure 2 The present invention also provides a BUG information reporting device for implementing the above method, comprising: The front-end user operation recording module 100 is used to record user operation data when a specific condition is triggered during the user operation process; The operation data transmission module 200 is used to buffer the recorded operation data and send the data in batches to the backend server when a preset condition is met; The back-end data processing module 300 is used to receive and store the operation data, parse and generate readable reproduction steps; The bug report display module 400 is used to display the generated reproduction steps in the bug report interface, and the user can view and edit these steps.

[0162] The device of this embodiment can be used to execute the above method embodiment, and its principles and technical effects are similar, which will not be repeated here.

[0163] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for reporting BUG information, It is characterized in that The following steps are involved: During the user operation process, the user operation data is recorded when a specific condition is triggered, and the specific condition includes an uncaught error thrown by the application, a specific operation performed by the user, or a manual trigger by the user; Capture key user operations, including click events, input events, navigation events, mouse and keyboard events, and generate corresponding event objects, which include operation type, target element identifier, operation timestamp and operation details; Buffering recorded operational data and sending the data in batches to a backend server for storage when preset conditions are met, such as reaching a certain number or time interval; The backend server receives and stores the operation data, and parses the operation data to generate readable reproduction steps, wherein the reproduction steps include template description and step optimization; The generated reproduction steps are displayed in the bug report interface, and users can view and edit these steps to complete the bug report.

2. A method for reporting BUG information according to claim 1, It is characterized in that The user operation data includes user ID, session ID, operation type, target element identifier, operation timestamp and operation details.

3. A method for reporting BUG information according to claim 1, It is characterized in that The transmission of the operation data is encrypted using the HTTPS protocol to ensure data security.

4. A method for reporting BUG information according to claim 3, It is characterized in that The method also includes the step of encrypting sensitive data at the client to prevent the sensitive information from being recorded and transmitted in plain text.

5. A method for reporting BUG information according to claim 1, It is characterized in that The operation data of the buffer record uses local storage technology, including LocalStorage and IndexedDB, to prevent data loss caused by page refresh or closing.

6. A method for reporting BUG information according to claim 1, It is characterized in that When the back-end server parses the operation data, it uses regular expressions and a template engine to generate a descriptive language, and the template engine includes Mustache and Handlebars.

7. A method for reporting BUG information according to claim 6, It is characterized in that The method also includes the step of optimizing the generated descriptive language using natural language processing technology to make it more natural and readable.

8. A method for reporting BUG information according to claim 1, It is characterized in that The reproduction step display component includes a user interface, allowing a user to view and edit the automatically generated reproduction steps and add supplementary information.

9. A method for reporting BUG information according to claim 1, It is characterized in that The user operation record plug-in is integrated into the front-end application, captures user operations through event listeners, and is loaded when the application is started.

10. A BUG information reporting device for implementing the method according to any one of claims 1 to 9, It is characterized in that include: The front-end user operation recording module is used to record user operation data when specific conditions are triggered during the user operation process; Operation data transmission module, used to buffer recorded operation data and send the data in batches to the backend server when the preset conditions are met; The backend data processing module is used to receive and store operation data, parse and generate readable reproduction steps; The bug report display module is used to display the generated reproduction steps in the bug report interface, and users can view and edit these steps.

Images