CN112579438A - Multifunctional automatic test tool and test method - Google Patents
Multifunctional automatic test tool and test method Download PDFInfo
- Publication number
- CN112579438A CN112579438A CN202011382616.1A CN202011382616A CN112579438A CN 112579438 A CN112579438 A CN 112579438A CN 202011382616 A CN202011382616 A CN 202011382616A CN 112579438 A CN112579438 A CN 112579438A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- testing
- unit
- parameters
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a multifunctional automatic testing tool, which comprises: testing the main interface; the performance testing module is arranged on the testing main interface and used for testing the performance of the android application; the stability testing module is arranged on the testing main interface and used for testing the stability of the android application; and the interface testing module is arranged on the testing main interface and used for testing the interface. The invention also discloses a multifunctional automatic test method, the interface test obtains the interface test result by calling the interface test module at the test main interface, the stability test of the android application obtains the stability test result by calling the stability test module at the test main interface, and the performance test of the android application obtains the performance test result by calling the performance test module at the test main interface. The testing tool has the functions of interface testing and android application stability and performance testing, provides a visual interface, simplifies the testing operation process and reduces the technical requirements on testers.
Description
Technical Field
The invention relates to the technical field of automatic testing. More specifically, the invention relates to a multifunctional automated testing tool and a testing method based on interface testing and android application performance and stability testing.
Background
With the rapid increase of the usage amount of the android system, the number of android applications is rapidly increased, and the development of the applications cannot be separated from the testing of software products. At present, an adb command and a monkey command are generally used for testing the stability and performance of Android applications, an adb tool in Android sdk can directly operate and manage an Android simulator or a real Android device (such as a G1 mobile phone), and performance tests of power consumption, flow, starting time, memory, CPU and the like of the Android applications can be realized by operating a shell (command line). The Monkey test is used for testing the stability of the android application by simulating key input, touch screen input, gesture input and the like of a user. However, when testing, the adb command and the monkey command need to enter a command line of the operating system first, then the relevant adb command is input into the command line, and the operating system executes subsequent business logic operations after acquiring the relevant adb command.
Interface test is mainly used for testing interfaces between a system and other external systems and interfaces between submodules in the system, and currently, a Jmeter or Postman tool is mainly used for interface test, wherein the interface test tool acquires basic information of the interfaces by providing an interface input interface and then executes subsequent business logic operation. When the interface test tool is used, the information input of the interface needs to be input respectively, and the operation of inputting the information also has stronger technical performance.
Currently, the interface test and the performance test are separated, the interface test is to be performed in an interface test tool, and the android performance and stability test is to be performed in a command line of an operating system. Both the interface test and the android application performance and stability test require strong technical capability and are not suitable for all users. In addition, the performance and stability test results of the conventional interface test and android application are relatively complex, and the reading of information by common technicians is troublesome, which also puts forward higher requirements on the testing technicians. Therefore, the development of a tool capable of simultaneously realizing the interface test and the performance and stability test of android application has wide application prospect.
Disclosure of Invention
An object of the present invention is to solve at least the above problems and to provide at least the advantages described later.
The invention also aims to provide a multifunctional automatic testing tool, which integrates the functions of interface testing and android application stability and performance testing.
The invention also aims to provide a multifunctional automatic testing method, which integrates the functions of interface testing and android application stability and performance testing, and simplifies the operation and processing of technical testers.
To achieve these objects and other advantages in accordance with the purpose of the invention, there is provided a multifunctional automated testing tool comprising:
testing the main interface;
the performance testing module is arranged on the testing main interface and used for testing the performance of the android application, and the performance testing comprises a starting time test, a CPU test, a flow test, a memory test and a power consumption test;
the stability testing module is arranged on the testing main interface and used for testing the stability of the android application;
and the interface testing module is arranged on the testing main interface and used for testing the interface.
Preferably, the multifunctional automated testing tool, the stability testing module comprises:
the Monkey test interface is used for displaying stability parameters and stability test results of the stability test;
the stability parameter setting unit is used for setting stability parameters related to the application stability of the android testing device on a Monkey testing interface when the android testing device is successfully connected with the testing PC, and the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100;
the stability testing unit comprises a first splicing unit, a first execution unit and a first analysis unit, wherein the first splicing unit is used for acquiring stability parameters in a Monkey testing interface and splicing the stability parameters into a first adb command, the first execution unit is used for creating a thread pool and calling Runtime classes in the thread pool to execute the first adb command, and the first analysis unit is used for acquiring a returned result of the first execution unit in real time and analyzing the returned result to acquire a stability testing result;
and the stability result output unit is used for outputting and displaying the stability test result analyzed by the first analysis unit on a Monkey test interface.
Preferably, the multifunctional automated testing tool comprises: the system comprises a starting time testing submodule for starting time testing, a CPU testing submodule for CPU testing, a flow testing submodule for flow testing, a memory testing submodule for memory testing and a power consumption testing submodule for power consumption testing.
Preferably, the multifunctional automated testing tool, wherein the start time testing submodule comprises:
the starting time test interface is used for displaying starting time parameters of the starting time test and starting time test results;
the starting time parameter setting unit is used for setting starting time parameters related to the application of the android testing device in a starting time testing interface when the android testing device is successfully connected with the testing PC, wherein the starting time parameters include an android device number, an application package name and a starting mode, and the starting mode is starting for the first time or starting for the non-first time;
the starting time testing unit comprises a second splicing unit, a second execution unit and a second analysis unit, wherein the second splicing unit is used for acquiring starting time parameters in a starting time testing interface and splicing the starting time parameters into a second adb command, the second execution unit is used for calling a Runtime class to execute the second adb command, and the second analysis unit is used for acquiring a returned result of the second execution unit and analyzing the returned result to acquire a starting time testing result;
the starting time result output unit is used for outputting and displaying the starting time test result analyzed by the second analysis unit on a starting time test interface;
wherein the power consumption test submodule comprises:
the power consumption test interface is used for displaying power consumption parameters and power consumption test results of the power consumption test;
the power consumption parameter setting unit is used for setting power consumption parameters related to the application of the android testing device on a power consumption testing interface when the android testing device is successfully connected with the testing PC, wherein the power consumption parameters include the number of the android testing device, the name of an application package and the state of the testing application, and the state of the testing application is in use, in operation or in closing;
the power consumption test unit comprises a third splicing unit, a third execution unit and a third analysis unit, wherein the third splicing unit is used for acquiring power consumption parameters in a power consumption test interface and splicing the power consumption parameters into a third adb command, the third execution unit is used for calling a Runtime class to execute the third adb command, and the third analysis unit is used for acquiring a result returned by the third execution unit and analyzing the result to obtain a power consumption test result;
and the power consumption result output unit is used for outputting and displaying the power consumption test result analyzed by the third analysis unit on a power consumption test interface.
Preferably, the multifunctional automated testing tool, wherein the CPU testing submodule includes:
the CPU test interface is used for displaying CPU parameters and CPU test results of the CPU test;
the CPU parameter setting unit is used for setting CPU parameters related to the application of the android testing device on a CPU testing interface when the android testing device is successfully connected with the testing PC, wherein the CPU parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the CPU test unit comprises a fourth splicing unit, a fourth execution unit and a fourth analysis unit, wherein the fourth splicing unit is used for acquiring CPU parameters in a CPU test interface and splicing the CPU parameters into a fourth adb command, the fourth execution unit is used for creating a first thread and calling a Runtime class in the first thread to execute the fourth adb command, and the fourth analysis unit is used for acquiring a returned result of the fourth execution unit in real time and analyzing the returned result to acquire a CPU test result;
the CPU result output unit is used for outputting and displaying the CPU test result analyzed by the fourth analysis unit on a CPU test interface;
wherein, the flow test submodule comprises:
the flow test interface is used for displaying flow parameters and flow test results of the flow test;
the flow parameter setting unit is used for setting flow parameters related to the application of the android testing device on a flow testing interface when the android testing device is successfully connected with the testing PC, wherein the flow parameters include an android device number, an application package name, execution time and refreshing time;
the flow test unit comprises a fifth splicing unit, a fifth execution unit and a fifth analysis unit, wherein the fifth splicing unit is used for acquiring flow parameters in the flow test interface and splicing the flow parameters into a fifth adb command, the fifth execution unit is used for creating a second thread and calling a Runtime class in the second thread to execute the fifth adb command, and the fifth analysis unit is used for acquiring a return result of the fifth execution unit in real time and analyzing the return result to acquire a flow test result;
the flow result output unit is used for outputting and displaying the flow test result analyzed by the fifth analysis unit on a flow test interface;
wherein, the memory test submodule comprises:
the memory test interface is used for displaying memory parameters and memory test results of the memory test;
the memory parameter setting unit is used for setting memory parameters related to the application of the android testing device in a memory testing interface when the android testing device is successfully connected with the testing PC, wherein the memory parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the memory test unit comprises a sixth splicing unit, a sixth execution unit and a sixth analysis unit, wherein the sixth splicing unit is used for acquiring memory parameters in the memory test interface and splicing the memory parameters into a sixth adb command, the sixth execution unit is used for creating a third thread and calling a Runtime class in the third thread to execute the sixth adb command, and the sixth analysis unit is used for acquiring a return result of the sixth execution unit in real time and analyzing the return result to acquire a memory test result;
and the memory result output unit is used for outputting and displaying the memory test result analyzed by the sixth analysis unit on a memory test interface.
Preferably, the multifunctional automated testing tool, the interface testing module comprises:
the interface test interface is used for displaying interface parameters and interface test results of the interface test;
the interface parameter setting unit is used for setting interface parameters related to a test interface on the interface test interface, wherein the interface parameters comprise a request mode, a request address, a test concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode;
the interface testing unit comprises an obtaining unit for obtaining interface parameters in an interface testing interface, a calling unit for calling the http policy to send an interface request through the interface parameters, and a seventh analyzing unit for obtaining the http policy object returned by the calling unit and analyzing the http policy object to obtain an interface testing result;
and the interface result output unit is used for outputting and displaying the interface test result analyzed by the seventh analysis unit on an interface test interface.
The invention also discloses a multifunctional automatic test method, the interface test obtains the interface test result by calling the interface test module at the test main interface, the stability test of the android application obtains the stability test result by calling the stability test module at the test main interface, and the performance test of the android application obtains the performance test result by calling the performance test module at the test main interface.
Preferably, the multifunctional automated testing method comprises the following steps: the interface testing method comprises the steps that a user inputs interface parameters related to interface testing on an interface testing interface through an interface parameter setting unit, an obtaining unit obtains the interface parameters in the interface testing interface, then a calling unit calls an HttpClient to send an interface request through the interface parameters, a seventh analyzing unit obtains an HttpResponse object returned by the calling unit and analyzes the HttpResponse object to obtain an interface testing result, and then an interface result output unit outputs and displays the interface testing result on the interface testing interface, wherein the interface parameters comprise a request mode, a request address, a testing concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode.
Preferably, the multifunctional automated testing method comprises the following steps: the user inputs stability parameters related to stability of the android application on a Monkey test interface through a stability parameter setting unit, a first splicing unit obtains the stability parameters in the Monkey test interface and splices the stability parameters into a first adb command, a first execution unit creates a thread pool, the thread pool calls Runtime classes to execute the first adb command, a first analysis unit obtains a return result of the first execution unit in real time and analyzes the return result to obtain a stability test result, and the stability test result of the android application is output and displayed on the Monkey test interface through a stability result output unit, wherein the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; and the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100.
Preferably, the method for testing the starting time in the android application performance test comprises the following steps: a user inputs a starting time parameter related to starting time of an android application in a starting time test interface through a starting time parameter setting unit, a second splicing unit obtains the starting time parameter in the starting time test interface and splices the starting time parameter into a second adb command, a second execution unit calls Runtime to execute the second adb command, a second analysis unit obtains a result returned by the second execution unit and analyzes the result to obtain a starting time test result, and then the starting time test result of the android application is output and displayed on the starting time test interface through a starting time result output unit, wherein the starting time parameter comprises an android equipment number, an application package name and a starting mode, and the starting mode is first starting or non-first starting;
the method for testing the power consumption in the android application performance test comprises the following steps: a user inputs power consumption parameters related to the power consumption of an android application in a power consumption test interface through a power consumption parameter setting unit, a third splicing unit obtains the power consumption parameters in the power consumption test interface and splices the power consumption parameters into a third adb command, a third execution unit calls Runtime classes to execute the third adb command, a third analysis unit obtains a result returned by the third execution unit and analyzes the result to obtain a power consumption test result, and then the power consumption test result of the android application is output and displayed in the power consumption test interface through a power consumption result output unit, wherein the power consumption parameters comprise the number of the android device, the name of an application package and the state of the test application, and the state of the test application is in use, in operation and in closing;
the method for testing the CPU in the android application performance test comprises the following steps: a user inputs CPU parameters related to an android application CPU on a CPU test interface through a CPU parameter setting unit, a fourth splicing unit obtains the CPU parameters in the CPU test interface and splices the CPU parameters into a fourth adb command, a fourth execution unit creates a first thread and calls Runtime classes in the first thread to execute the fourth adb command, a fourth analysis unit obtains a result returned by the fourth execution unit and analyzes the result to obtain a CPU test result, and the CPU test result of the android application is output and displayed on the CPU test interface through a CPU result output unit, wherein the CPU parameters comprise an android device number, an application package name, execution time and refreshing time;
the flow testing method in the android application performance test comprises the following steps: a user inputs flow parameters related to android application flow in a flow test interface through a flow parameter setting unit, a fifth splicing unit obtains the flow parameters in the flow test interface and splices the flow parameters into a fifth adb command, a fifth execution unit creates a second thread and calls Runtime classes in the second thread to execute the fifth adb command, a fifth analysis unit obtains a result returned by the fifth execution unit and analyzes the result to obtain a flow test result, and the flow test result of the android application is output and displayed on the flow test interface through a flow result output unit, wherein the flow parameters comprise an android device number, an application package name, execution time and refresh time;
the method for testing the memory in the android application performance test comprises the following steps: a user inputs memory parameters related to an android application memory on a memory test interface through a memory parameter setting unit, a sixth splicing unit obtains the memory parameters in the memory test interface and splices the memory parameters into a sixth adb command, a sixth execution unit creates a third thread and calls Runtime classes in the third thread to execute the sixth adb command, a sixth analysis unit obtains a result returned by the sixth execution unit and analyzes the result to obtain a memory test result, and the memory test result of the android application is output and displayed on the memory test interface through a memory result output unit, wherein the memory parameters comprise an android device number, an application package name, execution time and refresh time.
The invention at least comprises the following beneficial effects:
the multifunctional automatic test tool and the method integrate the interface test and the android application performance and stability test, provide a visual test interface, simplify the operation steps of the interface test, the android application performance test and the stability test, make the test result clear, make common testers perform the test, and reduce the technical requirements on the testers.
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention.
Drawings
FIG. 1 is a schematic diagram of the multifunctional automated test tool of the present invention;
FIG. 2 is a schematic diagram of the stability test module according to the present invention;
FIG. 3 is a schematic diagram of the start time test submodule of the present invention;
FIG. 4 is a schematic diagram of the interface test module according to the present invention;
FIG. 5 is a flow chart of a testing method of the interface test according to the present invention;
FIG. 6 is a schematic flow chart of a testing method for a stability test of an android application according to the present invention;
fig. 7 is a schematic flow chart of a testing method for testing the starting time in the android application performance test of the present invention.
Detailed Description
The present invention is further described in detail below with reference to the attached drawings so that those skilled in the art can implement the invention by referring to the description text.
It should be noted that the experimental methods described in the following embodiments are all conventional methods unless otherwise specified.
ADB is named as Android Debug Bridge, and can be used for operating a command line of a mobile phone device or a simulator.
Monkey command: monkey is a command line tool in Android, and sends a pseudo-random user event stream (such as key input, touch screen input, gesture input, and the like) to a system to realize stress testing on a mobile phone application program. The Monkey test is used for testing the stability of the android application by simulating key input, touch screen input, gesture input and the like of a user.
And (3) performance testing: various performance indexes of the system are tested by simulating various normal, peak and abnormal load conditions through an automatic testing tool.
Interface testing: the interface test of the present application is directed to an interface of a software class, and a specific interface test scheme described below is specifically directed to an interface which can obtain a request result in a Get mode or a Post mode.
As shown in fig. 1, the present invention provides a multifunctional automated testing tool, comprising:
testing the main interface;
the performance testing module is arranged on the testing main interface and used for testing the performance of the android application, and the performance testing comprises a starting time test, a CPU test, a flow test, a memory test and a power consumption test;
the stability testing module is arranged on the testing main interface and used for testing the stability of the android application;
and the interface testing module is arranged on the testing main interface and used for testing the interface.
The invention also provides a multifunctional automatic test method, the interface test obtains the interface test result by calling the interface test module at the test main interface, the stability test of the android application obtains the stability test result by calling the stability test module at the test main interface, and the performance test of the android application obtains the performance test result by calling the performance test module at the test main interface.
In this technical scheme, with the interface test, the stability test and the capability test integration of tall and erect application of ann are in a testing tool, and, when having changed technical staff in the past and carrying out stability test and capability test to tall and erect application of ann, need pass through operating system's command line to the mode of complicated loaded down with trivial details adb order of test item input, this instrument only needs the technical staff to install the testing tool among this technical scheme in test PC, when the stability and the performance of using on the tall and erect equipment of ann will be tested, tall and erect equipment of ann that will await measuring is connected with test PC, get into the test main interface of testing tool, carry out the functional test of the corresponding application of tall and erect equipment of ann through corresponding test module respectively, to the interface test, then need not to connect tall and erect equipment of ann and test PC. The tool greatly simplifies the operation and the processing of testing technicians, improves the working efficiency of the test, reduces the technical requirements on the testing technicians, and improves the adaptability of the testing tool.
In another embodiment, as shown in fig. 2, the stability testing module includes:
the Monkey test interface is used for displaying stability parameters and stability test results of the stability test;
the stability parameter setting unit is used for setting stability parameters related to the application stability of the android testing device on a Monkey testing interface when the android testing device is successfully connected with the testing PC, and the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100;
the stability testing unit comprises a first splicing unit, a first execution unit and a first analysis unit, wherein the first splicing unit is used for acquiring stability parameters in a Monkey testing interface and splicing the stability parameters into a first adb command, the first execution unit is used for creating a thread pool and calling Runtime classes in the thread pool to execute the first adb command, and the first analysis unit is used for acquiring a returned result of the first execution unit in real time and analyzing the returned result to acquire a stability testing result;
and the stability result output unit is used for outputting and displaying the stability test result analyzed by the first analysis unit on a Monkey test interface.
In the multifunctional automated testing method, as shown in fig. 6, the testing method for the stability test of the android application is as follows: the user inputs stability parameters related to stability of the android application on a Monkey test interface through a stability parameter setting unit, a first splicing unit obtains the stability parameters in the Monkey test interface and splices the stability parameters into a first adb command, a first execution unit creates a thread pool, the thread pool calls Runtime classes to execute the first adb command, a first analysis unit obtains a return result of the first execution unit in real time and analyzes the return result to obtain a stability test result, and the stability test result of the android application is output and displayed on the Monkey test interface through a stability result output unit, wherein the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; and the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100.
In this technical scheme, when testing technical personnel will test the stability that the android device that awaits measuring was used, on the PC of installing this technical scheme's testing tool, connect PC and the android device that awaits measuring, get into the test main interface of testing tool, then get into Monkey test interface through the stability module, wherein the equipment number of the android device that awaits measuring is connected the back system automatic acquisition at the android device that awaits measuring and PC, the testing personnel need input concrete application package name, the number of execution times, the seed number, delay time, execution mode and log level, for example: when the stability of the Taobao applied to the android device is tested, the name of an application package is input to com, Taobao and Taobao, the execution times are input to 10000, the seed number is input to 10000, the delay time(s) is 500, the log grade can be selected to be detailed, simple and general according to the requirement, and the detail, simple and general correspond to the content grade of the test result;
in addition, the second type of parameters, namely the touch event parameter, the screen-swiping event parameter, the main navigation event parameter, the navigation event parameter and the system key event parameter, are set according to the test requirements, and the set parameters represent the number of times that a tester wants to perform operations on the treasure-panning application, if the touch event is set to be 100, the touch event means that the treasure-panning application is subjected to 100 touch operations in the test, and if the touch event parameter is set to be 0, the touch event means that the touch operation is not performed on the treasure-panning application in the operation. However, it should be noted that the sum of the values of all the parameters of the second type is 100;
and after the stability parameters related to the application to be tested are input, starting the test, sequentially executing the stability test unit and the stability result output unit, and obtaining a corresponding test result on a Monkey test interface.
In another technical solution, as shown in fig. 1, the multifunctional automated testing tool includes: the system comprises a starting time testing submodule for starting time testing, a CPU testing submodule for CPU testing, a flow testing submodule for flow testing, a memory testing submodule for memory testing and a power consumption testing submodule for power consumption testing.
The multifunctional automated testing tool, as shown in fig. 3, the start time testing submodule includes:
the starting time test interface is used for displaying starting time parameters of the starting time test and starting time test results;
the starting time parameter setting unit is used for setting starting time parameters related to the application of the android testing device in a starting time testing interface when the android testing device is successfully connected with the testing PC, wherein the starting time parameters include an android device number, an application package name and a starting mode, and the starting mode is starting for the first time or starting for the non-first time;
the starting time testing unit comprises a second splicing unit, a second execution unit and a second analysis unit, wherein the second splicing unit is used for acquiring starting time parameters in a starting time testing interface and splicing the starting time parameters into a second adb command, the second execution unit is used for calling a Runtime class to execute the second adb command, and the second analysis unit is used for acquiring a returned result of the second execution unit and analyzing the returned result to acquire a starting time testing result;
and the starting time result output unit is used for outputting and displaying the starting time test result analyzed by the second analysis unit on the starting time test interface.
In the multifunctional automated testing method, as shown in fig. 7, the method for starting the time test in the android application performance test includes: a user inputs starting time parameters related to starting time of an android application on a starting time test interface through a starting time parameter setting unit, a second splicing unit obtains the starting time parameters in the starting time test interface and splices the starting time parameters into a second adb command, a second execution unit calls Runtime type to execute the second adb command, a second analysis unit obtains a return result of the second execution unit and analyzes the return result to obtain a starting time test result, and then the starting time test result of the android application is output and displayed on the starting time test interface through a starting time result output unit, wherein the starting time parameters comprise an android equipment number, an application package name and a starting mode, and the starting mode is first starting or non-first starting.
In this technical scheme, when the test technical staff will test the start time that the android device that awaits measuring used, on the PC of installing this technical scheme's testing tool, connect PC and the android device that awaits measuring, get into the test main interface of testing tool, then get into start time test interface through the start time test submodule piece among the capability test module, wherein the equipment number of the android device that awaits measuring is connected the back system automatic acquisition at the android device that awaits measuring and PC, test technical staff need input specific application package name to and select the start mode, for example: when testing the starting time of the Taobao applied to the android device, inputting' com.
And after the input of the starting time parameters related to the application to be tested is finished, starting the test, sequentially executing a starting time test unit and a starting time result output unit, and obtaining a corresponding test result on a starting time test interface.
The multifunctional automated testing tool, wherein the power consumption test submodule comprises:
the power consumption test interface is used for displaying power consumption parameters and power consumption test results of the power consumption test;
the power consumption parameter setting unit is used for setting power consumption parameters related to the application of the android testing device on a power consumption testing interface when the android testing device is successfully connected with the testing PC, wherein the power consumption parameters include the number of the android testing device, the name of an application package and the state of the testing application, and the state of the testing application is in use, in operation or in closing;
the power consumption test unit comprises a third splicing unit, a third execution unit and a third analysis unit, wherein the third splicing unit is used for acquiring power consumption parameters in a power consumption test interface and splicing the power consumption parameters into a third adb command, the third execution unit is used for calling a Runtime class to execute the third adb command, and the third analysis unit is used for acquiring a result returned by the third execution unit and analyzing the result to obtain a power consumption test result;
and the power consumption result output unit is used for outputting and displaying the power consumption test result analyzed by the third analysis unit on a power consumption test interface.
The method for testing the power consumption in the android application performance test comprises the following steps: the power consumption parameter setting unit is used for inputting power consumption parameters related to android application power consumption in a power consumption testing interface, the third splicing unit is used for obtaining the power consumption parameters in the power consumption testing interface and splicing the power consumption parameters into a third adb command, the third execution unit calls Runtime classes to execute the third adb command, the third analyzing unit is used for obtaining a return result of the third execution unit and analyzing the return result to obtain a power consumption testing result, the power consumption testing result of the android application is output and displayed on the power consumption testing interface through the power consumption result output unit, the power consumption parameters comprise an android device number, an application package name and a testing application state, and the testing application state is in use, in operation and in closing.
In this technical scheme, when the test technical staff will test the power consumption that the android device that awaits measuring used, on the PC of installing this technical scheme's testing tool, connect PC and the android device that awaits measuring, get into the test main interface of testing tool, then get into the power consumption test interface through the power consumption test submodule piece among the capability test module, wherein the equipment number of the android device that awaits measuring is connected the back system automatic acquisition at the android device that awaits measuring and PC, test technical staff need input specific application package name to and select the state that the test was used, for example: when the testing panning application is used for power consumption of the android device, the name of an application package is input to com.
In the test process, the following steps are required: firstly, connecting an android device and a PC through a USB; closing other irrelevant application software; inputting power consumption parameters; starting a power consumption test starting button; disconnecting the USB connection; sixthly, operating the android device according to the state of the selected test application, for example, using the treasure washing application in the android device for a period of time, or waiting for a period of time or closing for a period of time; seventhly, connecting the android device and the PC again through the USB, starting a power consumption test ending button, and obtaining a test result of the tested elutriation device in a corresponding state; and the test result is displayed on a starting time test interface. The power consumption test starting button and the power consumption test ending button correspond to the control of starting execution and ending execution of the power consumption test unit.
The multifunctional automated testing tool, wherein, the CPU test submodule includes:
the CPU test interface is used for displaying CPU parameters and CPU test results of the CPU test;
the CPU parameter setting unit is used for setting CPU parameters related to the application of the android testing device on a CPU testing interface when the android testing device is successfully connected with the testing PC, wherein the CPU parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the CPU test unit comprises a fourth splicing unit, a fourth execution unit and a fourth analysis unit, wherein the fourth splicing unit is used for acquiring CPU parameters in a CPU test interface and splicing the CPU parameters into a fourth adb command, the fourth execution unit is used for creating a first thread and calling a Runtime class in the first thread to execute the fourth adb command, and the fourth analysis unit is used for acquiring a returned result of the fourth execution unit in real time and analyzing the returned result to acquire a CPU test result;
and the CPU result output unit is used for outputting and displaying the CPU test result analyzed by the fourth analysis unit on a CPU test interface.
The method for testing the CPU in the android application performance test comprises the following steps: a user inputs CPU parameters related to an android application CPU on a CPU test interface through a CPU parameter setting unit, a fourth splicing unit obtains the CPU parameters in the CPU test interface and splices the CPU parameters into a fourth adb command, a fourth execution unit creates a first thread and calls Runtime classes in the first thread to execute the fourth adb command, a fourth analysis unit obtains a result returned by the fourth execution unit and analyzes the result to obtain a CPU test result, and the CPU test result of the android application is output and displayed on the CPU test interface through a CPU result output unit, wherein the CPU parameters comprise an android device number, an application package name, execution time and refreshing time.
In this technical scheme, when testing technical staff wants to test the occupation ratio of the CPU of the android device application that awaits measuring in cell-phone CPU, on the PC of the test tool who installs this technical scheme, connect PC and the android device that awaits measuring, get into the test main interface of test tool, then get into CPU test interface through the CPU test submodule piece in the capability test module, wherein the equipment number of the android device that awaits measuring is automatic to be obtained at the android device that awaits measuring and PC connection back system, testing technical staff need input concrete application package name, test execution time (in minutes), and refresh time (in seconds), for example: when the Taobao is tested and applied to the CPU of the android device, the name of an application package is input to 'com.taobao.taobao', the execution time can be input to '10', and the refresh time is input to '3', namely the CPU occupancy rate of the android device is occupied by the Taobao within 10 minutes every 3 seconds.
After the CPU parameters related to the application to be tested are input, starting the test, sequentially executing a CPU test unit and a CPU result output unit, and obtaining a corresponding test result on a CPU test interface.
The multifunctional automated testing tool, wherein the flow test submodule comprises:
the flow test interface is used for displaying flow parameters and flow test results of the flow test;
the flow parameter setting unit is used for setting flow parameters related to the application of the android testing device on a flow testing interface when the android testing device is successfully connected with the testing PC, wherein the flow parameters include an android device number, an application package name, execution time and refreshing time;
the flow test unit comprises a fifth splicing unit, a fifth execution unit and a fifth analysis unit, wherein the fifth splicing unit is used for acquiring flow parameters in the flow test interface and splicing the flow parameters into a fifth adb command, the fifth execution unit is used for creating a second thread and calling a Runtime class in the second thread to execute the fifth adb command, and the fifth analysis unit is used for acquiring a return result of the fifth execution unit in real time and analyzing the return result to acquire a flow test result;
and the flow result output unit is used for outputting and displaying the flow test result analyzed by the fifth analysis unit on a flow test interface.
The flow testing method in the android application performance test comprises the following steps: a user inputs flow parameters related to android application flow in a flow test interface through a flow parameter setting unit, a fifth splicing unit obtains the flow parameters in the flow test interface and splices the flow parameters into a fifth adb command, a fifth execution unit creates a second thread and calls Runtime classes in the second thread to execute the fifth adb command, a fifth analysis unit obtains a result returned by the fifth execution unit and analyzes the result to obtain a flow test result, and the flow test result of the android application is output and displayed on the flow test interface through a flow result output unit, wherein the flow parameters comprise an android device number, an application package name, execution time and refresh time.
In this technical scheme, when the test technical staff wants to test the flow that uses in the android device that awaits measuring, on the PC of installing this technical scheme's testing tool, connect PC and the android device that awaits measuring, get into the test main interface of testing tool, then get into flow test interface through the flow test submodule piece among the capability test module, wherein the equipment number of the android device that awaits measuring is connected the back system automatic acquisition at android device that awaits measuring and PC, test technical staff need input concrete application package name, test execution time (in minutes), and refresh time (in seconds), for example: when testing the flow consumed by the Taobao application on the android device, the application package name is input to com.
After the flow parameters related to the application to be tested are input, the test is started, the flow test unit and the flow result output unit are sequentially executed, and a corresponding test result is obtained on a flow test interface.
The multifunctional automated testing tool, wherein the memory testing submodule comprises:
the memory test interface is used for displaying memory parameters and memory test results of the memory test;
the memory parameter setting unit is used for setting memory parameters related to the application of the android testing device in a memory testing interface when the android testing device is successfully connected with the testing PC, wherein the memory parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the memory test unit comprises a sixth splicing unit, a sixth execution unit and a sixth analysis unit, wherein the sixth splicing unit is used for acquiring memory parameters in the memory test interface and splicing the memory parameters into a sixth adb command, the sixth execution unit is used for creating a third thread and calling a Runtime class in the third thread to execute the sixth adb command, and the sixth analysis unit is used for acquiring a return result of the sixth execution unit in real time and analyzing the return result to acquire a memory test result;
and the memory result output unit is used for outputting and displaying the memory test result analyzed by the sixth analysis unit on a memory test interface.
The method for testing the memory in the android application performance test comprises the following steps: a user inputs memory parameters related to an android application memory on a memory test interface through a memory parameter setting unit, a sixth splicing unit obtains the memory parameters in the memory test interface and splices the memory parameters into a sixth adb command, a sixth execution unit creates a third thread and calls Runtime classes in the third thread to execute the sixth adb command, a sixth analysis unit obtains a result returned by the sixth execution unit and analyzes the result to obtain a memory test result, and the memory test result of the android application is output and displayed on the memory test interface through a memory result output unit, wherein the memory parameters comprise an android device number, an application package name, execution time and refresh time.
In this technical scheme, when the test technical staff will test the shared memory of the android device application that awaits measuring, on the PC of the testing tool who installs this technical scheme, connect PC and the android device that awaits measuring, get into the test main interface of testing tool, then get into the memory test interface through the memory test submodule piece in the capability test module, wherein the equipment number of the android device that awaits measuring is connected the back system automatic acquisition at the android device that awaits measuring and PC, the test technical staff need input concrete application package name, test execution time (in minutes), and refresh time (in seconds), for example: when the test elutriation is applied to the occupied memory of the android device, the name of an application package is input to com.
After the memory parameters related to the application to be tested are input, starting the test, sequentially executing the memory test unit and the memory result output unit, and obtaining a corresponding test result on a memory test interface.
In another technical solution, as shown in fig. 4, the interface testing module of the multifunctional automated testing tool includes:
the interface test interface is used for displaying interface parameters and interface test results of the interface test;
the interface parameter setting unit is used for setting interface parameters related to a test interface on the interface test interface, wherein the interface parameters comprise a request mode, a request address, a test concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode;
the interface testing unit comprises an obtaining unit for obtaining interface parameters in an interface testing interface, a calling unit for calling the http policy to send an interface request through the interface parameters, and a seventh analyzing unit for obtaining the http policy object returned by the calling unit and analyzing the http policy object to obtain an interface testing result;
and the interface result output unit is used for outputting and displaying the interface test result analyzed by the seventh analysis unit on an interface test interface.
As shown in fig. 5, the multifunctional automated testing method includes the following steps: the interface testing method comprises the steps that a user inputs interface parameters related to interface testing on an interface testing interface through an interface parameter setting unit, an obtaining unit obtains the interface parameters in the interface testing interface, then a calling unit calls an HttpClient to send an interface request through the interface parameters, a seventh analyzing unit obtains an HttpResponse object returned by the calling unit and analyzes the HttpResponse object to obtain an interface testing result, and then an interface result output unit outputs and displays the interface testing result on the interface testing interface, wherein the interface parameters comprise a request mode, a request address, a testing concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode.
In the technical scheme, when a test technician needs to perform interface test, the test technician enters a test main interface of the test tool on a PC (personal computer) provided with the test tool of the technical scheme, and then enters an interface test interface through an interface test module, the test technician needs to select a request mode (a Get mode or a Post mode), input an address and concurrency number of a request interface, and can selectively set a request head parameter and a request body parameter according to an actual interface to be tested. The request address of the interface is the request address of the interface to be tested, and can be the interface request address of a certain application in the android device, and also can be the interface request address of a certain application or a webpage on the test PC.
After the input of the interface parameters related to the interface to be tested is finished, the test is started, the interface test unit and the interface result output unit are sequentially executed, and the corresponding test result is obtained on the interface test interface.
While embodiments of the invention have been described above, it is not limited to the applications set forth in the description and the embodiments, which are fully applicable in various fields of endeavor to which the invention pertains, and further modifications may readily be made by those skilled in the art, it being understood that the invention is not limited to the details shown and described herein without departing from the general concept defined by the appended claims and their equivalents.
Claims (10)
1. Multi-functional automatic test tool, its characterized in that includes:
testing the main interface;
the performance testing module is arranged on the testing main interface and used for testing the performance of the android application, and the performance testing comprises a starting time test, a CPU test, a flow test, a memory test and a power consumption test;
the stability testing module is arranged on the testing main interface and used for testing the stability of the android application;
and the interface testing module is arranged on the testing main interface and used for testing the interface.
2. The multi-functional automated test tool of claim 1, wherein the stability testing module comprises:
the Monkey test interface is used for displaying stability parameters and stability test results of the stability test;
the stability parameter setting unit is used for setting stability parameters related to the application stability of the android testing device on a Monkey testing interface when the android testing device is successfully connected with the testing PC, and the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100;
the stability testing unit comprises a first splicing unit, a first execution unit and a first analysis unit, wherein the first splicing unit is used for acquiring stability parameters in a Monkey testing interface and splicing the stability parameters into a first adb command, the first execution unit is used for creating a thread pool and calling Runtime classes in the thread pool to execute the first adb command, and the first analysis unit is used for acquiring a returned result of the first execution unit in real time and analyzing the returned result to acquire a stability testing result;
and the stability result output unit is used for outputting and displaying the stability test result analyzed by the first analysis unit on a Monkey test interface.
3. The multi-functional automated test tool of claim 1, wherein the performance testing module comprises: the system comprises a starting time testing submodule for starting time testing, a CPU testing submodule for CPU testing, a flow testing submodule for flow testing, a memory testing submodule for memory testing and a power consumption testing submodule for power consumption testing.
4. The multi-functional automated test tool of claim 3, wherein the start time test submodule comprises:
the starting time test interface is used for displaying starting time parameters of the starting time test and starting time test results;
the starting time parameter setting unit is used for setting starting time parameters related to the application of the android testing device in a starting time testing interface when the android testing device is successfully connected with the testing PC, wherein the starting time parameters include an android device number, an application package name and a starting mode, and the starting mode is starting for the first time or starting for the non-first time;
the starting time testing unit comprises a second splicing unit, a second execution unit and a second analysis unit, wherein the second splicing unit is used for acquiring starting time parameters in a starting time testing interface and splicing the starting time parameters into a second adb command, the second execution unit is used for calling a Runtime class to execute the second adb command, and the second analysis unit is used for acquiring a returned result of the second execution unit and analyzing the returned result to acquire a starting time testing result;
the starting time result output unit is used for outputting and displaying the starting time test result analyzed by the second analysis unit on a starting time test interface;
wherein the power consumption test submodule comprises:
the power consumption test interface is used for displaying power consumption parameters and power consumption test results of the power consumption test;
the power consumption parameter setting unit is used for setting power consumption parameters related to the application of the android testing device on a power consumption testing interface when the android testing device is successfully connected with the testing PC, wherein the power consumption parameters include the number of the android testing device, the name of an application package and the state of the testing application, and the state of the testing application is in use, in operation or in closing;
the power consumption test unit comprises a third splicing unit, a third execution unit and a third analysis unit, wherein the third splicing unit is used for acquiring power consumption parameters in a power consumption test interface and splicing the power consumption parameters into a third adb command, the third execution unit is used for calling a Runtime class to execute the third adb command, and the third analysis unit is used for acquiring a result returned by the third execution unit and analyzing the result to obtain a power consumption test result;
and the power consumption result output unit is used for outputting and displaying the power consumption test result analyzed by the third analysis unit on a power consumption test interface.
5. The multi-functional automated test tool of claim 3, wherein the CPU test submodule comprises:
the CPU test interface is used for displaying CPU parameters and CPU test results of the CPU test;
the CPU parameter setting unit is used for setting CPU parameters related to the application of the android testing device on a CPU testing interface when the android testing device is successfully connected with the testing PC, wherein the CPU parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the CPU test unit comprises a fourth splicing unit, a fourth execution unit and a fourth analysis unit, wherein the fourth splicing unit is used for acquiring CPU parameters in a CPU test interface and splicing the CPU parameters into a fourth adb command, the fourth execution unit is used for creating a first thread and calling a Runtime class in the first thread to execute the fourth adb command, and the fourth analysis unit is used for acquiring a returned result of the fourth execution unit in real time and analyzing the returned result to acquire a CPU test result;
the CPU result output unit is used for outputting and displaying the CPU test result analyzed by the fourth analysis unit on a CPU test interface;
wherein, the flow test submodule comprises:
the flow test interface is used for displaying flow parameters and flow test results of the flow test;
the flow parameter setting unit is used for setting flow parameters related to the application of the android testing device on a flow testing interface when the android testing device is successfully connected with the testing PC, wherein the flow parameters include an android device number, an application package name, execution time and refreshing time;
the flow test unit comprises a fifth splicing unit, a fifth execution unit and a fifth analysis unit, wherein the fifth splicing unit is used for acquiring flow parameters in the flow test interface and splicing the flow parameters into a fifth adb command, the fifth execution unit is used for creating a second thread and calling a Runtime class in the second thread to execute the fifth adb command, and the fifth analysis unit is used for acquiring a return result of the fifth execution unit in real time and analyzing the return result to acquire a flow test result;
the flow result output unit is used for outputting and displaying the flow test result analyzed by the fifth analysis unit on a flow test interface;
wherein, the memory test submodule comprises:
the memory test interface is used for displaying memory parameters and memory test results of the memory test;
the memory parameter setting unit is used for setting memory parameters related to the application of the android testing device in a memory testing interface when the android testing device is successfully connected with the testing PC, wherein the memory parameters include the number of the android testing device, the name of an application package, the execution time and the refreshing time;
the memory test unit comprises a sixth splicing unit, a sixth execution unit and a sixth analysis unit, wherein the sixth splicing unit is used for acquiring memory parameters in the memory test interface and splicing the memory parameters into a sixth adb command, the sixth execution unit is used for creating a third thread and calling a Runtime class in the third thread to execute the sixth adb command, and the sixth analysis unit is used for acquiring a return result of the sixth execution unit in real time and analyzing the return result to acquire a memory test result;
and the memory result output unit is used for outputting and displaying the memory test result analyzed by the sixth analysis unit on a memory test interface.
6. The multi-functional automated test tool of claim 1, wherein the interface test module comprises:
the interface test interface is used for displaying interface parameters and interface test results of the interface test;
the interface parameter setting unit is used for setting interface parameters related to a test interface on the interface test interface, wherein the interface parameters comprise a request mode, a request address, a test concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode;
the interface testing unit comprises an obtaining unit for obtaining interface parameters in an interface testing interface, a calling unit for calling the http policy to send an interface request through the interface parameters, and a seventh analyzing unit for obtaining the http policy object returned by the calling unit and analyzing the http policy object to obtain an interface testing result;
and the interface result output unit is used for outputting and displaying the interface test result analyzed by the seventh analysis unit on an interface test interface.
7. The multifunctional automatic testing method is characterized in that an interface test result is obtained by calling an interface testing module at a testing main interface in the interface test, a stability test result is obtained by calling the stability testing module at the testing main interface in the stability test of the android application, and a performance test result is obtained by calling the performance testing module at the testing main interface in the performance test of the android application.
8. The multifunctional automated testing method of claim 7, wherein the testing method of the interface test is: the interface testing method comprises the steps that a user inputs interface parameters related to interface testing on an interface testing interface through an interface parameter setting unit, an obtaining unit obtains the interface parameters in the interface testing interface, then a calling unit calls an HttpClient to send an interface request through the interface parameters, a seventh analyzing unit obtains an HttpResponse object returned by the calling unit and analyzes the HttpResponse object to obtain an interface testing result, and then an interface result output unit outputs and displays the interface testing result on the interface testing interface, wherein the interface parameters comprise a request mode, a request address, a testing concurrency number, a request header parameter and a request body parameter, and the request mode is a Get mode or a Post mode.
9. The multifunctional automated testing method of claim 7, wherein the testing method for the stability test of android applications is: the user inputs stability parameters related to stability of the android application on a Monkey test interface through a stability parameter setting unit, a first splicing unit obtains the stability parameters in the Monkey test interface and splices the stability parameters into a first adb command, a first execution unit creates a thread pool, the thread pool calls Runtime classes to execute the first adb command, a first analysis unit obtains a return result of the first execution unit in real time and analyzes the return result to obtain a stability test result, and the stability test result of the android application is output and displayed on the Monkey test interface through a stability result output unit, wherein the stability parameters comprise: the first type of parameters comprise an android device number, an application package name, execution times, seed numbers, delay time, an execution mode and log levels; and the second type of parameters comprise a touch event parameter, a screen-sliding event parameter, a main navigation event parameter, a navigation event parameter and a system key event parameter, and the sum of the numerical values of all the parameters in the second type of parameters is 100.
10. The multifunctional automated testing method of claim 7, wherein the method for starting time testing in android application performance testing comprises: a user inputs a starting time parameter related to starting time of an android application in a starting time test interface through a starting time parameter setting unit, a second splicing unit obtains the starting time parameter in the starting time test interface and splices the starting time parameter into a second adb command, a second execution unit calls Runtime to execute the second adb command, a second analysis unit obtains a result returned by the second execution unit and analyzes the result to obtain a starting time test result, and then the starting time test result of the android application is output and displayed on the starting time test interface through a starting time result output unit, wherein the starting time parameter comprises an android equipment number, an application package name and a starting mode, and the starting mode is first starting or non-first starting;
the method for testing the power consumption in the android application performance test comprises the following steps: a user inputs power consumption parameters related to the power consumption of an android application in a power consumption test interface through a power consumption parameter setting unit, a third splicing unit obtains the power consumption parameters in the power consumption test interface and splices the power consumption parameters into a third adb command, a third execution unit calls Runtime classes to execute the third adb command, a third analysis unit obtains a result returned by the third execution unit and analyzes the result to obtain a power consumption test result, and then the power consumption test result of the android application is output and displayed in the power consumption test interface through a power consumption result output unit, wherein the power consumption parameters comprise the number of the android device, the name of an application package and the state of the test application, and the state of the test application is in use, in operation and in closing;
the method for testing the CPU in the android application performance test comprises the following steps: a user inputs CPU parameters related to an android application CPU on a CPU test interface through a CPU parameter setting unit, a fourth splicing unit obtains the CPU parameters in the CPU test interface and splices the CPU parameters into a fourth adb command, a fourth execution unit creates a first thread and calls Runtime classes in the first thread to execute the fourth adb command, a fourth analysis unit obtains a result returned by the fourth execution unit and analyzes the result to obtain a CPU test result, and the CPU test result of the android application is output and displayed on the CPU test interface through a CPU result output unit, wherein the CPU parameters comprise an android device number, an application package name, execution time and refreshing time;
the flow testing method in the android application performance test comprises the following steps: a user inputs flow parameters related to android application flow in a flow test interface through a flow parameter setting unit, a fifth splicing unit obtains the flow parameters in the flow test interface and splices the flow parameters into a fifth adb command, a fifth execution unit creates a second thread and calls Runtime classes in the second thread to execute the fifth adb command, a fifth analysis unit obtains a result returned by the fifth execution unit and analyzes the result to obtain a flow test result, and the flow test result of the android application is output and displayed on the flow test interface through a flow result output unit, wherein the flow parameters comprise an android device number, an application package name, execution time and refresh time;
the method for testing the memory in the android application performance test comprises the following steps: a user inputs memory parameters related to an android application memory on a memory test interface through a memory parameter setting unit, a sixth splicing unit obtains the memory parameters in the memory test interface and splices the memory parameters into a sixth adb command, a sixth execution unit creates a third thread and calls Runtime classes in the third thread to execute the sixth adb command, a sixth analysis unit obtains a result returned by the sixth execution unit and analyzes the result to obtain a memory test result, and the memory test result of the android application is output and displayed on the memory test interface through a memory result output unit, wherein the memory parameters comprise an android device number, an application package name, execution time and refresh time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011382616.1A CN112579438B (en) | 2020-12-01 | 2020-12-01 | Multifunctional automatic test tool and test method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011382616.1A CN112579438B (en) | 2020-12-01 | 2020-12-01 | Multifunctional automatic test tool and test method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112579438A true CN112579438A (en) | 2021-03-30 |
| CN112579438B CN112579438B (en) | 2022-07-08 |
Family
ID=75126702
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011382616.1A Active CN112579438B (en) | 2020-12-01 | 2020-12-01 | Multifunctional automatic test tool and test method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112579438B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114168476A (en) * | 2021-12-10 | 2022-03-11 | 惠州Tcl移动通信有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN114356771A (en) * | 2021-12-31 | 2022-04-15 | 龙芯中科(武汉)技术有限公司 | Operation method, device and equipment of data processing entity |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002031657A2 (en) * | 2000-10-12 | 2002-04-18 | Sun Microsystems, Inc. | Automatic performance test generation |
| CN102141960A (en) * | 2011-03-18 | 2011-08-03 | 广东欧珀移动通信有限公司 | Automatic test method based on Android |
| CN103577309A (en) * | 2012-07-25 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Automatic test method and device |
| US20140173319A1 (en) * | 2011-08-31 | 2014-06-19 | Zte Corporation | Method and Device for Monitoring Power Consumption of Application in Android Terminal |
| CN104881364A (en) * | 2015-06-26 | 2015-09-02 | 上海斐讯数据通信技术有限公司 | Automated testing method and system applied to Android system |
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN105760301A (en) * | 2016-02-24 | 2016-07-13 | 惠州Tcl移动通信有限公司 | Automatic testing method and system based on Monkey command |
| CN106445764A (en) * | 2016-09-29 | 2017-02-22 | 福州大学 | Method for realizing automatic testing of stability of android facility |
| CN106649107A (en) * | 2016-12-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Automated testing method and device for stability of Android system |
| CN106776294A (en) * | 2016-11-29 | 2017-05-31 | 任子行网络技术股份有限公司 | Android mobile phone automated testing method and system |
| CN107562636A (en) * | 2017-09-21 | 2018-01-09 | 北京金山安全软件有限公司 | Method and device for testing starting time of application software |
| CN110196798A (en) * | 2019-06-06 | 2019-09-03 | 百度在线网络技术（北京）有限公司 | Performance data determines method, apparatus, equipment and readable storage medium storing program for executing |
| CN110309066A (en) * | 2019-06-13 | 2019-10-08 | 合肥移瑞通信技术有限公司 | A kind of test method and system based on monkey tool |
| WO2020082585A1 (en) * | 2018-10-25 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Method and device for interface testing |
-
2020
- 2020-12-01 CN CN202011382616.1A patent/CN112579438B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002031657A2 (en) * | 2000-10-12 | 2002-04-18 | Sun Microsystems, Inc. | Automatic performance test generation |
| CN102141960A (en) * | 2011-03-18 | 2011-08-03 | 广东欧珀移动通信有限公司 | Automatic test method based on Android |
| US20140173319A1 (en) * | 2011-08-31 | 2014-06-19 | Zte Corporation | Method and Device for Monitoring Power Consumption of Application in Android Terminal |
| CN103577309A (en) * | 2012-07-25 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Automatic test method and device |
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN104881364A (en) * | 2015-06-26 | 2015-09-02 | 上海斐讯数据通信技术有限公司 | Automated testing method and system applied to Android system |
| CN105760301A (en) * | 2016-02-24 | 2016-07-13 | 惠州Tcl移动通信有限公司 | Automatic testing method and system based on Monkey command |
| CN106445764A (en) * | 2016-09-29 | 2017-02-22 | 福州大学 | Method for realizing automatic testing of stability of android facility |
| CN106776294A (en) * | 2016-11-29 | 2017-05-31 | 任子行网络技术股份有限公司 | Android mobile phone automated testing method and system |
| CN106649107A (en) * | 2016-12-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Automated testing method and device for stability of Android system |
| CN107562636A (en) * | 2017-09-21 | 2018-01-09 | 北京金山安全软件有限公司 | Method and device for testing starting time of application software |
| WO2020082585A1 (en) * | 2018-10-25 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Method and device for interface testing |
| CN110196798A (en) * | 2019-06-06 | 2019-09-03 | 百度在线网络技术（北京）有限公司 | Performance data determines method, apparatus, equipment and readable storage medium storing program for executing |
| CN110309066A (en) * | 2019-06-13 | 2019-10-08 | 合肥移瑞通信技术有限公司 | A kind of test method and system based on monkey tool |
Non-Patent Citations (4)
| Title |
|---|
| 武西康等: "基于Android的智能手机软件性能测试系统研究", 《信息通信》 * |
| 武西康等: "基于Android的智能手机软件性能测试系统研究", 《信息通信》, no. 04, 15 April 2016 (2016-04-15) * |
| 裘文成: "安卓APP安全性在线分析系统设计", 《电子世界》 * |
| 裘文成: "安卓APP安全性在线分析系统设计", 《电子世界》, no. 10, 23 May 2019 (2019-05-23) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114168476A (en) * | 2021-12-10 | 2022-03-11 | 惠州Tcl移动通信有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN114356771A (en) * | 2021-12-31 | 2022-04-15 | 龙芯中科(武汉)技术有限公司 | Operation method, device and equipment of data processing entity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112579438B (en) | 2022-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112579438B (en) | Multifunctional automatic test tool and test method | |
| US7302675B2 (en) | System and method for analyzing a graphical program using debugging graphical programs | |
| US6282699B1 (en) | Code node for a graphical programming system which invokes execution of textual code | |
| JP4112886B2 (en) | Device bus protocol compliant test method and system | |
| US7895575B2 (en) | Apparatus and method for generating test driver | |
| US8473275B2 (en) | Method for integrating event-related information and trace information | |
| US8234089B2 (en) | Auto-scheduling of tests | |
| US20130283237A1 (en) | Debugging a Statechart for a Real Time Target | |
| CN104834600B (en) | A kind of method for testing Android application controls | |
| CN105183630B (en) | Applied program testing method and device | |
| CN112270149A (en) | Verification platform automation integration method and system, electronic equipment and storage medium | |
| CN111339731B (en) | FPGA (field programmable Gate array) verification platform and method for SoC (System on chip) | |
| Grechanik et al. | Creating GUI testing tools using accessibility technologies | |
| US9495265B2 (en) | Test executive system with processing of results data in chunks | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| US6952655B2 (en) | User defined processing function | |
| CN114578790B (en) | Unmanned aerial vehicle flight control automatic test method, system, equipment and medium | |
| Olsen Jr et al. | Research directions for user interface software tools | |
| EP2634693A1 (en) | Method and apparatus for interacting with runnung software | |
| CN114089959A (en) | Enterprise management software rapid development system | |
| Xiao et al. | Covana: Precise identification of problems in Pex | |
| Organ | enVision: the inside story | |
| CN111723006B (en) | Automatic test frame and industrial computer based on C # | |
| CN113225717B (en) | Control method and device of Bluetooth equipment and computer readable storage medium | |
| Sinnig et al. | A formal model for generating integrated functional and user interface test cases |
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 |