CN111382048A - Management method and device for mobile equipment on real machine test platform - Google Patents

Abstract

The invention provides a management method and device for mobile equipment on a real machine test platform. The method is applied to a mobile device, and includes: after the mobile device is connected to a proxy server, starting a designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation; using the designated daemon process Detecting the current device state of the mobile device, and judging whether the current device state is abnormal; A test case script of the device; the test case script is parsed and executed by the designated daemon to maintain the mobile device. The present invention can continuously monitor the state of the mobile device and obtain and execute the corresponding test case script according to the abnormal state, so as to realize the automatic maintenance of the mobile device.

Description

Management method and device for mobile equipment on real machine test platform

technical field

The invention relates to the technical field of remote real machine testing, in particular to a management method and device for mobile equipment on a real machine testing platform, a computer storage medium and a computing device.

Background technique

The remote real machine test platform is a platform for remotely controlling the use of mobile phones, which can provide real machine operation in the cloud, so as to provide users with the functional modules, performance, security, capacity, compatibility, ease of use, hardware environment, Cross-event, interface and other tests greatly facilitate the development and testing of mobile software and apps.

During mobile testing, mobile phone and proxy server (such as PC (Personal Computer) proxy) establish adb (Android Debug Bridge, Android Debug Bridge) through USB (Universal Serial Bus, Universal Serial Bus) data line or WiFi network Connect, and enable the USB debugging mode under the developer options on the mobile phone, so that the user can operate and test the mobile phone on the test platform through the proxy server. However, there are usually hundreds or thousands of mobile phone devices on the real machine test platform. In the daily operation process, there are often abnormalities such as disconnection of the USB connection of some mobile phone devices, automatic shutdown of the developer mode, etc., which affect the normal operation of the test. At this time, specialized maintenance personnel are required to perform corresponding maintenance processing on the equipment, which increases labor costs and is inefficient.

Therefore, there is an urgent need for a method that can monitor the abnormal state of the mobile phone on the real device test platform in real time and automatically maintain the abnormal mobile phone.

SUMMARY OF THE INVENTION

In view of the above problems, the present invention is proposed to provide a mobile device management method and apparatus on a real machine test platform, a computer storage medium and a computing device that overcome the above problems or at least partially solve the above problems.

According to an aspect of the embodiments of the present invention, a method for managing mobile devices on a real machine test platform is provided, applied to the mobile device, including:

After the mobile device is connected to the proxy server, start a designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation;

Detect the current device state of the mobile device through the designated daemon process, and determine whether the current device state is abnormal;

If so, obtain a test case script for maintaining the mobile device from the real machine test platform through the designated daemon process according to the information of the mobile device;

The test case script is parsed and executed by the designated daemon to maintain the mobile device.

Optionally, the designated daemon process is a java daemon process;

Start the specified daemon process in the mobile device through the proxy server without suspending the operation, including:

The target dex file is run in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon process.

Optionally, the target dex file is converted from an executable jar package containing device status monitoring and test case script execution logic through an Android software development kit, and is preconfigured in the mobile device.

Optionally, the mobile device uses USB or WiFi to connect with the proxy server through an adb command.

Optionally, the current device state of the mobile device is detected by the designated daemon process, including:

The current device state of the mobile device is periodically detected by the designated daemon.

Optionally, judging whether the current device state is abnormal, including:

Determine if the USB connection is broken; and/or

Determines whether developer mode is automatically turned off.

Optionally, after detecting the current device state of the mobile device, the method further includes:

The current device state of the mobile device is reported to the real device test platform.

Optionally, the test case script is pre-configured in the real machine test platform according to the device model, operating system version and/or device exception type;

Obtain a test case script for maintaining the mobile device from the real machine test platform according to the information of the mobile device through the designated daemon, including:

Through the designated daemon process, a test case for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device script.

Optionally, the test case script is in json format.

Optionally, maintaining the mobile device includes:

Simulate user operations by specifying method names and parameters in the test case script.

Optionally, the user operation includes at least one of the following:

Sleep, swipe, tap.

Optionally, executing the test case script includes:

The test case script is executed by an automated testing framework.

Optionally, the method further includes:

If it is determined that the current device state is not abnormal, the designated daemon process is made to wait for the next detection of the current device state of the mobile device.

According to another aspect of the embodiments of the present invention, there is also provided a management device for a mobile device on a real machine test platform, which is applied to the mobile device, including:

a process startup module, adapted to start a designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation after the mobile device is connected to the proxy server;

a state detection module, adapted to detect the current device state of the mobile device through the designated daemon process, and determine whether the current device state is abnormal;

a script obtaining module, adapted to obtain a test case script for maintaining the mobile device from the real machine test platform through the designated daemon process according to the information of the mobile device if it is judged that the current device state is abnormal; as well as

The script parsing and execution module is adapted to parse and execute the test case script through the designated daemon process, so as to maintain the mobile device.

Optionally, the designated daemon process is a java daemon process;

The process startup module is also adapted to:

The target dex file is run in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon process.

Optionally, the target dex file is converted from an executable jar package containing device status monitoring and test case script execution logic through an Android software development kit, and is preconfigured in the mobile device.

Optionally, the mobile device uses USB or WiFi to connect with the proxy server through an adb command.

Optionally, the state detection module is further adapted to:

The current device state of the mobile device is periodically detected by the designated daemon.

Optionally, the state detection module is further adapted to:

Determine if the USB connection is broken; and/or

Determines whether developer mode is automatically turned off.

Optionally, the state detection module is further adapted to:

After detecting the current device state of the mobile device, the current device state of the mobile device is reported to the real machine test platform.

Optionally, the test case script is pre-configured in the real machine test platform according to the device model, operating system version and/or device exception type;

The script acquisition module is also adapted to:

Through the designated daemon process, a test case for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device script.

Optionally, the test case script is in json format.

Optionally, the script parsing execution module is further adapted to:

Simulate user operations by specifying method names and parameters in the test case script.

Optionally, the user operation includes at least one of the following:

Sleep, swipe, tap.

Optionally, the script parsing execution module is further adapted to:

The test case script is executed by an automated testing framework.

Optionally, the device further includes:

The process waiting module is adapted to make the designated daemon wait for the next detection of the current device state of the mobile device if it is determined that the current device state is not abnormal.

According to yet another aspect of the embodiments of the present invention, there is also provided a computer storage medium, where the computer storage medium stores computer program codes, which, when the computer program codes are executed on a computing device, cause the computing device to execute according to the The management method of a mobile device on a real machine test platform described in any one of the above.

According to yet another aspect of the embodiments of the present invention, a computing device is also provided, including:

processor; and

memory in which computer program code is stored;

When the computer program code is executed by the processor, it causes the computing device to execute the method for managing a mobile device on a real machine test platform according to any one of the above.

The method and device for managing a mobile device on a real machine test platform provided by the embodiment of the present invention, when the mobile device goes online on the real machine test platform, start a designated daemon process in the mobile device through a proxy server in a manner that does not suspend operation, Then, the current device status of the mobile device is detected by the designated daemon process and whether it is abnormal, if so, the test case script for maintaining the mobile device is obtained from the real machine test platform according to the information of the mobile device, and the test case script is executed. Parse and execute, so as to implement maintenance operations on the mobile device. Since the designated daemon is started in a way that does not suspend, even if the mobile device is in an abnormal state where the USB connection is disconnected or the developer mode is automatically turned off, the designated daemon can still be in the running state, so as to continuously monitor the state of the mobile device and target The abnormal state is obtained and the corresponding test case script is executed to realize the automatic maintenance of the mobile device.

Further, by obtaining preconfigured test case scripts for different mobile device models, system versions and abnormal types from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device, And by specifying method names and parameters in the test case script to simulate a series of user operations, it can realize the accurate automatic processing of abnormal state problems with fixed processing steps by executing the test case script.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

The above and other objects, advantages and features of the present invention will be more apparent to those skilled in the art from the following detailed description of the specific embodiments of the present invention in conjunction with the accompanying drawings.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

1 shows a flowchart of a method for managing a mobile device on a real machine test platform according to an embodiment of the present invention;

Fig. 2 shows the apk construction flow chart of Android system;

Fig. 3 shows the flow chart of the management method of the mobile device on the real machine test platform according to another embodiment of the present invention;

FIG. 4 shows a schematic structural diagram of an apparatus for managing a mobile device on a real machine test platform according to an embodiment of the present invention; and

FIG. 5 shows a schematic structural diagram of an apparatus for managing a mobile device on a real machine test platform according to another embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

The remote real machine test platform is an important tool for mobile device software and app development and testing. There are usually hundreds or thousands of mobile devices on the real machine test platform for operation. In the daily operation process, there are often abnormalities such as disconnection of the USB connection of some mobile devices, automatic shutdown of the developer mode, etc., which affect the normal operation of the test. In the prior art, in response to such an abnormality, specialized maintenance personnel are required to perform corresponding maintenance processing on the equipment, which increases labor costs and is inefficient. Moreover, in the prior art, the java process is directly started through the adb command in USB debugging or developer mode. The java process started in this way depends on the USB connection of the device. When the USB connection is disconnected, the java process will be killed and cannot effectively monitor and maintain the device status.

In order to solve the above technical problem, an embodiment of the present invention proposes a management method for a mobile device on a real machine test platform. FIG. 1 shows a flowchart of a method for managing a mobile device on a real machine test platform according to an embodiment of the present invention. Referring to FIG. 1 , the method is applied to a mobile device and may at least include the following steps S102 to S108.

Step S102, after the mobile device is connected to the proxy server, start the designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation.

In step S104, the current device state of the mobile device is detected by a designated daemon process, and it is determined whether the current device state is abnormal.

Step S106, if yes, obtain a test case script for maintaining the mobile device from the real machine test platform by specifying the daemon process according to the information of the mobile device.

Step S108, parse and execute the test case script by specifying a daemon process to maintain the mobile device.

The method for managing a mobile device on a real machine test platform provided by the embodiment of the present invention, when the mobile device goes online on the real machine test platform, starts a designated daemon process in the mobile device through a proxy server in a way that does not suspend operation, and then passes The designated daemon detects the current device status of the mobile device and judges whether it is abnormal. If so, obtain the test case script for maintaining the mobile device from the real machine test platform according to the information of the mobile device, and parse and analyze the test case script. Execute, so as to realize the maintenance operation of the mobile device. Since the designated daemon is started in a way that does not suspend, even if the mobile device is in an abnormal state where the USB connection is disconnected or the developer mode is automatically turned off, the designated daemon can still be in the running state, so as to continuously monitor the state of the mobile device and target The abnormal state is obtained and the corresponding test case script is executed to realize the automatic maintenance of the mobile device.

The mobile devices mentioned above may include smart mobile terminals such as mobile phones, tablet computers, and smart watches, which can be equipped with an operating system and have the ability to access the Internet. Preferably, the mobile device is equipped with an Android system. The proxy server can be a PC proxy, which is connected to the background heartbeat of the real machine test platform after being started, that is, the validity of the communication connection between the proxy server and the real machine test platform is ensured through a heartbeat mechanism.

In the above step S102, the mobile device may connect with the proxy server through the adb command.

In one way, the mobile device can use a USB data cable to connect to the proxy server, then enable USB debugging in the mobile device, and enter the adb devices command on the command line of the proxy server to establish a communication connection between the mobile device and the proxy server , to debug mobile devices through a proxy server.

In another way, the mobile device can use the WiFi network to connect with the proxy server, after obtaining the IP address of the mobile device, execute the adb connect command in the proxy server, and pass the IP address and port number (usually 5555) of the mobile device, The communication connection between the mobile device and the proxy server can be established to debug the mobile device through the proxy server.

In an optional embodiment, the designated daemon process is a java daemon process. At this point, the step of starting the specified daemon process in the mobile device through the proxy server without suspending operation can be further implemented as:

Run the target dex file in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon.

The Nohup command runs the command specified by the Command parameter and any associated Arg parameters, causing the process to continue running regardless of any pending SIGHUP signals. Dex file is a binary stream file format that can be executed and loaded by dalvik virtual machine (DVM) or ART (Android Runtime) virtual machine. Compared with class file, redundant information is removed and the class information of the entire java project is integrated. , the file size is small and the loading speed is fast.

The Android application layer is implemented in Java and kotlin programming languages. When compiling Android applications, the compiler first compiles Java and kotlin languages into java bytecodes, and then converts the bytecode files into corresponding dex files. Inside the Android system, the dex file can be run directly through the command dalvikvm of the dalvik virtual machine, and the Android system supports the nohup command. The following lists a code example to start the java process through the adb command in the Android system:

adb shell "nohup dalvikvm-cp/data/local/tmp/traget.dexcom.abc.opentest.main>/dev/null 2>&1&"

The java process started by the nohup command can still be running even after the USB connection of the mobile device is disconnected or the developer mode is turned off.

Further, the target dex file mentioned above is converted from the executable jar package containing the device status monitoring and test case script execution logic through the Android SDK (Software DevelopmentKit, software development kit), and is pre-configured on the mobile phone. in the device.

The generation and configuration process of the target dex file will be described below in conjunction with the apk (Android Package) construction flow chart of the Android system shown in FIG. 2 .

