CN109684214B - UI (user interface) testing method and device - Google Patents
UI (user interface) testing method and device Download PDFInfo
- Publication number
- CN109684214B CN109684214B CN201811574053.9A CN201811574053A CN109684214B CN 109684214 B CN109684214 B CN 109684214B CN 201811574053 A CN201811574053 A CN 201811574053A CN 109684214 B CN109684214 B CN 109684214B
- Authority
- CN
- China
- Prior art keywords
- use case
- case
- target
- identifier
- instruction
- 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.)
- Active
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/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
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)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention provides a method and a device for testing a User Interface (UI), wherein the method comprises the following steps: the method comprises the steps of receiving a modification instruction which aims at a first case and carries an identifier of a first operation to be modified, modifying the first case according to the modification instruction to obtain a modified first case, and sending a target application program and the target case to a target terminal when receiving a test instruction for carrying out target case test on the target application program so that the target terminal can execute the target case on the target application program. Therefore, when a tester needs to modify the first case, the first case is modified only according to the identifier of the operation to be modified, the whole case does not need to be recorded again, and the test efficiency of the UI can be improved.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a UI testing method and device.
Background
With the rapid development of mobile terminals (e.g., smart phones and tablet computers), UI (user interface) testing of applications of the mobile terminals is also increasingly important. The purpose of UI testing is to ensure that the user interface of the application provides the user with the proper operations to access and browse the test object functionality, and that the user interface meets the expected requirements of the developer.
The existing UI test method comprises the following steps: the method comprises the steps of firstly, recording a use case, and secondly, playing back the use case. When the use case recording is carried out, a tester can record a plurality of operations such as clicking, sliding and the like in a user interface of an application program by using use case recording software, so that a use case containing a plurality of operations is obtained. When the UI test needs to be performed on the application program, a recorded case (i.e., a playback case) can be executed on the application program in the mobile terminal, and a test result can be obtained. However, when the application program is updated or different test scenarios are applied, a tester may need to modify the operation in a certain use case, and at this time, the tester may only re-record the whole use case, and then execute the re-recorded use case on the application program in the mobile terminal.
Therefore, in the prior art, when a tester needs to modify an operation in a use case, the tester needs to record the whole use case containing the operation again, and the efficiency of UI test is low.
Disclosure of Invention
The embodiment of the invention aims to provide a UI testing method and device so as to improve the UI testing efficiency. The specific technical scheme is as follows:
in a first aspect, to achieve the above object, an embodiment of the present invention discloses a UI testing method, where the method includes:
receiving a modification instruction aiming at a first case, wherein the modification instruction carries an identifier of a first operation to be modified;
modifying the first case according to the modification instruction to obtain a modified first case;
when a test instruction for carrying out target case test on a target application program is received, the test instruction carries an identification of a target terminal, and the target application program and the target case are sent to the target terminal so that the target terminal can execute the target case on the target application program, wherein the target case comprises a modified first case.
Optionally, the modification instruction further carries a modified target operation parameter;
the modifying the first case according to the modifying instruction comprises:
determining an operation corresponding to the identifier of the first operation in the first use case;
and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into the target operation parameter.
Optionally, the modification instruction further carries a modified target operation parameter and an identifier of an execution sequence of the first operation in the first use case;
the modifying the first case according to the modifying instruction comprises:
determining an operation corresponding to the identifier of the first operation;
and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
Optionally, the modifying the first case according to the modification instruction includes:
determining an operation corresponding to the identifier of the first operation in the first use case;
and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
Optionally, before the sending the target application and the target use case to the target terminal, the method further includes:
receiving a case adding instruction, wherein the case adding instruction carries a second case and an identifier of an execution sequence of the second case in the target case;
and adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
Optionally, the method further includes:
receiving a query operation instruction, wherein the query operation instruction carries an identifier of a third use case to be queried;
and sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to a user terminal so that the user terminal displays each operation and the operation parameters of each operation.
Optionally, the method further includes:
receiving a query case instruction input by a user, wherein the query case instruction carries an authority identifier of the user;
determining a fourth use case allowing the user to inquire according to the authority identifier;
sending the use case information of the fourth use case to a user terminal so that the user terminal can display the use case information of the fourth use case, wherein the use case information comprises at least one of the following: the name of the fourth use case, the description of the fourth use case, the identifier of the function of the fourth use case for testing, and the identifier of the application program to which the fourth use case belongs.
Optionally, after the target application and the target use case are sent to the target terminal, the method further includes:
acquiring a display interface of the target terminal when the target application program executes preset operation in the target use case, wherein the preset operation comprises at least one of the following operations: click operation, slide operation and drag operation;
and sending the display interface to a user terminal so that the user terminal displays the display interface.
Optionally, the target terminal is a terminal in a remote live machine platform or a terminal connected locally.
Optionally, the method further includes:
receiving a test history query instruction;
sending result information of a use case executed within a preset time length before the current time to a user terminal so as to enable the user terminal to display the result information, wherein the result information comprises at least one of the following: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case is execution success, execution failure or execution exception.
In a second aspect, to achieve the above object, an embodiment of the present invention discloses a UI testing apparatus, including:
the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a modification instruction aiming at a first case, and the modification instruction carries an identifier of a first operation to be modified;
the modification module is used for modifying the first case according to the modification instruction to obtain a modified first case;
the sending module is used for sending the target application program and the target case to the target terminal when receiving a test instruction for carrying out target case test on the target application program, so that the target case is executed by the target application program by the target terminal, wherein the target case comprises a modified first case.
Optionally, the modification instruction further carries a modified target operation parameter;
the modification module is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into the target operation parameter.
Optionally, the modification instruction further carries a modified target operation parameter and an identifier of an execution sequence of the first operation in the first use case;
the modification module is specifically configured to determine an operation corresponding to the identifier of the first operation;
and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
Optionally, the modification module is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
Optionally, the apparatus further comprises:
the case adding module is used for receiving a case adding instruction, wherein the case adding instruction carries a second case and an identifier of an execution sequence of the second case in the target case;
and adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
Optionally, the apparatus further comprises:
the operation query module is used for receiving a query operation instruction, wherein the query operation instruction carries an identifier of a third use case to be queried;
and sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to a user terminal so that the user terminal displays each operation and the operation parameters of each operation.
Optionally, the apparatus further comprises:
the system comprises a use case query module, a use case query module and a case query module, wherein the use case query module is used for receiving a query use case instruction input by a user, and the query use case instruction carries an authority identifier of the user;
determining a fourth use case allowing the user to inquire according to the authority identifier;
sending the use case information of the fourth use case to a user terminal so that the user terminal can display the use case information of the fourth use case, wherein the use case information comprises at least one of the following: the name of the fourth use case, the description of the fourth use case, the identifier of the function of the fourth use case for testing, and the identifier of the application program to which the fourth use case belongs.
Optionally, the apparatus further comprises:
a processing module, configured to obtain a display interface of the target terminal when the target application executes preset operations in the target use case, where the preset operations include at least one of: click operation, slide operation and drag operation;
and sending the display interface to a user terminal so that the user terminal displays the display interface.
Optionally, the target terminal is a terminal in a remote live machine platform or a terminal connected locally.
Optionally, the apparatus further comprises:
the test history query module is used for receiving a test history query instruction;
sending result information of a use case executed within a preset time length before the current time to a user terminal so as to enable the user terminal to display the result information, wherein the result information comprises at least one of the following: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case is execution success, execution failure or execution exception.
In another aspect of the present invention, to achieve the above object, an embodiment of the present invention further discloses an electronic device, where the electronic device includes:
a memory for storing a computer program;
and a processor configured to implement the UI testing method according to the first aspect when executing the program stored in the memory.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium runs on a computer, the UI testing method according to the first aspect is implemented.
In another aspect of the present invention, an embodiment of the present invention further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the UI testing method according to the first aspect.
The UI testing method and device provided by the embodiment of the invention can receive a modification instruction carrying an identifier of a first operation to be modified aiming at a first case, modify the first case according to the modification instruction to obtain a modified first case, and when a testing instruction for testing a target case of a target application program is received, the target application program and the target case are sent to a target terminal so that the target terminal can execute the target case on the target application program. Therefore, when a tester needs to modify the first case, the first case is modified only according to the identifier of the first operation, namely, the first operation needing to be modified is modified only, the whole case does not need to be recorded again, and the test efficiency of the UI can be improved.
Of course, not all of the advantages described above need to be achieved at the same time in the practice of any one product or method of the invention.
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 system framework diagram of a UI test provided by an embodiment of the invention;
FIG. 2 is a flowchart of a UI testing method according to an embodiment of the invention;
fig. 3 is a schematic diagram of a display interface of a target device according to an embodiment of the present invention;
fig. 4 is a schematic view of a display interface of a target device according to an embodiment of the present invention;
fig. 5 is a schematic view of a display interface of a target device according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a display interface of a target device according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a display interface of a target device according to an embodiment of the present invention;
FIG. 8 is a block diagram of a UI testing device according to an embodiment of the invention;
fig. 9 is a structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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 invention.
The invention provides a UI test method and device, which can be applied to target equipment, wherein the target equipment can be a computer. Referring to fig. 1, fig. 1 is a system framework diagram of a UI test according to an embodiment of the present invention.
Wherein, the server can include: the httpserver (hypertext transfer protocol server) module provides a corresponding interface for the tester to modify and view the use case and other functions at the PC side. The uiautotest (user interface automation test) module is a module obtained by secondary development based on an open source framework uiautomator2 and is used for interacting with a mobile phone and executing a use case. The DB (Database) is used to store the result data of the UI test, and may be a mysql Database.
The PC (personal computer) side includes: the httpserver module is used for providing an interface for interacting with the httpserver module of the server side, responding to an instruction sent by the httpserver module of the server side to determine that a use case is executed at the PC side, and calling the uiautotest module of the PC side; the uiautotest module can interact with a mobile phone connected with the PC end under the calling of the httpserver module of the PC end to execute a use case. The PC terminal can be connected to the mobile phone through a USB (Universal Serial Bus). The target device may be the PC side.
The Open-stf (Open-smartphone test farm) is connected with the uiautotest module at the server side, and is used for receiving an instruction sent by the uiautotest module at the server side to determine that a use case is executed in the mobile phone connected with the Open-stf.
The present invention will be described in detail with reference to specific examples.
Referring to fig. 2, fig. 2 is a flowchart of a UI testing method according to an embodiment of the present invention, where the method may include the following steps:
s201: a modification instruction for the first instance is received.
Wherein, the modification instruction can carry the identifier of the first operation to be modified. The tester usually needs to modify the use cases according to the business requirements, and for a certain use case, the tester usually only needs to modify one or more operations in the use case. The first operation may be an operation to be modified by a tester, the identifier of the first operation may be a serial number of the first operation, and the serial number of the first operation may be obtained according to an order in which the first operation is generated. The identifier of the first operation may also be an identifier of an operation type of the first operation, and the operation type may be a click operation, a slide operation, or the like.
In the embodiment of the present invention, a plurality of use cases preset by a tester may be stored in the target device. When a tester needs to modify a use case in a target device, the tester can input a modification instruction which is specific to a first case and carries an identifier of a first operation to the target device through an input component of the target device so as to modify the first case, and correspondingly, the target device can receive the modification instruction, so that the tester can be determined to modify the first case, and the operation which needs to be modified is the first operation. The first operation may be one operation or a plurality of operations.
For example, a use case list may be displayed in the operation interface of the target device, and each preset use case may be included in the use case list. Correspondingly, the tester can click and select the first case, the target device can determine that the tester needs to modify the first case, and the target device can display each operation currently contained in the first case, so that the tester can modify the operation in the first case.
Referring to fig. 3, fig. 3 is a schematic view of a display interface of a target device according to an embodiment of the present invention, where the example is an operation included in a use case displayed by the target device, and the use case includes two operations, namely "Start (Start) of clicking a launch screen" and "coordinate of a Booster icon", where an ID (Identification number) list indicates identifications of the two operations; the operation description is used for representing the execution process of the operation, and can be added by a tester according to the execution process of the operation; the operation description represents an operation parameter of the operation.
In addition, various function buttons, such as "add", "copy", "modify", and "delete" buttons in fig. 3, may also be provided in the display interface of the target device. The function of each button will be described in detail in the following embodiments.
S202: and modifying the first case according to the modification instruction to obtain the modified first case.
In the embodiment of the present invention, the target device may modify the first case according to the modification instruction, so as to obtain the modified first case.
Generally, the modification instruction may carry different information, and the target device may modify the first example in different ways according to the information carried in the modification instruction, specifically, the target device may modify the first example in the following ways:
in a first manner, the modification instruction may carry an identifier of the first operation to be modified and the modified target operation parameter, then S202 may include the following steps: determining an operation corresponding to the identifier of the first operation in the first use case; and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into a target operation parameter.
In this manner, the identity of the first operation may be the sequence number of the first operation.
In the embodiment of the present invention, when a tester needs to modify a certain operation (i.e., a first operation) in a first case, the tester may input a modification instruction carrying an identifier of the first operation and a modified target operation parameter to a target device.
Correspondingly, after receiving the modification instruction, the target device may obtain the identifier of the first operation and the target operation parameter, perform query in each operation included in the first case according to the identifier of the first operation, determine the operation corresponding to the identifier of the first operation, modify the operation parameter of the operation corresponding to the identifier of the first operation included in the first case into the target operation parameter by the target device, and then complete modification of the first operation, so as to obtain the modified first case.
For example, referring to fig. 3, each operation included in the first example may be displayed in the running interface of the target device, when the tester clicks the first operation in the selection graph and clicks the "modify" button, the target device may display the current operation parameter of the first operation, and then, the tester may modify the displayed operation parameter into the target operation parameter to complete the modification of the first operation, so as to obtain the modified first example.
In a second manner, the modification instruction may carry an identifier of the first operation to be modified, the modified target operation parameter, and an identifier of an execution sequence of the first operation in the first use case, then S202 may include the following steps: determining an operation corresponding to the identifier of the first operation; and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
In this manner, the identification of the first operation may be an identification of an operation type of the first operation.
In the embodiment of the present invention, when a tester needs to add an operation (i.e., a first operation) in a first use case, the tester may input, to a target device, a modification instruction carrying an identifier of the first operation, a target operation parameter, and an identifier of an execution sequence of the first operation in the first use case.
The target device may obtain a modification instruction of the identifier of the first operation, the target operation parameter, and the identifier of the execution sequence of the first operation in the first case, and then, the target device may determine the execution sequence of the first operation in the first case according to the identifier of the execution sequence of the first operation in the first case, and determine an operation corresponding to the identifier of the first operation, and further may add an operation corresponding to the identifier of the first operation in the first case, where the operation parameter is an operation of the target operation parameter, to obtain a first case including the first operation.
For example, referring to fig. 3, operations included in the first example may be displayed in an operation interface of the target device, the tester may click to select the first operation, then, the tester may click to a "new" button, the target device may display a list of the new operations, the tester may select an operation corresponding to the identifier of the first operation in the list of the new operations and input the target operation parameter, the target device may determine an operation corresponding to the identifier of the first operation selected by the tester and determine that the corresponding operation parameter is the target operation parameter, and then, the target device may add the operation (i.e., the first operation) including the determined processing action and the operation parameter being the target operation parameter to the first operation to obtain the first example including the first operation.
Or, the tester may click and select the first operation, then, the tester may click a "copy" button, the target device may display a list of generated operations that allow copying, the tester may select an operation corresponding to the identifier of the first operation from the list, and modify the operation parameter of the selected operation into the target operation parameter, the target device may determine a processing action included in the operation selected by the tester, and determine that the corresponding operation parameter is the target operation parameter, and then, the target device may add the operation (i.e., the first operation) including the determined processing action and having the operation parameter that is the target operation parameter to the front of the first operation, so as to obtain a first case including the first operation.
In a third mode, the modification instruction may carry an identifier of the first operation to be modified, and S202 may include the following steps: determining an operation corresponding to the identifier of the first operation in the first use case; and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
In this manner, the identity of the first operation may be the sequence number of the first operation.
In the embodiment of the present invention, the tester may further delete a currently existing operation (i.e., the first operation) in the first case, and the tester may input a modification instruction carrying an identifier of the first operation to the target device, and accordingly, the target device may obtain the identifier of the first operation, perform query in each operation included in the first case, determine an operation corresponding to the identifier of the first operation, and delete the determined operation from the first case, thereby obtaining the modified first case.
For example, referring to fig. 3, operations included in the first case may be displayed in the running interface of the target device, the tester may click to select the first operation, then, the tester may click a "delete" button, and the target device may delete the first operation from the first case to obtain the modified first case.
S203: and when a test instruction for carrying out target case test on the target application program is received, the target application program and the target case are sent to the target terminal, so that the target terminal executes the target case on the target application program.
The test instruction may carry an identifier of the target terminal, and the target use case may include the modified first use case.
In the embodiment of the invention, after the first case is modified, a tester can perform the UI test according to the modified first case, and the tester can input a test instruction for performing the target case test on the target application program to the target device, so as to implement the target case execution on the target application program on the target terminal.
Correspondingly, the target device can receive the test instruction and acquire the identifier of the target terminal, then the target device can send the target application program and the target case to the target terminal, and after receiving the target application program and the target case, the target terminal can execute the target case on the target application program to realize the UI test.
For example, referring to fig. 4, a selection box of a device list, a button of an upload application, and a list of currently available use cases may be set in the display interface of the target device. The tester can select a target terminal in a selection box of the equipment list, click a 'select file' button to select a tested target application program, and select a target case to be executed in a list of currently available cases.
In addition, the selected target terminal may also be displayed in the selection box of the device list, for example, when the user selects the target terminal and selects to execute the target use case, if waiting is displayed in the selection box of the device list: and 4, indicating that the current target terminal is occupied, and 4 indicating that the current target terminal has 4 to-be-executed case test tasks.
Optionally, the test of a combination of multiple use cases can also be implemented. Before S203, the method may further include the steps of:
step one, receiving a case adding instruction.
The case adding instruction may carry a second case and an identifier of an execution sequence of the second case in the target case, where the second case may be a preset case.
And step two, adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
In the embodiment of the invention, a tester can test the target terminal according to the generated multiple use cases. The tester may input a case adding instruction carrying the second case and the identifier of the execution sequence of the second case in the target case to the target device.
The target device may obtain the second use case and an identifier of an execution sequence of the second use case in the target use case, and then, the target device may determine the execution sequence of the second use case in the target use case according to the identifier of the execution sequence of the second use case in the target use case, and add the second use case in the target use case according to the execution sequence, and further, the target device may send the target use case including the first use case and the second use case and the target application program to the target terminal, and the target terminal may execute the target use case including the first use case and the second use case on the target application program.
For example, referring to fig. 5, fig. 5 shows the use cases included in the target use case: public operations, speed balls, menus and wallpaper center detail pages are started. The tester can click and select the 'speed ball' case and click the 'new adding' button, the target device can display a list of cases allowed to be added currently, the tester can select a second case from the list, and the target device can add the second case to the front of the 'speed ball' case, so that the second case is added to the target case.
Based on the processing, the multiple use cases can be added into the target use case so as to realize that the target terminal tests the multiple use cases. In this case, the target use case can be understood as a use case group including a plurality of use cases.
In addition, a 'set regression' button and a 'cancel regression' button can be arranged in the display interface of the target device, a user can select a certain case group and click the 'set regression' button, and the target device can set the case group as a regressive case group; the user can also select a certain regression case group and click the 'cancel regression' button, and the target device can set the case group as a non-regression case group. Based on the processing, the case group for executing regression can be triggered automatically or manually by a tester, so that the continuous integration of the cases is realized.
In addition, the test personnel can also inquire the information of the operation contained in the use case. The method may further comprise the steps of:
step one, receiving an inquiry operation instruction.
And step two, sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to the user terminal so that the user terminal displays each operation and the operation parameters of each operation.
The query operation instruction may carry an identifier of a third use case to be queried. The user terminal may be another terminal connected to the target device, or the user terminal may be a display section of the target device.
In the embodiment of the present invention, a tester may query information of operations included in each currently set use case in a target device. The tester may input a query operation instruction carrying an identifier of a use case to be queried (i.e., a third use case) to the target device.
The target device may query in each set use case according to the identifier of the third use case, determine a use case (that is, the third use case) corresponding to the identifier of the third use case, then, the target device may determine each operation and operation parameters of each operation included in the third use case, and send each operation and operation parameters of each operation included in the third use case to the user terminal, and the user terminal may display each operation and operation parameters of each operation included in the third use case.
In one implementation, the target device may display the operations and the operation parameters of the operations included in the third example, and referring to fig. 6, in fig. 6, the ID indicates the ID of the operations included in the third example, that is, the identifier of each operation, the operation description is the operation description of each operation included in the third example, and the operation description indicates the operation parameters of each operation included in the third example.
Secondly, the set cases can be inquired by a tester. The method may further comprise the steps of:
step one, receiving a query case instruction input by a user.
And step two, determining a fourth use case allowing the user to query according to the authority identifier.
And step three, sending the use case information of the fourth use case to the user terminal so that the user terminal can display the use case information of the fourth use case.
The query case instruction may carry an authority identifier of the user (i.e., a tester), and the authority identifier may be a user identifier of the user. The number of the fourth application examples may be one or plural.
The use case information may include at least one of: the name of the fourth use case, the description of the fourth use case, the identification of the function of the fourth use case for testing, and the identification of the application program to which the fourth use case belongs.
The case information may be information added by the tester for the fourth case when the tester sets the fourth case. The use case name of the fourth use case may be used to represent the function of the fourth use case; the use case description of the fourth use case can be a specific description of the function of the fourth use case, so that other testers can conveniently and quickly know the function of the fourth use case when inquiring or using the fourth use case; the identity of the function used by the fourth example for testing may be used to indicate that the fourth example is used for testing; the identifier of the application to which the fourth example belongs is used to indicate the application used by the fourth example for testing.
Generally, different testers have different test permissions for an application, for example, some testers only allow testing of antivirus functions in the application, and some testers only allow testing of garbage cleaning functions in the application. Therefore, when a certain case is generated, the tester allowed to query the case can be determined according to different authorities of the tester and the function to which the case belongs.
In the embodiment of the invention, a tester can inquire the set use cases in the target equipment. The target device can acquire the authority identifier of the tester, determine a case (namely, a fourth case) which is allowed to be queried by the tester according to the authority identifier, then the target device can acquire case information of the fourth case, send the case information of the fourth case to the user terminal, and the user terminal can display the case information of the fourth case.
For example, referring to fig. 7, fig. 7 is a list of use cases that a target device displays and that a tester allows to query currently, where an ID represents an identifier of each use case, a product represents an identifier of an application program that the use case is used for testing, and a module represents an identifier of a function that the use case is used for testing.
It can be understood that, when a use case is generated, a tester can determine the test authority of each other tester according to the function for testing of the use case and the application program for testing of the use case, and add an identifier of a tester allowed to query the use case in use case information of the use case.
Optionally, the target device may further provide the test result to the tester, and after S203, the method may further include the following steps:
step one, acquiring a display interface of a target terminal when a target application program executes preset operation in a target use case.
And step two, sending the display interface to the user terminal so that the user terminal can display the display interface.
Wherein the preset operation may include at least one of: a click operation, a slide operation, and a drag operation, and the click operation may include a short click operation and a long click operation.
Generally, after a preset operation is executed in a target application program, a display interface of a target terminal is changed, so that a target device can obtain the display interface of the target terminal when the preset operation is executed in a target application program in a target case, then the target device can send the obtained display interface to a user terminal, and the user terminal can display the display interface for a tester to browse.
In addition, the tester can also perform UI test in the terminal provided by the tester.
Optionally, the target terminal may be a terminal in a remote live machine platform, or the target terminal may also be a terminal connected locally.
Wherein, the terminal in the remote live machine platform is also the mobile phone connected with open-stf in fig. 1.
In the embodiment of the invention, if the terminal provided in the current remote real machine platform does not have a terminal required by a tester, the tester sends the target application program and the target case to the terminal directly connected with the target equipment (namely, the terminal connected locally) through the target equipment, so that the defect of insufficient terminal models in the remote real machine platform can be overcome.
Optionally, the method may further implement that a tester queries historical test information, and the method may further include the following steps:
step one, receiving a test history inquiry instruction.
And step two, sending result information of the use case executed within a preset time length before the current time to the user terminal so that the user terminal can display the result information.
Wherein the result information may include at least one of: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case may be execution success, execution failure, or execution exception.
The identifier of the terminal executing the use case may indicate that the terminal executing the use case is a terminal in a remote live machine platform, or indicate that the terminal executing the use case is a locally connected terminal. The execution result is an execution failure, which may indicate that a use case is faulty in the execution process, and the execution result is an execution exception, which may indicate that the use case cannot be executed due to the own program exception of the target device.
The UI testing method provided by the embodiment of the invention can receive a modification instruction which is specific to a first case and carries an identifier of a first operation to be modified, modify the first case according to the modification instruction to obtain a modified first case, and when a testing instruction for testing a target case of a target application program is received, the target application program and the target case are sent to a target terminal so that the target terminal can execute the target case on the target application program. Therefore, when a tester needs to modify the first case, the first case is modified only according to the identifier of the first operation, namely, the first operation needing to be modified is modified only, the whole case does not need to be recorded again, and the test efficiency of the UI can be improved.
In addition, based on the UI test method, a tester can generate and modify a use case through the target equipment without a code foundation and an automatic frame foundation, the technical threshold is low, and the maintenance cost after the use case is generated is low. The technical personnel can update the interface of the testing function which can be provided by the target equipment, thereby meeting different requirements of the testing personnel.
Corresponding to the embodiment of the method in fig. 2, referring to fig. 8, fig. 8 is a UI testing apparatus provided in an embodiment of the present invention, where the apparatus includes:
a receiving module 801, configured to receive a modification instruction for a first example, where the modification instruction carries an identifier of a first operation to be modified;
a modification module 802, configured to modify the first case according to the modification instruction, to obtain a modified first case;
a sending module 803, configured to, when a test instruction for performing a target case test on a target application program is received, where the test instruction carries an identifier of a target terminal, send the target application program and the target case to the target terminal, so that the target terminal executes the target case on the target application program, where the target case includes a modified first case.
Optionally, the modification instruction further carries a modified target operation parameter;
the modification module 802 is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into the target operation parameter.
Optionally, the modification instruction further carries a modified target operation parameter and an identifier of an execution sequence of the first operation in the first use case;
the modifying module 802 is specifically configured to determine an operation corresponding to the identifier of the first operation;
and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
Optionally, the modifying module 802 is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
Optionally, the apparatus further comprises:
the case adding module is used for receiving a case adding instruction, wherein the case adding instruction carries a second case and an identifier of an execution sequence of the second case in the target case;
and adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
Optionally, the apparatus further comprises:
the operation query module is used for receiving a query operation instruction, wherein the query operation instruction carries an identifier of a third use case to be queried;
and sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to a user terminal so that the user terminal displays each operation and the operation parameters of each operation.
Optionally, the apparatus further comprises:
the system comprises a use case query module, a use case query module and a case query module, wherein the use case query module is used for receiving a query use case instruction input by a user, and the query use case instruction carries an authority identifier of the user;
determining a fourth use case allowing the user to inquire according to the authority identifier;
sending the use case information of the fourth use case to a user terminal so that the user terminal can display the use case information of the fourth use case, wherein the use case information comprises at least one of the following: the name of the fourth use case, the description of the fourth use case, the identifier of the function of the fourth use case for testing, and the identifier of the application program to which the fourth use case belongs.
Optionally, the apparatus further comprises:
a processing module, configured to obtain a display interface of the target terminal when the target application executes preset operations in the target use case, where the preset operations include at least one of: click operation, slide operation and drag operation;
and sending the display interface to a user terminal so that the user terminal displays the display interface.
Optionally, the target terminal is a terminal in a remote live machine platform or a terminal connected locally.
Optionally, the apparatus further comprises:
the test history query module is used for receiving a test history query instruction;
sending result information of a use case executed within a preset time length before the current time to a user terminal so as to enable the user terminal to display the result information, wherein the result information comprises at least one of the following: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case is execution success, execution failure or execution exception.
The UI testing device provided by the embodiment of the invention can receive a modification instruction which is specific to a first case and carries an identifier of a first operation to be modified, the first case is modified according to the modification instruction to obtain a modified first case, and when a testing instruction for testing a target case of a target application program is received, the target application program and the target case are sent to a target terminal so that the target terminal can execute the target case on the target application program. Therefore, when a tester needs to modify the first case, the first case is modified only according to the identifier of the first operation, namely, the first operation needing to be modified is modified only, the whole case does not need to be recorded again, and the test efficiency of the UI can be improved.
Referring to fig. 9, fig. 9 is a block diagram of an electronic device according to an embodiment of the present invention, including a memory 901 and a processor 902, wherein,
a memory 901 for storing a computer program;
the processor 902, when executing the program stored in the memory 901, implements the following steps:
receiving a modification instruction aiming at a first case, wherein the modification instruction carries an identifier of a first operation to be modified;
modifying the first case according to the modification instruction to obtain a modified first case;
when a test instruction for carrying out target case test on a target application program is received, the test instruction carries an identification of a target terminal, and the target application program and the target case are sent to the target terminal so that the target terminal can execute the target case on the target application program, wherein the target case comprises a modified first case.
For specific implementation and related explanation of each step of the method, reference may be made to the foregoing method embodiment, which is not described herein again.
The electronic device may be provided with a communication interface for realizing communication between the electronic device and another device.
The processor, the communication interface, and the memory are configured to communicate with each other via a communication bus, where the communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
The embodiment of the invention also provides a computer-readable storage medium, wherein the computer-readable storage medium is stored with instructions, and when the computer-readable storage medium runs on a computer, the computer is enabled to execute the UI testing method provided by the embodiment of the invention.
Specifically, the UI test method includes:
receiving a modification instruction aiming at a first case, wherein the modification instruction carries an identifier of a first operation to be modified;
modifying the first case according to the modification instruction to obtain a modified first case;
when a test instruction for carrying out target case test on a target application program is received, the test instruction carries an identification of a target terminal, and the target application program and the target case are sent to the target terminal so that the target terminal can execute the target case on the target application program, wherein the target case comprises a modified first case.
It should be noted that other implementation manners of the UI test method are the same as those of the foregoing method embodiment, and are not described herein again.
Embodiments of the present invention further provide a computer program product including instructions, which, when running on a computer, causes the computer to execute the UI testing method provided by the embodiments of the present invention.
Specifically, the UI test method includes:
receiving a modification instruction aiming at a first case, wherein the modification instruction carries an identifier of a first operation to be modified;
modifying the first case according to the modification instruction to obtain a modified first case;
when a test instruction for carrying out target case test on a target application program is received, the test instruction carries an identification of a target terminal, and the target application program and the target case are sent to the target terminal so that the target terminal can execute the target case on the target application program, wherein the target case comprises a modified first case.
It should be noted that other implementation manners of the UI test method are the same as those of the foregoing method embodiment, and are not described herein again.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described above in accordance with the embodiments of the invention may be generated, in whole or in part, when the computer program instructions described above are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, the electronic device, the computer-readable storage medium, and the computer program product embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (20)
1. A User Interface (UI) testing method is characterized by comprising the following steps:
receiving a modification instruction aiming at a first case, wherein the modification instruction carries an identifier of a first operation to be modified;
modifying the first case according to the modification instruction to obtain a modified first case;
when a test instruction for carrying out target case test on a target application program is received, the test instruction carries an identification of a target terminal, and the target application program and the target case are sent to the target terminal so that the target terminal can execute the target case on the target application program, wherein the target case comprises a modified first case;
the modification instruction also carries modified target operation parameters;
the modifying the first case according to the modifying instruction comprises:
determining an operation corresponding to the identifier of the first operation in the first use case;
and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into the target operation parameter.
2. The method according to claim 1, wherein the modification instruction further carries an identifier of an execution order of the first operation in the first use case;
the modifying the first case according to the modifying instruction comprises:
determining an operation corresponding to the identifier of the first operation;
and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
3. The method of claim 1, wherein modifying the first instance according to the modification instruction comprises:
determining an operation corresponding to the identifier of the first operation in the first use case;
and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
4. The method of claim 1, wherein prior to said sending the target application and the target use case to the target terminal, the method further comprises:
receiving a case adding instruction, wherein the case adding instruction carries a second case and an identifier of an execution sequence of the second case in the target case;
and adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
5. The method of claim 1, further comprising:
receiving a query operation instruction, wherein the query operation instruction carries an identifier of a third use case to be queried;
and sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to a user terminal so that the user terminal displays each operation and the operation parameters of each operation.
6. The method of claim 1, further comprising:
receiving a query case instruction input by a user, wherein the query case instruction carries an authority identifier of the user;
determining a fourth use case allowing the user to inquire according to the authority identifier;
sending the use case information of the fourth use case to a user terminal so that the user terminal can display the use case information of the fourth use case, wherein the use case information comprises at least one of the following: the name of the fourth use case, the description of the fourth use case, the identifier of the function of the fourth use case for testing, and the identifier of the application program to which the fourth use case belongs.
7. The method of claim 1, wherein after the sending the target application and the target use case to the target terminal, the method further comprises:
acquiring a display interface of the target terminal when the target application program executes preset operation in the target use case, wherein the preset operation comprises at least one of the following operations: click operation, slide operation and drag operation;
and sending the display interface to a user terminal so that the user terminal displays the display interface.
8. The method of claim 1, wherein the target terminal is a terminal in a remote live platform or a locally connected terminal.
9. The method of claim 1, further comprising:
receiving a test history query instruction;
sending result information of a use case executed within a preset time length before the current time to a user terminal so as to enable the user terminal to display the result information, wherein the result information comprises at least one of the following: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case is execution success, execution failure or execution exception.
10. A user interface, UI, testing apparatus, the apparatus comprising:
the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a modification instruction aiming at a first case, and the modification instruction carries an identifier of a first operation to be modified;
the modification module is used for modifying the first case according to the modification instruction to obtain a modified first case;
the sending module is used for sending the target application program and the target case to the target terminal so that the target case is executed by the target application program by the target terminal when a test instruction for carrying out a target case test on the target application program is received, wherein the test instruction carries an identifier of the target terminal, and the target case comprises a modified first case;
the modification instruction also carries modified target operation parameters;
the modification module is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and modifying the determined operation parameter of the operation corresponding to the identifier of the first operation into the target operation parameter.
11. The apparatus according to claim 10, wherein the modification instruction further carries an identifier of an execution order of the first operation in the first use case;
the modification module is specifically configured to determine an operation corresponding to the identifier of the first operation;
and adding the first operation into the first use case according to the operation corresponding to the identifier of the first operation, the target operation parameter and the identifier of the execution sequence of the first operation in the first use case.
12. The apparatus according to claim 10, wherein the modification module is specifically configured to determine, in the first use case, an operation corresponding to the identifier of the first operation;
and deleting the determined operation corresponding to the identifier of the first operation from the first use case.
13. The apparatus of claim 10, further comprising:
the case adding module is used for receiving a case adding instruction, wherein the case adding instruction carries a second case and an identifier of an execution sequence of the second case in the target case;
and adding the second use case into the target use case according to the second use case and the identification of the execution sequence of the second use case in the target use case.
14. The apparatus of claim 10, further comprising:
the operation query module is used for receiving a query operation instruction, wherein the query operation instruction carries an identifier of a third use case to be queried;
and sending each operation contained in the use case corresponding to the identifier of the third use case and the operation parameters of each operation to a user terminal so that the user terminal displays each operation and the operation parameters of each operation.
15. The apparatus of claim 10, further comprising:
the system comprises a use case query module, a use case query module and a case query module, wherein the use case query module is used for receiving a query use case instruction input by a user, and the query use case instruction carries an authority identifier of the user;
determining a fourth use case allowing the user to inquire according to the authority identifier;
sending the use case information of the fourth use case to a user terminal so that the user terminal can display the use case information of the fourth use case, wherein the use case information comprises at least one of the following: the name of the fourth use case, the description of the fourth use case, the identifier of the function of the fourth use case for testing, and the identifier of the application program to which the fourth use case belongs.
16. The apparatus of claim 10, further comprising:
a processing module, configured to obtain a display interface of the target terminal when the target application executes preset operations in the target use case, where the preset operations include at least one of: click operation, slide operation and drag operation;
and sending the display interface to a user terminal so that the user terminal displays the display interface.
17. The apparatus of claim 10, wherein the target terminal is a terminal in a remote live platform or a locally connected terminal.
18. The apparatus of claim 10, further comprising:
the test history query module is used for receiving a test history query instruction;
sending result information of a use case executed within a preset time length before the current time to a user terminal so as to enable the user terminal to display the result information, wherein the result information comprises at least one of the following: the method comprises the steps of identifying a use case, starting execution time of the use case, finishing execution time of the use case, execution result of the use case and identification of a terminal for executing the use case; the execution result of the use case is execution success, execution failure or execution exception.
19. An electronic device comprising a memory and a processor, wherein,
the memory is used for storing a computer program;
the processor, when executing the program stored in the memory, implementing the method steps of any of claims 1-9.
20. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811574053.9A CN109684214B (en) | 2018-12-21 | 2018-12-21 | UI (user interface) testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811574053.9A CN109684214B (en) | 2018-12-21 | 2018-12-21 | UI (user interface) testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109684214A CN109684214A (en) | 2019-04-26 |
| CN109684214B true CN109684214B (en) | 2022-02-25 |
Family
ID=66188760
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811574053.9A Active CN109684214B (en) | 2018-12-21 | 2018-12-21 | UI (user interface) testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109684214B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012084131A (en) * | 2010-10-06 | 2012-04-26 | Internatl Business Mach Corp <Ibm> | Asynchronous code test method, computer program product, computer system, and process (asynchronous code test in integrated development environment (ide)) |
| CN103106138A (en) * | 2011-11-15 | 2013-05-15 | 阿里巴巴集团控股有限公司 | Method and device for synchronization of test case and test script |
| CN103970650A (en) * | 2014-04-09 | 2014-08-06 | 广州杰赛科技股份有限公司 | Distributed testing method and device |
| CN107844409A (en) * | 2016-09-18 | 2018-03-27 | 平安科技（深圳）有限公司 | Test example executing method and device |
| CN108255700A (en) * | 2017-03-27 | 2018-07-06 | 平安科技（深圳）有限公司 | Test result generation method and device |
-
2018
- 2018-12-21 CN CN201811574053.9A patent/CN109684214B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012084131A (en) * | 2010-10-06 | 2012-04-26 | Internatl Business Mach Corp <Ibm> | Asynchronous code test method, computer program product, computer system, and process (asynchronous code test in integrated development environment (ide)) |
| CN103106138A (en) * | 2011-11-15 | 2013-05-15 | 阿里巴巴集团控股有限公司 | Method and device for synchronization of test case and test script |
| CN103970650A (en) * | 2014-04-09 | 2014-08-06 | 广州杰赛科技股份有限公司 | Distributed testing method and device |
| CN107844409A (en) * | 2016-09-18 | 2018-03-27 | 平安科技（深圳）有限公司 | Test example executing method and device |
| CN108255700A (en) * | 2017-03-27 | 2018-07-06 | 平安科技（深圳）有限公司 | Test result generation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109684214A (en) | 2019-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959059B (en) | Test method and test platform | |
| CN110209386B (en) | Method for setting buried point of data, method and device for acquiring buried point data | |
| CN110851308A (en) | Test method, test device, electronic equipment and storage medium | |
| CN111488088B (en) | Equipment state identification method and device and intelligent terminal | |
| CN110716853A (en) | Test script recording method, application program testing method and related device | |
| CN111338931B (en) | Buried point testing method, device, equipment and storage medium | |
| CN113127323A (en) | Test method, test device, terminal equipment and storage medium | |
| CN111258680B (en) | Resource loading method and device, storage medium and electronic device | |
| WO2018121582A1 (en) | Script generation method and device | |
| CN106126424A (en) | A kind of visual automated testing method of script, device and mobile terminal | |
| CN108712478A (en) | A kind of method and apparatus for sharing boarding application | |
| CN113626102A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112882933A (en) | Script recording method, device, equipment and storage medium | |
| CN112306471A (en) | Task scheduling method and device | |
| CN109753437B (en) | Test program generation method and device, storage medium and electronic equipment | |
| CN111694550A (en) | Page display control method, device and system | |
| CN111798161A (en) | Flow configuration method, device, equipment and storage medium | |
| CN111522749A (en) | Page testing method and device, readable storage medium and electronic equipment | |
| CN107102937B (en) | User interface testing method and device | |
| CN108228611B (en) | Document information copying method and device | |
| CN109684214B (en) | UI (user interface) testing method and device | |
| CN109976828B (en) | Method and device for configuring file | |
| CN109710128B (en) | Shortcut key display method and device | |
| US10169216B2 (en) | Simulating sensors | |
| CN111143724A (en) | Data processing method, device, equipment and medium |
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 |