CN111309604B - Offline automatic test method, system, storage medium and mobile terminal - Google Patents
Offline automatic test method, system, storage medium and mobile terminal Download PDFInfo
- Publication number
- CN111309604B CN111309604B CN202010082159.8A CN202010082159A CN111309604B CN 111309604 B CN111309604 B CN 111309604B CN 202010082159 A CN202010082159 A CN 202010082159A CN 111309604 B CN111309604 B CN 111309604B
- Authority
- CN
- China
- Prior art keywords
- test
- mobile terminal
- computer
- module
- log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000010998 test method Methods 0.000 title claims description 15
- 238000012360 testing method Methods 0.000 claims abstract description 256
- 238000000034 method Methods 0.000 claims description 40
- 230000008569 process Effects 0.000 claims description 30
- 230000005856 abnormality Effects 0.000 claims description 7
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 241000282693 Cercopithecidae Species 0.000 description 24
- 230000006870 function Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000007781 pre-processing Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000001514 detection method Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 5
- 238000005192 partition Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- 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/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
The application provides an offline automatic testing method, an offline automatic testing system, a storage medium and a mobile terminal. The application can continuously supply power through the test time, so as to avoid the problem of short test time caused by excessively high test power consumption, and simultaneously can test a plurality of mobile terminals to meet the requirement of test quantity; the offline test is realized by storing the test log in the mobile terminal; and automatically generates test reports for analysis of the problem.
Description
Technical Field
The application relates to the technical field of mobile communication, in particular to an offline automatic testing method, an offline automatic testing system, a storage medium and a mobile terminal.
Background
The Monkey Test (Monkey Test) is a command execution application provided by the Google native system, which tests the system under Test by some irregular and unordered operations, just like a Monkey goes around a random point on a Test machine. By clicking the UI icon with a background command, a pseudo-random data stream is sent to the tested machine, causing the application to trigger some of the following: click, long press, slide, etc. The tester can check the phenomenon from the subjective interface, and whether the problems of Crash (no response problem) application or ANR (breakdown problem) application and the like occur or not is often applied to mobile phone equipment manufacturers. The instructions of the operation and Log files (or Log files) left in the testing process can be referred to by a tester or a developer, so that the reason for the problem is found, and whether the program is stable or not and how fault tolerance performance is achieved are judged. The Monkey test code is written in the Android system, and a tester can be used for calling and writing the test script code, generating a batch file and executing the batch file. The short-time test has no meaning, and the test duration of 3-7 days is generally required to reflect the problems of the device to be tested as comprehensively as possible, meanwhile, the whole process device consumes fast power, and once the device is not supplied with power, the Monkey test needs to be restarted. The traditional Monkey test needs to connect the device to be tested with a computer, saves the grabbed log file on the computer, but the connected computer cannot meet the power supply of the long-time Monkey test, and generally can be disconnected from charging after 24 hours, and at the moment, the connection needs to be carried out again by a tester. The number of tested devices is usually large in each test, so that a large number of log files are generated in the test process, the codes to be analyzed are messy and large in quantity, and the problems are not easy to quickly locate and establish loopholes (BUGs). Meanwhile, for the known problems of the historical version, testers often need to check whether the problems are repeated, and if so, the problems need to be described on the original BUG, and the BUG is not re-established.
Therefore, the present application provides an offline automatic testing method, system, storage medium and mobile terminal, so as to solve the above-mentioned problems.
Disclosure of Invention
The embodiment of the application provides an offline automatic test method, an offline automatic test system, a storage medium and a mobile terminal, which solve the problems that the test time of a Monkey test is long, the electric quantity consumption is high, the online test cannot meet the requirement of long-time power supply and the test log quantity is large and miscellaneous.
According to a first aspect of the present application, an offline automatic test method of an embodiment of the present application is applied to a mobile terminal, and the offline automatic test method includes: acquiring an automatic test starting command; automatically testing at least one application program and automatically generating a corresponding log; storing the log in the mobile terminal; powering the mobile terminal; stopping executing the automatic test command when the automatic test time reaches the preset time; and leading out the log to a computer for analysis to generate a test report.
Further, the offline automated testing method further comprises: before the step of acquiring the command for starting the automated test, the method further comprises the following preprocessing steps: connecting a plurality of mobile terminals to the computer; performing system test on the mobile terminal through the computer; acquiring authority of all applications of the mobile terminal through the computer; carrying out single-package test on the mobile terminal through the computer; selecting an application program to be tested of the mobile terminal by the computer; and setting the time for the mobile terminal to perform automatic test through a computer.
Further, in the step of storing the log in the mobile terminal, the method specifically includes the following steps: generating a command for acquiring the log; judging whether the log is normal or not; when judging that the log acquisition is normal, disconnecting the mobile terminal from the computer; and storing the log in the mobile terminal.
Further, in the step of exporting the log to a computer for parsing to generate a test report, the method further comprises the following steps: the computer analyzing the log to obtain stack information of the keywords; matching the stack information with the error information list in a fuzzy matching mode so as to update the error list; generating a test report; wherein the test report comprises: and the name and version number of the application program to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
According to a second aspect of the present application, an embodiment of the present application provides an offline automation test device, applied to a mobile terminal, the offline automation test device includes: the acquisition module is used for acquiring an automatic test starting command; the test module is used for automatically testing at least one application program and automatically generating a corresponding log; the storage module is used for storing the log in the mobile terminal; the power supply module is used for supplying power to the mobile terminal; the stopping module is used for stopping executing the automatic test command after the automatic test time reaches the preset time; and the export module is used for exporting the log to a computer for analysis to generate a test report.
Further, the offline automated testing system further comprises the following preprocessing module: the connection module is used for connecting a plurality of mobile terminals to the computer; the system test module is used for carrying out system test on the mobile terminal through the computer; the permission acquisition module is used for acquiring the permission of all applications of the mobile terminal through the computer; the single-packet testing module is used for carrying out single-packet testing on the mobile terminal through the computer; the application selection module is used for selecting the application program to be tested of the mobile terminal through the computer; and the time setting module is used for setting the preset time for the automatic test of the mobile terminal through a computer.
Further, the storage module comprises a generation sub-module for generating the log acquisition command; the judging sub-module is used for judging whether the obtained log is normal or not; the disconnection submodule is used for disconnecting the mobile terminal from the computer when judging that the log is normal; and the storage sub-module is used for storing the log in the mobile terminal.
Further, the deriving module includes: the analysis module is used for analyzing the log by the computer to obtain keyword stack information; the matching module is used for matching the stack information with the error information list in a fuzzy matching mode so as to update the error list; the generation module is used for generating a test report; the test report includes: and the name and version number of the application to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
According to a third aspect of the present application, an embodiment of the present application provides a storage medium having stored therein a plurality of instructions adapted to be loaded by a processor to perform the offline automated test method described above.
According to a fourth aspect of the present application, an embodiment of the present application provides a mobile terminal, which includes a processor and a memory, wherein the processor is electrically connected to the memory, the memory is used for storing instructions and data, and the processor is used for executing the steps in the offline automatic test method.
The embodiment of the application provides an off-line automatic test method, an off-line automatic test system, a storage medium and a mobile terminal, which are used for continuously supplying power for the test time so as to avoid the problem of short test time caused by overhigh test power consumption, and simultaneously can test a plurality of mobile terminals to meet the requirement of test quantity; the offline test is realized by storing the test log in the mobile terminal; and automatically generates test reports for analysis of the problem.
Drawings
The technical solution and other advantageous effects of the present application will be made apparent by the following detailed description of the specific embodiments of the present application with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of steps of an offline automated testing method according to an embodiment of the present application.
Fig. 2 is a schematic flow chart of a preprocessing step according to an embodiment of the present application.
Fig. 3 is a schematic flow chart of step S13 shown in fig. 1.
Fig. 4 is a schematic flow chart of step S16 shown in fig. 1.
Fig. 5 is a schematic structural diagram of an offline automated testing system according to an embodiment of the present application.
FIG. 6 is a schematic diagram of a preprocessing module according to an embodiment of the present application
Fig. 7 is a schematic structural diagram of the storage module shown in fig. 5.
Fig. 8 is a schematic structural diagram of the export module shown in fig. 5.
Fig. 9 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application.
Fig. 10 is a schematic diagram of a specific structure of a mobile terminal according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to fall within the scope of the application.
The terms first, second, third and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the objects so described may be interchanged where appropriate. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.
In the detailed description, the drawings and examples set forth below, which illustrate the principles of the present disclosure, are only for the purpose of illustration and are not to be construed as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present application may be implemented in any suitably arranged system. Exemplary embodiments will be described in detail, examples of which are illustrated in the accompanying drawings. Further, a mobile terminal according to an exemplary embodiment will be described in detail with reference to the accompanying drawings. Like reference symbols in the drawings indicate like elements.
The terminology used in the description of the particular embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The use of expressions in the singular encompasses plural forms of expressions unless the context clearly dictates otherwise. In the present description, it should be understood that terms such as "comprising," "having," "including," and "containing" are intended to specify the presence of the stated features, integers, steps, actions, or combinations thereof disclosed in the present description, but are not intended to preclude the presence or addition of one or more other features, integers, steps, actions, or combinations thereof. Like reference numerals in the drawings refer to like parts.
In the description of the present application, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be either fixedly connected, detachably connected, or integrally connected, for example; can be mechanically connected, electrically connected or can be communicated with each other; can be directly connected or indirectly connected through an intermediate medium, and can be communicated with the inside of two elements or the interaction relationship of the two elements. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art according to the specific circumstances.
The following disclosure provides many different embodiments, or examples, for implementing different features of the application. In order to simplify the present disclosure, components and arrangements of specific examples are described below. They are, of course, merely examples and are not intended to limit the application. Furthermore, the present application may repeat reference numerals and/or letters in the various examples, which are for the purpose of brevity and clarity, and which do not themselves indicate the relationship between the various embodiments and/or arrangements discussed. In addition, the present application provides examples of various specific processes and materials, but one of ordinary skill in the art will recognize the application of other processes and/or the use of other materials.
Specifically, referring to fig. 1, an embodiment of the present application provides an offline automatic testing method for a mobile terminal, which includes the following steps.
Step S11, acquiring an automatic test starting command.
In the embodiment of the application, the starting automatic test command can be obtained through the operation of a user on the mobile terminal or can be obtained through connecting to a computer. And starting an automatic test command to trigger a Monkey native code in the mobile terminal to carry out offline automatic test.
Referring to fig. 2, step S11 is preceded by preprocessing steps such as step S21 to step S26.
Step S21, connecting a plurality of mobile terminals to the computer.
In the embodiment of the application, a plurality of mobile terminals are connected to the computer at the same time, the computer is used for setting the background command codes one by one, the background command codes are spliced, so that a plurality of synchronous tests are realized, and a plurality of Monkey tests with different conditions can be performed by performing different test setting operations on each mobile terminal. The number of the tests is not limited, the connected mobile terminals can be simultaneously operated, for example, 8 mobile terminals to be tested are connected to a computer, a tester can open 8 Monkey test tool windows to simultaneously set each device, and click a Start button to activate a background command for completing splicing to Start testing.
And S22, performing system test on the mobile terminal through the computer.
In the embodiment of the application, the system tests a default test round, shortens the delay time between events in the Monkey test, and verifies whether the application can normally run in the quick event response process.
And step S23, acquiring the authority of all applications of the mobile terminal through the computer.
In the embodiment of the application, all rights of the test application are opened. The method aims to completely discover the problems occurring when the mobile terminal runs and is applied as much as possible, and avoid the influence on the test efficiency caused by long-time stay on a single interface.
And step S24, carrying out single-package testing on the mobile terminal through the computer.
In the embodiment of the application, the single-package test defaults to 5 rounds, and the single-package test is a test for ignoring abnormality, so that a plurality of problems in an application program can be found in the process of one-time execution.
And S25, selecting the application program to be tested of the mobile terminal by the computer.
In the embodiment of the application, the application program to be tested of the mobile terminal is selected by the computer, so that the test is targeted, unnecessary tests are reduced, and the test time is further shortened.
And step S26, setting the time for the mobile terminal to perform automatic test through a computer.
In the embodiment of the application, a random time number of 10000000 is set by default to realize long-time uninterrupted test, and the method is suitable for simultaneous test of a plurality of devices.
With continued reference to fig. 1.
And step S12, performing automatic test on at least one application program and automatically generating a corresponding log.
In the embodiment of the application, in the automatic test process, the Monkey native code transmits a pseudo-random user event stream to the system, so that the pressure test of the application program under development is realized.
Step S13, storing the log in the mobile terminal.
In the embodiment of the application, the log is stored in a storage path inside the mobile terminal to be tested by default in the test process, and a computer is not required to be connected, so that offline automatic test is realized.
Referring to fig. 3, step S13 specifically includes steps S31 to S34.
Step S31, generating and acquiring the log command.
In the embodiment of the application, the log is automatically generated in the automatic test process.
Step S32, judging whether the log acquisition is normal or not.
In the embodiment of the application, in the process of checking and testing, if the log acquired by the background is abnormal, the testing is automatically stopped so as to avoid unnecessary testing.
And step S33, when the acquisition log is judged to be normal, disconnecting the mobile terminal from the computer.
In the embodiment of the application, because in the prior art, the USB connection computer is used for charging the mobile terminal, the speed is low, the interface is few, and the mobile terminal to be tested is connected with the computer in a power supply only mode, the charging is easily influenced by charging protection, so that the charging cannot be continuously carried out for a long time, and the charging time is usually not more than 72 hours, so that the connection between the mobile terminal and the computer is disconnected, and the power supply mode is changed.
Step S34, storing the log in the mobile terminal.
In the embodiment of the application, the log is stored in a storage path inside the mobile terminal to be tested by default in the test process, and a computer is not required to be connected, so that offline automatic test is realized.
With continued reference to fig. 1.
And step S14, supplying power to the mobile terminal.
In the embodiment of the application, the mobile terminal is continuously powered in the test process. Preferably, the alternating current charging head is used for supplying power to the mobile terminal, and the charging current is large, so that the problems that the power consumption of the mobile terminal is too high and the computer cannot supply power for a long time in the testing process are solved.
And S15, stopping executing the automatic test command when the automatic test time reaches the preset time.
In the embodiment of the application, the preset time is generally longer than 7 days so as to ensure the readiness of the test result. The automatic test command can be stopped by the mobile terminal, or the computer can control the automatic test command to stop executing.
And S16, the log is exported to a computer for analysis to generate a test report.
In the embodiment of the application, after the test is finished, the computer is connected to the USB and is exported to the computer through an adb pull command. Wherein adb, android Debug Bridge, is a command line tool that allows a simulator or connected Android device to communicate, which can facilitate various device operations, such as installing and debugging applications, and provide access to Unix shell (which can be used to run various commands on the simulator or connected device); pull is derived.
Referring to fig. 4, step S16 specifically includes steps S41 to S43.
In step S41, the computer analyzes the log to obtain stack information of the keywords.
In the embodiment of the application, the seed value, the execution times and the package name of the test executed by the Monkey are displayed at the beginning of the log. The stack information of the key words includes information such as Crash problem (ANR) and no response problem (Crash). The analysis process is as follows, firstly checking whether ANR or Crash abnormality occurs in the Monkey test, then analyzing specific information in the log, checking the first Switch in the log, mainly checking what Activity is executed by the Monkey, such as what is executed in the log below, and in the next Switch, if other abnormality such as Crash or no response occurs, the problem can be found in the Activity.
And step S42, matching the stack information with an error information list in a fuzzy matching mode.
In the embodiment of the application, each application comprises an error information list, and similar fields with the error information list are searched in a fuzzy matching mode, so that newly-appearing error information (namely corresponding information generated by a BUG BUG) is screened in a log, and known error information is filtered.
Step S43, generating a test report; wherein the test report comprises: and the name and version number of the application program to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
In the embodiment of the application, the test report is automatically generated according to the matching result and backed up in the form document, so that the corresponding log information can be quickly positioned when the problem is conveniently analyzed.
Referring to fig. 5, an embodiment of the present application provides an offline automatic testing device, which is applied to a mobile terminal, and includes an acquisition module 501, a testing module 502, a storage module 503, a power supply module 504, a stopping module 505, and a deriving module 506.
The acquiring module 501 is configured to acquire an automatic test command.
In the embodiment of the application, the starting automatic test command can be obtained through the operation of a user on the mobile terminal or can be obtained through connecting to a computer. And starting an automatic test command to trigger a Monkey native code in the mobile terminal to carry out offline automatic test.
Referring to fig. 6, the offline automated testing system further includes the following preprocessing modules: a connection module 601, a system test module 602, a rights acquisition module 603, a single package test module 604, an application selection module 605, and a time test module 606.
The connection module 601 is configured to connect a plurality of mobile terminals to the computer.
In the embodiment of the application, a plurality of mobile terminals are connected to the computer at the same time, the computer is used for setting the background command codes one by one, the background command codes are spliced, so that a plurality of synchronous tests are realized, and a plurality of Monkey tests with different conditions can be performed by performing different test setting operations on each mobile terminal. The number of the tests is not limited, the connected mobile terminals can be simultaneously operated, for example, 8 mobile terminals to be tested are connected to a computer, a tester can open 8 Monkey test tool windows to simultaneously set each device, and click a Start button to activate a background command for completing splicing to Start testing.
The system test module 602 is connected with the connection module 601. The system test module 602 is configured to perform a system test on the mobile terminal through the computer.
In the embodiment of the application, the system tests a default test round, shortens the delay time between events in the Monkey test, and verifies whether the application can normally run in the quick event response process.
The rights acquisition module 603 is connected to the system test module 602. The permission acquisition module 603 is configured to acquire permission of all applications of the mobile terminal through the computer.
In the embodiment of the application, all rights of the test application are opened. The method aims to completely discover the problems occurring when the mobile terminal runs and is applied as much as possible, and avoid the influence on the test efficiency caused by long-time stay on a single interface.
The single package test module 604 is connected to the rights acquisition module 603. The single-packet testing module 604 is configured to perform a single-packet test on the mobile terminal through the computer.
In the embodiment of the application, the single-package test defaults to 5 rounds, and the single-package test is a test for ignoring abnormality, so that a plurality of problems in an application program can be found in the process of one-time execution.
The application selection module 605 interfaces with the single package test module 604. The application selection module 605 is used for selecting the application program to be tested of the mobile terminal through the computer.
In the embodiment of the application, the application program to be tested of the mobile terminal is selected by the computer, so that the test is targeted, unnecessary tests are reduced, and the test time is further shortened.
The time test module 606 is coupled to the application selection module 605. The time testing module 606 is configured to set, by using a computer, a time for the mobile terminal to perform an automated test.
In the embodiment of the application, a random time number of 10000000 is set by default to realize long-time uninterrupted test, and the method is suitable for simultaneous test of a plurality of devices.
With continued reference to fig. 5.
The test module 502 is connected to the acquisition module 501. The test module 502 is configured to perform an automated test on at least one application program, and automatically generate a corresponding log.
In the embodiment of the application, in the automatic test process, the Monkey native code transmits a pseudo-random user event stream to the system, so that the pressure test of the application program under development is realized.
The storage module 503 is connected to the test module 502. The storage module 503 is configured to store the log in the mobile terminal.
In the embodiment of the application, the log is stored in a storage path inside the mobile terminal to be tested by default in the test process, and a computer is not required to be connected, so that offline automatic test is realized.
Referring to fig. 7, the storage module 503 specifically includes an acquisition sub-module 701, a determination sub-module 702, a disconnection sub-module 703, and a storage sub-module 704.
The generating sub-module 701 is configured to generate the command to acquire the log.
In the embodiment of the application, the log is automatically generated in the automatic test process.
The judgment sub-module 702 is connected with the acquisition sub-module 701. The determination sub-module 702 determines whether it is normal to obtain the log.
In the embodiment of the application, in the process of checking and testing, if the log acquired by the background is abnormal, the testing is automatically stopped so as to avoid unnecessary testing.
The disconnection submodule 703 is connected to the judgment submodule 702. And the disconnection submodule 703 disconnects the connection between the mobile terminal and the computer when judging that the acquisition log is normal.
In the embodiment of the application, because in the prior art, the USB connection computer is used for charging the mobile terminal, the speed is low, the interface is few, and the mobile terminal to be tested is connected with the computer in a power supply only mode, the charging is easily influenced by charging protection, so that the charging cannot be continuously carried out for a long time, and the charging time is usually not more than 72 hours, so that the connection between the mobile terminal and the computer is disconnected, and the power supply mode is changed.
The storage sub-module 704 is connected to the disconnection sub-module 703. The storage sub-module 704 is configured to store the log in the mobile terminal.
In the embodiment of the application, the log is stored in a storage path inside the mobile terminal to be tested by default in the test process, and a computer is not required to be connected, so that offline automatic test is realized.
With continued reference to fig. 5.
The power supply module 504 is connected with the storage module 503. The power supply module 504 is configured to supply power to the mobile terminal.
In the embodiment of the application, the mobile terminal is continuously powered in the test process. Preferably, the alternating current charging head is used for supplying power to the mobile terminal, and the charging current is large, so that the problems that the power consumption of the mobile terminal is too high and the computer cannot supply power for a long time in the testing process are solved.
The stopping module 505 is connected to the power supply module 504. The stopping module 505 is configured to stop executing the automated test command when the automated test time reaches a preset time.
In the embodiment of the application, the preset time is generally longer than 7 days so as to ensure the readiness of the test result. The automatic test command can be stopped by the mobile terminal, or the computer can control the automatic test command to stop executing.
The export module 506 is connected to the stop module 505. The export module 506 is configured to export the log to a computer for parsing to generate a test report.
In the embodiment of the application, after the test is finished, the computer is connected to the USB and is exported to the computer through an adb pull command.
Referring to fig. 8, the deriving module 506 specifically includes an parsing module 801, a matching module 802, and a generating module 803.
The parsing module 801 is used for the computer to parse the log to obtain stack information of the keywords.
In the embodiment of the application, the seed value, the execution times and the package name of the test executed by the Monkey are displayed at the beginning of the log. The stack information of the key words includes information such as Crash problem (ANR) and no response problem (Crash). The analysis process is as follows, firstly checking whether ANR or Crash abnormality occurs in the Monkey test, then analyzing specific information in the log, checking the first Switch in the log, mainly checking what Activity is executed by the Monkey, such as what is executed in the log below, and in the next Switch, if other abnormality such as Crash or no response occurs, the problem can be found in the Activity.
The matching module 802 is connected to the parsing module 801. The matching module 802 matches the stack information with the error information list by fuzzy matching.
In the embodiment of the application, each application comprises an error information list, and similar fields with the error information list are searched in a fuzzy matching mode, so that newly-appearing error information is screened in a log, and known error information is filtered.
The generation module 803 is connected to the matching module 802. The generating module 803 is configured to generate a test report; wherein the test report comprises: and the name and version number of the application program to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
In the embodiment of the application, the test report is automatically generated according to the matching result and backed up in the form document, so that the corresponding log information can be quickly positioned when the problem is conveniently analyzed.
Referring to fig. 9, the embodiment of the application further provides a mobile terminal 900, where the mobile terminal 900 may be a mobile phone, a tablet, a computer, or other devices. As shown in fig. 9, the mobile terminal 900 includes a processor 901 and a memory 902. The processor 901 is electrically connected to the memory 902.
The processor 901 is a control center of the mobile terminal 900, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or loading an application program stored in the memory 902 and calling data stored in the memory 902, thereby performing overall monitoring of the mobile terminal.
In this embodiment, the mobile terminal 900 is provided with a plurality of storage partitions, where the plurality of storage partitions include a system partition and a target partition, and the processor 901 in the mobile terminal 900 loads instructions corresponding to the processes of one or more application programs into the memory 902 according to the following steps, and the processor 901 executes the application programs stored in the memory 902, so as to implement various functions:
Acquiring an automatic test starting command;
automatically testing at least one application program and automatically generating a corresponding log;
storing the log in the mobile terminal;
powering the mobile terminal;
stopping executing the automatic test command when the automatic test time reaches the preset time; and
and (5) exporting the log to a computer for analysis to generate a test report.
Referring to fig. 10, fig. 10 shows a specific block diagram of a mobile terminal 1000 according to an embodiment of the present application, and the mobile terminal 1000 may be used to implement the offline automated testing method provided in the above embodiment. The mobile terminal 1000 can be a cell phone or tablet. The mobile terminal 1000 includes the following components.
The RF circuit 1010 is configured to receive and transmit electromagnetic waves, and to perform mutual conversion between the electromagnetic waves and the electrical signals, thereby communicating with a communication network or other devices. RF circuitry 1010 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF circuitry 1010 may communicate with various networks such as the internet, intranets, wireless networks, or other devices via wireless networks. The wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. The wireless network may use various communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (Global System for Mobile Communication, GSM), enhanced mobile communications technology (Enhanced Data GSM Environment, EDGE), wideband code division multiple access technology (Wideband Code Division Multiple Access, WCDMA), code division multiple access technology (Code Division Access, CDMA), time division multiple access technology (Time Division Multiple Access, TDMA), wireless fidelity technology (Wireless Fidelity, wi-Fi) (e.g., american society of electrical and electronic engineers standards IEEE802.11 a, IEEE802.11 b, IEEE802.11g, and/or IEEE802.11 n), internet telephony (Voice over Internet Protocol, voIP), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wi-Max), other protocols for mail, instant messaging, and short messaging, as well as any other suitable communication protocols, including even those not currently developed.
The memory 1020 may be used to store software programs and modules, such as program instructions/modules corresponding to the offline automation test method in the above embodiments, and the processor 1080 executes the software programs and modules stored in the memory 1020 to perform various functional applications and data processing, i.e. to implement the functions of the offline automation test method. Memory 1020 may include high-speed random access memory, but may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 1020 may further include memory located remotely from processor 1080 and may be connected to mobile terminal 1000 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input unit 1030 may be used for receiving input numeric or character information and generating keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, the input unit 1030 may include a touch-sensitive surface 1031 and other input devices 1032. The touch-sensitive surface 1031, also referred to as a touch display screen or touch pad, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch-sensitive surface 1031 or thereabout using any suitable object or accessory such as a finger, stylus, etc.), and actuate the corresponding connection device according to a pre-set program. Alternatively, the touch sensitive surface 1031 may comprise two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 1080 and can receive commands from the processor 1080 and execute them. In addition, the touch sensitive surface 1031 may be implemented in a variety of types, such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch-sensitive surface 1031, the input unit 1030 may include other input devices 1032. In particular, other input devices 1032 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a track ball, a mouse, a joystick, etc.
The display unit 1040 may be used to display information input by a user or information provided to a user and various graphical user interfaces of the mobile terminal 1000, which may be composed of graphics, text, icons, video, and any combination thereof. The display unit 1040 may include a display panel 1041, and alternatively, the display panel 1041 may be configured in the form of an LCD (Liquid Crystal Display ), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch sensitive surface 1031 can overlay the display panel 1041, and upon detection of a touch operation thereon or thereabout by the touch sensitive surface 1031, is communicated to the processor 1080 to determine a type of touch event, and the processor 1080 then provides a corresponding visual output on the display panel 1041 based on the type of touch event. Although in fig. 10 the touch-sensitive surface 1031 and the display panel 1041 are implemented as two separate components for input and output functions, in some embodiments the touch-sensitive surface 1031 may be integrated with the display panel 1041 to implement the input and output functions.
The mobile terminal 1000 can also include at least one sensor 1050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 1041 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 1041 and/or the backlight when the mobile terminal 1000 moves to the ear. As one of the motion sensors, the gravitational acceleration sensor may detect the acceleration in all directions (generally, three axes), and may detect the gravity and direction when stationary, and may be used in applications for recognizing the gesture of a mobile phone (such as horizontal/vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer, and knocking), and other sensors such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, which may be further configured in the mobile terminal 1000, will not be described herein.
Audio circuitry 1060, speaker 1061, microphone 1062 may provide an audio interface between a user and mobile terminal 1000. Audio circuit 1060 may transmit the received electrical signal after audio data conversion to speaker 1061 for conversion by speaker 1061 into an audio signal output; on the other hand, microphone 1062 converts the collected sound signals into electrical signals, which are received by audio circuit 1060 and converted into audio data, which are processed by audio data output processor 1080 for transmission to, for example, another terminal via RF circuit 1010 or for output to memory 1020 for further processing. Audio circuitry 1060 may also include an ear bud jack to provide communication of a peripheral ear bud with mobile terminal 1000.
The mobile terminal 1000 can facilitate user email, web browsing, streaming media access, etc., via a transmission module 1070 (e.g., wi-Fi module) that provides wireless broadband internet access to the user. Although fig. 10 shows a transmission module 1070, it is to be understood that it does not belong to the necessary constitution of the mobile terminal 1000, and can be omitted entirely as required within the scope not changing the essence of the invention.
Processor 1080 is a control center of mobile terminal 1000 and connects the various parts of the overall handset using various interfaces and lines, and performs the various functions of mobile terminal 1000 and processes data by running or executing software programs and/or modules stored in memory 1020 and invoking data stored in memory 1020, thereby performing overall monitoring of the handset. Optionally, processor 1080 may include one or more processing cores; in some embodiments, processor 1080 may integrate an application processor primarily handling operating systems, user interfaces, applications, and the like, with a modem processor primarily handling wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1080.
The mobile terminal 1000 can also include a power source 1090 (e.g., a battery) for powering the various components, which can, in some embodiments, be logically connected to the processor 1080 by a power management system so as to perform functions such as managing charging, discharging, and power consumption by the power management system. The power source 1090 may also include one or more of any of a direct current or alternating current power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
Although not shown, the mobile terminal 1000 can also include a camera (e.g., front camera, rear camera), a bluetooth module, etc., and will not be described in detail herein. In particular, in this embodiment, the display unit of the mobile terminal is a touch screen display, the mobile terminal further includes a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
acquiring an automatic test starting command;
automatically testing at least one application program and automatically generating a corresponding log;
Storing the log in the mobile terminal;
powering the mobile terminal;
stopping executing the automatic test command when the automatic test time reaches the preset time; and
and (5) exporting the log to a computer for analysis to generate a test report.
In the implementation, each module may be implemented as an independent entity, or may be combined arbitrarily, and implemented as the same entity or several entities, and the implementation of each module may be referred to the foregoing method embodiment, which is not described herein again.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions or by controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor. To this end, embodiments of the present application provide a storage medium having stored therein a plurality of instructions capable of being loaded by a processor to perform the steps of any of the offline automated testing methods provided by embodiments of the present application.
Wherein the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
The steps in any of the offline automatic test methods provided by the embodiments of the present application can be executed due to the instructions stored in the storage medium, so that the beneficial effects that any of the offline automatic test methods provided by the embodiments of the present application can be achieved, and detailed descriptions of the foregoing embodiments are omitted. The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
The embodiment of the application provides an off-line automatic test method, an off-line automatic test system, a storage medium and a mobile terminal, which are used for continuously supplying power for the test time so as to avoid the problem of short test time caused by overhigh test power consumption, and simultaneously can test a plurality of mobile terminals to meet the requirement of test quantity; the offline test is realized by storing the test log in the mobile terminal; and automatically generates test reports for analysis of the problem.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
The offline automatic testing method, system, storage medium and mobile terminal provided by the embodiment of the application are described in detail, and specific examples are applied to illustrate the principle and implementation of the application, and the description of the above embodiment is only used for helping to understand the technical scheme and core idea of the application; those of ordinary skill in the art will appreciate that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.
Claims (8)
1. An offline automatic testing method applied to a mobile terminal is characterized by comprising the following steps:
connecting a plurality of mobile terminals to a computer, setting the mobile terminals one by one through the computer, splicing background command codes to realize synchronous testing of a plurality of mobile terminals, and carrying out different test setting operation on each mobile terminal to carry out testing of different conditions of the plurality of mobile terminals;
performing system test on the mobile terminal through the computer;
acquiring authority of all applications of the mobile terminal through the computer;
performing a single-package test on the mobile terminal by the computer, wherein the single-package test comprises a test for ignoring anomalies so as to find a plurality of problems in an application program in one execution process;
selecting an application program to be tested of the mobile terminal by the computer; and
setting the time for the mobile terminal to perform automatic test through a computer;
acquiring an automatic test starting command;
automatically testing at least one application program and automatically generating a corresponding log;
storing the log in the mobile terminal;
powering the mobile terminal;
Stopping executing the automatic test command when the automatic test time reaches the preset time; and
and (5) exporting the log to a computer for analysis to generate a test report.
2. The offline automated testing method of claim 1, wherein in the step of storing the log in the mobile terminal, the method specifically comprises the steps of:
generating a command for acquiring the log;
judging whether the log is normal or not;
when judging that the log acquisition is normal, disconnecting the mobile terminal from the computer; and
and storing the log in the mobile terminal.
3. The offline automated testing method of claim 1, wherein in the step of exporting the log to a computer for parsing to generate a test report, further comprising the steps of:
the computer analyzing the log to obtain stack information of the keywords;
matching the stack information with the error information list in a fuzzy matching mode so as to update the error list; and
generating a test report; wherein the test report comprises: and the name and version number of the application program to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
4. An offline automated testing system applied to a mobile terminal, the offline automated testing system comprising:
the connection module is used for connecting a plurality of mobile terminals to a computer, setting the mobile terminals one by one through the computer, splicing background command codes to realize synchronous test of a plurality of mobile terminals, and carrying out different test setting operation on each mobile terminal to carry out test of different conditions of the plurality of mobile terminals;
the system test module is used for carrying out system test on the mobile terminal through the computer;
the permission acquisition module is used for acquiring the permission of all applications of the mobile terminal through the computer;
the single-package test module is used for carrying out single-package test on the mobile terminal through the computer, wherein the single-package test comprises a test of neglecting abnormality so as to find a plurality of problems in an application program in one execution process;
the application selection module is used for selecting the application program to be tested of the mobile terminal through the computer; and
the time setting module is used for setting preset time for the mobile terminal to perform automatic test through a computer;
the acquisition module is used for acquiring an automatic test starting command;
The test module is used for automatically testing at least one application program and automatically generating a corresponding log;
the storage module is used for storing the log in the mobile terminal;
the power supply module is used for supplying power to the mobile terminal;
the stopping module is used for stopping executing the automatic test command after the automatic test time reaches the preset time; and
and the export module is used for exporting the log to a computer for analysis to generate a test report.
5. The offline automated testing system of claim 4, wherein the storage module comprises:
the generation sub-module is used for generating and acquiring the log command;
the judging sub-module is used for judging whether the obtained log is normal or not;
the disconnection submodule is used for disconnecting the mobile terminal from the computer when judging that the log is normal; and
and the storage sub-module is used for storing the log in the mobile terminal.
6. The offline automated testing system of claim 4, wherein the export module comprises:
the analysis module is used for analyzing the log by the computer to obtain keyword stack information;
The matching module is used for matching the stack information with the error information list in a fuzzy matching mode so as to update the error list; and
the generation module is used for generating a test report; the test report includes: and the name and version number of the application to be tested, the occurrence times, the position and the time of errors and the reproduction error information.
7. A storage medium having stored therein a plurality of instructions adapted to be loaded by a processor to perform the offline automated test method of any of claims 1 to 3.
8. A mobile terminal comprising a processor and a memory, the processor being electrically connected to the memory, the memory being for storing instructions and data, the processor being for performing the steps of the off-line automated test method of any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010082159.8A CN111309604B (en) | 2020-02-07 | 2020-02-07 | Offline automatic test method, system, storage medium and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010082159.8A CN111309604B (en) | 2020-02-07 | 2020-02-07 | Offline automatic test method, system, storage medium and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309604A CN111309604A (en) | 2020-06-19 |
| CN111309604B true CN111309604B (en) | 2023-10-03 |
Family
ID=71159926
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010082159.8A Active CN111309604B (en) | 2020-02-07 | 2020-02-07 | Offline automatic test method, system, storage medium and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309604B (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007061241A1 (en) * | 2005-11-25 | 2007-05-31 | Fusionsoft Co., Ltd. | Error test method for mobile communication terminals |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic testing method and device |
| CN103092756A (en) * | 2013-01-08 | 2013-05-08 | 彭勇 | Interactive automated testing system and method thereof |
| CN103560829A (en) * | 2013-10-31 | 2014-02-05 | 上海斐讯数据通信技术有限公司 | Method and system for automatic testing of UNI ports |
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
| CN104050075A (en) * | 2013-03-11 | 2014-09-17 | 百度国际科技（深圳）有限公司 | Test method and device for Andriod application program |
| CN104331373A (en) * | 2014-11-28 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Monkey test system and method |
| CN105760301A (en) * | 2016-02-24 | 2016-07-13 | 惠州Tcl移动通信有限公司 | Automatic testing method and system based on Monkey command |
| CN105786694A (en) * | 2014-12-26 | 2016-07-20 | 展讯通信(天津)有限公司 | Automatic test system and method, and mobile terminals |
| CN106294158A (en) * | 2016-08-11 | 2017-01-04 | 北京小米移动软件有限公司 | Terminal test method, Apparatus and system |
| WO2017020721A1 (en) * | 2015-08-04 | 2017-02-09 | 阿里巴巴集团控股有限公司 | Service function testing method and device |
| CN107239493A (en) * | 2017-04-28 | 2017-10-10 | 努比亚技术有限公司 | Mobile terminal and its offline logs processing method, computer-readable recording medium |
| CN108984363A (en) * | 2018-05-23 | 2018-12-11 | 福建天泉教育科技有限公司 | A kind of method and system of concurrent testing |
| CN109522181A (en) * | 2018-10-22 | 2019-03-26 | 郑州云海信息技术有限公司 | A kind of performance test methods of distributed memory system, device and equipment |
| CN110069398A (en) * | 2019-03-15 | 2019-07-30 | 平安普惠企业管理有限公司 | Programmed pressure test control method, device, computer equipment and storage medium |
| CN110162453A (en) * | 2018-02-11 | 2019-08-23 | 腾讯科技（深圳）有限公司 | Test method, device, computer readable storage medium and computer equipment |
| US10417113B1 (en) * | 2016-03-10 | 2019-09-17 | Amdocs Development Limited | System, method, and computer program for web testing and automation offline storage and analysis |
| CN110457199A (en) * | 2018-05-08 | 2019-11-15 | 北京京东尚科信息技术有限公司 | The method and apparatus of performance test |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8954929B2 (en) * | 2010-03-29 | 2015-02-10 | Microsoft Corporation | Automatically redirecting method calls for unit testing |
| US10649888B2 (en) * | 2018-01-31 | 2020-05-12 | Dell Products L.P. | Parallelizable data-driven testing |
-
2020
- 2020-02-07 CN CN202010082159.8A patent/CN111309604B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007061241A1 (en) * | 2005-11-25 | 2007-05-31 | Fusionsoft Co., Ltd. | Error test method for mobile communication terminals |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic testing method and device |
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
| CN103092756A (en) * | 2013-01-08 | 2013-05-08 | 彭勇 | Interactive automated testing system and method thereof |
| CN104050075A (en) * | 2013-03-11 | 2014-09-17 | 百度国际科技（深圳）有限公司 | Test method and device for Andriod application program |
| CN103560829A (en) * | 2013-10-31 | 2014-02-05 | 上海斐讯数据通信技术有限公司 | Method and system for automatic testing of UNI ports |
| CN104331373A (en) * | 2014-11-28 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Monkey test system and method |
| CN105786694A (en) * | 2014-12-26 | 2016-07-20 | 展讯通信(天津)有限公司 | Automatic test system and method, and mobile terminals |
| WO2017020721A1 (en) * | 2015-08-04 | 2017-02-09 | 阿里巴巴集团控股有限公司 | Service function testing method and device |
| CN105760301A (en) * | 2016-02-24 | 2016-07-13 | 惠州Tcl移动通信有限公司 | Automatic testing method and system based on Monkey command |
| US10417113B1 (en) * | 2016-03-10 | 2019-09-17 | Amdocs Development Limited | System, method, and computer program for web testing and automation offline storage and analysis |
| CN106294158A (en) * | 2016-08-11 | 2017-01-04 | 北京小米移动软件有限公司 | Terminal test method, Apparatus and system |
| CN107239493A (en) * | 2017-04-28 | 2017-10-10 | 努比亚技术有限公司 | Mobile terminal and its offline logs processing method, computer-readable recording medium |
| CN110162453A (en) * | 2018-02-11 | 2019-08-23 | 腾讯科技（深圳）有限公司 | Test method, device, computer readable storage medium and computer equipment |
| CN110457199A (en) * | 2018-05-08 | 2019-11-15 | 北京京东尚科信息技术有限公司 | The method and apparatus of performance test |
| CN108984363A (en) * | 2018-05-23 | 2018-12-11 | 福建天泉教育科技有限公司 | A kind of method and system of concurrent testing |
| CN109522181A (en) * | 2018-10-22 | 2019-03-26 | 郑州云海信息技术有限公司 | A kind of performance test methods of distributed memory system, device and equipment |
| CN110069398A (en) * | 2019-03-15 | 2019-07-30 | 平安普惠企业管理有限公司 | Programmed pressure test control method, device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| Android移动终端稳定性自动化测试系统的研究;黎伟毅;郭太良;林志贤;;有线电视技术(03);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309604A (en) | 2020-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111666222B (en) | Test method and related device | |
| CN111239617B (en) | Control method and device for charge and discharge test, storage medium and system | |
| CN103473163B (en) | application program detection method and device | |
| CN112415367B (en) | Drive chip abnormality detection method, drive chip abnormality detection device, electronic device and readable storage medium | |
| CN106502906A (en) | A kind of method and apparatus of test application program | |
| CN112199246B (en) | Terminal test method and device, storage medium and mobile terminal | |
| CN112148579B (en) | User interface testing method and device | |
| CN101645033A (en) | Debugging method in abnormality of mobile phone software | |
| CN106294108B (en) | Application program testing method and device | |
| CN106407800A (en) | A hook method and a terminal device | |
| CN112115038A (en) | Application testing method and device and storage medium | |
| CN107832214A (en) | Test method, device, storage medium, terminal equipment and system | |
| CN109245195A (en) | The method, apparatus and storage device of mobile terminal and charging process | |
| CN107884619A (en) | Load power consumption test system and method, mobile terminal | |
| CN109196480B (en) | Method for displaying equipment identification, mobile terminal and terminal equipment | |
| CN110908701B (en) | Firmware version switching method and device, storage medium and electronic equipment | |
| CN111897726A (en) | Abnormity positioning method, abnormity positioning device, storage medium and mobile terminal | |
| EP3129883B1 (en) | Method and apparatus for repairing dynamic link library file | |
| CN111309604B (en) | Offline automatic test method, system, storage medium and mobile terminal | |
| CN110633192B (en) | Test method, test device, terminal equipment and computer readable storage medium | |
| CN112199270B (en) | Program testing method, device, equipment and medium | |
| CN116303085A (en) | Test reason analysis method, device, equipment and storage medium | |
| CN112860501B (en) | Detection method, detection device, storage medium and mobile terminal | |
| CN111309605B (en) | Terminal test method and device, storage medium and terminal equipment | |
| CN112667868B (en) | Data detection method and device |
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 |