Referring to Figure 2, in a typical apk construction process, first, use the AAPT (Android Asset PackagingTool) tool to package the resource files under the res folder of the java project into R.java files and resources.arsc files. If there is aidl, then The aidl interface is converted into a java interface class through the aidl tool. Next, compile R.java and aidl.java into class files through the java compiler. Then, package the source class file and third-party jar or library into a dex file through dx.bat. Then, the apkbuilder tool packages all uncompiled resources (assets, so, jni), resources.arsc files, and generated dex files to generate an apk file. Finally, use the jarsigner tool to sign the apk through the configured signature file (Debug or Release Keystore, debug or release keystore) to obtain the signed apk (signed apk), and then use the zipalign tool to align and optimize the signed apk, Makes accessing apk files faster through memory mapping, reducing runtime memory usage.

Specifically, for the target dex file in the embodiment of the present invention, a java project is first created, and after implementing business logic including device status monitoring and test case script execution logic according to the above construction process, an executable jar package source.jar is generated . Then, convert the executable jar package into a dex package through the dx.bat tool in the Android SDK. The following is a code example of converting the executable jar package into a dex package through the Android SDK tool:

//\SDK\build-tools\27.0.3\dx.bat

dx--dex--output=traget.dex source.jar

In the above step S104, the current device state of the mobile device is detected by the designated daemon process, and it is determined whether the current device state is abnormal.

Preferably, the current device state of the mobile device is periodically detected by a designated daemon process, so as to monitor the state of the mobile device. The detection period of the equipment state can be set according to actual needs, such as 1 hour, 10 minutes, etc., which is not limited in the present invention.

Preferably, judging whether the current device state is abnormal can be further implemented as:

Determine if the USB connection of the mobile device is disconnected; and/or

Determines whether the developer mode of the mobile device is automatically turned off.

For example, when a prompt indicating that the USB connection has been disconnected is detected, but the plug-in operation of the USB data cable is not detected, it can be determined that the USB connection of the mobile device is disconnected. For another example, when a prompt indicating that the developer mode has been turned off is detected, but the user's operation of turning off the developer mode option is not detected, it can be determined that the developer mode of the mobile device has been turned off automatically.

In an optional embodiment, after the current device state of the mobile device is detected by the designated daemon process, the current device state of the mobile device may also be reported to the real device test platform, and specifically, the current device state of the mobile device may be reported to the real device test platform. backend system.

In the aforementioned embodiments, the current device state is detected by a designated daemon process inside the mobile device and it is determined whether the current device state is abnormal. In another alternative embodiment, after the current device state of the mobile device is reported to the real device test platform, the real device test platform may determine whether the current device state is abnormal, and return the determination result to the designated daemon process. In this implementation manner, the operation and basis for judging whether the current device state is abnormal are the same as the above, and are not repeated here.

In the above step S106, if it is determined that the current device state is abnormal, a test case script for maintaining the mobile device is obtained from the real machine test platform through the designated daemon process according to the information of the mobile device. Wherein, the test case script is pre-configured in the background system of the real machine test platform, which is implemented by using custom script rules. The information of the mobile device mentioned here may include the manufacturer of the mobile device, the version of the operating system, and the like.

In an optional embodiment, the test case script is in json format. JSON (JavaScriptObject Notation, JS Object Notation) is a lightweight data exchange format that uses a text format that is completely independent of programming languages to store and represent data, which is easy for humans to read and write, and easy for machines to parse and generate. Effectively improve network transmission efficiency.

In an optional embodiment, the test case script is pre-configured in the real machine test platform according to the device model, operating system version and/or device exception type. At this time, the step of acquiring the test case script for maintaining the mobile device from the real machine test platform by specifying the daemon process according to the information of the mobile device can be further implemented as follows:

By specifying the daemon process, the test case script for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device. The abnormal types of the current device state mentioned here may include disconnection of USB connection and/or automatic shutdown of developer mode.

In the above step S108, the test case script is parsed and executed by the designated daemon process, so as to maintain the mobile device.

In an optional embodiment, the test case script is automatically executed by an automated testing framework to maintain the mobile device.

Preferably, by simulating user operations by specifying method names and parameters in the test case script, automatic execution of maintenance operations on the mobile device is realized. The simulated user operation may include at least one of operations such as sleeping, sliding the screen, and clicking. An example of a test case script for maintaining a mobile device in an abnormal state is listed below:

