CN114780437A - Auxiliary correction method and system for software automatic test script - Google Patents
Auxiliary correction method and system for software automatic test script Download PDFInfo
- Publication number
- CN114780437A CN114780437A CN202210567344.5A CN202210567344A CN114780437A CN 114780437 A CN114780437 A CN 114780437A CN 202210567344 A CN202210567344 A CN 202210567344A CN 114780437 A CN114780437 A CN 114780437A
- Authority
- CN
- China
- Prior art keywords
- script
- software
- click
- area
- automatic test
- 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.)
- Granted
Links
- 238000013515 script Methods 0.000 title claims abstract description 118
- 238000012360 testing method Methods 0.000 title claims abstract description 42
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000012937 correction Methods 0.000 title claims abstract description 15
- 230000002159 abnormal effect Effects 0.000 claims abstract description 26
- 238000012544 monitoring process Methods 0.000 claims abstract description 10
- 239000003086 colorant Substances 0.000 claims description 4
- 230000000694 effects Effects 0.000 description 3
- 230000007257 malfunction Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
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/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a software automatic test script auxiliary correction method and a system, which relate to the image recognition and automatic test technology, and the method comprises the following steps: displaying an operation area and a script area of the software to be tested, wherein a mouse can move between the operation area and the script area; generating a script statement in the script area according to the mouse operation; monitoring whether the distance between the click positions of two adjacent click operations is smaller than a first threshold value or not; when the distance is smaller than a first threshold value, judging whether the two clicked objects are the same components or not, and if so, judging that the previous clicking operation is abnormal operation; and marking the script statement which is judged to be related to the abnormal operation, and displaying the mark in the script area. The scheme can remind the user of possible abnormal operation, so that the user is helped to quickly correct wrong scripts.
Description
Technical Field
The application relates to an automatic testing and image recognition technology, in particular to a software automatic testing script auxiliary correction method and a system.
Background
Automated testing tools are important tools in software testing. When an automated testing tool is used for testing software, a test engineer is required to open the software to be tested in the automated testing tool, and then a test script is recorded manually. The automatic testing tool can simulate manual operation software according to the content of the script when the automatic testing is carried out so as to achieve the purpose of testing software errors.
In fact, even when a sophisticated test engineer records a script, it is inevitable that errors, such as repeated clicks, misoperation due to software jamming, etc., will occur, so that the test engineer may need to record again or look over a lengthy test script for manual modification.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art. Therefore, the invention provides a software automatic test script auxiliary correction method and a system, which are used for automatically identifying possible error operation in a script.
In one aspect, an embodiment of the present application provides a software automatic test script auxiliary correction method, including the following steps:
displaying an operation area and a script area of the software to be tested, wherein a mouse can move between the operation area and the script area;
monitoring mouse operation aiming at the operation area;
generating a script statement in the script area according to the mouse operation;
monitoring whether the distance between the click positions of two adjacent click operations is smaller than a first threshold value or not, wherein the click operations comprise double click, single click, dragging and long press;
when the distance is smaller than a first threshold value, judging whether the objects clicked twice are the same components, and if so, judging that the previous clicking operation is abnormal operation;
and marking the script statement which is judged to be related to the abnormal operation, and displaying the mark in the script area.
In some embodiments, further comprising the steps of:
reading component information of a software interface;
and judging whether the component can be operated by the clicking operation according to the component information, and if not, judging that the clicking operation is abnormal operation.
In some embodiments, further comprising the steps of:
acquiring a corresponding software interface screenshot during clicking operation;
and judging whether the component is operable or not according to the screenshot of the software interface, and if not, judging that the clicking operation is abnormal.
In some embodiments, the determining whether the two clicked objects are the same component specifically includes:
and judging whether the two-click software interface screenshots are the same images, if so, judging that the two-click objects are the same components, and if not, judging that the two-click objects are not the same components.
In some embodiments, a fast playback preview step is further included, the fast preview step comprising the sub-steps of:
acquiring a preview instruction;
acquiring corresponding target playback operation according to the preview instruction, wherein the target playback operation refers to click operation corresponding to the script statement selected by the preview instruction;
reading software interface screenshots corresponding to a set number of click operations before and after the target playback operation and software interface screenshots corresponding to the target playback operation, and simulating click positions on the software interface screenshots according to click instructions recorded in the script to obtain playback frames;
the plurality of playback frames are played in sequence.
In some embodiments, the fast preview step further comprises the sub-steps of:
and marking script statements corresponding to the script area by using set colors and/or patterns according to the currently played playback frame.
In some embodiments, the method further comprises the steps of:
associating script statements with the screenshot of the software interface in the recorded script;
when the mouse enters the script area, monitoring the mouse operation;
when a script statement is selected by mouse operation, displaying the screenshot of the software interface and a corresponding click position;
or,
and when the time that the mouse stays in the script sentence exceeds the preset time length, displaying the software interface screenshot and the corresponding click position.
In some embodiments, the following steps are included:
acquiring a clearing instruction;
all marked script statements are deleted.
In some embodiments, it is determined whether the time interval between two clicking operations is smaller than a second threshold, and when the time interval between two clicking operations is smaller than the second threshold, it is determined as an abnormal operation.
On the other hand, the embodiment of the present application provides an auxiliary correcting system for a software automatic test script, including:
a memory for storing a program;
and the processor is used for recording the program so as to execute the software automatic test script auxiliary correction method.
According to the embodiment of the application, the mouse operation of a mouse in an operation area is monitored, the corresponding script statement is generated in the script area, whether the distance between click positions of two adjacent click operations is smaller than a certain value or not is monitored, whether the same component is clicked by the two operations is further analyzed under the condition that the distance between the click positions of the two adjacent click operations is smaller than the certain value or not, the operation may be caused by misoperation or software jamming, the script statement judged to be abnormal operation can be marked and processed, when a tester finds the marked statement, the corresponding script statement of the erroneous operation can be deleted by moving the mouse area, and the invalid click and the repeated click in the script can be effectively simplified.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
FIG. 1 is a flow chart of a software automatic test script auxiliary correction method provided in the present embodiment;
FIG. 2 is a schematic diagram of a software interface provided by the present solution;
fig. 3 is another schematic diagram of the software interface provided by the present solution.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described in detail and completely through implementation by referring to the drawings in the examples of the present application, and it is obvious that the described examples are some examples of the present application, but not all examples. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1 and fig. 2, the embodiment provides a software automatic test script auxiliary correction method, including the following steps:
and S1, displaying an operation area and a script area of the software to be tested, wherein the mouse can move between the operation area and the script area. As shown in fig. 2, in the present embodiment, an operation area and a script area are displayed, where the operation area is actually an area displaying an interface of the software to be tested. And the script area is used for displaying the content of the currently recorded script content (namely the script statement) in real time. The sizes of the two areas can be adjusted by dragging the mouse. Of course, a menu bar is also included on the interface of the whole test software. In the script area, what content is recorded will generate what statements.
And S2, monitoring mouse operation aiming at the operation area.
The mouse operation in this step includes all activities of the mouse, including moving, clicking or combining. The purpose of listening to the area includes the need to record scripts and the need to analyze for malfunctions. Generally, the common misoperation in recording scripts includes: repeated clicking caused by software incarceration, and mistaken touching of a non-operation area is the most common operation. The scheme mainly detects the errors, provides a convenient operation mode for deleting the statements, avoids re-recording caused by the tiny errors, or needs to check and modify the script at any time, and can improve the testing efficiency.
S3, generating script statement in script area according to mouse operation. In this step, a script statement is generated according to an operation of the mouse, where the script statement mainly records a screen position clicked by the user, a software interface screenshot, and the like, so as to generate an identification instruction for identifying the software interface screenshot and execute a corresponding operation at a corresponding position, where the operations may be a mouse click operation or a keyboard entry operation.
S4, monitoring whether the distance between the click positions of two adjacent click operations is smaller than a first threshold value or not, wherein the click operations comprise double click, single click, dragging and long press. In the scheme, in order to identify main operation errors, click operation is mainly analyzed. For repeated clicks caused by software jamming or misoperation, whether error points exist or repeated clicks exist can be judged based on the distance between two clicks. Therefore, when the click positions of the two operations are close, whether the two clicks belong to the same component can be analyzed.
It should be noted that whether the two clicks of the user belong to the "double click" operation is determined by the operating system, and the "double click" belongs to the one-click operation in this embodiment. For example, in operating an operation of dragging the verification code, the user may fail the dragging at the time of the first dragging, and thus, the user performs the same operation again. The drag points of the two operations are very close, and thus the operation is determined to be suspicious. At this time, it is necessary to further analyze whether the two operations are directed to the same component, because it cannot be excluded that two different operation components are located in the vicinity.
And S5, when the distance is smaller than a first threshold value, judging whether the objects clicked twice are the same components, and if so, judging that the previous clicking operation is abnormal operation.
In this step, there may be multiple ways to determine whether the clicked object is the same component.
For example, in some embodiments, determining whether the two clicked objects are the same component specifically includes:
and judging whether the two-click software interface screenshots are the same images, if so, judging that the two-click objects are the same components, and if not, judging that the two-click objects are not the same components. This is mainly caused by a stuck or incorrect click by the user to a hot zone (operability area) of the operating component. In general, in software design, in order to avoid false touch by a user, operable components are designed according to a certain interval, and in this case, the first threshold value may be set to be smaller than the interval. Therefore, if the corresponding screenshots of the two previous and next operations are the same screen, it is shown that the previous operation does not trigger any effect. This may be a hotspot where the software has not responded or where the user has not clicked on the component. Of course, this method is relatively simple in processing and does not require complicated recognition, although the accuracy is not necessarily sufficient. Whether repeated clicking is required to be judged only by matching whether the interfaces change before and after clicking, and the mode can avoid that two interfaces with the same button position are identified as the same component clicked by a user.
The other mode is to judge whether screenshots of two software interfaces are the same images or not, and judge whether the positions corresponding to two clicking operations belong to one component or not. This approach requires that the image recognition program can identify and partition some common components.
Still another mode is that part of software can provide an interface for outputting an interface component, the interface is used to obtain an element component and a corresponding position of the current interface, and whether two clicks belong to the same component can be determined by clicking the position, which is more accurate.
S6, marks the script sentence determined to be related to the abnormal operation, and displays the mark in the script area.
In particular, the marking may mark the code with different colors, and may also mark the code with different ground colors. Generally, one screenshot corresponds to a plurality of script statements, the script statements corresponding to the same screenshot are divided into one code block, and all the script statements in one code block can be deleted at one time based on user operation.
Of course, because the suspected misoperation may also be part of the test, the scheme only marks and displays the abnormal operation, but not directly processes the abnormal operation, and the user can quickly operate the script statements by using a mouse.
According to the embodiment of the application, the mouse operation of a mouse in an operation area is monitored, the corresponding script statement is generated in the script area, whether the distance between click positions of two adjacent click operations is smaller than a certain value or not is monitored, whether the same component is clicked by the two operations is further analyzed under the condition that the distance between the click positions of the two adjacent click operations is smaller than the certain value or not, the operation may be caused by misoperation or software jamming, the script statement judged to be abnormal operation can be marked and processed, when a tester finds the marked statement, the corresponding script statement of the erroneous operation can be deleted by moving the mouse area, and the invalid click and the repeated click in the script can be effectively simplified.
In some embodiments, in order to further analyze the abnormal operation to help a tester optimize the test script during recording, it is determined whether an interval between two click operations is smaller than a second threshold, and when the interval between two click operations is smaller than the second threshold, it is determined that the abnormal operation is performed.
Generally, when a normal tester conducts a test, a script is recorded while a test case is watched, and therefore a certain time interval generally exists between operations. Therefore, a plurality of operations in a short time tend to be abnormal operations. The two operations with the time interval smaller than the second threshold may be both determined as abnormal operations, or the previous or subsequent one may be determined as abnormal operations, and reminded. And the tester can disregard it when considering itself as normal operation.
In some embodiments, to detect the operation of clicking on the garbage area, the following steps are further included:
and reading the component information of the software interface.
And judging whether the component can be operated by the clicking operation according to the component information, and if not, judging that the clicking operation is abnormal operation.
In particular, in this embodiment, an interface needs to be provided by the software to be tested so that the test software can read the component information of the current interface. At this time, whether the assembly is overlapped with the clicking operation target position or not can be determined according to the position of the assembly and the clicking operation target position, and whether the tester is in the position where clicking has no operation significance can be judged.
In some embodiments, in order to detect the operation of clicking the useless area, the present embodiment provides another feasible solution, further including the following steps:
and acquiring a corresponding software interface screenshot in the clicking operation.
And judging whether the component is operable or not according to the screenshot of the software interface, and if not, judging that the clicking operation is abnormal.
Specifically, in the scheme, the positions of the components are identified through the screenshot of the software interface, and if the components clicked by the user obviously do not belong to the identified operation components (namely, the components with operability such as buttons, input boxes and the like), the situation that the user is operating a meaningless area can be indicated. Whether the user is intentionally or unintentionally, the user can be identified and an associated prompt is provided for the user to edit the script.
In some embodiments, as shown in FIG. 3, the user may have inadvertently performed a malfunction, and thus a visualization-based approach may be needed after the malfunction to determine how to adjust the script statements. In this embodiment, therefore, a fast playback preview step is also included, said fast preview step comprising the sub-steps of:
and acquiring a preview instruction. The user triggers the preview through a button provided by the software via a toolbar or the like.
And acquiring corresponding target playback operation according to the preview instruction, wherein the target playback operation refers to click operation corresponding to the script statement selected by the preview instruction. In the present embodiment, unlike normal script playback, script playback is essentially an operation on software, and therefore requires an operation on software from the beginning, actually an operation on software under test. The playback operation of the scheme refers to that a certain operation possibly selected by a user is mistakenly played back to the user for observation in a certain mode by adding the screenshot corresponding to the relevant operation and the position clicked by the user at that time. So that the user can determine the operation corresponding to the code.
And reading the software interface screenshots corresponding to the click operations of the set number before and after the target playback operation and the software interface screenshots corresponding to the target playback operation, and simulating click positions on the software interface screenshots according to click instructions recorded in the script to obtain playback frames. The playback frame can be regarded as a picture obtained by adding the corresponding operation position identifier to the screenshot of the software interface corresponding to the script statement. The frames of a plurality of operations before and after are played in sequence, and the content recorded by the test software can be restored.
The plurality of playback frames are played in sequence. And when the playback frame is played, the script statement corresponding to the playback frame is correspondingly marked. Namely, according to the currently played playback frame, a script statement corresponding to the script area is marked by a set color and/or pattern.
The user can clearly see what operation the recorded context performs by himself, and each operation corresponds to what code. The effect of this embodiment is that the user can check his past operation by using the playback frame at any time, and can select playback at any position without stopping the test. The script area can be directly operated by moving the mouse, so that the user can very conveniently confirm and modify the script.
In some embodiments, in order to facilitate the user to browse, the user may also directly browse the playback frame corresponding to the script statement instead of selecting the playback mode, so that the user may also quickly confirm his/her own operation, and the method further includes the following steps:
and associating the script statement with the screenshot of the software interface in the recorded script.
And when the mouse enters the script area, monitoring the operation of the mouse.
And when a script statement is selected by mouse operation, displaying the screenshot of the software interface and the corresponding click position.
Or,
and when the time that the mouse stays in the script sentence exceeds the preset time length, displaying the screenshot of the software interface and the corresponding click position.
As shown in fig. 3, the user may click on certain codes that pop up a playback frame on one side. The implemented UI may also follow the previous UI scheme for multiple playback frame playback.
In some embodiments, the user may directly one-click clear after determining the suspicious operation, including the steps of:
a clear instruction is fetched.
All marked script statements are deleted.
On the other hand, the embodiment of the present application provides an auxiliary correcting system for a software automatic test script, including:
a memory for storing a program;
and the processor is used for recording the program so as to execute the software automatic test script auxiliary correction method.
It is to be noted that the foregoing is only illustrative of the presently preferred embodiments and application of the principles of the present invention. Those skilled in the art will appreciate that the present application is not limited to the particular embodiments described herein, but is capable of many obvious modifications, rearrangements and substitutions without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims (10)
1. A software automatic test script auxiliary correction method is characterized by comprising the following steps:
displaying an operation area and a script area of the software to be tested, wherein a mouse can move between the operation area and the script area;
monitoring mouse operation aiming at the operation area;
generating a script statement in the script area according to the mouse operation;
monitoring whether the distance between the click positions of two adjacent click operations is smaller than a first threshold value or not, wherein the click operations comprise double click, single click, dragging and long press;
when the distance is smaller than a first threshold value, judging whether the objects clicked twice are the same components, and if so, judging that the previous clicking operation is abnormal operation;
and marking the script statement which is judged to be related to the abnormal operation, and displaying the mark in the script area.
2. The software automatic test script auxiliary correction method according to claim 1, further comprising the following steps:
reading component information of a software interface;
and judging whether the component can be operated by the clicking operation according to the component information, and if not, judging that the clicking operation is abnormal operation.
3. The software automatic test script auxiliary correcting method according to claim 1, characterized by further comprising the following steps:
acquiring a corresponding software interface screenshot during clicking operation;
and judging whether the component is operable or not according to the screenshot of the software interface, and if not, judging that the clicking operation is abnormal.
4. The method for assisting in correcting the software automatic test script according to claim 1, wherein judging whether the objects clicked twice are the same component specifically comprises:
and judging whether the screenshots of the software interfaces clicked twice are the same, if so, judging that the objects clicked twice are the same components, and if not, judging that the objects clicked twice are not the same components.
5. The software automatic test script auxiliary correcting method according to claim 1, further comprising a fast playback preview step, wherein the fast preview step comprises the following sub-steps:
acquiring a preview instruction;
acquiring corresponding target playback operation according to the preview instruction, wherein the target playback operation refers to click operation corresponding to the script statement selected by the preview instruction;
reading software interface screenshots corresponding to a set number of click operations before and after the target playback operation and software interface screenshots corresponding to the target playback operation, and simulating click positions on the software interface screenshots according to click instructions recorded in the script to obtain playback frames;
the plurality of playback frames are played in sequence.
6. The software automatic test script auxiliary correcting method according to claim 1, wherein the quick preview step further comprises the following sub-steps:
and marking script statements corresponding to the script area by using set colors and/or patterns according to the currently played playback frame.
7. The software automatic test script auxiliary correction method according to claim 1, characterized in that the method further comprises the following steps:
associating script statements with the software interface screenshots in the recorded scripts;
when the mouse enters the script area, monitoring mouse operation;
when a script statement is selected by mouse operation, displaying the software interface screenshot and a corresponding click position; or,
and when the time that the mouse stays in the script sentence exceeds the preset time length, displaying the software interface screenshot and the corresponding click position.
8. The software automatic test script auxiliary correction method according to claim 1, characterized by comprising the following steps:
acquiring a clearing instruction;
all marked script statements are deleted.
9. The method for assisting in correcting the software automatic test script according to claim 1, wherein it is determined whether an interval time between two click operations is smaller than a second threshold, and when the interval time between two click operations is smaller than the second threshold, it is determined that the operation is abnormal.
10. A software automatic test script auxiliary correction system is characterized by comprising:
a memory for storing a program;
a processor for recording the program to execute the software automatic test script assisted amending method of any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210567344.5A CN114780437B (en) | 2022-05-24 | 2022-05-24 | Auxiliary correction method and system for software automatic test script |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210567344.5A CN114780437B (en) | 2022-05-24 | 2022-05-24 | Auxiliary correction method and system for software automatic test script |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114780437A true CN114780437A (en) | 2022-07-22 |
| CN114780437B CN114780437B (en) | 2023-01-31 |
Family
ID=82409524
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210567344.5A Active CN114780437B (en) | 2022-05-24 | 2022-05-24 | Auxiliary correction method and system for software automatic test script |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114780437B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019923A (en) * | 2011-09-22 | 2013-04-03 | 腾讯科技（深圳）有限公司 | Method and system of simulated click test |
| CN105740153A (en) * | 2016-02-29 | 2016-07-06 | 网易（杭州）网络有限公司 | Cloud testing method and device |
| CN107135660A (en) * | 2015-12-11 | 2017-09-05 | 华为技术有限公司 | A kind of false-touch prevention method, device and electronic equipment |
| US10108432B1 (en) * | 2009-04-16 | 2018-10-23 | Intuit Inc. | Generating a script based on user actions |
| CN109683739A (en) * | 2018-12-06 | 2019-04-26 | 深圳前海达闼云端智能科技有限公司 | The method and apparatus for adjusting operation interface, storage medium and electronic equipment |
| CN110134600A (en) * | 2019-05-09 | 2019-08-16 | 北京小米移动软件有限公司 | Test script method for recording, device and storage medium |
| CN112699057A (en) * | 2021-03-24 | 2021-04-23 | 广州弘一信息科技股份有限公司 | Early warning system in software development process |
-
2022
- 2022-05-24 CN CN202210567344.5A patent/CN114780437B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10108432B1 (en) * | 2009-04-16 | 2018-10-23 | Intuit Inc. | Generating a script based on user actions |
| CN103019923A (en) * | 2011-09-22 | 2013-04-03 | 腾讯科技（深圳）有限公司 | Method and system of simulated click test |
| CN107135660A (en) * | 2015-12-11 | 2017-09-05 | 华为技术有限公司 | A kind of false-touch prevention method, device and electronic equipment |
| CN105740153A (en) * | 2016-02-29 | 2016-07-06 | 网易（杭州）网络有限公司 | Cloud testing method and device |
| CN109683739A (en) * | 2018-12-06 | 2019-04-26 | 深圳前海达闼云端智能科技有限公司 | The method and apparatus for adjusting operation interface, storage medium and electronic equipment |
| CN110134600A (en) * | 2019-05-09 | 2019-08-16 | 北京小米移动软件有限公司 | Test script method for recording, device and storage medium |
| CN112699057A (en) * | 2021-03-24 | 2021-04-23 | 广州弘一信息科技股份有限公司 | Early warning system in software development process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114780437B (en) | 2023-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106844217B (en) | Method and device for embedding point of applied control and readable storage medium | |
| CN104956339B (en) | Software test script is generated from video | |
| US10073766B2 (en) | Building signatures of application flows | |
| WO2017005148A1 (en) | Automatic software-testing method and device | |
| US20140189576A1 (en) | System and method for visual matching of application screenshots | |
| US20140218385A1 (en) | System and method for visual segmentation of application screenshots | |
| US20160033953A1 (en) | Peripheral device for programmable controller and debug support program | |
| JP4381436B2 (en) | Scenario generation device and scenario generation program | |
| US20180039559A1 (en) | Method and apparatus for creating reference images for an automated test of software with a graphical user interface | |
| CN110851299A (en) | Automatic flow exception eliminating method, device, equipment and storage medium | |
| JP6653929B1 (en) | Automatic determination processing device, automatic determination processing method, inspection system, program, and recording medium | |
| CN105824742A (en) | Operation recording method and device of user interface | |
| CN114780437B (en) | Auxiliary correction method and system for software automatic test script | |
| KR101774815B1 (en) | Cursor location recognition test automation system and test automation method using the same | |
| US20170212798A1 (en) | Ladder program display device having automatic trace function for self-holding circuit of ladder program | |
| CN111274086A (en) | Computer software fault monitoring system | |
| CN111026644B (en) | Operation result labeling method and device, storage medium and electronic equipment | |
| JP2008299502A (en) | Test case validity automatic verification program and test case validity automatic verification result display method | |
| CN113127348B (en) | Method, system and storage medium for recording automatic test script of software | |
| CN113448832B (en) | Control exposure detection method and application program operation monitoring system | |
| US11995146B1 (en) | System and method for displaying real-time code of embedded code in a browser-window of a software application | |
| CN116643987A (en) | Verification method, device, equipment and medium for test behaviors | |
| JP2011134270A (en) | Unit test support device, method and program | |
| TWI301203B (en) | Test point pitch analyzing method for logic circuit | |
| CN115981995A (en) | Test case generation method, system and storage medium based on application screen recording record |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |