CN107102949B - Application program offline testing method and tool - Google Patents
Application program offline testing method and tool Download PDFInfo
- Publication number
- CN107102949B CN107102949B CN201710526720.5A CN201710526720A CN107102949B CN 107102949 B CN107102949 B CN 107102949B CN 201710526720 A CN201710526720 A CN 201710526720A CN 107102949 B CN107102949 B CN 107102949B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- application program
- module
- tool
- 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/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The embodiment of the application provides an application program offline testing method and a tool. Wherein, the test tool includes: the engine module is used for displaying a test case management interface to a user through the Android device and responding to touch operation aiming at the test case management interface to obtain a test case identifier and corresponding test parameters; the daemon module is used for determining a corresponding test case according to the test case identifier and the test parameters and sending a test command to the test module; and the test module is used for executing the test case according to the test command so as to test the application program to be tested. The test tool provided by the embodiment of the application realizes offline automatic test on the application program on the equipment installed by the application program.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an application offline testing method and tool.
Background
UIAutomator (automated user interface testing tool) is a user interface testing tool commonly used by Android, and has the unique advantages of rich and easy-to-use interfaces, capability of cross-process and the like.
Generally, when the UI test is performed on an application program by using the UIAutomator, first, the application program to be tested needs to be installed in an android (android) device, a tester determines an object included in the application program to be tested, and then creates a corresponding test case in the UIAutomator for each object. The test case can simulate the operation of the user aiming at the application program, and the test case code is compiled into a Jar package. And copying the Jar package to Android equipment provided with the application program to be tested. After the copying is finished, the Android device provided with the application to be tested and a computer where the UIAutomator is located are connected, and the instruction for running the test case is executed in a command window of the UIAutomator. And after receiving the operation instruction, the test case operates in the Android equipment provided with the application to be tested and outputs a corresponding operation result.
However, the test mode depends on the connection of the Android device and the computer where the uiautomation is located through the data line, and certain limitation is caused to the test environment.
Disclosure of Invention
The embodiment of the application provides an application program offline testing method and an application program offline testing tool, which are used for getting rid of dependence on a computer end when an application program is tested, and realizing offline automatic testing of the application program on equipment installed by the application program.
The embodiment of the application provides an application program offline testing method, which is executed by a testing tool installed on the same Android device as an application program to be tested, and the method comprises the following steps:
displaying a test case management interface to a user through the Android device;
responding to the touch operation aiming at the test case management interface, and acquiring a test case identifier and a corresponding test parameter;
and executing the corresponding test case according to the test case identification and the test parameters so as to test the application program to be tested.
Further optionally, before the test tool performs the method, the method further includes: the testing tool applies for system permission to an operating system of the Android device based on a system signature of an internal fixed code module, so that the testing tool runs on the Android device through a root account.
Further optionally, the applying, by the testing tool, a system permission to an operating system of the Android device based on a system signature of the internal fixed code module, so that the testing tool runs on the Android device with a root account, includes: the testing tool sends an installation request to an operating system of the Android device to trigger the operating system to acquire a system signature from the internal fixed code module and to perform signature verification on the system signature; and when the system signature passes signature verification, the test tool obtains a root account authorized by the operating system of the Android device.
Further optionally, executing a corresponding test case according to the test case identifier and the test parameter to test the application program to be tested, including: executing a corresponding test case according to the test case identification and the test parameters so as to simulate a user to operate the application program to be tested; and displaying the process of the test case simulation user for operating the application program to be tested on the Android equipment.
Further optionally, after executing the corresponding test case to test the application program to be tested according to the test case identifier and the test parameter, the method further includes: responding to the touch operation of a test result display control on the test case management interface, and displaying the execution result of the test case; or responding to the touch operation of the running log display control on the test case management interface, and displaying the log record generated by executing the test case; or responding to the touch operation of an analysis control on the test case management interface, analyzing the execution result of the test case and displaying the analysis result; and/or synchronizing the execution result of the test case and/or the log record generated by executing the test case and/or the analysis result of the execution result of the test case to a computer end in response to the operation of a remote communication control on the test case management interface.
The embodiment of the present application further provides an application offline test tool, the test tool and an application to be tested are installed on the same Android device, and the test tool includes:
the engine module is used for displaying a test case management interface to a user through the Android device and responding to touch operation aiming at the test case management interface to obtain a test case identifier and corresponding test parameters;
the daemon module is used for determining a corresponding test case according to the test case identifier and the test parameters and sending a test command to the test module;
and the test module is used for executing the test case according to the test command so as to test the application program to be tested.
Further optionally, the daemon module is further configured to: before the testing tool executes the method, applying system permission to an operating system of the Android device so that the testing tool runs on the Android device through a root account.
Further optionally, the test module is specifically configured to: executing a corresponding test case according to the test case identification and the test parameters so as to simulate a user to operate the application program to be tested; the daemon module is further configured to: and displaying the process of the test case simulation user for operating the application program to be tested on the Android equipment.
Further optionally, the daemon module is further configured to: acquiring an execution result of the test case and/or a log record generated by executing the test case; and sending the execution result of the test case and/or the log record generated by executing the test case to the engine module.
Further optionally, the engine module is specifically configured to: responding to touch operation of a test result display control on the test case management interface, and displaying the received execution result of the test case; or, responding to the touch operation of the running log display control on the test case management interface, and displaying the received log record generated by executing the test case; or responding to the touch operation of an analysis control on the test case management interface, analyzing the execution result of the test case and displaying the analysis result; and/or synchronizing the execution result of the test case and/or the log record generated by executing the test case and/or the analysis result of the execution result of the test case to a computer end in response to the operation of a remote communication control on the test case management interface.
According to the application program offline testing method and the application program offline testing tool, the testing tool and the application program to be tested are installed on the same Android device, and then the testing tool can show a testing case management interface to a user on the Android device. And when the touch operation of the user on the test case management interface is acquired, the test case identification and the corresponding test parameters are acquired, and the corresponding test case is executed to test the application program to be tested based on the test case identification and the test parameters. According to the technical scheme, when the application program is tested, dependence on a computer end is eliminated, and offline automatic testing of the application program on equipment installed by the application program is achieved.
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, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of an application offline testing method according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of an application offline testing method according to an embodiment of the present disclosure;
fig. 3 is a block diagram of an application offline testing tool according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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 some, but not all, embodiments of the present invention. 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.
Fig. 1 is a schematic flowchart of an application offline testing method provided in an embodiment of the present application, and with reference to fig. 1, the method includes:
And 103, executing a corresponding test case according to the test case identification and the test parameters to test the application program to be tested.
Aiming at the step 101, the Android device comprises a mobile phone or a tablet computer with an Android system. And an application program to be tested and a testing tool are installed on the Android device.
The test case management interface is one or more operable interfaces displayed to a user after the test tool is installed on the Android device. At least one control can be arranged on the test case management interface. The user can manage the test case and initiate other operations such as a test command and the like through the at least one control.
For step 102, the touch operation on the test case management interface may be a user-initiated touch operation on a control on the test interface, where the touch operation includes, but is not limited to, a single click, a continuous click, a long press, or a hover.
When the touch operation aiming at the test case management interface is detected, the test case identification and the corresponding test parameters can be determined according to the object control of the touch operation. The test case identifier may be an identification number capable of uniquely specifying the test case or a name of the test case. The test parameters may include at least one of test objects of the test cases, execution times of the test cases, and time intervals between two adjacent tests.
For step 103, after the test case identifier is determined, the test case corresponding to the test case identifier is determined, and the application program to be tested can be tested according to the test object contained in the test parameters, the execution times of the test case, and the time interval between two adjacent tests.
In the offline testing method for the application program, the testing tool and the application program to be tested are installed on the same Android device, and then the testing tool can show the test case management interface to the user on the Android device. And when the touch operation of the user on the test case management interface is acquired, the test case identification and the corresponding test parameters are acquired, and the corresponding test case is executed to test the application program to be tested based on the test case identification and the test parameters. According to the technical scheme, when the application program is tested, dependence on a computer end is eliminated, and offline automatic testing of the application program on equipment installed by the application program is achieved.
It should be noted that, in the technical solution of the embodiment of the present application, the test tool needs to run the test case on the Android device to simulate the operation of the user on the application program to be tested. Therefore, the authority of the test tool in the operating system of the Android device needs to be raised to the highest level, namely, the test tool runs in the operating system of the Android device in a root account. The right of the test tool can be lifted by performing system signature on an Android package (apk) of the test tool. In an alternative embodiment, the system signature may be applied to the apk of the test tool after modification and debugging of the test tool.
However, in the process of actual testing, repeated modification and debugging of the test tool are required as the test requirements change and the test cases are upgraded and maintained. Thus, in an alternative embodiment, the apk of the test tool may be split into multiple modules and a fixed code module may be selected from the multiple modules specifically for system signature. Furthermore, the testing tool can apply for system permission from an operating system of the Android device based on the system signature of the internal fixed code module, so that the testing tool runs on the Android device through a root account.
The fixed code module can be a module which does not need to change codes when the test tool is modified and debugged, so that the system signature does not need to be carried out on the apk of the test tool again after the test tool is modified and debugged, and the upgrading process of the test tool is simplified. The following section will further describe the technical solution of the embodiment of the present application with reference to fig. 2.
Fig. 2 is a schematic flowchart of another method for offline testing an application according to an embodiment of the present application, and with reference to fig. 2, the method includes:
And step 203, when the system signature passes the signature verification, the operating system of the Android device opens the system permission to the test tool so that the test tool can operate as a root account.
And step 204, the test tool displays a test case management interface to a user through the Android device.
And step 206, the test tool executes the corresponding test case according to the test case identification and the test parameters to test the application program to be tested, and displays the test case to the user on the Android device to simulate the operation of the user on the application program to be tested.
For step 201, generally, when receiving an installation request of a test tool, an operating system of an Android device scans in an apk of the test tool to obtain a system signature file of the test tool. In this embodiment, the fixed code module in the testing tool includes the system signature, so that the operating system of the Android device can obtain the system signature from the internal fixed code module of the testing tool.
In step 202, after the system signature of the test tool is determined, the operating system of the Android device further verifies the system signature to determine whether the system authority of the test tool can be granted. Of course, in addition to verifying the system signature, other non-system level signatures contained by the apk may also be verified. The signature verification process is a mature prior art and is not described in detail herein.
For step 203, when the operating system of the Android device determines that the system signature in the fixed code module passes the signature verification, the system permission may be opened to the test tool so that the test tool operates as a root account. At this time, the test tool can obtain the highest authority of the operating system of the Android device, and can operate all application programs installed on the Android device, including the application program to be tested.
Aiming at step 204, after the installation and the starting are completed, the test tool displays a test case management interface to a user through the Android device.
The test case management interface can be provided with at least one control, and a user can manage the test case and perform other operations through the at least one control. For example, optionally, the test case management interface may be provided with: the system comprises a test case selection control, a test parameter setting control, a test starting control, a test result display control, a running log display control, a remote communication control and the like. Of course, in the embodiment of the present application, the control on the test case management interface includes, but is not limited to, the control described above.
The control can be a button type control, a pull-down menu control, a text type control, etc. according to different functions. For example, the test case selection control may be a button type control, and each button corresponds to a test case identifier. The test case selection control can also be a drop-down menu control, and a plurality of test case identifications can be displayed in the drop-down menu for the user to select.
The test case management interface can be one interface or a plurality of interfaces. When the test case management interface includes multiple interfaces, the multiple different interfaces may be exposed at different stages of testing. For example, before the test is started, a test case management interface is displayed, and a test case selection control, a test parameter setting control and a starting test control can be displayed on the test case management interface. For another example, another test case management interface is displayed after the test is finished, and a test result display control, a running log display control, a remote communication control, and the like can be displayed on the test case management interface.
For step 205, when the touch operation for the test case management interface is detected, the object control and the operation content of the touch operation may be determined according to the touch position of the touch operation and the operation sequence of the touch operation for different positions on the test case management interface. The operation content may be a pull-down and selection operation for a pull-down menu control, or an input operation for a text control.
Optionally, in this embodiment, the test control has a corresponding relationship with the test case identifier, and the test case identifier may be determined after determining the object control and the operation content of the touch operation. Optionally, the test parameters may be obtained by an input operation for the text-based control.
For step 206, after the test case identifier and the test parameters are determined, the test case indicated by the test case identifier may be run through the operating system of the Android device. In the execution process of the test case, UI test operations such as clicking, sliding or inputting the application program to be tested by simulating user operation of the test case can be displayed on the Android device.
In the embodiment, the test tool performs system signature on the internal fixed code module to realize right-lifting, so that after the test tool is modified and debugged, system repeated signature on apk of the test tool is not required, and the upgrading process of the test tool is simplified.
It should be noted that, in the above embodiments of the present application, after the corresponding test case is executed to test the application program to be tested according to the test case identifier and the test parameter, if the touch operation directed to the test result display control on the test case management interface is detected, the touch operation is responded to, and the execution result of the test case is displayed. And if the touch operation on the running log display control on the test case management interface is detected, responding to the touch operation and displaying the log record generated by executing the test case. And if the touch operation aiming at the analysis control on the test case management interface is detected, responding to the touch operation, analyzing the execution result of the test case and displaying the analysis result. And if the operation aiming at the remote communication control on the test case management interface is detected, responding to the operation, and synchronizing the execution result of the test case and/or the log record generated by the execution of the test case and/or the analysis result of the execution result of the test case to the computer end.
Fig. 3 is a block diagram of an application offline testing tool according to an embodiment of the present disclosure. The test tool and the application program to be tested are installed on the same Android device, and the method comprises the following steps: an engine module 301, a daemon module 302, and a test module 303.
The engine module 301 is configured to display a test case management interface to a user through an Android device, and respond to a touch operation for the test case management interface to obtain a test case identifier and corresponding test parameters. After obtaining the test case identifier and the corresponding test parameter, the engine module 301 may send the test case identifier and the corresponding test parameter to the daemon module 302 through the intent mechanism of the Android.
The daemon module 302 is configured to determine a corresponding test case according to the received test case identifier and the test parameter, and send a test command to the test module 303. Optionally, the daemon module 302 may send a test command to the test module 303 through getcommit (). exec function. The test command carries a path of the test case, a test case identifier and a test parameter.
In the test module 303, at least one test case is stored, and a library of uiautomators is introduced, so as to execute a corresponding test case according to a received test command sent by the daemon module 302, so as to test an application program to be tested.
Optionally, the test module 303 may also be directly connected to the computer terminal through an ADB (Android Debug Bridge) to receive a test command sent by the computer terminal to execute the test case.
Further optionally, before the test tool tests the application program to be tested, the daemon module 302 is used as a fixed code module of the test tool, and is used for performing system signature, and before the test tool executes the test method corresponding to fig. 1 to fig. 2, applies for a system permission to an operating system of the Android device, so that the test tool runs on the Android device with a root account.
Further optionally, the daemon module 302 is specifically configured to: when the testing tool sends an installation request to an operating system of the Android device, the operating system is triggered to acquire a system signature from the internal fixed code module and perform signature verification on the system signature; and when the system signature passes signature verification, the test tool obtains a root account authorized by the operating system of the Android device.
Further optionally, the test module 303 is specifically configured to: executing a corresponding test case according to the test case identification and the test parameters so as to simulate a user to operate the application program to be tested; correspondingly, when the test module 303 executes the corresponding test case, the daemon module 302 is further configured to: and displaying the process of the test case simulating the operation of the application program to be tested by the user on the Android device.
Further optionally, after the test module 303 executes the corresponding test case, the daemon module 302 is further configured to: collecting the execution result of the test case and/or the log record generated by executing the test case, and sending the execution result of the test case and/or the log record generated by executing the test case to the engine module 301.
Further optionally, the engine module 301 is specifically configured to: responding to the touch operation of a test result display control on the test case management interface, and displaying the execution result of the received test case; and/or displaying the received log record generated by executing the test case in response to the touch operation of the running log display control on the test case management interface; and/or responding to the touch operation of the analysis control on the test case management interface, analyzing the execution result of the test case and displaying the analysis result.
In addition, optionally, as shown in fig. 3, the engine module 301 may also communicate with the computer side through a specific Socket. Furthermore, the engine module 301 may synchronize the execution result of the test case and/or the log record generated by executing the test case and/or the result of analyzing the execution result of the test case to the computer end in response to the operation directed to the remote communication control on the test case management interface.
According to the application program offline testing tool provided by the embodiment, the engine module, the daemon module and the testing module are packaged in one apk, so that the testing tool and an application program to be tested can be installed on the same Android device, offline testing of the application program to be tested is achieved, and dependence on a computer end is eliminated.
In addition, it should be noted that, in the test tool provided in the embodiment of the present application, a framework with a plurality of separated modules is adopted for design, and a daemon module only responsible for data transmission is used as a system signature object, so that a step that the test tool needs to be re-signed every time the test tool is upgraded and maintained is avoided, a test flow is simplified, and test efficiency is improved.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (6)
1. An application program offline testing method is characterized by being executed by a testing tool installed on the same Android device as an application program to be tested, and the method comprises the following steps:
separating apk of the test tool into a plurality of modules, and selecting a fixed code module from the plurality of modules to be specially used for system signature;
the testing tool applies for system permission to an operating system of the Android device based on a system signature of an internal fixed code module so that the testing tool runs on the Android device through a root account;
displaying a test case management interface to a user through the Android device;
responding to the touch operation aiming at the test case management interface, and acquiring a test case identifier and a corresponding test parameter;
executing a corresponding test case according to the test case identification and the test parameters to test the application program to be tested;
responding to the touch operation of a test result display control on the test case management interface, and displaying the execution result of the test case;
responding to touch operation of an analysis control on the test case management interface, analyzing an execution result of the test case and displaying the analysis result; and the number of the first and second groups,
and responding to the operation of the remote communication control on the test case management interface, and synchronizing the execution result of the test case and the analysis result of the execution result of the test case to a computer terminal.
2. The method of claim 1, wherein the test tool applies for system permission from an operating system of the Android device based on a system signature of an internal fixed code module so that the test tool runs on the Android device in a root account, and the method comprises the following steps:
the testing tool sends an installation request to an operating system of the Android device to trigger the operating system to acquire a system signature from the internal fixed code module and to perform signature verification on the system signature;
and when the system signature passes signature verification, the test tool obtains a root account authorized by the operating system of the Android device.
3. The method according to claim 1, wherein executing the corresponding test case to test the application program to be tested according to the test case identifier and the test parameter comprises:
executing a corresponding test case according to the test case identification and the test parameters so as to simulate a user to operate the application program to be tested;
and displaying the process of the test case simulation user for operating the application program to be tested on the Android equipment.
4. The utility model provides an application off-line testing tool, its characterized in that, the testing tool is installed on same Android equipment with the application that awaits measuring, the testing tool includes:
the engine module is used for displaying a test case management interface to a user through the Android device and responding to touch operation aiming at the test case management interface to obtain a test case identifier and corresponding test parameters;
the system comprises a daemon module, a testing tool and a control module, wherein the daemon module is used as a fixed code module of the testing tool and is used for carrying out system signature and applying system permission to an operating system of the Android equipment so as to enable the testing tool to run on the Android equipment through a root account; the test module is also used for determining a corresponding test case according to the test case identification and the test parameters and sending a test command to the test module;
the test module is used for executing the test case according to the test command so as to test the application program to be tested;
the engine module is specifically configured to:
responding to touch operation of a test result display control on the test case management interface, and displaying the received execution result of the test case;
responding to touch operation of an analysis control on the test case management interface, analyzing an execution result of the test case and displaying the analysis result; and
and responding to the operation of the remote communication control on the test case management interface, and synchronizing the execution result of the test case and the analysis result of the execution result of the test case to a computer terminal.
5. The test tool of claim 4, wherein the test module is specifically configured to: executing a corresponding test case according to the test case identification and the test parameters so as to simulate a user to operate the application program to be tested;
the daemon module is further configured to: and displaying the process of the test case simulation user for operating the application program to be tested on the Android equipment.
6. The testing tool of any of claims 4-5, wherein the daemon module is further configured to:
acquiring an execution result of the test case and/or a log record generated by executing the test case;
and sending the execution result of the test case and/or the log record generated by executing the test case to the engine module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710526720.5A CN107102949B (en) | 2017-06-30 | 2017-06-30 | Application program offline testing method and tool |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710526720.5A CN107102949B (en) | 2017-06-30 | 2017-06-30 | Application program offline testing method and tool |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107102949A CN107102949A (en) | 2017-08-29 |
| CN107102949B true CN107102949B (en) | 2020-06-09 |
Family
ID=59663848
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710526720.5A Active CN107102949B (en) | 2017-06-30 | 2017-06-30 | Application program offline testing method and tool |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107102949B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108984390B (en) * | 2018-06-04 | 2022-08-30 | 卡斯柯信号有限公司 | Universal automatic test framework for signal system off-line tool and application thereof |
| CN111370053A (en) * | 2018-12-25 | 2020-07-03 | 北京兆易创新科技股份有限公司 | eMMC test method and device |
| CN110888805A (en) * | 2019-11-11 | 2020-03-17 | 北京仁科互动网络技术有限公司 | RESTful API playback test method and system |
| CN111258898B (en) * | 2020-01-15 | 2023-03-28 | 深圳平安医疗健康科技服务有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN112597043A (en) * | 2020-12-28 | 2021-04-02 | 深圳供电局有限公司 | Software testing method and device, computer equipment and storage medium |
| CN112948259A (en) * | 2021-03-29 | 2021-06-11 | 深圳市广和通无线股份有限公司 | Application testing method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
| US8832502B2 (en) * | 2012-07-25 | 2014-09-09 | International Business Machines Corporation | Hardware verification using acceleration platform |
| CN104281518A (en) * | 2013-07-02 | 2015-01-14 | 腾讯科技（深圳）有限公司 | Terminal application test method, device, system and platform and mobile terminal |
| CN105335278A (en) * | 2014-06-16 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Testing method and device |
| CN105653438A (en) * | 2014-11-12 | 2016-06-08 | 成都鼎桥通信技术有限公司 | Method and device for cross-process automated testing of Android device |
| CN106126414A (en) * | 2016-06-14 | 2016-11-16 | 珠海格力电器股份有限公司 | Application software testing method and system |
| CN106844186A (en) * | 2015-12-03 | 2017-06-13 | 腾讯科技（深圳）有限公司 | The off line test method and terminal device of application |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070118899A1 (en) * | 2002-05-17 | 2007-05-24 | Satyam Computer Services Limited Of Mayfair Centre | System and method for automated safe reprogramming of software radios |
| CN1921384A (en) * | 2006-09-12 | 2007-02-28 | 上海交通大学 | Public key infrastructure system, local safety apparatus and operation method |
-
2017
- 2017-06-30 CN CN201710526720.5A patent/CN107102949B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8832502B2 (en) * | 2012-07-25 | 2014-09-09 | International Business Machines Corporation | Hardware verification using acceleration platform |
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
| CN104281518A (en) * | 2013-07-02 | 2015-01-14 | 腾讯科技（深圳）有限公司 | Terminal application test method, device, system and platform and mobile terminal |
| CN105335278A (en) * | 2014-06-16 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Testing method and device |
| CN105653438A (en) * | 2014-11-12 | 2016-06-08 | 成都鼎桥通信技术有限公司 | Method and device for cross-process automated testing of Android device |
| CN106844186A (en) * | 2015-12-03 | 2017-06-13 | 腾讯科技（深圳）有限公司 | The off line test method and terminal device of application |
| CN106126414A (en) * | 2016-06-14 | 2016-11-16 | 珠海格力电器股份有限公司 | Application software testing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107102949A (en) | 2017-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107102949B (en) | Application program offline testing method and tool | |
| CN108959068B (en) | Software interface testing method, device and storage medium | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CN107688530B (en) | Software testing method and device | |
| CN105094783B (en) | method and device for testing stability of android application | |
| US9521564B2 (en) | Wireless automation test apparatus and method for mobile device | |
| CN106776294B (en) | Automatic android mobile phone testing method and system | |
| CN111240973B (en) | Equipment testing method and system based on simulation and readable storage medium | |
| CN105787364B (en) | Automatic testing method, device and system for tasks | |
| CN103365770A (en) | Mobile terminal software testing system and software testing method | |
| CN110493812B (en) | Distribution network test processing method, device and system, processor and master control equipment | |
| CN110347085B (en) | Automated test system, method, vehicle, and computer-readable medium | |
| CN106201882A (en) | Automated operating system method of testing based on Jenkins and system | |
| CN103973858B (en) | The Auto-Test System of mobile terminal | |
| CN107562637B (en) | Method, device, system and storage medium for software testing | |
| CN109543417B (en) | Vulnerability mining method and device based on Qemu platform | |
| WO2020231745A1 (en) | Analyzing time-series data in an automated application testing system | |
| CN106407054B (en) | BMC automatic test system and method | |
| CN110119350A (en) | Software Development Kit test method, device and equipment and computer storage medium | |
| CN111736951A (en) | Simulation method for automatic driving, computer device, and storage medium | |
| CN114647572A (en) | Method and system for software application component testing | |
| CN111949548B (en) | Automatic unauthorized penetration testing method and storage device | |
| KR20150025106A (en) | Verification apparatus, terminal device, system, method and computer-readable medium for monitoring of application verification result | |
| CN112269697B (en) | Equipment storage performance testing method, system and related device | |
| CN211554929U (en) | Human-computer interaction interface automatic identification system based on Android OS |
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 | ||
| CB02 | Change of applicant information |
Address after: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant after: Shanghai zhihuilin Medical Technology Co.,Ltd. Address before: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant before: Shanghai Zhihui Medical Technology Co.,Ltd. Address after: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant after: Shanghai Zhihui Medical Technology Co.,Ltd. Address before: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant before: SHANGHAI MROBOT TECHNOLOGY Co.,Ltd. Address after: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant after: SHANGHAI MROBOT TECHNOLOGY Co.,Ltd. Address before: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant before: SHANGHAI MUYE ROBOT TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200514 Address after: 201400 Shanghai Fengxian District Xinyang Highway 1800 Lane 2 2340 Rooms Applicant after: SHANGHAI MUMU JUCONG ROBOT TECHNOLOGY Co.,Ltd. Address before: Room 402, Building 33 Guangshun Road, Changning District, Shanghai, 2003 Applicant before: Shanghai zhihuilin Medical Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |