CN111475423A - Data entry method and device, electronic equipment and readable storage medium - Google Patents
Data entry method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN111475423A CN111475423A CN202010601978.9A CN202010601978A CN111475423A CN 111475423 A CN111475423 A CN 111475423A CN 202010601978 A CN202010601978 A CN 202010601978A CN 111475423 A CN111475423 A CN 111475423A
- Authority
- CN
- China
- Prior art keywords
- data
- program
- interactive
- host program
- host
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3696—Methods or tools to render software testable
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a data entry method, a data entry device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: receiving operation data of a host program, and judging whether to execute program defect entry operation or not according to the operation data; if the program defect entry operation is executed, acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of the terminal equipment corresponding to the host program; and generating program defect information according to the interactive interface picture, the interactive data and the operating data, and calling a preset interface to input the program defect information. According to the method, under the condition that the program defect entry operation is executed, the program defect information is automatically acquired, the preset interface is called to upload, the function of automatically uploading the defects is achieved, and the program defect entry efficiency is improved.
Description
Technical Field
The invention relates to the field of data processing, in particular to a data entry method and device, electronic equipment and a readable storage medium.
Background
With the wide application of program software, a program defect tracking management system for program defects is developed, and the program defect tracking management system can track program defects generated in the running process of an application program. The program defect tracking management system comprises a background management module, a background database, a front-end recording module and the like.
At present, when an application program in operation has defects, technicians are usually required to collect program defect information, and program defect information is manually entered through a front-end entry module of a program defect tracking management system, however, the collection process of the program defect information is complex, the operation of manually entering the program defect information is complex, the entry period is long, the efficiency of entering the program defect information is low, and the user experience is low.
Disclosure of Invention
In view of the above, the present invention provides a data entry method, an apparatus, an electronic device and a readable storage medium to overcome the disadvantages of the prior art.
A first aspect of an embodiment of the present invention provides a data entry method, including:
receiving operation data of a host program, and judging whether to execute program defect entry operation according to the operation data;
if the program defect entry operation is executed, acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of terminal equipment corresponding to the host program;
generating program defect information according to the interactive interface picture, the interactive data and the operating data, and calling a preset interface to input the program defect information.
A second aspect of the embodiments of the present invention provides a data entry device, including:
the defect entry determining module is used for receiving the operation data of the host program and judging whether to execute program defect entry operation according to the operation data;
the defect information acquisition module is used for acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of the terminal equipment corresponding to the host program if the program defect entry operation is executed;
and the defect information input module is used for generating program defect information according to the interactive interface picture, the interactive data and the operating data and calling a preset interface to input the program defect information.
A third aspect of the embodiments of the present invention provides a server, where the server includes a processor, an input device, an output device, and a memory, where the processor, the input device, the output device, and the memory are connected to each other, where the memory is used to store a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect of the embodiments of the present invention.
A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium is used for a computer program for electronic data exchange, and the computer program is used for causing a computer to execute some or all of the steps described in the first aspect of the embodiments of the present invention.
A fifth aspect of embodiments of the present invention provides a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps as described in the first aspect of embodiments of the present invention, which may be a software installation package.
The technical scheme provided by the invention can have the following beneficial effects:
the invention discloses a data entry method, which comprises the following steps: after receiving operation data of the host program, judging whether to execute program defect entry operation according to the data, if so, acquiring a current interactive interface picture of the host program, interactive data of the host program and operation data of terminal equipment corresponding to the host program, generating program defect information according to the interactive interface picture, the interactive data and the operation data, and calling a preset interface to enter the program defect information. According to the method, after the condition of executing the program defect entry operation is met, the program defect information is automatically acquired, then the preset interface is called to enter the program defect information, the method does not need to rely on technical personnel to acquire the defect information, and the information can be automatically uploaded after the defect information is automatically collected, so that the automatic entry function of the program defect is realized, the entry efficiency of the program defect information is improved, and the user experience is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a method for recording a program defect according to an embodiment of the present invention.
Fig. 2a is a schematic diagram of a labeling interface according to an embodiment of the present invention.
Fig. 2b is a schematic diagram of a pop-up interface of a callout box according to an embodiment of the present invention.
Fig. 3 is a flowchart of a method for monitoring an interactive operation event according to an embodiment of the present invention.
Fig. 4 is a flowchart of a method for monitoring an interactive operation event according to an embodiment of the present invention.
Fig. 5 is a flowchart of a method for monitoring network interaction events according to an embodiment of the present invention.
Fig. 6 is a flowchart of a method for monitoring program exception events according to an embodiment of the present invention.
Fig. 7 is a structural diagram of a program defect entry device according to an embodiment of the present invention.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Fig. 9 is a block diagram of a program defect tracking management system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for recording program defects according to an embodiment of the present invention.
The invention discloses a Software Development Kit (SDK) of a front-end recording device. The present SDK operates so that the embedded application becomes a subroutine, and the host application becomes a host program of the present SDK. The method of the present invention is applied to the SDK. As shown in fig. 1, the data entry method in this embodiment includes:
step 101: and receiving operation data of the host program, and judging whether to execute program defect entry operation according to the operation data.
Optionally, after the host program is started, the SDK may start monitoring the host program, and the SDK may perform information interaction with the host program in real time.
Step 102: and if the program defect entry operation is executed, acquiring the current interactive interface picture of the host program, the interactive data of the host program and the running data of the terminal equipment corresponding to the host program.
The interactive data here includes interactive operation data of the user on the host program of the terminal device and network interactive data of the host program. The interactive operation data is 'interactive data' between the user and the host program, such as page jump, button click, slide list and other interactive operations. The network interaction data refers to data for network interaction between the host program and the server corresponding to the host program, namely data for network request and response, and the part of data is interaction data between the host program and the server; such as header information of a hypertext Transfer Protocol (HTTP) request, response information, and the like. The running data of the mobile device includes, for example, program running stack information, Central Processing Unit (CPU) usage, memory usage, and the like.
Step 103: generating program defect information according to the interactive interface picture, the interactive data and the operating data, and calling a preset interface to input the program defect information.
According to the method, program defect information does not need to be recorded and uploaded manually, and the recorded and uploaded defect data also comprise operation data of the mobile equipment. The method and the device not only improve the efficiency of inputting and submitting the program defects of the mobile equipment, but also enrich the data content of the program defects which are input and submitted.
In one embodiment, determining whether to perform a program bug entry operation based on the operation data includes:
judging whether the operation data contains callback error information or not, wherein the callback error information is returned by an operation system corresponding to the host program; if the callback error information is contained, determining that the host program is in an abnormal state, and executing program defect entry operation; if the callback error information is not contained, determining that the host program is in a non-abnormal state, and continuously executing the monitoring operation on the host program. The callback error message is sent to the host program by the terminal device. When the host program is crashed or jammed, the operating system of the terminal device sends a callback error message to the host program to inform the host program of the error reason. When the SDK receives callback error information, the SDK indicates that the host program is abnormal and program defect entry is needed. According to the method, the defect entry is carried out by judging whether callback error information is contained, so that the automatic monitoring function of program defect entry is realized, and the self-starting of program defect entry is realized.
In an embodiment, the present invention further discloses another method for determining whether to execute a program defect entry operation, which includes: the operation data is user operation data; judging whether to execute the program defect entry operation according to the operation data comprises the following steps: determining a user request corresponding to user operation data; and judging whether the user request is a preset interface starting request operation or not, and if so, executing program defect entry operation. When the host program is started, the SDK generates a key control of the defect entry, and adds the key control to the top layer of the interactive interface view of the host program. And simultaneously setting the state of the defect entry as an activated state, starting a timer, calling a hiding method of the key if the user does not execute preset operation aiming at the key within 10 seconds, hiding the key to enable the key not to be displayed on an interactive interface any more, and simultaneously setting the state of the defect entry as an inactivated state. If the user clicks the key within 10 seconds, it should be noted that the setting of the 10-second time limit is not unique and may be set according to the requirements of the developer and the application scenario, and the preset operation may include: click operation, long press operation, slide operation, etc., and are not limited herein. In the method, the program defect entry function is started under the operation request of the user, the program defect active entry function is realized, multiple ways of starting the program defects are realized, and the user experience is improved.
In one embodiment, when the state of the defect entry is an inactive state, the SDK starts monitoring shaking events of the terminal device, when a user shakes the mobile device, the SDK receives the shaking events of the mobile device, sets the state of the defect entry to an active state, calls a concealment canceling method of a key control of the defect entry, and displays the key on an interactive interface of the host program. It should be noted that the specific form of the listening event to the terminal device is not unique, and is not limited to a shaking event, and may be a multi-click event, or a slide-down event, and the specific representation form may be determined according to the specific use condition of the terminal device.
In one embodiment, the acquiring a current interactive interface picture of a host program, interactive data of the host program, and operation data of a terminal device corresponding to the host program in the present invention includes: performing screen capture operation aiming at the current interface of the host program to obtain a screen capture picture of the current interface; performing labeling operation on the current interface screenshot picture to obtain an interactive interface picture; and acquiring interactive data and operating data from a preset database. When the program defect entry operation is executed, the SDK can generate a screen capture instruction to the host program, the host program can interact with an operating system where the host program is located after receiving the instruction, the operating system is requested to execute the screen capture operation, and a current interface screen capture picture of the host program is generated and returned to the SDK. And the SDK sends a marking operation instruction to a host program to execute marking operation after receiving the current interface screenshot picture, and generates an interactive interface picture. Meanwhile, after the host program is started, the SDK can autonomously monitor the interactive data of the user on the host program of the terminal equipment and the running data of the host program and store the monitored data in a preset database, and when the program defect entry operation is started, the SDK can acquire the required interactive data and the running data in the preset database. In the embodiment, the program defect information not only comprises interactive data of the host program, but also comprises interactive interface pictures when defects occur and running information of the mobile device, so that the content of the program defect information is enriched, and detailed data support is provided for solving the causes of the program defects.
The SDK in the above embodiment realizes two program defect entry judgment modes. One is that when the host program runs abnormally, the program defect entry operation is executed, and the other is that the user requests to perform the program defect entry operation. The two methods respectively realize a passive entry mode and an active entry mode of program defect entry. Therefore, the method not only can autonomously monitor the abnormity of the host program in the running process and autonomously record the defects, but also can perform the recording operation of the program defects according to the requirements of users.
In one embodiment, the present invention also discloses a specific operation procedure when performing the labeling operation, and details are as follows. Fig. 2a is a schematic diagram of a labeling interface according to an embodiment of the present invention. Fig. 2b is a schematic diagram of a pop-up interface of a callout box according to an embodiment of the present invention. Referring to fig. 2a and 2b, the process of performing a labeling operation on the current interface screenshot picture to obtain an interactive interface picture includes: displaying a current interface screen capture picture and a preset labeling prompt box; receiving annotation data which is input in an annotation prompt box by a user and aims at the current interface screenshot picture, wherein the annotation data comprises: at least one group of labeling coordinates and labeling content information corresponding to any group of labeling coordinates; and executing labeling operation on the current interface screenshot picture based on the labeling data to obtain an interactive interface picture. When the picture annotation operation is performed, the SDK displays an editable interface on the current interface screenshot, as shown in fig. 2a, which is a current interface screenshot, in which a plurality of function selection boxes of the host program are provided, for example: when a program defect entry operation is executed, the SDK can generate a 'wrong' label on a current interface screenshot, the current interface is a labeling interface at the moment, namely whether a labeling input editing operation is performed or not by a user can be selected, if the labeling is performed, a check mark button on the lower portion of a picture 2a needs to be clicked, then the SDK can display a labeling frame popup interface for the user to perform an input operation of additional defect information, the labeling interface is a labeling prompt box shown in a picture 2b, the user inputs a defect label needing to be added in an editing frame in the box, then a 'confirm' button is clicked, the SDK can receive labeling data input by the user and then generates an interactive interface picture by combining with the current interface screenshot picture. The program defect information in this embodiment includes an interactive interface picture, which includes a screenshot of a current interactive interface of a host degree when the program defect is entered, and also includes additional annotation data of the defect information by the user, so that content data of the program defect information is enriched.
In one embodiment, the obtaining of the interaction data and the operation data from the preset database includes: acquiring current time and preset duration; determining an extraction time period based on the current time and a preset time length; extracting interaction data and operation data corresponding to the extraction time period from a preset database, wherein the interaction data comprise interaction operation data and network interaction data, and the operation data comprise one or more than one of the following data: program running stack data, central processing unit utilization rate and memory utilization rate. The SDK is provided with an internal preset database, data obtained by monitoring the host degree by the SDK are stored in the internal preset database, and when the program defect entry operation is executed, the SDK can read interactive data and running data in the preset database. When the program defect entry operation is executed, the SDK generates a database data reading instruction, the instruction comprises current time generated by the instruction and preset time, the current time is time for executing the program defect entry operation, the preset time can be selected according to actual conditions, for example, the current time is 16:17 minutes, the preset time is 10 seconds, and data within 10 seconds before the storage time is 16:17 minutes can be read in the database. Thus, the acquisition operation of the interactive data and the running data is completed. The program defect information in the above embodiment includes interactive data and running data, where the running data is running information of the terminal device, and the interactive data includes interactive operation data and network interactive data, so that the content of the program defect information is enriched, and the running condition of the terminal device when the host program has a defect can be known, so as to facilitate debugging of the host program.
In one embodiment, the user operates and starts the host program, the host program starts the SDK, and the SDK simultaneously starts 3 listeners. Monitoring the interactive operation of the user on the host program, monitoring the network communication interaction between the host program and the server, and monitoring whether the host program is abnormal or not. The data obtained by the first two listeners are stored in the corresponding databases, and the third listener starts a program defect passive entry operation process when receiving the data generated by the host program exception. Meanwhile, the terminal equipment can be a mobile phone, a tablet and the like, and the specific situation is not limited. It should be noted that the number limit of the listeners is not set uniquely here, and may be set according to the requirements of developers and application scenarios.
In one embodiment, after the calling the preset interface to enter the program defect information, the method further includes: acquiring the running state of a host program; and when the host program is in the stop running state, stopping executing the monitoring operation on the host program. When the host program stops running, the SDK stops monitoring the host program. The autonomous monitoring function of the host program is realized.
In one embodiment, the entry method is described in detail, and specifically referring to fig. 3, fig. 3 is a timing chart of the entry method of the program defect according to another embodiment of the present invention. As shown in fig. 3, the logging device in the program defect tracking management system is the protected device of the present invention, and is configured to execute the logging method of the present embodiment. The method for recording the program defects comprises the following steps:
step 301: after receiving a starting instruction sent by the host program, starting monitoring of interactive operation of a user in the host program, and storing interactive operation data in an internal preset database of the entry equipment.
Step 302: and starting monitoring of network interaction operation of the host program, and storing network interaction data in an internal preset database.
Step 303: and starting the host program to monitor when the host program is abnormal, and triggering a passive entry mode when the host program is abnormal.
Meanwhile, through step 304: and actively recording the program defects to receive a program defect active recording request initiated by a user.
After triggering the passive entry or the active entry, step 305 is executed: and sending a screen capture request to a host program, further sending the screen capture request to an operating system of the mobile equipment, calling an Application Programming Interface (API) of the operating system, and capturing a screen through a screen capture function of the operating system.
Step 306: and acquiring a current interface screen capture picture.
Step 307: and displaying the screenshot picture of the current interface, and making the user annotate the picture.
Step 308: and acquiring the annotated interactive interface picture.
Step 309: and acquiring interactive operation data of the host program and network interactive data of the host program.
Step 310: and sending an operation data request instruction of the mobile device.
Step 311: operational data of a mobile device is received.
Step 312: integrating the interactive interface picture, the interactive operation data, the network interactive data and the operation data of the mobile equipment;
step 313: requesting to input and submit defect information; and sending a request to a background manager of the program defect tracking management system for inputting and submitting defect information, and receiving a request result returned by the background manager.
In this embodiment, the running process of the host program is monitored, the interactive operation of the user in the host program and the network interactive event of the host program are recorded, meanwhile, the abnormal event of the host program can be monitored, and when the host program is abnormal (program crash, program stuck, etc.), the defect of the passive program is recorded. And meanwhile, an input instruction of a user can be received, and active program defect input is carried out. When the program defect is recorded, uploading and recording the screen capture picture, the interactive operation data, the network interactive data and the running data of the mobile equipment to a program defect tracking management system. The whole running process of the host program can be monitored, program defect information can be automatically uploaded, and the content of the defect information is rich.
In one embodiment, the host program starts to complete, starts an interactive operation monitor of the host program, starts to monitor page jump, button click, list sliding and other interactive operation events of the host program, and starts a background silent screen recording operation, in the process of recording user interactive operation data, the iOS system slightly differs from the Android system in the implementation of a Runtime Method screen swiping (Runtime Method swizzleing) technology, the page listening function, the user operation listening duration and the like are realized by calling a plurality of control components, for example, a page display or hidden Method component in an exchange control component is used for monitoring the presentation and hiding of a page, a Method component in an exchange UIControl framework is used for recording the event of a user clicking button, a proxy Method in an exchange uis control framework is used for monitoring the sliding operation of the uis screen framework is used for monitoring the sliding operation of the user, the Android system calls a default screen drawing component of a video through a byte code instrumentation plane (ordered program), a program, a development process monitor program, a background screen editing process is used for recording the content of a background screen, and the user interaction screen recording operation of the background screen drawing the content of the user interaction screen of the user, the user interaction screen browsing process is not less than the default screen, the background screen recording process, the user interaction screen reading process is not less than the default screen reading process, the default screen reading process of the background screen reading process, the background screen reading process is not less than the default screen reading process, the default screen reading process of the user interaction process of the host program, the virtual screen reading process of the virtual system, the virtual screen reading process of the virtual system is not less than the virtual screen reading process of the virtual system, the virtual process of the virtual system, the virtual system is not only the virtual system, the virtual:
step 401: and monitoring the interactive operation events of the user.
Step 402: and judging whether the interactive operation event is a user interactive operation event.
Step 403: and if the interactive operation event is the user interactive operation event, storing the interactive operation information into an internal database.
Step 404: and if the interactive operation event is not the user interactive operation event, judging whether the interactive operation event is a request interactive operation event.
Step 405: and if the interactive operation event is a request interactive operation event, acquiring interactive operation information from an internal database and returning the interactive operation information to the request terminal.
Step 406: if the interactive operation event is not the request interactive operation event, judging whether the monitoring event is a stop monitoring event; if yes, the monitoring of the interactive operation event is finished.
In one embodiment, the host program is started, and the SDK starts a network interaction listener of the host program, starts to listen to network interaction data of the host program, the iOS system obtains all requested interaction information in the network listener by using an NSUR L Protocol of the operating system, and registers the network listener by using a registerClass method component of an NSUR L Protocol framework, the Android system uses an AOP technique of byte code instrumentation, inserts logic for recording network interaction data in an initiating method and a responding method of a network request, stores the recorded event information in an internal memory, simultaneously listens for an event requesting network interaction data, and returns the network interaction data that has been stored as responding data, when the host program stops, the network interaction listener of the host program is stopped, and all listening behaviors are ended, fig. 5 is a flow chart of a network interaction event listening method provided by an embodiment of the present invention, as shown in fig. 5, the network interaction event listening method includes:
step 501: and monitoring the network interaction event.
Step 502: and judging whether the network interaction event is a network interaction event carried out by a host program.
Step 503: and if the network interaction event is the network interaction event carried out by the host program, storing the network interaction information into an internal database.
Step 504: if the network interaction event is not the network interaction event carried out by the host program, judging whether the network interaction event is a request network interaction event.
Step 505: if the network interaction event is a request network interaction event, network interaction information is obtained from an internal database and returned to the request terminal.
Step 506: if the network interaction event is not the request network interaction event, judging whether the network interaction event is a stop monitoring event; if yes, the network interaction event monitoring is finished.
In the embodiment, the monitor is used for monitoring the network exchange event of the host program, recording the network exchange data of the host program in real time and providing data support for program defect analysis.
In one embodiment, a listening process for a bug exception event of a host program is also described. Referring to fig. 6, fig. 6 is a flowchart illustrating a method for monitoring program exception events according to an embodiment of the present invention. As shown in fig. 6, the method for monitoring program exception events includes:
step 601: and monitoring the abnormal occurrence of the host program.
Step 602: and judging whether the interaction event is an abnormal occurrence event of the host program.
Step 603: and if the interaction event is the host program abnormal occurrence event, executing program defect passive entry operation.
Step 604: if the interaction event is not the abnormal event of the host program, judging whether the interaction event is a stop monitoring event; if yes, the host program is abnormal and the event monitoring is finished.
In this embodiment, the program exception event is monitored, whether the host program has an exception event can be known in time, and if the host program has an exception, the program defect is recorded. And the monitoring on the abnormal event of the host program is realized.
Referring to fig. 7, fig. 7 is a structural diagram of a program defect entry device according to an embodiment of the present invention. As shown in fig. 7, a data entry device includes:
a defect entry determining module 701, configured to receive operation data of a host program, and determine whether to execute a program defect entry operation according to the operation data;
a defect information obtaining module 702, configured to obtain, if the program defect entry operation is executed, a current interactive interface picture of the host program, interactive data of the host program, and operating data of a terminal device corresponding to the host program;
and a defect information entry module 703, configured to generate program defect information according to the interactive interface picture, the interactive data, and the operating data, and call a preset interface to enter the program defect information.
In a possible example, in terms of determining whether to execute a program defect entry operation according to the operation data, the defect entry determining module 701 is specifically configured to: judging whether the operation data contains callback error information or not, wherein the callback error information is returned by an operation system corresponding to the host program; and if the callback error information is contained, determining that the host program is in an abnormal state, and executing the program defect entry operation.
In one possible example, the operation data is user operation data; in the aspect of determining whether to execute a program defect entry operation according to the operation data, the defect entry determining module 701 is specifically configured to: determining a user request corresponding to the user operation data; and judging whether the user request is a preset interface starting request operation or not, and if so, executing program defect entry operation.
In a possible example, in the aspect of acquiring the current interactive interface picture of the host program, the interactive data of the host program, and the operation data of the terminal device corresponding to the host program, the defect information acquiring module 702 is specifically configured to: performing screen capture operation aiming at the current interface of the host program to obtain a screen capture picture of the current interface; performing labeling operation on the current interface screenshot picture to obtain the interactive interface picture; and acquiring the interaction data and the operation data from a preset database.
In a possible example, in the aspect that the annotation operation is performed on the current interface screenshot picture to obtain the interactive interface picture, the defect information obtaining module 702 is specifically configured to: displaying the current interface screenshot picture and a preset labeling prompt box; receiving annotation data, input by a user in the annotation prompt box, for the current interface screenshot picture, wherein the annotation data includes: at least one group of labeling coordinates and labeling content information corresponding to any group of labeling coordinates; and executing labeling operation on the current interface screenshot picture based on the labeling data to obtain the interactive interface picture.
In a possible example, in the aspect of acquiring the interaction data and the operation data from the preset database, the defect information acquiring module 702 is specifically configured to: acquiring current time and preset duration; determining an extraction time period based on the current time and the preset duration; extracting interaction data and operation data corresponding to the extraction time period from the preset database, wherein the interaction data comprise interaction operation data and network interaction data, and the operation data comprise one or more of the following data: program running stack data, central processing unit utilization rate and memory utilization rate.
In a possible example, after the calling the preset interface to enter the program defect information, the defect information entry module 703 is further configured to: acquiring the running state of the host program; and when the host program is in a running stop state, stopping executing the monitoring operation on the host program.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and as shown in the drawing, the electronic device 800 includes an application processor 810, a memory 820, a communication interface 830, and one or more programs 821, where the one or more programs 821 are stored in the memory 820 and configured to be executed by the application processor 810, and the one or more programs 821 include instructions for:
receiving operation data of a host program, and judging whether to execute program defect entry operation or not according to the operation data;
if the program defect entry operation is executed, acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of the terminal equipment corresponding to the host program;
and generating program defect information according to the interactive interface picture, the interactive data and the operating data, and calling a preset interface to input the program defect information.
The above description has introduced the solution of the embodiment of the present invention mainly from the perspective of the method-side implementation process. It is understood that the electronic device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The embodiment of the present invention may perform the division of the functional units for the electronic device according to the method example described above, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one control unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Referring to fig. 9, fig. 9 is a block diagram of a system for program defect tracking management according to an embodiment of the present invention. As shown in fig. 9, a program defect tracking management system includes:
a background manager 902, a background database 903 and an entry device 901 as described above connected to the background manager 902.
With regard to the apparatus and system of the above embodiments, specific embodiments thereof have been described in detail in relation to the embodiments of the method, and will not be described in detail herein.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present invention, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A data entry method, comprising:
receiving operation data of a host program, and judging whether to execute program defect entry operation according to the operation data;
if the program defect entry operation is executed, acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of terminal equipment corresponding to the host program;
generating program defect information according to the interactive interface picture, the interactive data and the operating data, and calling a preset interface to input the program defect information.
2. The method according to claim 1, wherein the acquiring the current interactive interface picture of the host program, the interactive data of the host program, and the operation data of the terminal device corresponding to the host program comprises:
performing screen capture operation aiming at the current interface of the host program to obtain a screen capture picture of the current interface;
performing labeling operation on the current interface screenshot picture to obtain the interactive interface picture;
and acquiring the interaction data and the operation data from a preset database.
3. The method of claim 2, wherein the performing the annotation operation on the current interface screenshot picture to obtain the interactive interface picture comprises:
displaying the current interface screenshot picture and a preset labeling prompt box;
receiving annotation data, input by a user in the annotation prompt box, for the current interface screenshot picture, wherein the annotation data includes: at least one group of labeling coordinates and labeling content information corresponding to any group of labeling coordinates;
and executing labeling operation on the current interface screenshot picture based on the labeling data to obtain the interactive interface picture.
4. The method of claim 2, wherein the obtaining the interaction data and the operation data from a preset database comprises:
acquiring current time and preset duration;
determining an extraction time period based on the current time and the preset duration;
extracting interaction data and operation data corresponding to the extraction time period from the preset database, wherein the interaction data comprise interaction operation data and network interaction data, and the operation data comprise one or more of the following data: program running stack data, central processing unit utilization rate and memory utilization rate.
5. The method of claim 1, wherein said determining whether to perform a program bug entry operation based on said operation data comprises:
judging whether the operation data contains callback error information or not, wherein the callback error information is returned by an operation system corresponding to the host program;
and if the callback error information is contained, determining that the host program is in an abnormal state, and executing the program defect entry operation.
6. The method of claim 1, wherein the operational data is user operational data;
the judging whether to execute the program defect entry operation according to the operation data comprises the following steps:
determining a user request corresponding to the user operation data;
and judging whether the user request is a preset interface starting request operation or not, and if so, executing program defect entry operation.
7. The method according to claim 1, wherein after the calling a preset interface to enter the program defect information, the method further comprises:
acquiring the running state of the host program;
and when the host program is in a running stop state, stopping executing the monitoring operation on the host program.
8. A data entry device, comprising:
the defect entry determining module is used for receiving the operation data of the host program and judging whether to execute program defect entry operation according to the operation data;
the defect information acquisition module is used for acquiring a current interactive interface picture of the host program, interactive data of the host program and running data of the terminal equipment corresponding to the host program if the program defect entry operation is executed;
and the defect information input module is used for generating program defect information according to the interactive interface picture, the interactive data and the operating data and calling a preset interface to input the program defect information.
9. An electronic device comprising a processor, an input device, an output device, and a memory, the processor, the input device, the output device, and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that a computer program for electronic data exchange is stored, which computer program, when being executed by a processor, carries out the steps of the method of one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010601978.9A CN111475423A (en) | 2020-06-29 | 2020-06-29 | Data entry method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010601978.9A CN111475423A (en) | 2020-06-29 | 2020-06-29 | Data entry method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111475423A true CN111475423A (en) | 2020-07-31 |
Family
ID=71764020
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010601978.9A Pending CN111475423A (en) | 2020-06-29 | 2020-06-29 | Data entry method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111475423A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791723A (en) * | 2021-09-23 | 2021-12-14 | 苏州美能华智能科技有限公司 | Data entry method, device and storage medium |
| CN113806233A (en) * | 2021-10-11 | 2021-12-17 | 成都觅瑞科技有限公司 | Method and device for acquiring program crash information, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323748A (en) * | 2014-07-01 | 2016-02-10 | 腾讯科技（深圳）有限公司 | Testing error uploading method and device |
| CN107368413A (en) * | 2017-07-12 | 2017-11-21 | 网易有道信息技术（北京）有限公司 | A kind of method and apparatus for submitting vulnerability information |
| CN107577594A (en) * | 2017-07-12 | 2018-01-12 | 捷开通讯(深圳)有限公司 | The abnormal method of record test, intelligent terminal and the device with store function |
| CN108170605A (en) * | 2017-12-28 | 2018-06-15 | 广州启生信息技术有限公司 | Submission method, client and the computer readable storage medium of bug information |
| CN109558331A (en) * | 2018-12-14 | 2019-04-02 | 瑞庭网络技术（上海）有限公司 | Defect inspection method, device, equipment and the storage medium of application program |
| CN109558739A (en) * | 2017-09-26 | 2019-04-02 | 腾讯科技（深圳）有限公司 | Program operating method, device, terminal and readable medium |
-
2020
- 2020-06-29 CN CN202010601978.9A patent/CN111475423A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323748A (en) * | 2014-07-01 | 2016-02-10 | 腾讯科技（深圳）有限公司 | Testing error uploading method and device |
| CN107368413A (en) * | 2017-07-12 | 2017-11-21 | 网易有道信息技术（北京）有限公司 | A kind of method and apparatus for submitting vulnerability information |
| CN107577594A (en) * | 2017-07-12 | 2018-01-12 | 捷开通讯(深圳)有限公司 | The abnormal method of record test, intelligent terminal and the device with store function |
| CN109558739A (en) * | 2017-09-26 | 2019-04-02 | 腾讯科技（深圳）有限公司 | Program operating method, device, terminal and readable medium |
| CN108170605A (en) * | 2017-12-28 | 2018-06-15 | 广州启生信息技术有限公司 | Submission method, client and the computer readable storage medium of bug information |
| CN109558331A (en) * | 2018-12-14 | 2019-04-02 | 瑞庭网络技术（上海）有限公司 | Defect inspection method, device, equipment and the storage medium of application program |
Non-Patent Citations (1)
| Title |
|---|
| 范建新主编: "《多媒体·网络·办公自动化实用技术》", 31 December 1997, 南京：东南大学出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791723A (en) * | 2021-09-23 | 2021-12-14 | 苏州美能华智能科技有限公司 | Data entry method, device and storage medium |
| CN113806233A (en) * | 2021-10-11 | 2021-12-17 | 成都觅瑞科技有限公司 | Method and device for acquiring program crash information, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3417380B1 (en) | Recording web conferences | |
| CN104063305B (en) | The method for testing pressure of intelligent terminal software, device and system | |
| TWI509409B (en) | Methods and systems for viewing log data recorded during execution of a program | |
| US20200328952A1 (en) | Distributed Tracing for Application Performance Monitoring | |
| CN107239389B (en) | Method and device for determining user operation record in hybrid APP | |
| US8433733B2 (en) | Web application record-replay system and method | |
| US20150120816A1 (en) | Tracking use of content of an online library | |
| CN106681701B (en) | Task display method and device | |
| CN105260082B (en) | A kind of test data methods of exhibiting and exploitation terminal | |
| US20120218396A1 (en) | Method and apparatus for usability testing of a mobile device | |
| US10275341B2 (en) | Mobile application usability testing | |
| CN111008135A (en) | APP test method, device, equipment and storage medium | |
| CN110837474A (en) | Script recording method, device, terminal and storage medium | |
| CN112115038A (en) | Application testing method and device and storage medium | |
| CN111813629A (en) | Method, device and equipment for generating monitoring data of Web page | |
| CN111475423A (en) | Data entry method and device, electronic equipment and readable storage medium | |
| CN113656102A (en) | Data point burying method and device, storage medium and electronic equipment | |
| CN103826164A (en) | Method and device for recording video watching | |
| CN111949509A (en) | Application software response time testing method, device, equipment and storage medium | |
| CN113824987A (en) | Method, medium, device and computing equipment for determining time consumption of first frame of live broadcast room | |
| CN109753530B (en) | Data processing method and device, medium and terminal thereof | |
| CN114217803A (en) | Page function problem processing method and device and electronic equipment | |
| CN114531345B (en) | Flow comparison result storage method, device, equipment and storage medium | |
| US20160283050A1 (en) | Adaptive tour interface engine | |
| CN110837467B (en) | Software testing method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200731 |