CN106649107B - Automatic testing method and device for stability of android system - Google Patents
Automatic testing method and device for stability of android system Download PDFInfo
- Publication number
- CN106649107B CN106649107B CN201611129937.4A CN201611129937A CN106649107B CN 106649107 B CN106649107 B CN 106649107B CN 201611129937 A CN201611129937 A CN 201611129937A CN 106649107 B CN106649107 B CN 106649107B
- Authority
- CN
- China
- Prior art keywords
- android
- information
- files
- unit
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- 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 invention discloses an automatic android system stability testing method and device, and relates to the field of android testing. The method comprises the following steps: establishing an android test project; importing a static library; modifying a configuration file of an android test project; in a test code directory of an android test project, a JUnit test case is newly built, a performance data dotting script is implanted, current mobile terminal memory and CPU information are obtained, the obtained memory and CPU information are used as dynamic broadcast files, sent out through broadcast messages and recorded in a local file of a mobile terminal; adding configuration items supporting the checking list; executing: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files, storing the static files to the local, generating reports after the testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server; and displaying the information of the basic performance report. The invention can analyze the potential performance hazard.
Description
Technical Field
The invention relates to the field of android testing, in particular to an automatic testing method and device for android system stability.
Background
The stability test is an important test in the special line test of the mobile end product, which means that the mobile end product performs repeated and long-term operation for a long period of time (usually not less than 8 hours), and whether system resources are abnormally occupied under the pressure test is an important quality standard for the mobile end product to be released on line.
In the Android automation test, sometimes a software is required to be stress tested, and the performance of the software is checked. If the test is performed manually, the efficiency is much lower and it is boring. At this time, one command line tool Monkey in the Android system can reduce a lot of repeated and tedious work. Monkey is a stability and pressure testing tool carried by the android system. The Monkey tool looks like a Monkey with skin being adjusted, and is used in APP (APPlication) to make a click, touch, roll and jump. The Monkey test is a quick and effective means for automatic test under an Android platform, and the Monkey tool can simulate the operations of a user touching a screen, sliding a trackball, pressing keys and the like to perform pressure test on software on a simulator or mobile phone equipment, so as to detect the stability and the robustness of the software. The principle of the method is that a pseudorandom user event stream (such as key input, touch input, gesture input and the like) is sent to a system, and stress testing of an application program under development is achieved.
The Monkey tool can randomly generate events without any subjectivity and is convenient to use. However, also due to this randomness, the traditional Monkey test can only be used as a stability test tool. In the Monkey test, it is difficult to analyze the potential performance hazard due to the randomness of events.
Disclosure of Invention
The invention aims to overcome the defects of the background technology, and provides an automatic testing method and device for the stability of an android system, which can analyze potential performance hazards.
The invention provides an automatic test method for android system stability, which comprises the following steps:
s1, establishing an android test project;
s2, importing a static library;
s3, modifying the configuration file of the android test project;
s4, creating a JUnit test case in a test code directory of an android test project, implanting a performance data dotting script, acquiring current mobile terminal memory and CPU information, taking the acquired memory and CPU information as dynamic broadcast files, sending the dynamic broadcast files through broadcast messages, and recording the dynamic broadcast files in a local file of the mobile terminal;
s5, adding configuration items supporting the check list;
s6, executing: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files to the local, generating reports after testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server;
and S7, displaying the information of the basic performance report.
On the basis of the above technical solution, in step S1, an android test project is established using Java language.
On the basis of the above technical solution, step S2 further includes the following steps: when the current interface is detected to be the concerned activity, acquiring control information of the activity through communication with a view service on the mobile terminal to obtain coordinate information of the specified control; clicking on the coordinate returns to the designated interface.
On the basis of the above technical solution, the configuration items in step S5 include: specifying a percentage of touch events; a sliding event; a trackball event; a navigation event; a system key event; switching between activities; specifying a seed value for generating a random event; specifying a detailed level of the print information; ignoring the crash; ignore timeout; ignoring the security exception; and directly killing the process after an error occurs.
On the basis of the technical scheme, the graph in the basic performance report records the executed events by using nodes.
The invention also provides an automatic testing device for the stability of the android system, which comprises a project establishing unit, a static library importing unit, a configuration file modifying unit, a test case newly-built unit, a configuration unit, an execution unit and a display unit;
the project building unit is used for: establishing an android test project;
the static library importing unit is used for: importing a static library;
the configuration file modification unit is used for: modifying a configuration file of an android test project;
the test case new unit is used for: in a test code directory of an android test project, a JUnit test case is newly built, a performance data dotting script is implanted, current mobile terminal memory and CPU information are obtained, the obtained memory and CPU information are used as dynamic broadcast files, the dynamic broadcast files are sent out through broadcast messages and are recorded in local files of the mobile terminal;
the configuration unit is used for: adding configuration items supporting the checking list;
the execution unit is to: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files to the local, generating reports after testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server;
the display unit is used for: and displaying the information of the basic performance report.
On the basis of the technical scheme, the project building unit uses Java language to build android test project projects.
On the basis of the above technical solution, the static library importing unit is further configured to: when the current interface is detected to be the concerned activity, acquiring control information of the activity through communication with a view service on the mobile terminal to obtain coordinate information of the specified control; clicking on the coordinate returns to the designated interface.
On the basis of the above technical solution, the configuration items include: specifying a percentage of touch events; a sliding event; a trackball event; a navigation event; a system key event; switching between activities; specifying a seed value for generating a random event; specifying a detailed level of the print information; ignoring the crash; ignore timeout; ignoring the security exception; and directly killing the process after an error occurs.
On the basis of the technical scheme, the graph in the basic performance report records the executed events by using nodes.
Compared with the prior art, the invention has the following advantages:
(1) the invention further excavates potential performance hazards by combining a special performance tool. The method uses Java language to establish Android Test Project engineering, and random Test Advanced Monkey (smart Monkey Test tool) is combined with JUnit Test in principle, wherein JUnit is a unit Test framework of the Java language; in the running test process, the crash stack information of the APP to be tested and the native crash information are recorded, and meanwhile, according to the configuration items, the Advanced Monkey can output a performance report. A tester uses the Advanced Monkey to perform stability test, can find out the operation steps causing crash according to crash information in a report, synchronously collects performance data, and analyzes the potential performance hazard according to the performance data, thereby making up places which cannot be covered by manual test.
(2) The invention develops a large Robotium test case (based on a Robotium test case) based on a Robotium automatic test framework to perform activity depth traversal and node operation on App, and develops an Advanced Monkey App (smart Monkey test application) tool. The Robotium is a foreign Android automatic test framework, mainly aims at black box automatic test of Application of an Android platform, provides an API (Application Programming Interface) for simulating various gesture operations (clicking, long pressing, sliding and the like), searching and assertion mechanisms, and can operate various controls. Robotium achieves automated testing of applications in combination with a testing framework provided by the Android authority. The method and the device can accurately identify the operation on the page and avoid invalid click.
(3) The invention supports Checklist configuration and can provide simple functional verification.
Drawings
Fig. 1 is a flowchart of an automated testing method for android system stability in the embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the figures and the embodiments.
Referring to fig. 1, an embodiment of the present invention provides an automated testing method for android system stability, including the following steps:
s1, establishing an Android Test Project (Android Test Project) Project by using Java language;
s2, importing libs (static libraries) required by Advanced Monkey, robotium-solo.jar, douyu-common.jar and douyu-common.jar packages to realize the function of accurately identifying the operation on the page and avoiding invalid click;
typically, a module will have a fixed entry into it, and exit from it will also return to the fixed entry interface. Adding a judgment, namely checking whether the current interface is the interface after each operation, if so, clicking the entrance control, returning to the module, and continuing the test; this ensures that the stability test is always performed in this module.
The specific implementation mode is as follows: when detecting that the current interface is concerned activity, acquiring control information of the activity by communicating with a View Server (View service) on the mobile phone to obtain coordinate information of a specified control; clicking on this coordinate returns to the designated interface.
S3, modifying an Android manifest. Modifying the field of the name and the targetPackage (corresponding to the field name) in the instrumentation TAG, and filling the field content with a package name com.douyuu.testRunner and an application package name air.tv.douyuu.android (APP application package name) of a jar (packaging written classes) package respectively.
S4, creating a JUnit Test Case in a src file (Test code directory) of an android Test project, wherein the JUnit Test Case needs to inherit a com. The Python script achieves the function of executing the adb shell dumpsysmeminfo and the adb shell dumpsys CPU info commands after each operation is completed, namely acquiring the current mobile phone memory and CPU information, taking the acquired memory and CPU information as dynamic broadcast files, sending the dynamic broadcast files through broadcast messages, recording the dynamic broadcast files in the mobile phone local files, and reporting details in step S7.
S5, adding configuration items supporting the checklist
The Checklist configuration is supported, providing simple functional verification: the optimization idea of the invention is to write the business operation into an automation script, abstract the script into a Monkey event, and configure the execution proportion.
Since the improvement of the native monkey test technology needs to extend monkey command parameters, in order to achieve this, source code modification needs to be carried out on monkey. Jar is the user's configuration steps after generation for new monkey.
(1) According to different android platform versions, pushing the monkey.jar of the corresponding platform to the/data/local/tmp/monkey.jar
(2) Generate the following executable file/data/local/tmp/monkey (directory file address in mobile phone)
(3) Adding execution authority to data/local/tmp/monkey (directory file address in mobile phone)
(4) The monkey run command using this extended function is detailed as follows:
create newly the assets folder in the project, add the configuration. Adding configuration items supporting a check list in a config.properties file, setting the position of an output report, defaulting to a/mnt/sdcard/report/(path address) directory, and setting an automatic login switch, and respectively setting a user name and a password input during initial automatic login. The content required for the following edit box, i.e. the corresponding content in advance, is then edited on the automation test App.
Configuration items supporting the check list are added in the Advanced config.
The configuration items comprise:
- -pct-touch: specifying the percentage of touch events, for example: -pct-touch 5%;
also relevant are the following options:
-pct-motion < percent > (slip event);
-pct-trackball < percent > (trackball event);
-pct-nav < percent > (navigation event up/down/left/right);
-pct-majornav < percent > (main navigation event back key, menu key);
-pct-syskeys < percent > (system key events Home, Back, startCall, endCall, volumeControl);
-pct-appswitch < percentage > (switching between activities);
-pct-anyseven < percent >;
-s: specifying seed values that produce random events, identical seed values producing identical sequences of events, for example: -s 200;
-v: specifying a detailed level of the print information, one-v adding one level, the default level being 0;
-p: specifying valid packages (if not, all packages in the system are valid), where one-p corresponds to one valid package, e.g.: -p com.ckt-p com.ckt.asura;
-c: activity must contain at least one designated category to be started, otherwise it cannot be started;
- -throttle: interval after each event ends-reducing the stress on the system (if not specified, the system will send the sequence of events as soon as possible), for example: - - -throttle 100;
- - -dbg-no-events: the activated activity is initialized, but no event is generated.
-hprof: the analysis report is generated immediately before and after the event sequence is sent after the item is specified-it is generally recommended that the item be specified.
- -ignore-craches: ignoring the crash;
- -align-timeouts: ignore timeout;
- -align-security-exceptions: ignoring the security exception;
- - -kill-process-after-error: directly killing the process after an error occurs;
- -monitor-native-creats: tracking a crash problem of a local method;
-wait-dbg: the monkey test is performed knowing that the debugger is connected.
S6, executing
And collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files locally, generating reports after testing, uploading the reports to a WEB server, and generating basic performance reports and blast information by the WEB server.
The method is executed in a Run as Android Test (running mode), and after the execution is finished, the uploading operation can be automatically executed, so that the files in the mobile phone can be uploaded to an automation platform WEB server, and the output report of the Advanced Monkey can be checked through the WEB server.
S7, displaying information of basic performance report
(1) Basic performance reporting
According to the configuration item, the Advanced Monkey will output the performance report to the output report catalog. The performance report is an html or xml file beginning with performance.
In the Html format performance report, first, the relevant information of the app to be tested is listed, including a package name, a Uid (user unique identifier), and a Pid (process unique identifier) and a process name of each process under the Uid.
The following is a chart of CPU (Central Processing Unit), memory, and flow. The CPU occupancy rate of each process is recorded in the CPU diagram, the occupancy rate of each process PSS (physical memory actually used, including the memory occupied by the shared library) and USS (Unique Set Size, physical memory occupied by a process alone, not including the memory occupied by the shared library) are recorded in the memory diagram, and the total traffic usage rate and the traffic difference between two collection points are recorded in the traffic diagram.
The graphs in the basic performance report record events executed by the Advanced Monkey with the node, and can be used for assisting in positioning the operation causing curve fluctuation.
In the performance report in the Xml format, each operation is an acquisition point, in which a timestamp, a total CPU occupancy of a testing handset, a traffic difference, a traffic sum, an event on a node, and Pid, CPU occupancy, PSS, USS, and the like of each process are recorded, and details can be viewed by clicking the node, usually, a CPU and memory threshold is set, the CPU is set to be 50% and the memory occupies 200MB according to a common test standard, if a performance value exceeds the threshold when the operation is performed, red is marked on a curve, a tester needs to manually confirm whether the performance is a problem or not, if the performance is a problem, the performance is submitted to be developed to be solved, and the event exceeding the threshold needs to be concerned under a common condition.
(2) crash information
The Advanced Monkey can automatically record the blast stack information of the detected APP and the native blast information.
Crash information is output in your configured directory as a txt file beginning with stack information. Each crash individually outputs one file. Native creatsh information is recorded in a file beginning with dmp, and can be viewed through google-breaking pad (google cross-platform crash dump and analysis module tool).
The embodiment of the invention also provides an automatic testing device for the stability of the android system, which comprises an engineering establishing unit, a static library importing unit, a configuration file modifying unit, a test case newly-built unit, a configuration unit, an executing unit and a display unit;
the project building unit is used for: establishing an android test project by using Java language;
the static library importing unit is used for: importing a static library; when the current interface is detected to be the concerned activity, acquiring control information of the activity through communication with a view service on the mobile terminal to obtain coordinate information of the specified control; clicking the coordinate, namely returning to the specified interface;
the configuration file modification unit is used for: modifying a configuration file of an android test project;
the test case new unit is used for: in a test code directory of an android test project, a JUnit test case is newly built, a performance data dotting script is implanted, current mobile terminal memory and CPU information are obtained, the obtained memory and CPU information are used as dynamic broadcast files, the dynamic broadcast files are sent out through broadcast messages and are recorded in local files of the mobile terminal;
the configuration unit is used for: adding configuration items supporting the checking list; the configuration items comprise: specifying a percentage of touch events; a sliding event; a trackball event; a navigation event; a system key event; switching between activities; specifying a seed value for generating a random event; specifying a detailed level of the print information; ignoring the crash; ignore timeout; ignoring the security exception; directly killing the process after an error occurs;
the execution unit is to: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files to the local, generating reports after testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server;
the display unit is used for: and displaying information of the basic performance report, wherein the graph in the basic performance report records the executed events by using the nodes.
Various modifications and variations of the embodiments of the present invention may be made by those skilled in the art, and they are also within the scope of the present invention, provided they are within the scope of the claims of the present invention and their equivalents.
What is not described in detail in the specification is prior art that is well known to those skilled in the art.
Claims (10)
1. An automated android system stability testing method is characterized by comprising the following steps:
s1, establishing an android test project;
s2, importing a static library;
s3, modifying the configuration file of the android test project;
s4, newly building a JUnit test case in a test code directory of an android test project, implanting a performance data dotting script, acquiring the current mobile terminal memory and CPU information after each operation is finished, taking the acquired memory and CPU information as a dynamic broadcast file, sending the dynamic broadcast file through a broadcast message, and recording the dynamic broadcast file in a local file of the mobile terminal;
s5, adding configuration items supporting the check list;
s6, executing: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files to the local, generating reports after testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server;
s7, displaying the basic performance report information, including:
a CPU graph for: recording the CPU occupancy rate of each process;
a memory map for: and recording the occupation situation of each process PSS and USS.
2. The automated android system stability testing method of claim 1, in which: in step S1, an android test project is created using the Java language.
3. The automated android system stability testing method of claim 1, in which: the step S2 further includes the steps of: when the current interface is detected to be the concerned activity, acquiring control information of the activity through communication with a view service on the mobile terminal to obtain coordinate information of the specified control; clicking on the coordinate returns to the designated interface.
4. The automated android system stability testing method of claim 1, in which: the configuration items in step S5 include: specifying a percentage of touch events; a sliding event; a trackball event; a navigation event; a system key event; switching between activities; specifying a seed value for generating a random event; specifying a detailed level of the print information; ignoring the crash; ignore timeout; ignoring the security exception; and directly killing the process after an error occurs.
5. The automated android system stability testing method of claim 1, in which: the graphs in the base performance report record events performed with nodes.
6. An automated testing device for android system stability is characterized by comprising a project establishing unit, a static library importing unit, a configuration file modifying unit, a test case newly-built unit, a configuration unit, an execution unit and a display unit;
the project building unit is used for: establishing an android test project;
the static library importing unit is used for: importing a static library;
the configuration file modification unit is used for: modifying a configuration file of an android test project;
the test case new unit is used for: in a test code directory of an android test project, a JUnit test case is newly built, a performance data dotting script is implanted, current mobile terminal memory and CPU information are obtained after each operation is finished, the obtained memory and CPU information are used as dynamic broadcast files, the dynamic broadcast files are sent out through broadcast messages and are recorded in local files of the mobile terminals;
the configuration unit is used for: adding configuration items supporting the checking list;
the execution unit is to: collecting dynamic broadcast files in the testing process, processing the dynamic broadcast files into static files convenient to display, storing the static files to the local, generating reports after testing is finished, uploading the reports to a WEB server, and generating basic performance reports and breakdown information by the WEB server;
the display unit is used for: information to display a basic performance report, comprising:
a CPU graph for: recording the CPU occupancy rate of each process;
a memory map for: and recording the occupation situation of each process PSS and USS.
7. The automated android system stability testing device of claim 6, in which: the project building unit builds android test project projects by using Java language.
8. The automated android system stability testing device of claim 6, in which: the static library importing unit is further configured to: when the current interface is detected to be the concerned activity, acquiring control information of the activity through communication with a view service on the mobile terminal to obtain coordinate information of the specified control; clicking on the coordinate returns to the designated interface.
9. The automated android system stability testing device of claim 6, in which: the configuration items include: specifying a percentage of touch events; a sliding event; a trackball event; a navigation event; a system key event; switching between activities; specifying a seed value for generating a random event; specifying a detailed level of the print information; ignoring the crash; ignore timeout; ignoring the security exception; and directly killing the process after an error occurs.
10. The automated android system stability testing device of claim 6, in which: the graphs in the base performance report record events performed with nodes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611129937.4A CN106649107B (en) | 2016-12-09 | 2016-12-09 | Automatic testing method and device for stability of android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611129937.4A CN106649107B (en) | 2016-12-09 | 2016-12-09 | Automatic testing method and device for stability of android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106649107A CN106649107A (en) | 2017-05-10 |
| CN106649107B true CN106649107B (en) | 2020-06-12 |
Family
ID=58824714
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611129937.4A Active CN106649107B (en) | 2016-12-09 | 2016-12-09 | Automatic testing method and device for stability of android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106649107B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107193733A (en) * | 2017-05-12 | 2017-09-22 | 微梦创科网络科技（中国）有限公司 | Simulate the methods, devices and systems of Monkey tests |
| CN107480036A (en) * | 2017-07-07 | 2017-12-15 | 网易（杭州）网络有限公司 | Automatic test approach, device, storage medium and the terminal of iOS Mobile solutions |
| CN107783904B (en) * | 2017-09-27 | 2021-03-16 | 武汉斗鱼网络科技有限公司 | Unit test pile de-weighting method, device, computer readable storage medium and equipment |
| CN109960644A (en) * | 2017-12-22 | 2019-07-02 | 北京奇虎科技有限公司 | A kind of test method and system of SDK |
| CN109508276B (en) * | 2018-11-09 | 2023-03-14 | 四川长虹电器股份有限公司 | Method for improving equipment factory detection efficiency on Android platform |
| CN110851117B (en) * | 2019-10-15 | 2023-04-11 | 福建天晴在线互动科技有限公司 | Method and storage medium for importing static library to item by one key |
| CN111258802A (en) * | 2020-02-10 | 2020-06-09 | 同盾控股有限公司 | Method for capturing application program crash information and related equipment |
| CN112579438B (en) * | 2020-12-01 | 2022-07-08 | 河南芯盾网安科技发展有限公司 | Multifunctional automatic test tool and test method |
| CN112463613B (en) * | 2020-12-01 | 2023-09-15 | 广州朗国电子科技股份有限公司 | Test driving system and method based on adb and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103106140A (en) * | 2013-01-24 | 2013-05-15 | Tcl集团股份有限公司 | Intelligent display device testing information display method |
| CN103713991A (en) * | 2012-10-08 | 2014-04-09 | 腾讯科技（深圳）有限公司 | Method and device for testing application programs on Android devices |
| CN104317699A (en) * | 2014-07-24 | 2015-01-28 | 小米科技有限责任公司 | Application program verifying method and device |
-
2016
- 2016-12-09 CN CN201611129937.4A patent/CN106649107B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103713991A (en) * | 2012-10-08 | 2014-04-09 | 腾讯科技（深圳）有限公司 | Method and device for testing application programs on Android devices |
| CN103106140A (en) * | 2013-01-24 | 2013-05-15 | Tcl集团股份有限公司 | Intelligent display device testing information display method |
| CN104317699A (en) * | 2014-07-24 | 2015-01-28 | 小米科技有限责任公司 | Application program verifying method and device |
Non-Patent Citations (1)
| Title |
|---|
| "Activity Testing Tutorial";匿名;《https://web.archive.org/web/20140421084749/https://stuff.mit.edu/afs/sipb/project/android/docs/tools/testing/activity_test.html》;20140421;第1-11页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106649107A (en) | 2017-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106649107B (en) | Automatic testing method and device for stability of android system | |
| CN105094783B (en) | method and device for testing stability of android application | |
| CN104461894B (en) | The operation record device and method of Android software | |
| CN104407980B (en) | Mobile solution automatic test device and method | |
| CN108959068B (en) | Software interface testing method, device and storage medium | |
| CN106649063B (en) | Method and system for monitoring time-consuming data during program operation | |
| CN111159049B (en) | Automatic interface testing method and system | |
| CN102567198B (en) | System and method for testing application program in physical system environment | |
| CN109302522A (en) | Test method, device and computer system and medium | |
| CN104331373A (en) | Monkey test system and method | |
| CN107133174A (en) | Test case code automatically generating device and method | |
| CN105787364B (en) | Automatic testing method, device and system for tasks | |
| CN106547687A (en) | Application testing method, apparatus and system | |
| CN105338110A (en) | Remote debugging method, platform and server | |
| US20160283357A1 (en) | Call stack relationship acquiring method and apparatus | |
| CN105912473A (en) | BDD-based mobile APP automatic testing platform and testing method | |
| CN102467442A (en) | Software testing method, system and equipment | |
| CN112241360A (en) | Test case generation method, device, equipment and storage medium | |
| CN113672441B (en) | Method and device for testing intelligent equipment | |
| CN103312851A (en) | Intelligent cellphone application interaction interface program usability testing method | |
| CN106354629A (en) | Construction method of iOS system mobile application automatic test system based on multiple stages of servers | |
| CN110162453B (en) | Test method, test device, computer readable storage medium and computer equipment | |
| CN110908915B (en) | Test coverage rate display method and device and computer system | |
| CN113448834A (en) | Buried point testing method and device, electronic equipment and storage medium | |
| CN111651232A (en) | One-machine multi-control method, device and system and electronic equipment |
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 |