[

{"function":"sleep","params":[2],"expects":[]},

{"function":"swipe","params":[613,1264,690,566],"expects":[]},

{"function":"sleep","params":[2],"expects":[]},

{"function":"swipe","params":[654,1246,699,244],"expects":[]},

{"function":"sleep","params":[2],"expects":[]},

{"function":"swipe","params":[684,1130,277,0],"expects":[]},

{"function":"sleep","params":[4],"expects":[]},

{"function":"swipe","params":[464,721,464,721],"expects":[]},

{"function":"sleep","params":[11],"expects":[]},

{"function":"clickbymd5","params":["29ecb03e5763e493717649999bf35e68"],"expects":[]}

]

Since there are usually fixed processing steps for handling device exceptions such as USB connection disconnection and automatic shutdown of developer mode, by simulating a series of user operations with specified method names and parameters in the test case script, when a device exception is found, Only by acquiring and executing the test case script, the automatic maintenance of abnormal equipment can be realized without special maintenance personnel, which greatly saves labor costs and improves maintenance efficiency.

In an optional embodiment, the method of the present invention may further comprise the following steps:

If it is determined that the current device state is not abnormal, the designated daemon process is made to wait for the next detection of the current device state of the mobile device.

Various implementations of each link of the embodiment shown in FIG. 1 have been described above. The following will describe in detail the implementation process of the mobile device management method on the real machine test platform of the present invention through specific embodiments.

FIG. 3 shows a schematic flowchart of a method for managing a mobile device on a real machine test platform according to a specific embodiment of the present invention. In this embodiment, the mobile device terminal, the proxy server and the real device test platform are combined to describe the management method of the mobile device on the real device test platform. In this embodiment, the mobile device is a mobile phone, and the proxy server is a PC proxy. Referring to FIG. 3 , the method is applied to a mobile phone terminal, and may at least include the following steps S302 to S310.

Step S302, using USB to establish a connection with the PC agent through an adb command.

Specifically, the mobile phone is connected to the PC using a USB data cable, then USB debugging is enabled in the mobile phone, and the adb devices command is entered on the command line of the PC agent to establish the connection.

Step S304, run the target dex file inside the mobile phone through the nohup command of the adb process of the PC agent to start the java daemon process.

Among them, when the java daemon process is started, the execution environment of the mobile terminal is initialized.

In step S306, the current state of the mobile phone is regularly detected by the java daemon, and it is determined whether the current state of the mobile phone is abnormal.

Specifically, determine whether the USB connection of the mobile phone is disconnected; and/or determine whether the developer mode of the mobile phone is automatically turned off.

Step S308, if it is determined that the current state of the mobile phone is abnormal, the test case script is obtained from the real device test platform through the java daemon process according to the device model, operating system version and abnormal type of the mobile phone.

Wherein, the test case script is pre-configured in the real machine test platform according to the device model, operating system version and/or device exception type.

Specifically, the abnormal types of the mobile phone include disconnection of the USB connection and/or automatic shutdown of the developer mode.

In step S310, the test case script is parsed by the java daemon, and the test utilization script is executed by an automated test framework to maintain the mobile phone.

In this embodiment, before the connection between the mobile phone and the PC agent is established, after the PC agent is started, the PC agent is connected with the real machine test platform by heartbeat, that is, the communication connection between the proxy server and the real machine test platform is ensured through the heartbeat mechanism. effectiveness.

In the embodiment of the present invention, the java daemon process is started by the nohup command, even after the USB connection of the mobile device is disconnected or the developer mode is turned off, it can still be in the running state, so that the device state can be effectively monitored and the test case script used for maintenance can be executed. At the same time, by obtaining pre-configured test case scripts for different mobile device models, system versions and exception types from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device, it is possible to Realize accurate automation of abnormal state problems with fixed processing steps by executing test case scripts.

Based on the same inventive concept, an embodiment of the present invention also provides an apparatus for managing mobile devices on a real machine test platform, which is used to support the management method for mobile devices on a real machine test platform provided by any one of the above embodiments or a combination thereof. FIG. 4 shows a schematic structural diagram of an apparatus for managing a mobile device on a real machine test platform according to an embodiment of the present invention. Referring to FIG. 4 , the apparatus is applied to a mobile device and may at least include: a process initiation module 410 , a state detection module 420 , a script acquisition module 430 , and a script parsing and execution module 440 .

Now introduce the functions of each component or device of the management device of the mobile device on the real machine test platform of the embodiment of the present invention and the connection relationship between each part:

The process starting module 410 is adapted to start a designated daemon process in the mobile device through the proxy server in a manner that does not suspend running after the mobile device is connected to the proxy server.

