CN104866427A - Application testing method and device based on Monkey command and terminal - Google Patents
Application testing method and device based on Monkey command and terminal Download PDFInfo
- Publication number
- CN104866427A CN104866427A CN201510303641.9A CN201510303641A CN104866427A CN 104866427 A CN104866427 A CN 104866427A CN 201510303641 A CN201510303641 A CN 201510303641A CN 104866427 A CN104866427 A CN 104866427A
- Authority
- CN
- China
- Prior art keywords
- test access
- window
- pseudo
- random event
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses an application testing method, a device and a terminal based on Monkey commands, wherein the method comprises the following steps: receiving a Monkey command for a target application; responding to the Monkey command, and running the target application; respectively taking each test entrance as an entrance of a Monkey, and executing a pseudo-random event aiming at the test entrance; monitoring whether the window name of the uppermost window of the terminal is matched with the window name corresponding to the test entry or not in the execution process of the pseudorandom event aiming at the test entry; if not, pausing the execution of the pseudo-random event aiming at the test entry, setting the window with the window name matched with the window name corresponding to the test entry as the uppermost window by the control terminal, and continuing to execute the pseudo-random event aiming at the test entry; and when the testing of at least two testing inlets of the target application is finished and the total executing number of the pseudo-random events reaches the preset total number of the pseudo-random events, determining that the testing of the target application is finished. By adopting the invention, the effectiveness of the application test can be improved.
Description
Technical field
The present invention relates to Internet technical field, particularly relate to a kind of application testing method based on Monkey order, device and terminal.
Background technology
Monkey order is the command-line tool of the measuring stability that Google provides.Although pass through the title that-p parameter can specify tested application bag.But in actual test, often can run into and effectively cannot control random occurrence, and the test after making it loses the situation of value.
Such as, to test " stable case of cleaning great master ", the form of Monkey order is adb shellmonkey – p com.cleanmaster.mguard_cn 30000, namely specifies for " cleaning great master " this application execution 30,000 pseudo-random event.But in reality test, may when execution to 5000 events, trigger home key events, get back to main screen, after this, Monkey order control terminal has entered into Another application, as " QQ ", now before effective Monkey process terminates, remaining random occurrence does not occur in " in cleaning great master ", not the Validity Test for " cleaning great master " naturally, belong to invalid test yet.Visible, the application testing at present based on Monkey order cannot ensure Validity Test as much as possible.
Summary of the invention
Embodiment of the present invention technical matters to be solved is, provides a kind of application testing method based on Monkey order, device and terminal, to ensure based on the Validity Test in the application testing of Monkey order as far as possible, improves the validity of application testing.
In order to solve the problems of the technologies described above, embodiments provide a kind of application testing method based on Monkey order, comprising:
Receive the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Respond described Monkey order, run described intended application;
Respectively using the entrance of each test access as Monkey, perform the pseudo-random event for this test access;
In the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
If do not mate, suspend and perform the described pseudo-random event for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continues to perform the described pseudo-random event for this test access;
When at least two test accesss of described intended application have all been tested, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
Wherein, described respectively using the entrance of each test access as Monkey, and the pseudo-random event for this test access described in performing comprises the following steps:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
Wherein, described respectively using the entrance of each test access as Monkey, and the pseudo-random event for this test access described in performing comprises the following steps:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
Wherein, whether the window name of the described monitoring terminal the superiors window window name corresponding with this test access also comprises after mating:
If coupling, then, when the number of executions of the described pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, determine that this test access has been tested.
Wherein, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by described control terminal, comprising:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
Correspondingly, the embodiment of the present invention additionally provides a kind of application testing device based on Monkey order, comprising:
Receiver module, for receiving the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Running module, for responding described Monkey order, running described intended application;
Execution module, for respectively using the entrance of each test access as Monkey, performs the pseudo-random event for this test access;
Monitoring modular, in the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
Control module, for when the monitoring result of described monitoring modular is not for mating, control described execution module and suspend the described pseudo-random event for this test access of execution, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and controls the described pseudo-random event for this test access of described execution module continuation execution;
Determination module, has all tested at least two test accesss when described intended application, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
Wherein, described execution module, specifically for being realized the entrance of each test access as Monkey by following steps, and performs the described pseudo-random event for this test access:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
Wherein, described execution module, specifically for being realized the entrance of each test access as Monkey by following steps, and performs the described pseudo-random event for this test access:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
Wherein, described execution module, be also coupling for the monitoring result when described monitoring modular, and when reaching the described default pseudo-random event quantity for this test access for the number of executions of the pseudo-random event of this test access, determine that this test access has been tested.
Wherein, described control module, is set to the superiors' window specifically for realizing control terminal in the following manner by the window that window name corresponding with this test access for window name is mated:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
Correspondingly, the embodiment of the present invention additionally provides a kind of terminal, comprises the above-mentioned application testing device based on Monkey order.
Implement the embodiment of the present invention, there is following beneficial effect:
When receiving the Monkey order for intended application, respond this Monkey order, run this intended application, and each test access Monkey order comprised respectively is as the entrance of Monkey, perform the pseudo-random event for this test access, in the implementation of the pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates, if do not mate, then suspend the pseudo-random event performed for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continue to perform the pseudo-random event for this test access, when all test accesss of intended application have all been tested, and the execution of pseudo-random event sum reaches default pseudo-random event sum, determine that this intended application has been tested, owing to having preset at least two test accesss, and the pseudo-random event quantity set respectively for each test access, thus, all pseudo-random event can be avoided only with the entrance that single test access (i.e. the function choosing-item of intended application) is Monkey, ensure that the Test coverage for intended application is more comprehensive, simultaneously, owing to performing in the process for the pseudo-random event of each test access, the window name whether correspondingly with this test access monitoring this terminal the superiors window is mated, thus, can ensure for the execution of the pseudo-random event of this test access it is perform in the window corresponding with this test access, ensure that based on the Validity Test in the application testing of Monkey order, improve the validity of application testing.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic flow sheet of a kind of application testing method based on Monkey order that the embodiment of the present invention provides;
Fig. 2 is the schematic flow sheet of the another kind that provides of the embodiment of the present invention based on the application testing method of Monkey order;
Fig. 3 is the structural representation of a kind of application testing device based on Monkey order that the embodiment of the present invention provides;
Fig. 4 is the structural representation of the another kind that provides of the embodiment of the present invention based on the application testing device of Monkey order.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Embodiments provide a kind of application testing method based on Monkey order, device and terminal, can ensure as far as possible, based on the Validity Test in the application testing of Monkey order, to be described in detail respectively below.
Refer to Fig. 1, the schematic flow sheet of Fig. 1 a kind of application testing method based on Monkey order disclosed in the embodiment of the present invention.As shown in Figure 1, can should comprise the following steps based on the application testing method of Monkey order:
S101, receive Monkey order for intended application, this Monkey order comprises at least two test accesss of intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset.
In the embodiment of the present invention, said method can be applied to terminals such as including but not limited to smart mobile phone, panel computer, palm PC, and above-mentioned intended application can be various types of application of installing in terminal, as " cleaning great master ", " battery doctor " etc.
In the embodiment of the present invention, when tester wants to carry out stability test to certain application, tester can by comprising test access, pseudo-random event quantity for each test access to terminal input, and the Monkey order of pseudo-random event sum, triggering terminal is tested this application according to this Monkey order.
For example, suppose that tester wants to test the stability of " cleaning great master ", tester can apply the test access of " cleaning great master " by Offered target in test instruction, this test access can be each function choosing-item of intended application " cleaning great master ", as " garbage-cleaning ", " internal memory acceleration ", " installing and privacy ", " software administration ", and " setting " etc.Tester can also arrange the pseudo-random event quantity for each test access, as for " garbage-cleaning ", " internal memory acceleration ", " install and privacy ", " software administration ", and the pseudo-random event quantity of " setting " is respectively 10000, correspondingly, pseudorandom quantity add up to 50000.
S102, respond this Monkey order, run this intended application.
In the embodiment of the present invention, after terminal receives the test instruction for intended application, this test instruction can be responded, run this intended application.
Such as, when terminal receives the test instruction for " cleaning great master ", this test instruction can be responded, operational objective application " cleaning great master ".
S103, respectively using each test access as entrance, and to perform for the pseudo-random event of this test access.
In the embodiment of the present invention, after terminal operating intended application, the test access of the intended application that can comprise according to Monkey order, respectively using the entrance of each test access as Monkey, namely control objectives application enters function interface corresponding to each test access, and perform for this test access for random occurrence.
As the optional embodiment of one, in above-mentioned steps S103, respectively using the entrance of each test access as Monkey, perform the pseudo-random event for this test access, can comprise the following steps:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, perform the pseudo-random event for this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default random occurrence quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of this intended application have all been tested.
In this embodiment, terminal can be tested each test access of the intended application that Monkey order comprises at random, and when the number of executions of the pseudo-random event for all test accesss all reaches the default random occurrence quantity for this test access, determine that all test accesss of intended application have all been tested.
For example, still for the test for " cleaning great master " cited in step S101, after test starts, terminal can control, and " cleaning great master " enters arbitrary test access do not tested, test access is entered as terminal can control " cleaning great master "---" garbage-cleaning ", and the pseudo-random event performed for this test access, when the number of executions of the pseudo-random event for " garbage-cleaning " reaches 10000, terminal control " cleaning great master " enters other test access do not tested (" internal memory acceleration ", " install and privacy ", " software administration " or " setting "), and the pseudo-random event performed for this test access, when terminal pins is to " garbage-cleaning ", " internal memory acceleration ", " install and privacy ", " software administration ", and the number of executions of the pseudo-random event of " setting " is when all reaching 10000, determine that intended application " cleaning great master " all test accesss have all been tested.
As the optional embodiment of another kind, in above-mentioned steps S103, respectively using each test access as the entrance of Monkey, perform the pseudo-random event for this test access, can comprise the following steps:
Steps A 2, according to the testing sequence preset, be the entrance of Monkey by the test access of testing sequence optimum in the test access do not tested, perform the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of above-mentioned intended application have all been tested.
In this embodiment, tester is when to terminal input Monkey order, the testing sequence of each test access can also be set, this testing sequence can be arranged at random by tester, also can arrange according to the priority of each test access of intended application order from high to low, wherein, the priority of each test access of this intended application can be determined according to the frequency of utilization of function choosing-item corresponding to each test access of intended application, frequency of utilization is higher, and priority is higher; Frequency of utilization is lower, and priority is lower; The frequency of utilization of the function choosing-item that each test access of this intended application is corresponding can be determined by sampling statistics.
For example, still for the test for " cleaning great master " cited in step S101, suppose that the testing sequence of each test access preset is followed successively by " garbage-cleaning ", " internal memory acceleration ", " software administration ", " setting ", " install and privacy ", namely the testing sequence of " garbage-cleaning " is optimum, all the other reduce successively, after then test starts, terminal can control, and " cleaning great master " enters " garbage-cleaning ", and the pseudo-random event performed for this test access, when the number of executions of the pseudo-random event for " garbage-cleaning " reaches 10000, terminal control " cleaning great master " enters the test access of testing sequence optimum in the test access do not tested, i.e. " internal memory acceleration ", and the pseudo-random event performed for " internal memory acceleration ", by that analogy, until when reaching 10000 for the number of executions of the pseudo-random event of " install and privacy ", determine that intended application " cleaning great master " all test accesss have all been tested.
S104, in the implementation of the pseudo-random event for test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates.
In the embodiment of the present invention, consider in the process performing pseudo-random event, may " home key " event of triggering terminal, " exit button " in " back key " or function interface etc., thus cause the generation of invalid test, in order to ensure the Validity Test in application testing as far as possible, in the process for the pseudo-random event of certain test access of execution, can the window name of the monitor terminal the superiors window window name corresponding with this test access whether mate.
For example, still for the test for " cleaning great master " cited in step S101, suppose that terminal is performing the pseudo-random event for " garbage-cleaning ", then in the window that the window name that Validity Test should occur in the window name function window corresponding with " garbage-cleaning " is in this process mated.Therefore, can the window name of monitoring terminal the superiors' window in this process, if the window name of the function that the window name of the superiors' window is corresponding with " garbage-cleaning " is mated, namely the superiors' window is the function window that in the function window that function window that " garbage-cleaning " is corresponding or " garbage-cleaning " are corresponding, certain subfunction option is corresponding, then determine that the pseudo-random event for " garbage-cleaning " performed is Validity Test, otherwise, then think for invalid test.
If S105 does not mate, suspend the pseudo-random event performed for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continues to perform the pseudo-random event for this test access.
In the embodiment of the present invention, when the window name corresponding with this test access when the window name of terminal the superiors window is not mated, in order to avoid the generation of invalid test, terminal can suspend the pseudo-random event performed for this test access, and then, control terminal the window corresponding with this test access can be set to the superiors' window, and continue to perform the pseudo-random event for this test access.
As the optional embodiment of one, in the embodiment of the present invention, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, comprising:
When terminal the superiors window is desktop window, judge the window whether terminal opens the window name window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for this window name mated is window maximized;
Otherwise control terminal operational objective is applied, and controls this intended application and enter this test access;
When terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
In this embodiment, if the window name of the terminal the superiors window window name corresponding with this test access is not mated, then terminal can carry out respective handling according to the situation of current the superiors' window further.
When terminal the superiors window is desktop window, " exit button " that then may trigger " home key " event or trigger in function interface corresponding to this test access, now, the window whether terminal has opened the window name window name corresponding with this test access and mate can be judged further, if open, then can think and trigger " home key " event in test process, the window of the window name coupling that this window name is corresponding with test access has been minimized, thus, can control terminal window name corresponding with test access for this window name is mated window maximized, if do not open, then can think and to trigger " exit button " in test process, the window of the window name coupling that this window name is corresponding with test access has been closed, thus, and can the application of control terminal operational objective, and control objectives application enters this test access.
When terminal the superiors window is window corresponding to intended application, can think in test process, trigger " back key " event, intended application has exited test access, return to upper level function interface, such as, " cleaning great master " has returned to main interface from the function interface that " garbage-cleaning " is corresponding.Thus, terminal can control this intended application and reenter this test access.
S106, all to test when at least two test accesss of intended application, and when the execution of pseudo-random event sum reaches default pseudo-random event sum, determined that intended application has been tested.
In the embodiment of the present invention, when at least two test accesss of above-mentioned intended application have all been tested, and when the execution of pseudo-random event sum reaches default pseudo-random event sum, determine that intended application has been tested.
Visible, in the method flow described by Fig. 1, by setting the test access of application testing, and for the pseudo-random event quantity of each test access, thus, can ensure that the Test coverage for intended application is more comprehensive; Simultaneously, by performing in the process for the pseudo-random event of each test access, the window name whether monitoring terminal the superiors window is corresponding with this test access is mated, and when not mating, suspend the pseudo-random event performed for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continue to perform the pseudo-random event for this test access, thus, effectively reduce the generation of invalid test, provide the validity of application testing.
Refer to Fig. 2, the another kind that Fig. 2 provides for the embodiment of the present invention is based on the schematic flow sheet of the application testing method of Monkey order.As shown in Figure 2, can should comprise the following steps based on the application testing method of Monkey order:
S201, receive Monkey order for intended application, this Monkey order comprises at least two test accesss of intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset.
In the embodiment of the present invention, said method can be applied to terminals such as including but not limited to smart mobile phone, panel computer, palm PC, and above-mentioned intended application can be various types of application of installing in terminal, as " cleaning great master ", " battery doctor " etc.
In the embodiment of the present invention, when tester wants to carry out stability test to certain application, tester can by comprising test access, pseudo-random event quantity for each test access to terminal input, and the Monkey order of pseudo-random event sum, triggering terminal is tested this application according to this Monkey order.
For example, suppose that tester wants to test the stability of " cleaning great master ", tester can apply the test access of " cleaning great master " by Offered target in test instruction, this test access can be each function choosing-item of intended application " cleaning great master ", as " garbage-cleaning ", " internal memory acceleration ", " installing and privacy ", " software administration ", and " setting " etc.Tester can also arrange the pseudo-random event quantity for each test access, as for " garbage-cleaning ", " internal memory acceleration ", " install and privacy ", " software administration ", and the pseudo-random event quantity of " setting " is respectively 10000, correspondingly, pseudorandom quantity add up to 50000.
S202, respond this Monkey order, run this intended application.
In the embodiment of the present invention, after terminal receives the test instruction for intended application, this test instruction can be responded, run this intended application.
Such as, when terminal receives the test instruction for " cleaning great master ", this test instruction can be responded, operational objective application " cleaning great master ".
S203, using the entrance of arbitrary test access do not tested as Monkey, perform the pseudo-random event for this test access.
In the embodiment of the present invention, after terminal operating intended application, the test access of the intended application that can comprise according to Monkey order, respectively using the entrance of each test access as Monkey, namely control objectives application enters function interface corresponding to each test access, and perform for this test access for random occurrence.
In embodiments of the present invention, the test access do not tested for Stochastic choice is described as the entrance of Monkey, but worth explanation, in the technical scheme that the embodiment of the present invention provides, also the entrance of Monkey can be determined in the mode of nonrandom selection, as the testing sequence according to each test access preset, respectively using the entrance of the test access of testing sequence optimum in the test access do not tested as Monkey, its specific implementation see the associated description in above-mentioned steps S103, can not repeat them here.
S204, in the implementation of the pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates.If so, S205 is gone to step; Otherwise, go to step S206.
In the embodiment of the present invention, consider in the process performing pseudo-random event, may " home key " event of triggering terminal, " exit button " in " back key " or function interface etc., thus cause the generation of invalid test, in order to ensure the Validity Test in application testing as far as possible, in the process for the pseudo-random event of certain test access of execution, can the window name of the monitor terminal the superiors window window name corresponding with this test access whether mate.
For example, still for the test for " cleaning great master " cited in step S201, suppose that terminal is performing the pseudo-random event for " garbage-cleaning ", then in the window that the window name that Validity Test should occur in the window name function window corresponding with " garbage-cleaning " is in this process mated.Therefore, can the window name of monitoring terminal the superiors' window in this process, if the window name of the function that the window name of the superiors' window is corresponding with " garbage-cleaning " is mated, namely the superiors' window is the function window that in the function window that function window that " garbage-cleaning " is corresponding or " garbage-cleaning " are corresponding, certain subfunction option is corresponding, then determine that the pseudo-random event for " garbage-cleaning " performed is Validity Test, otherwise, then think for invalid test.
S205, time-out perform the pseudo-random event for this test access, and the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continue to perform the pseudo-random event for this test access.
In the embodiment of the present invention, when the window name corresponding with this test access when the window name of terminal the superiors window is not mated, in order to avoid the generation of invalid test, terminal can suspend the pseudo-random event performed for this test access, and then, control terminal the window corresponding with this test access can be set to the superiors' window, and continue to perform the pseudo-random event for this test access.
As the optional embodiment of one, in the embodiment of the present invention, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, comprising:
When terminal the superiors window is desktop window, judge the window whether terminal opens the window name window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for this window name mated is window maximized;
Otherwise control terminal operational objective is applied, and controls this intended application and enter this test access;
When terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
In this embodiment, if the window name of the terminal the superiors window window name corresponding with this test access is not mated, then terminal can carry out respective handling according to the situation of current the superiors' window further.
When terminal the superiors window is desktop window, " exit button " that then may trigger " home key " event or trigger in function interface corresponding to this test access, now, the window whether terminal has opened the window name window name corresponding with this test access and mate can be judged further, if open, then can think and trigger " home key " event in test process, the window of the window name coupling that this window name is corresponding with test access has been minimized, thus, can control terminal window name corresponding with test access for this window name is mated window maximized, if do not open, then can think and to trigger " exit button " in test process, the window of the window name coupling that this window name is corresponding with test access has been closed, thus, and can the application of control terminal operational objective, and control objectives application enters this test access.
When terminal the superiors window is window corresponding to intended application, can think in test process, trigger " back key " event, intended application has exited test access, return to upper level function interface, such as, " cleaning great master " has returned to main interface from the function interface that " garbage-cleaning " is corresponding.Thus, terminal can control this intended application and reenter this test access.
S206, when the number of executions of the described pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, determine that this test access has been tested.
In the embodiment of the present invention, if in the implementation of the pseudo-random event for certain test access, the window name that the window name of the terminal the superiors window monitored is corresponding with test access is mated all the time, then can think that this pseudo-random event is Validity Test, and then, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, can determine that this test access has been tested.
S207, judge whether to there is the test access do not tested; If be judged as YES, go to step S203; Otherwise, go to step S208.
In the embodiment of the present invention, terminal can be tested each test access of the intended application that Monkey order comprises at random, and when the number of executions of the pseudo-random event for all test accesss all reaches the default random occurrence quantity for this test access, determine that all test accesss of intended application have all been tested.
For example, still for the test for " cleaning great master " cited in step S101, after test starts, terminal can control, and " cleaning great master " enters arbitrary test access do not tested, test access is entered as terminal can control " cleaning great master "---" garbage-cleaning ", and the pseudo-random event performed for this test access, when the number of executions of the pseudo-random event for " garbage-cleaning " reaches 10000, terminal control " cleaning great master " enters other test access do not tested (" internal memory acceleration ", " install and privacy ", " software administration " or " setting "), and the pseudo-random event performed for this test access, when terminal pins is to " garbage-cleaning ", " internal memory acceleration ", " install and privacy ", " software administration ", and the number of executions of the pseudo-random event of " setting " is when all reaching 10000, determine that intended application " cleaning great master " all test accesss have all been tested.
S208, all to test when at least two test accesss of intended application, and when the execution of pseudo-random event sum reaches default pseudo-random event sum, determined that intended application has been tested.
In the embodiment of the present invention, when at least two test accesss of above-mentioned intended application have all been tested, and when the execution of pseudo-random event sum reaches default pseudo-random event sum, determine that intended application has been tested.
By describing above and can finding out, in the technical scheme that the embodiment of the present invention provides, when receiving the Monkey order for intended application, respond this Monkey order, run this intended application, and each test access Monkey order comprised respectively is as the entrance of Monkey, perform the pseudo-random event for this test access, in the implementation of the pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates, if do not mate, then suspend the pseudo-random event performed for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continue to perform the pseudo-random event for this test access, when all test accesss of intended application have all been tested, and the execution of pseudo-random event sum reaches default pseudo-random event sum, determine that this intended application has been tested, owing to having preset at least two test accesss, and the pseudo-random event quantity set respectively for each test access, thus, all pseudo-random event can be avoided only with the entrance that single test access (i.e. the function choosing-item of intended application) is Monkey, ensure that the Test coverage for intended application is more comprehensive, simultaneously, owing to performing in the process for the pseudo-random event of each test access, the window name whether correspondingly with this test access monitoring this terminal the superiors window is mated, thus, can ensure for the execution of the pseudo-random event of this test access it is perform in the window corresponding with this test access, ensure that based on the Validity Test in the application testing of Monkey order, improve the validity of application testing.
Be apparatus of the present invention embodiment below, apparatus of the present invention embodiment and the inventive method embodiment belong to same design, for performing the method described in the inventive method embodiment.For convenience of explanation, apparatus of the present invention embodiment only illustrates the part relevant to apparatus of the present invention embodiment, and concrete ins and outs do not disclose, and please refer to the description of the inventive method embodiment, repeats no longer one by one herein.
Refer to Fig. 3, the structural representation of a kind of application testing device based on Monkey order that Fig. 3 provides for the embodiment of the present invention.As shown in Figure 3, can should comprise based on the application testing device of Monkey order:
Receiver module 301, for receiving the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Running module 302, for responding described Monkey order, running described intended application;
Execution module 303, for respectively using the entrance of each test access as Monkey, performs the pseudo-random event for this test access;
Monitoring modular 304, in the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
Control module 305, for when the monitoring result of described monitoring modular 304 is not for mating, control described execution module 303 and suspend the described pseudo-random event for this test access of execution, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and controls the described pseudo-random event for this test access of described execution module 303 continuation execution;
Determination module 306, has all tested at least two test accesss when described intended application, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
In an alternative embodiment, described execution module 303, specifically for being realized the entrance of each test access as Monkey by following steps, and can perform the described pseudo-random event for this test access:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
In an alternative embodiment, described execution module 303, specifically for being realized the entrance of each test access as Monkey by following steps, and can perform the described pseudo-random event for this test access:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
In an alternative embodiment, described execution module 303, can also be used for when the monitoring result of described monitoring modular 304 is coupling, and when reaching the described default pseudo-random event quantity for this test access for the number of executions of the pseudo-random event of this test access, determine that this test access has been tested.
In an alternative embodiment, described control module 305, can be set to the superiors' window specifically for realizing control terminal in the following manner by the window that window name corresponding with this test access for window name is mated:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
Fig. 4 is the another kind that provides in the embodiment of the present invention structural representation based on the application testing device of Monkey order.As shown in Figure 4, should comprise based on the application testing device of Monkey order: at least one processor 401, such as CPU, at least one user interface 403, storer 404, at least one communication bus 402.Wherein, communication bus 402 is for realizing the connection communication between these assemblies.Wherein, user interface 403 can comprise display screen (Display), and optional user interface 403 can also comprise wireline interface, the wave point of standard.Storer 404 can be high-speed RAM storer, also can be non-labile storer (non-volatile memory), such as at least one magnetic disk memory.Storer 404 can also be optionally that at least one is positioned at the memory storage away from aforementioned processor 401.Wherein store batch processing code in storer 404, and processor 401 calls the program code stored in storer 404, for performing following operation:
Receive the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Respond described Monkey order, run described intended application;
Respectively using the entrance of each test access as Monkey, perform the pseudo-random event for this test access;
In the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
If do not mate, suspend and perform the described pseudo-random event for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continues to perform the described pseudo-random event for this test access;
When at least two test accesss of described intended application have all been tested, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
In an alternative embodiment, processor 401 calls the program code of storage in storer 404 respectively using the entrance of each test access as Monkey, and performs the described pseudo-random event for this test access, can specifically comprise the following steps:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
In an alternative embodiment, processor 401 calls the program code of storage in storer 404 respectively using the entrance of each test access as Monkey, and performs the described pseudo-random event for this test access, can specifically comprise the following steps:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
In an alternative embodiment, processor 401 calls after whether the window name of program code monitoring terminal the superiors window that stores in the storer 404 window name corresponding with this test access mate, and can also perform following operation:
If coupling, then, when the number of executions of the described pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, determine that this test access has been tested.
In an alternative embodiment, processor 401 calls the program code control terminal stored in storer 404 and the window that window name corresponding with this test access for window name is mated is set to the superiors' window, can specifically comprise:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
The embodiment of the present invention additionally provides a kind of terminal, can comprise arbitrary application testing device based on Monkey order as shown in Figure 3-4.
In the description of this instructions, specific features, structure, material or feature that the description of reference term " embodiment ", " some embodiments ", " example ", " concrete example " or " some examples " etc. means to describe in conjunction with this embodiment or example are contained at least one embodiment of the present invention or example.In this manual, to the schematic representation of above-mentioned term not must for be identical embodiment or example.And the specific features of description, structure, material or feature can combine in one or more embodiment in office or example in an appropriate manner.In addition, when not conflicting, the feature of the different embodiment described in this instructions or example and different embodiment or example can carry out combining and combining by those skilled in the art.
In addition, term " first ", " second " only for describing object, and can not be interpreted as instruction or hint relative importance or imply the quantity indicating indicated technical characteristic.Thus, be limited with " first ", the feature of " second " can express or impliedly comprise at least one this feature.In describing the invention, the implication of " multiple " is at least two, such as two, three etc., unless otherwise expressly limited specifically.
Describe and can be understood in process flow diagram or in this any process otherwise described or method, represent and comprise one or more for realizing the module of the code of the executable instruction of the step of specific logical function or process, fragment or part, and the scope of the preferred embodiment of the present invention comprises other realization, wherein can not according to order that is shown or that discuss, comprise according to involved function by the mode while of basic or by contrary order, carry out n-back test, this should understand by embodiments of the invention person of ordinary skill in the field.
In flow charts represent or in this logic otherwise described and/or step, such as, the sequencing list of the executable instruction for realizing logic function can be considered to, may be embodied in any computer-readable medium, for instruction execution system, device or equipment (as computer based system, comprise the system of processor or other can from instruction execution system, device or equipment instruction fetch and perform the system of instruction) use, or to use in conjunction with these instruction execution systems, device or equipment.With regard to this instructions, " computer-readable medium " can be anyly can to comprise, store, communicate, propagate or transmission procedure for instruction execution system, device or equipment or the device that uses in conjunction with these instruction execution systems, device or equipment.The example more specifically (non-exhaustive list) of computer-readable medium comprises following: the electrical connection section (electronic installation) with one or more wiring, portable computer diskette box (magnetic device), random access memory (RAM), ROM (read-only memory) (ROM), erasablely edit ROM (read-only memory) (EPROM or flash memory), fiber device, and portable optic disk ROM (read-only memory) (CDROM).In addition, computer-readable medium can be even paper or other suitable media that can print described program thereon, because can such as by carrying out optical scanning to paper or other media, then carry out editing, decipher or carry out process with other suitable methods if desired and electronically obtain described program, be then stored in computer memory.
Should be appreciated that each several part of the present invention can realize with hardware, software, firmware or their combination.In the above-described embodiment, multiple step or method can with to store in memory and the software performed by suitable instruction execution system or firmware realize.Such as, if realized with hardware, the same in another embodiment, can realize by any one in following technology well known in the art or their combination: the discrete logic with the logic gates for realizing logic function to data-signal, there is the special IC of suitable combinational logic gate circuit, programmable gate array (PGA), field programmable gate array (FPGA) etc.
Those skilled in the art are appreciated that realizing all or part of step that above-described embodiment method carries is that the hardware that can carry out instruction relevant by program completes, described program can be stored in a kind of computer-readable recording medium, this program perform time, step comprising embodiment of the method one or a combination set of.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing module, also can be that the independent physics of unit exists, also can be integrated in a module by two or more unit.Above-mentioned integrated module both can adopt the form of hardware to realize, and the form of software function module also can be adopted to realize.If described integrated module using the form of software function module realize and as independently production marketing or use time, also can be stored in a computer read/write memory medium.
The above-mentioned storage medium mentioned can be ROM (read-only memory), disk or CD etc.Although illustrate and describe embodiments of the invention above, be understandable that, above-described embodiment is exemplary, can not be interpreted as limitation of the present invention, and those of ordinary skill in the art can change above-described embodiment within the scope of the invention, revises, replace and modification.
Claims (11)
1. based on an application testing method for Monkey order, it is characterized in that, comprising:
Receive the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Respond described Monkey order, run described intended application;
Respectively using the entrance of each test access as Monkey, perform the pseudo-random event for this test access;
In the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
If do not mate, suspend and perform the described pseudo-random event for this test access, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and continues to perform the described pseudo-random event for this test access;
When at least two test accesss of described intended application have all been tested, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
2. method according to claim 1, is characterized in that, described respectively using the entrance of each test access as Monkey, and the pseudo-random event performed for this test access comprises the following steps:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
3. method according to claim 1, is characterized in that, described respectively using the entrance of each test access as Monkey, and the pseudo-random event for this test access described in performing comprises the following steps:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
4. method according to claim 1, is characterized in that, whether the window name of the described monitoring terminal the superiors window window name corresponding with this test access also comprises after mating:
If coupling, then, when the number of executions of the described pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, determine that this test access has been tested.
5. method according to claim 1, is characterized in that, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by described control terminal, comprising:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
6., based on an application testing device for Monkey order, it is characterized in that, comprising:
Receiver module, for receiving the Monkey order for intended application, described Monkey order comprises at least two test accesss of described intended application, the default pseudo-random event quantity for each test access, and the pseudo-random event sum preset;
Running module, for responding described Monkey order, running described intended application;
Execution module, for respectively using the entrance of each test access as Monkey, performs the pseudo-random event for this test access;
Monitoring modular, in the implementation of the described pseudo-random event for this test access, whether the window name that the window name of monitoring terminal the superiors window is corresponding with this test access mates;
Control module, for when the monitoring result of described monitoring modular is not for mating, control described execution module and suspend the described pseudo-random event for this test access of execution, the window that window name corresponding with this test access for window name is mated is set to the superiors' window by control terminal, and controls the described pseudo-random event for this test access of described execution module continuation execution;
Determination module, has all tested at least two test accesss when described intended application, and the execution of pseudo-random event sum reaches described default pseudo-random event sum, determines that described intended application has been tested.
7. device according to claim 6, is characterized in that, described execution module, specifically for being realized the entrance of each test access as Monkey by following steps, and performs the described pseudo-random event for this test access:
Steps A 1, using the entrance of arbitrary test access do not tested as Monkey, and perform for the pseudo-random event of this test access;
Step B1, when the number of executions of the pseudo-random event for this test access reaches the default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A1; Otherwise, determine that at least two test accesss of described intended application have all been tested.
8. device according to claim 6, is characterized in that, described execution module, specifically for being realized the entrance of each test access as Monkey by following steps, and performs the described pseudo-random event for this test access:
Steps A 2, according to the testing sequence preset, the test access of testing sequence optimum in the test access for test, as the entrance of Monkey, is performed the pseudo-random event for this test access;
Step B2, when the number of executions of the pseudo-random event for this test access reaches the described default pseudo-random event quantity for this test access, judge whether to there is the test access do not tested, if be judged as YES, go to step A2; Otherwise, determine that at least two test accesss of described intended application have all been tested.
9. device according to claim 6, is characterized in that,
Described execution module, is also coupling for the monitoring result when described monitoring modular, and when reaching the described default pseudo-random event quantity for this test access for the number of executions of the pseudo-random event of this test access, determines that this test access has been tested.
10. device according to claim 6, is characterized in that, described control module, specifically for realizing control terminal in the following manner, the window that window name corresponding with this test access for window name is mated is set to the superiors' window:
When described terminal the superiors window is desktop window, judge the window whether terminal opens the window name corresponding with this test access and mate;
If be judged as YES, what window name corresponding with this test access for described window name mated is window maximized;
Otherwise control terminal runs described intended application, and control described intended application and enter this test access;
When described terminal the superiors window is window corresponding to this intended application, controls this intended application and enter this test access.
11. 1 kinds of terminals, is characterized in that, comprise the application testing device based on Monkey order as described in any one of claim 6-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510303641.9A CN104866427B (en) | 2015-06-05 | 2015-06-05 | Application testing method and device based on Monkey command and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510303641.9A CN104866427B (en) | 2015-06-05 | 2015-06-05 | Application testing method and device based on Monkey command and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104866427A true CN104866427A (en) | 2015-08-26 |
| CN104866427B CN104866427B (en) | 2018-01-23 |
Family
ID=53912273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510303641.9A Active CN104866427B (en) | 2015-06-05 | 2015-06-05 | Application testing method and device based on Monkey command and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104866427B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070094541A1 (en) * | 2005-10-25 | 2007-04-26 | Hua Kang | Method and apparatus for generating test execution sequences automatically for a software testing process |
| CN102110053A (en) * | 2011-03-18 | 2011-06-29 | 广东欧珀移动通信有限公司 | Random testing method based on Android |
| CN102141960A (en) * | 2011-03-18 | 2011-08-03 | 广东欧珀移动通信有限公司 | Automatic test method based on Android |
| CN102999419A (en) * | 2011-09-13 | 2013-03-27 | 百度在线网络技术（北京）有限公司 | Android test incident record and playback methods and device |
| CN103942146A (en) * | 2014-04-22 | 2014-07-23 | 上海斐讯数据通信技术有限公司 | Visual Monkey test method and device |
-
2015
- 2015-06-05 CN CN201510303641.9A patent/CN104866427B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070094541A1 (en) * | 2005-10-25 | 2007-04-26 | Hua Kang | Method and apparatus for generating test execution sequences automatically for a software testing process |
| CN102110053A (en) * | 2011-03-18 | 2011-06-29 | 广东欧珀移动通信有限公司 | Random testing method based on Android |
| CN102141960A (en) * | 2011-03-18 | 2011-08-03 | 广东欧珀移动通信有限公司 | Automatic test method based on Android |
| CN102999419A (en) * | 2011-09-13 | 2013-03-27 | 百度在线网络技术（北京）有限公司 | Android test incident record and playback methods and device |
| CN103942146A (en) * | 2014-04-22 | 2014-07-23 | 上海斐讯数据通信技术有限公司 | Visual Monkey test method and device |
Non-Patent Citations (3)
| Title |
|---|
| BIRGIT HOFER ET AL.: "GUI Savvy End-to-End Testing with Smart Monkeys", 《SOFTWARE TESTING，VERIFICATION AND VALIDATION（ICST），2014IEEE SEVENTH INTERNATIONAL CONFERENCE ON》 * |
| 池云: "Android系统稳定性测试探究", 《电子测试》 * |
| 黄莹: "基于Android平台智能手机多方通话软件测试系统的研究与实现", 《中国优秀硕士学位论文全文数据库·信息科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104866427B (en) | 2018-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9280451B2 (en) | Testing device | |
| US20140211021A1 (en) | Test system for evaluating mobile device and driving method thereof | |
| CN103019942B (en) | Method and system for automatically testing applications to be tested based on android system | |
| CN103984626B (en) | A kind of method and device for generating test case script | |
| CN110377520B (en) | Transaction scenario testing method and device, electronic equipment and readable storage medium | |
| CN111475417A (en) | Automatic testing method, device, equipment and storage medium | |
| CN110197698B (en) | Method and device for automatically testing influence of different power states of SSD (solid State drive) | |
| CN104777416A (en) | Testing method and tester for circuit board | |
| CN104834601A (en) | Android system-based automatic testing method for memory leakage of intelligent terminal | |
| CN110597675A (en) | Chip testing method and device, storage medium and burner | |
| CN112231206A (en) | Script editing method for application program test, computer readable storage medium and test platform | |
| CN104199693A (en) | Method, device and terminal for obtaining boot time | |
| CN107977318A (en) | A kind of energy consumption and performance test methods of Android application programs | |
| CN106201810A (en) | A kind of method of testing, device | |
| CN112445670B (en) | eMMC test method and device | |
| CN110928787B (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| CN112202951A (en) | Mobile phone compatibility testing method and related device | |
| CN105893233A (en) | Method and system used for automatically testing firmware | |
| CN105095072A (en) | Application testing method and device and terminal | |
| CN103577290A (en) | Test script playback rhythm control method and system | |
| CN115145381A (en) | Method, system, storage medium and equipment for remotely resetting BMC chip | |
| CN110795330A (en) | Monkey pressure testing method and device | |
| CN104866427A (en) | Application testing method and device based on Monkey command and terminal | |
| CN113687942B (en) | Detection method and device and electronic equipment | |
| CN114997102A (en) | Physical layer verification method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |