CN110096323B - Parallel android application UI automatic exploration method - Google Patents

Parallel android application UI automatic exploration method Download PDF

Info

Publication number
CN110096323B
CN110096323B CN201910248660.4A CN201910248660A CN110096323B CN 110096323 B CN110096323 B CN 110096323B CN 201910248660 A CN201910248660 A CN 201910248660A CN 110096323 B CN110096323 B CN 110096323B
Authority
CN
China
Prior art keywords
exploration
activity
task
executed
application
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
Application number
CN201910248660.4A
Other languages
Chinese (zh)
Other versions
CN110096323A (en
Inventor
曹春
邓靖
余萍
马晓星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanjing University
Original Assignee
Nanjing University
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nanjing University filed Critical Nanjing University
Priority to CN201910248660.4A priority Critical patent/CN110096323B/en
Publication of CN110096323A publication Critical patent/CN110096323A/en
Application granted granted Critical
Publication of CN110096323B publication Critical patent/CN110096323B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application provides a parallel android application UI automatic exploration method, a system comprises a control device and more than one test device, and the method comprises the following steps: the control equipment takes out the exploration task to be executed from the task queue and distributes the exploration task to the idle test equipment; after receiving the exploration task, the idle test equipment enters the activity to be explored and continuously executes the input event in the activity to be explored until a preset condition is reached; the control equipment records a UI jump diagram in the process of completing a UI exploration task of activity to be explored, triggers a new activity in the process, generates a new activity UI exploration task and puts the new activity UI exploration task into the task queue; and when the exploration tasks to be executed do not exist in the task queue and each testing device finishes the respective exploration task, the control device splices and records the UI jump diagrams of each activity. Thus, the efficiency of UI traversal is greatly improved.

Description

Parallel android application UI automatic exploration method
Technical Field
The application relates to the technical field of software testing, in particular to a parallel android application UI automatic exploration method.
Background
The UI (User Interface) traversal is a part of application (for example, Android application, IOS application and the like) test, and development and testers can be helped to understand, develop and perfect the application more deeply by constructing a UI jump diagram of the application.
At present, an automatic traversal technology for the application UI is usually based on a model to explore the application UI, and the main methods include depth-first search and breadth-first search, and both methods have the problem of difficult state backtracking. Specifically, when the application executes until a new UI cannot be found, the application needs to trace back to the previous UI to continue exploring the unexplored new UI, and the tracing back of the application often needs to restart the application and re-execute the previously executed input event, which is very tedious and leads to low UI traversal efficiency.
In addition, the existing UI traversal technology only performs traversal of the application UI on one test device, so that the traversal efficiency is limited.
Disclosure of Invention
In order to at least partially overcome the above-mentioned deficiencies in the prior art, the embodiments of the present application propose the following technical solutions:
in a first aspect, an embodiment of the present application provides a method for automatically exploring a UI of a parallelized android application, where the method is applied to a control device and one or more test devices that are communicatively connected to each other, where each of the one or more test devices has an application to be tested, and the method includes:
the control equipment takes out an exploration task to be executed from a task queue, wherein the exploration task is a UI exploration task of activity to be detected of the application to be detected;
the control equipment determines idle test equipment which does not execute the exploration task currently from the more than one test equipment, and allocates the exploration task to be executed to the idle test equipment;
after receiving the exploration task to be executed, the idle test equipment enters the activity to be explored, and continuously executes an input event according to the current UI of the application to be tested in the activity to be explored until a preset condition is reached so as to complete the UI exploration task of the activity to be explored;
the control equipment records a UI jump diagram of the idle test equipment in the process of completing the UI exploration task of the activity to be explored, triggers a new activity in the process, generates the UI exploration task of the activity and puts the UI jump diagram into the task queue as a new exploration task to be executed;
and when the exploration tasks to be executed do not exist in the task queue and the test equipment executing the exploration tasks completes the respective exploration tasks, the control equipment splices and records the UI jump diagrams of the activities.
In a second aspect, an embodiment of the present application provides a method for automatically exploring a parallel android application UI, including a control device and one or more test devices that are communicatively connected to each other; wherein the more than one test equipment are all provided with applications to be tested,
the control equipment takes out an exploration task to be executed from a task queue, wherein the exploration task is a UI exploration task of activity to be detected of the application to be detected;
the control equipment determines idle test equipment which does not execute the exploration task currently from the more than one test equipment, and allocates the exploration task to be executed to the idle test equipment;
after receiving the exploration task to be executed, the idle test equipment enters the activity to be explored, and continuously executes an input event according to the current UI of the application to be tested in the activity to be explored until a preset condition is reached so as to complete the UI exploration task of the activity to be explored;
the control equipment records a UI jump diagram of the idle test equipment in the process of completing the UI exploration task of the activity to be explored, triggers a new activity in the process, generates the UI exploration task of the activity and puts the UI jump diagram into the task queue as a new exploration task to be executed;
and when the exploration tasks to be executed do not exist in the task queue and the test equipment executing the exploration tasks completes the respective exploration tasks, the control equipment splices and records the UI jump diagrams of the activities.
Compared with the prior art, the method has the following beneficial effects:
the application provides a parallel android application UI automatic exploration method, a system comprises a control device and more than one test device, and the method comprises the following steps: the control equipment takes out the exploration task to be executed from the task queue and distributes the exploration task to the idle test equipment; after receiving the exploration task, the idle test equipment enters the activity to be explored and continuously executes the input event in the activity to be explored until a preset condition is reached; the control equipment records a UI jump diagram in the process of completing a UI exploration task of activity to be explored, triggers a new activity in the process, generates a new activity UI exploration task and puts the new activity UI exploration task into the task queue; and when the exploration tasks to be executed do not exist in the task queue and each testing device finishes the respective exploration task, the control device splices and records the UI jump diagrams of each activity. Thus, the efficiency of UI traversal is greatly improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic composition diagram of a method for automatically exploring a parallelized UI of an android application according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for automatically exploring a parallelized UI of an android application according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating that executing a BACK event may rollback to jump BACK to the UI of the activity to be explored;
fig. 4 is a schematic diagram illustrating a relationship between each activity and a task queue according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Referring to fig. 1, fig. 1 is a schematic composition diagram of a method for automatically exploring a UI of a parallelized android application according to an embodiment of the present application. The application UI automatic exploration method comprises a control device and more than one test device which are mutually connected in a communication mode. By using the method for automatically exploring the application UI, which will be described later, after the application to be tested is input into the control device, the UI traversal graph of the application to be tested can be obtained as output.
In this embodiment, the control device may be a computer device, the test device may be an electronic device (e.g., a mobile phone, a tablet, etc.) having a display screen, and an application to be tested (e.g., an Android application, an IOS application, etc.) is installed in the test device. Optionally, the communication connection between the control device and the one or more test devices may be as shown in fig. 1: the control device may be a central host, and each test device is connected to a slave host communicatively connected to the central host in a USB connection.
Referring to fig. 2, fig. 2 is a schematic flowchart of an automatic UI exploration method for a parallelized android application according to the present application. The specific steps of the method are described in detail below.
Step one, taking out an exploration task to be executed from a task queue, wherein the exploration task is a UI exploration task of activity to be explored of the application to be tested;
in this embodiment, each exploration task corresponds to a specific activity. In one embodiment, the exploration task includes an initial UI exploration task of starting activity of the application to be tested. Correspondingly, when the test is started, the control device analyzes the installation package of the application to be tested, determines the starting activity of the application to be tested, and generates and stores the initial UI exploration task. In the subsequent steps, the test device assigned to the initial UI exploration task starts the application to be tested, that is, enters the start activity of the application to be tested.
And step two, the control equipment determines idle test equipment which does not execute the exploration task currently from the more than one test equipment, and allocates the exploration task to be executed to the idle test equipment.
In this embodiment, the control device may monitor the current working state of each test device: when the test device does not currently execute the allocated exploration task, the working state of the test device (namely, the idle test device) is an idle state; when the test device is currently executing the assigned exploration task, the working state of the test device is a busy state.
And step three, after receiving the exploration task to be executed, the idle test equipment enters the activity to be explored, and continuously executes an input event according to the current UI of the application to be explored within the activity to be explored until a preset condition is reached, so as to complete the UI exploration task of the activity to be explored.
In this embodiment, after the idle test device enters an activity to be explored, the UI of the activity to be explored is explored by continuously executing an input event. Optionally, the input condition executed each time may be randomly generated by the idle test device according to the current UI of the application to be tested. Any input event performed may not trigger a new UI, and may trigger a new UI. Further, the triggered new UI may belong to the activity to be explored or may belong to a new activity (i.e., a new activity is triggered). After triggering a new activity, the idle test equipment continues to execute an input condition (for example, a BACK event of an Android system) to jump BACK to the activity to be explored, and further continues to explore the UI of the activity to be explored.
As shown in fig. 3, the principle that executing a BACK event may jump BACK to the UI of the activity to be explored is illustrated. When a new Activity is triggered, the new Activity is pushed into a Back Stack (Back Stack) of activities to become the Activity displayed on the test equipment, and the last Activity (i.e., the Activity to be explored) enters a sleep state. After the BACK event is input, the Activity (i.e., the new Activity) displayed by the test equipment is exited, the stack is popped from the rollback stack top, the Activity is destroyed after popping, and the last Activity (i.e., the Activity to be explored) becomes the Activity at the stack top again and becomes the Activity displayed on the test equipment.
Therefore, when the executor finds that the input event triggers to jump to another Activity, the Activity at the top of the stack is the other Activity, the Activity specified by the task is pressed down in the rollback stack, and in order to rollback to the Activity specified by the task, the current Activity can be exited only by inputting a BACK event in the Android system.
In this embodiment, after a preset condition is reached, the idle test device completes exploration of the UI of the activity to be explored, and does not execute an input event any more. Optionally, the idle test device may execute a preset number of input conditions, continue to execute the preset number of input conditions if the currently executed preset number of input conditions trigger a new UI, and stop executing the input event if the currently executed preset number of input conditions do not trigger the new UI (that is, the preset condition is reached).
Optionally, as shown in fig. 2, for each activity, the control device may further record a sequence of all input events from the start of the application to be tested to the time when the activity is triggered, so as to obtain a reproduction sequence of the activity. In this way, the test device may enter the activity to be explored by executing the playback sequence of the activity to be explored recorded by the control device.
And step four, the control equipment records the UI jump diagram of the idle test equipment in the process of completing the UI exploration task of the activity to be explored, triggers a new activity in the process, generates the UI exploration task of the new activity and puts the UI exploration task into the task queue as a new exploration task to be executed.
Referring to fig. 4, fig. 4 is a schematic diagram illustrating a relationship between an activity and the task queue. Starting from the first activity to be explored (assumed to be a in fig. 4), as shown in fig. 4, the control apparatus generates a UI exploration task of a as the first exploration task to be executed and puts it in the task queue. When the test is started, each test device is in an idle state, and the control device can take the UI exploration task of A out of the task queue and allocate the UI exploration task to any test device for execution. Further, as shown in fig. 4, assuming that new activities B and C are triggered during the execution of the UI exploration task of a, the control apparatus generates and puts the UI exploration task of B and the UI exploration task of C into the task queue. If the control device detects that the two test devices are in the idle state, the UI search task of B and the UI search task of C may be respectively taken out from the task queue and allocated to the two test devices for execution. Further, as shown in fig. 4, if B triggers new activities D and E while being allocated to the idle test device being executed, the control device generates a UI exploration task of D and a UI exploration task of E to be put into the task sequence. If the control device detects that two test devices (e.g., a and C) are in an idle state, the UI search task of D and the UI search task of E may be respectively taken out of the task queue and allocated to the two test devices for execution.
With the continuous emergence of new activities and new exploration tasks, different exploration tasks to be executed can be executed by different test equipment respectively at the same time, namely, UI exploration can be carried out on a plurality of activities to be explored in parallel.
Optionally, the control device may further record a sequence of each activity trigger, and preferentially allocate, for more than one to-be-executed exploration task, the to-be-executed exploration task corresponding to the activity that is triggered first to the idle test device according to the sequence of the more than one activity trigger that is one-to-one corresponding to the more than one to-be-executed exploration task.
And fifthly, when the exploration tasks to be executed do not exist in the task queue and the test equipment executing the exploration tasks all complete the respective exploration tasks, the control equipment splices and records the UI jump diagrams of the activities.
In this embodiment, when the search task to be executed does not exist in the task queue and the test devices executing the search task all complete their search tasks, it indicates that the UI search of the entire application to be tested is completed, and the control device splices the recorded UI jump maps of the activities to implement UI traversal of the application to be tested.
Therefore, the UI of each activity of the application to be tested is explored in parallel by adopting a plurality of test devices, the application does not need to be restarted, the input event before the application is repeatedly executed is not needed, and the UI traversal efficiency is greatly improved.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (6)

1. A parallel UI (user interface) automatic exploration method for android applications is characterized by being applied to control equipment and more than one test equipment which are in communication connection with each other, wherein the more than one test equipment are respectively provided with an application to be tested, and the method comprises the following steps:
the control equipment takes out an exploration task to be executed from a task queue, wherein the exploration task is a UI exploration task of activity to be detected of the application to be detected;
the control equipment determines idle test equipment which does not execute the exploration task currently from the more than one test equipment, and allocates the exploration task to be executed to the idle test equipment;
after receiving the exploration task to be executed, the idle test equipment enters the activity to be explored, and continuously executes an input event according to the current UI of the application to be tested in the activity to be explored until a preset condition is reached so as to complete the UI exploration task of the activity to be explored;
the control equipment records a UI jump diagram of the idle test equipment in the process of completing a UI exploration task of activity to be explored, triggers new activity in the process, generates a new UI exploration task of activity and puts the new UI exploration task into the task queue as a new exploration task to be executed;
and when the exploration tasks to be executed do not exist in the task queue and the test equipment executing the exploration tasks completes the respective exploration tasks, the control equipment splices and records the UI jump diagrams of the activities.
2. The method for automatically exploring the UI of the parallelized android application of the claim 1, wherein the exploration task comprises an initial UI exploration task for starting activity of the application to be tested;
before the control device fetches the exploration task to be executed from the task queue, the method further includes:
and the control equipment analyzes the installation package of the application to be tested, determines the starting activity of the application to be tested, generates the initial UI exploration task and puts the initial UI exploration task into the task queue as the exploration task to be executed.
3. The method according to claim 1, wherein the method further comprises:
for each activity, the control device records a sequence of all input events from the start of the application to be tested to the triggering of the activity, and obtains a reproduction sequence of the activity.
4. The method for automatically exploring the UI of the parallelized android application, according to claim 1, continuously executing the input event according to the current UI of the application to be tested within the activity to be explored until a preset condition is reached, comprising:
executing a preset number of input conditions;
if the input conditions of the preset number currently executed trigger a new UI, continuously executing the input conditions of the preset number;
if the input conditions of the currently executed preset number do not trigger a new UI, stopping executing the input event;
if the currently executed input condition triggers a new activity, a BACK event is executed to jump BACK to the activity to be explored.
5. The method according to claim 1, wherein the method further comprises:
the control equipment records the sequence of each activity trigger;
allocating the exploration task to be performed to the idle test device, comprising:
and aiming at more than one exploration task to be executed, preferentially distributing the exploration tasks to be executed corresponding to the activities triggered first to the idle test equipment according to the sequence of more than one activity triggers corresponding to the more than one exploration tasks to be executed one by one.
6. A parallel android application UI automatic exploration method is characterized by comprising control equipment and more than one test equipment which are in communication connection with each other; wherein the more than one test equipment are all provided with applications to be tested
The control equipment takes out an exploration task to be executed from a task queue, wherein the exploration task is a UI exploration task of activity to be detected of the application to be detected;
the control equipment determines idle test equipment which does not execute the exploration task currently from the more than one test equipment, and allocates the exploration task to be executed to the idle test equipment;
after receiving the exploration task to be executed, the idle test equipment enters the activity to be explored, and continuously executes an input event according to the current UI of the application to be tested in the activity to be explored until a preset condition is reached so as to complete the UI exploration task of the activity to be explored;
the control equipment records a UI jump diagram of the idle test equipment in the process of completing a UI exploration task of activity to be explored, triggers new activity in the process, generates a new UI exploration task of activity and puts the new UI exploration task into the task queue as a new exploration task to be executed;
and when the exploration tasks to be executed do not exist in the task queue and the test equipment executing the exploration tasks completes the respective exploration tasks, the control equipment splices and records the UI jump diagrams of the activities.
CN201910248660.4A 2019-03-29 2019-03-29 Parallel android application UI automatic exploration method Active CN110096323B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910248660.4A CN110096323B (en) 2019-03-29 2019-03-29 Parallel android application UI automatic exploration method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910248660.4A CN110096323B (en) 2019-03-29 2019-03-29 Parallel android application UI automatic exploration method

Publications (2)

Publication Number Publication Date
CN110096323A CN110096323A (en) 2019-08-06
CN110096323B true CN110096323B (en) 2022-03-18

Family

ID=67444102

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910248660.4A Active CN110096323B (en) 2019-03-29 2019-03-29 Parallel android application UI automatic exploration method

Country Status (1)

Country Link
CN (1) CN110096323B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102224491A (en) * 2008-09-22 2011-10-19 Mts系统公司 Testing machine with workflow based test procedure
KR20140002815A (en) * 2012-06-24 2014-01-09 김현수 Automating gui test of android applications
CN104699600A (en) * 2013-12-10 2015-06-10 博雅网络游戏开发(深圳)有限公司 Testing system and method for installation package application
CN105279017A (en) * 2015-09-30 2016-01-27 北京奇虎科技有限公司 Cloud test platform based task distribution method, apparatus and system
CN107357727A (en) * 2017-07-04 2017-11-17 广州君海网络科技有限公司 APP testing results method, apparatus, readable storage medium storing program for executing and computer equipment
CN107678940A (en) * 2017-08-30 2018-02-09 苏州朗动网络科技有限公司 Automation exploratory testing method and system based on Android APP
CN108459966A (en) * 2018-03-21 2018-08-28 东软集团股份有限公司 Dispatching method, device, equipment and the computer readable storage medium of test suite

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102224491A (en) * 2008-09-22 2011-10-19 Mts系统公司 Testing machine with workflow based test procedure
KR20140002815A (en) * 2012-06-24 2014-01-09 김현수 Automating gui test of android applications
CN104699600A (en) * 2013-12-10 2015-06-10 博雅网络游戏开发(深圳)有限公司 Testing system and method for installation package application
CN105279017A (en) * 2015-09-30 2016-01-27 北京奇虎科技有限公司 Cloud test platform based task distribution method, apparatus and system
CN107357727A (en) * 2017-07-04 2017-11-17 广州君海网络科技有限公司 APP testing results method, apparatus, readable storage medium storing program for executing and computer equipment
CN107678940A (en) * 2017-08-30 2018-02-09 苏州朗动网络科技有限公司 Automation exploratory testing method and system based on Android APP
CN108459966A (en) * 2018-03-21 2018-08-28 东软集团股份有限公司 Dispatching method, device, equipment and the computer readable storage medium of test suite

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
Android应用并行自动化测试技术研究与实现;陈学亮 等;《广东通信技术》;20161115;全文 *
Automated mobile UI test fragility: an exploratory assessment study on Android;Riccardo Coppola etc.;《INTUITEST 2016: Proceedings of the 2nd International Workshop on User Interface Test Automation》;20160721;全文 *
Data flow oriented UI testing: exploiting data flows and UI elements to test Android applications;Nataniel P. Borges Jr etc.;《ISSTA 2017: Proceedings of the 26th ACM SIGSOFT International Symposium on Software Testing and Analysis》;20170710;全文 *
规则驱动的Android应用DFS测试技术;叶佳,葛红军,曹春等;《计算机科学》;20180915;全文 *

Also Published As

Publication number Publication date
CN110096323A (en) 2019-08-06

Similar Documents

Publication Publication Date Title
WO2016095554A1 (en) Test method, device and system for application
US9665473B2 (en) Smart tester application for testing other applications
CN106681811B (en) Multithreading scheduling method and device based on thread pool
CN108845954B (en) Pressure testing method, system and storage medium
WO2019227708A1 (en) Online debugging apparatus and method for test case, and computer-readable storage medium
US7779302B2 (en) Automated testing framework for event-driven systems
CN106681701B (en) Task display method and device
CN107967207B (en) Method and device for testing user interface interaction function
US20130138381A1 (en) Handheld electronic device testing method
CN105975367B (en) Test method and device for mobile equipment
CN111258913A (en) Automatic algorithm testing method and device, computer system and readable storage medium
CN110597720A (en) Application program testing method and device, electronic equipment and storage medium
CN102999419A (en) Android test incident record and playback methods and device
CN103473178A (en) Method and system for optimizing testing process execution
CN110750453A (en) HTML 5-based intelligent mobile terminal testing method, system, server and storage medium
CN114218072A (en) Test script generation method and device, storage medium and computer equipment
CN110096323B (en) Parallel android application UI automatic exploration method
CN105138458A (en) Method and system for recording automatic testing scripts by combining intelligent terminal and computer terminal
JP2016514326A (en) Method and system for analyzing a trace timeline of computer system activity
JP6642024B2 (en) Management device, management method and management program
CN115599645B (en) Method and device for testing stability of linux driving module
CN105339974B (en) Analog sensor
CN107391354B (en) Method and system for automatically monitoring terminal performance and storage device
Park et al. Self-adaptive middleware framework for internet of things
CN112596750B (en) Application testing method and device, electronic equipment and computer readable storage 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