The state detection module 420, connected with the process initiation module 410, is adapted to detect the current device state of the mobile device through the designated daemon process, and determine whether the current device state is abnormal.

The script obtaining module 430 is connected to the state detection module 420 and is adapted to obtain a test case script for maintaining the mobile device from the real machine test platform through the designated daemon process according to the information of the mobile device if it is determined that the current device state is abnormal.

The script parsing and executing module 440 is connected to the script obtaining module 430 and is adapted to parse and execute the test case script through the designated daemon process, so as to maintain the mobile device.

In an optional embodiment, if the designated daemon process is a java daemon process, the process startup module 410 is further adapted to:

Run the target dex file in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon.

Further, the target dex file is converted from an executable jar package containing device status monitoring and test case script execution logic through the Android software development kit, and is preconfigured in the mobile device.

In an optional embodiment, the mobile device is connected to the proxy server through adb commands using USB or WiFi.

In an optional embodiment, the state detection module 420 is further adapted to:

Periodically detect the current device state of a mobile device by specifying a daemon.

In an optional embodiment, the state detection module 420 is further adapted to:

Determine if the USB connection is broken; and/or

Determines whether developer mode is automatically turned off.

In an optional embodiment, the state detection module 420 is further adapted to:

After detecting the current device state of the mobile device, the current device state of the mobile device is reported to the real machine test platform.

In an optional embodiment, the test case script is pre-configured in the real machine test platform according to the device model, operating system version and/or device exception type, and the script obtaining module 430 is further adapted to:

By specifying the daemon process, the test case script for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device.

In an optional embodiment, the test case script is in json format.

In an optional embodiment, the script parsing and execution module 440 is further adapted to:

Simulate user actions by specifying method names and parameters in test case scripts.

Further, the above-mentioned user operation includes at least one of the following:

Sleep, swipe, tap.

In an optional embodiment, the script parsing and execution module 440 is further adapted to:

Execute test case scripts through an automated testing framework.

In an optional embodiment, as shown in FIG. 5 , the apparatus for managing mobile devices on the real machine test platform shown in FIG. 4 may further include a process waiting module 450 . The process waiting module 450 is connected to the state detection module 420, and is adapted to make the designated daemon wait for the next detection of the current device state of the mobile device if it is determined that the current device state is not abnormal.

Based on the same inventive concept, an embodiment of the present invention also provides a computer storage medium. The computer storage medium stores computer program code, which, when executed on a computing device, causes the computing device to execute the method for managing a mobile device on a real machine test platform according to any one of the foregoing embodiments or a combination thereof.

Based on the same inventive concept, an embodiment of the present invention further provides a computing device. The computing device may include:

processor; and

memory in which computer program code is stored;

When the computer program code is executed by the processor, it causes the computing device to execute the method for managing a mobile device on a real machine test platform according to any one of the above embodiments or a combination thereof.

According to any one of the foregoing optional embodiments or a combination of multiple optional embodiments, the embodiments of the present invention can achieve the following beneficial effects:

The method and device for managing a mobile device on a real machine test platform provided by the embodiment of the present invention, when the mobile device goes online on the real machine test platform, start a designated daemon process in the mobile device through a proxy server in a manner that does not suspend operation, Then, the current device status of the mobile device is detected by the designated daemon process and whether it is abnormal, if so, the test case script for maintaining the mobile device is obtained from the real machine test platform according to the information of the mobile device, and the test case script is executed. Parse and execute, so as to implement maintenance operations on the mobile device. Since the designated daemon is started in a way that does not suspend, even if the mobile device is in an abnormal state where the USB connection is disconnected or the developer mode is automatically turned off, the designated daemon can still be in the running state, so as to continuously monitor the state of the mobile device and target The abnormal state is obtained and the corresponding test case script is executed to realize the automatic maintenance of the mobile device.

Further, by obtaining preconfigured test case scripts for different mobile device models, system versions and abnormal types from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device, And by specifying method names and parameters in the test case script to simulate a series of user operations, it can realize the accurate automatic processing of abnormal state problems with fixed processing steps by executing the test case script.

Those skilled in the art can clearly understand that, for the specific working processes of the systems, devices and units described above, reference may be made to the corresponding processes in the foregoing method embodiments, and for the sake of brevity, details are not described herein.

In addition, each functional unit in each embodiment of the present invention may be physically independent of each other, or two or more functional units may be integrated together, or all functional units may be integrated into one processing unit. The above-mentioned integrated functional units may be implemented in the form of hardware, and may also be implemented in the form of software or firmware.

Those skilled in the art can understand that: if the integrated functional unit is implemented in the form of software and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present invention or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, which includes several instructions to make a computer A computing device (such as a personal computer, a server, or a network device, etc.) executes all or part of the steps of the methods described in the embodiments of the present invention when running the instructions. The aforementioned storage medium includes: a U disk, a removable hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk and other media that can store program codes.

Alternatively, all or part of the steps of implementing the foregoing method embodiments may be accomplished by program instructions related to hardware (such as a personal computer, a server, or a computing device such as a network device), and the program instructions may be stored in a computer-readable storage In the medium, when the program instructions are executed by the processor of the computing device, the computing device executes all or part of the steps of the methods described in the embodiments of the present invention.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: Within the spirit and principle of the present invention, it is still possible to modify the technical solutions recorded in the foregoing embodiments, or to perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the corresponding technical solutions deviate protection scope of the present invention.

According to an aspect of the embodiments of the present invention, A1. a management method of a mobile device on a real machine test platform is provided, which is applied to the mobile device side, including:

After the mobile device is connected to the proxy server, start a designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation;

Detect the current device state of the mobile device through the designated daemon process, and determine whether the current device state is abnormal;

If so, obtain a test case script for maintaining the mobile device from the real machine test platform through the designated daemon process according to the information of the mobile device;

The test case script is parsed and executed by the designated daemon to maintain the mobile device.

A2. The method according to A1, wherein the designated daemon process is a java daemon process;

Start the specified daemon process in the mobile device through the proxy server without suspending the operation, including:

The target dex file is run in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon process.

A3. The method according to A2, wherein the target dex file is converted from an executable jar package containing device status monitoring and test case script execution logic through an Android software development kit, and is preconfigured in the in mobile devices.

A4. The method of A1, wherein the mobile device is connected to the proxy server through an adb command using USB or WiFi.

A5. The method according to A1, wherein detecting the current device state of the mobile device by the designated daemon process includes:

The current device state of the mobile device is periodically detected by the designated daemon.

A6. The method according to A1, wherein judging whether the current device state is abnormal comprises:

Determine if the USB connection is broken; and/or

Determines whether developer mode is automatically turned off.

A7. The method according to A1, wherein after detecting the current device state of the mobile device, further comprising:

The current device state of the mobile device is reported to the real device test platform.

A8. The method according to A1, wherein the test case script is pre-configured in the real machine test platform according to device model, operating system version and/or device exception type;

Obtain a test case script for maintaining the mobile device from the real machine test platform according to the information of the mobile device through the designated daemon, including:

Through the designated daemon process, a test case for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device script.

A9. The method according to A1, wherein the test case script is in json format.

A10. The method according to A1, wherein maintaining the mobile device includes:

Simulate user operations by specifying method names and parameters in the test case script.

A11. The method according to A10, wherein the user operation includes at least one of the following:

Sleep, swipe, tap.

A12. The method according to A1, wherein executing the test case script includes:

The test case script is executed by an automated testing framework.

A13. The method according to any one of A1-A12, wherein, further comprising:

If it is determined that the current device state is not abnormal, the designated daemon process is made to wait for the next detection of the current device state of the mobile device.

According to another aspect of the embodiments of the present invention, B14. A management device for a mobile device on a real machine test platform is also provided, which is applied to the mobile device and includes:

a process startup module, adapted to start a designated daemon process in the mobile device through the proxy server in a manner that does not suspend operation after the mobile device is connected to the proxy server;

a state detection module, adapted to detect the current device state of the mobile device through the designated daemon process, and determine whether the current device state is abnormal;

a script obtaining module, adapted to obtain a test case script for maintaining the mobile device from the real machine test platform through the designated daemon process according to the information of the mobile device if it is judged that the current device state is abnormal; as well as

The script parsing and execution module is adapted to parse and execute the test case script through the designated daemon process, so as to maintain the mobile device.

B15. The device according to B14, wherein the designated daemon process is a java daemon process;

The process startup module is also adapted to:

The target dex file is run in the mobile device through the nohup command of the adb process of the proxy server to start the java daemon process.

B16. The device according to B15, wherein the target dex file is converted from an executable jar package containing device status monitoring and test case script execution logic through an Android software development kit, and is preconfigured in the in mobile devices.

B17. The apparatus of B14, wherein the mobile device connects with the proxy server through an adb command using USB or WiFi.

B18. The apparatus of B14, wherein the state detection module is further adapted to:

The current device state of the mobile device is periodically detected by the designated daemon.

B19. The apparatus of B14, wherein the state detection module is further adapted to:

Determine if the USB connection is broken; and/or

Determines whether developer mode is automatically turned off.

B20. The apparatus of B14, wherein the state detection module is further adapted to:

After detecting the current device state of the mobile device, the current device state of the mobile device is reported to the real machine test platform.

B21. The apparatus according to B14, wherein the test case script is pre-configured in the real machine test platform according to device model, operating system version and/or device exception type;

The script acquisition module is also adapted to:

Through the designated daemon process, a test case for maintaining the mobile device is obtained from the real machine test platform according to the abnormal type of the current device state, the model of the mobile device and/or the operating system version of the mobile device script.

B22. The apparatus according to B14, wherein the test case script is in json format.

B23. The apparatus according to B14, wherein the script parsing execution module is further adapted to:

Simulate user operations by specifying method names and parameters in the test case script.

B24. The apparatus according to B23, wherein the user operation includes at least one of the following:

Sleep, swipe, tap.

B25. The apparatus according to B14, wherein the script parsing execution module is further adapted to:

The test case script is executed by an automated testing framework.

B26. The device according to any one of B14-B25, further comprising:

The process waiting module is adapted to make the designated daemon wait for the next detection of the current device state of the mobile device if it is determined that the current device state is not abnormal.

According to yet another aspect of the embodiments of the present invention, C27. A computer storage medium is also provided, the computer storage medium stores computer program code, when the computer program code is executed on a computing device, causes the computing device The management method of the mobile device on the real machine test platform according to any one of A1-A13 is executed.

According to yet another aspect of the embodiments of the present invention, D28. A computing device is also provided, comprising:

processor; and

memory in which computer program code is stored;

When the computer program code is executed by the processor, it causes the computing device to execute the method for managing a mobile device on a real machine test platform according to any one of A1-A13.

Claims (10)

1. A management method of mobile equipment on a real machine test platform is applied to a mobile equipment terminal and comprises the following steps:

after the mobile equipment is connected with the proxy server, starting a specified daemon process in the mobile equipment in a non-suspended running mode through the proxy server;

detecting the current equipment state of the mobile equipment through the designated daemon process, and judging whether the current equipment state is abnormal or not;

if so, acquiring a test case script for maintaining the mobile equipment from the real machine test platform through the specified daemon process according to the information of the mobile equipment;

and analyzing and executing the test case script through the specified daemon process so as to maintain the mobile equipment.

2. The method of claim 1, wherein the designated daemon is a java daemon;

launching, by the proxy server, a specified daemon in the mobile device in a non-suspended manner, comprising:

and running a target dex file in the mobile equipment through a nohup command of the adb process of the proxy server so as to start the java daemon.

3. The method of claim 2, wherein the target dex file is obtained by converting an executable jar package containing device state monitoring and test case script execution logic through an Android software development kit, and is configured in the mobile device in advance.

4. The method of claim 1, wherein the mobile device connects with the proxy server through an adb command using USB or WiFi.

5. The method of claim 1, wherein detecting, by the designated daemon, a current device state of the mobile device comprises:

and periodically detecting the current equipment state of the mobile equipment through the designated daemon process.

6. The method of claim 1, wherein determining whether the current device state is abnormal comprises:

judging whether the USB connection is broken; and/or

It is determined whether the developer mode is automatically turned off.

7. The method of claim 1, wherein upon detecting a current device state of the mobile device, further comprising:

and reporting the current equipment state of the mobile equipment to the real machine test platform.

8. A management device of mobile equipment on a real machine test platform is applied to a mobile equipment terminal and comprises:

the process starting module is suitable for starting a specified daemon process in the mobile equipment in a non-suspended running mode through the proxy server after the mobile equipment is connected with the proxy server;

the state detection module is suitable for detecting the current equipment state of the mobile equipment through the designated daemon process and judging whether the current equipment state is abnormal or not;

the script obtaining module is suitable for obtaining a test case script for maintaining the mobile equipment from the real machine test platform through the specified daemon process according to the information of the mobile equipment if the current equipment state is judged to be abnormal; and

and the script analysis execution module is suitable for analyzing and executing the test case script through the specified daemon process so as to maintain the mobile equipment.

9. A computer storage medium having computer program code stored thereon which, when run on a computing device, causes the computing device to perform a method of managing mobile devices on a live testing platform according to any of claims 1-7.

10. A computing device, comprising:

a processor; and

a memory storing computer program code;

the computer program code, when executed by the processor, causes the computing device to perform a method of managing mobile devices on a live testing platform according to any of claims 1-7.

Images