CN104699607A - Automation testing method and system for mobile terminal - Google Patents
Automation testing method and system for mobile terminal Download PDFInfo
- Publication number
- CN104699607A CN104699607A CN201510099845.5A CN201510099845A CN104699607A CN 104699607 A CN104699607 A CN 104699607A CN 201510099845 A CN201510099845 A CN 201510099845A CN 104699607 A CN104699607 A CN 104699607A
- Authority
- CN
- China
- Prior art keywords
- scene
- script file
- driving layer
- order
- judging
- 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.)
- Pending
Links
Landscapes
- Telephone Function (AREA)
Abstract
The invention provides an automation testing method and an automation testing system for a mobile terminal. The automation testing method comprises the following steps: A, when detecting that a script file is opened, reading the scene circulation times and the scene types in the script file, and analyzing the script file to obtain a driving layer instruction; B, transmitting the driving layer instruction to a driving layer to execute, when a present driving layer instruction is executed, outputting corresponding testing result, if the testing result corresponding to the present driving layer instruction is accepted and the scene circulation times of the scene types corresponding to the present driving layer instruction is achieved, judging whether a next script file is available or not, and if the next script file is available, opening the next script file, and returning to the step A. By adopting the automation testing method and the automation testing system, the requirements on the programming levels of testing operators and the testing scenes can be alleviated, the testing cost can be reduced, and the testing efficiency can be improved.
Description
Technical field
The present invention relates to technical field of measurement and test, in particular a kind of mobile terminal automation testing method and system.
Background technology
Along with cell-phone function becomes increasingly complex, the manpower that cell phone software test drops into gets more and more, and testing cost is more and more higher, and traditional manual testing is difficult to meet growing cell phone software testing requirement, and the automatic test implementing cell phone software becomes a kind of trend.But at present the cell phone software automatic test of main flow depends on for the corresponding test procedure of PC exploitation compiling, thus control mobile terminal to be tested and complete test.But, because the operating system (Windows) of PC self is more complicated, the test procedure that causing matches when testing uses is also comparatively complicated, namely test based on PC method to the programming levels of tester and the requirement of test scene higher, cause testing cost high, and testing efficiency is low.
Therefore, prior art has yet to be improved and developed.
Summary of the invention
In view of above-mentioned the deficiencies in the prior art, the object of the present invention is to provide a kind of mobile terminal automation testing method and system, be intended to solve in prior art to the programming levels of tester and the requirement of test scene higher, cause testing cost high, and the defect that testing efficiency is low.
Technical scheme of the present invention is as follows:
A kind of mobile terminal automation testing method, wherein, said method comprising the steps of:
A, when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order;
B, will drive layer command transfer to drive layer perform, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and returning steps A.
Described mobile terminal automation testing method, wherein, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
Described kind of mobile terminal automation testing method, wherein, described steps A specifically comprises:
A1, when detecting that script file is opened, then read scene corresponding to script file;
A2, judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then performing steps A 3, then performing steps A 4 when not having;
The scene loop number of times of A3, reading scene, performs steps A 5;
A4, the scene loop number of times of scene is set to 1, performs steps A 5;
The scene loop number of times of A5, saving scenario;
A6, judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then performing steps A 7, then performing steps A 8 when not having;
The scene type of A7, reading scene, and perform steps A 9;
A8, the scene type of scene is set to common scenarios, and performs steps A 9;
The scene type of A9, saving scenario;
Variable in A10, analyzing script file, and script file is converted sentence by sentence to the order of driving layer.
Described kind of mobile terminal automation testing method, wherein, described step B specifically comprises:
B1, the driving layer execution that will layer order driven to be sent to mobile terminal;
B2, judge when the execution result of front wheel driving layer order, when execution result for by time then perform step B3, when execution result be unsuccessfully time then perform step B5;
B3, judge whether to reach the scene loop number of times of specifying, then performing step B7 when being, when no, then perform step B4;
Whether B4, the scene type judging scene are the scene of attempting designated cycle number of times, then performing step B7, when no, then perform step B1 when being;
B5, judge that whether the scene type of scene is the scene of forced circulation predetermined number of times, then performing step B6 when being, when no, then perform step B7;
B6, judge whether to reach the scene loop number of times of specifying, then performing step B7 when being, when no, then perform step B1;
B7, the execution terminating when the order of front wheel driving layer;
B8, judge whether next script file, when sometimes then opening next script file and returning steps A.
A kind of mobile terminal automation testing system, wherein, comprising:
Obtain and parsing module, for when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order;
Judge and control module, perform to driving layer for layer command transfer will be driven, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
Described mobile terminal automation testing system, wherein, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
Described mobile terminal automation testing system, wherein, described acquisition and parsing module specifically comprise:
Scene acquiring unit, for when detecting that script file is opened, then reads scene corresponding to script file;
First judging unit, for judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then starting cycle index acquiring unit, then starts cycle index setting unit when not having;
Cycle index acquiring unit, for reading the scene loop number of times of scene, restarts cycle index storage unit;
Cycle index setting unit, for the scene loop number of times of scene is set to 1, restarts cycle index storage unit;
Cycle index storage unit, for the scene loop number of times of saving scenario;
Second judging unit, for judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then starting scene type acquiring unit, then starts scene type setting unit when not having;
Scene type acquiring unit, for reading the scene type of scene, and starts scene type storage unit;
Scene type setting unit, for the scene type of scene is set to common scenarios, and starts scene type storage unit;
Scene type storage unit, for the scene type of saving scenario;
Resolution unit, for the variable in analyzing script file, and converts the order of driving layer to sentence by sentence by script file.
Described mobile terminal automation testing system, wherein, described judgement and control module specifically comprise:
Transmitting element, for performing the driving layer driving layer order to be sent to mobile terminal;
3rd judging unit, for judging the execution result when the order of front wheel driving layer, when execution result for by time then start the 4th judging unit, when execution result be unsuccessfully time then start the 5th judging unit;
4th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element when being, then start the 5th judging unit when no;
5th judging unit, for judging whether the scene type of scene is the scene of attempting designated cycle number of times, then starting stopping performance element, then starting transmitting element when being when no;
6th judging unit, for judging that whether the scene type of scene is the scene of forced circulation predetermined number of times, then starting the 7th judging unit, when no, then start stopping performance element when being;
7th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element, when no, then start transmitting element when being;
Stop performance element, for terminating the execution when the order of front wheel driving layer;
Control module, for having judged whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
The invention provides a kind of mobile terminal automation testing method and system, method comprises: A, when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and resolve script file, obtains driving layer order; B, will drive layer command transfer to drive layer perform, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and returning steps A.The present invention can reduce the requirement to tester's programming levels and test scene, reduces testing cost simultaneously, improves testing efficiency.
Accompanying drawing explanation
Fig. 1 is the process flow diagram of mobile terminal automation testing method of the present invention preferred embodiment.
Fig. 2 obtains the particular flow sheet driving layer order in mobile terminal automation testing of the present invention.
Fig. 3 is according to the particular flow sheet driving layer order to carry out test automatically in mobile terminal automation testing of the present invention.
Fig. 4 is the structured flowchart of mobile terminal automation testing system of the present invention preferred embodiment.
Embodiment
The invention provides a kind of mobile terminal automation testing method and system, for making object of the present invention, technical scheme and effect clearly, clearly, the present invention is described in more detail below.Should be appreciated that specific embodiment described herein only in order to explain the present invention, be not intended to limit the present invention.
Refer to Fig. 1, Fig. 1 is the process flow diagram of mobile terminal automation testing method of the present invention preferred embodiment.As shown in Figure 1, it comprises the following steps:
Step S100, when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order.
In embodiments of the invention, bright when detecting that script file is opened, then read the scene loop number of times in script file and scene type, when obtaining, then each sentence of script file is all resolved, after being parsed, obtain the driving layer order corresponding with script file.
In the specific implementation, the instruction set of script file comprises in the present invention:
Click: click screen specified coordinate point;
Slide: swipe;
Drag: drag;
Press: click appointment physical button;
Into: enter specified page;
Type: input arbitrary string;
Call: dial assigned number;
Answer: receive calls;
Wake: wake screen up;
WaitID: wait object ID to be specified;
WaitDes: wait object Des to be specified;
EndCall: terminate call;
SendSMS: the note sending given content;
ClickByStr: click screen according to screen display character string;
CheckByStr: check screen according to screen display character string;
ClickByID: click screen according to Object ID;
CheckByID: check screen according to Object ID
TakeImg: screenshotss;
ClickByImg: click screen according to icon;
GetImgByRect: the rectangular area of screen printing is saved in specified path;
CheckByImg: the image checking screen appointed area;
CheckSwitchOn: the character string according to switch control display judges whether this control is in the state of choosing;
WaitStr: wait for that designated character string occurs;
ClickByClass: click screen according to Class title;
WaitSysStart: waiting system starts;
DeleteChar: delete character;
DragByStr: carry out Dragging movement according to character string;
ClickByDes: click according to Content-desc;
CheckByDes: check whether screen exists according to Content-desc;
DragByDes: carry out Dragging movement according to Content-desc;
SwitchByStr: open or close switch switch (comprising radio beginning) according to character string;
SetRotationTo: screen rotation direction is set;
SelectListByClass: cancel/select tick boxes list;
ClickByStrInList: click according to character string in drop-down list, slide downward can search whole drop-down list;
CheckByStrInList: check screen according to screen display character string, slide downward can search whole drop-down list;
CheckByStrInList_Not: check screen according to screen display character string, slide downward can search whole drop-down list;
CheckSwitchOff: judge whether this control is according to the character string of switch control display and do not choose state;
CheckByDes_Not: check whether screen does not exist according to Content-desc;
DragByStrInMulScreen: Dragging movement can carried out in horizontal rolling interface according to character string;
ClickByStr_Match: click according to character string fuzzy matching;
CheckByStr_Match: check screen according to character string fuzzy matching;
CheckByStr_Match_Not: check whether screen does not exist according to character string fuzzy matching;
ClickByDes_Match: click according to Content-desc fuzzy matching;
CheckByDes_Match: check screen according to Content-desc fuzzy matching;
CheckByDes_Match_Not: check whether screen does not exist according to Content-desc fuzzy matching;
ClickByID_Match: click according to Content-desc fuzzy matching;
CheckByID_Match: check screen according to Content-desc fuzzy matching;
CheckByID_Match_Not: check whether screen does not exist according to Content-desc fuzzy matching;
ClickByStrInList_Match: click according to fuzzy strings in drop-down list, slide downward can search whole drop-down list;
CheckByStrInList_Match: check screen according to fuzzy strings, slide downward can search whole drop-down list;
CheckByStrInList_Match_Not: check whether screen does not exist according to fuzzy strings, slide downward can search whole drop-down list;
ChickByStrInMulScreen: click action can carried out in horizontal rolling interface according to character string.
The Sentence format of script is: key word+parameter 1+parameter 2+... + [switch parameter].
Wherein, key word is one of them in the instruction set of script file; The quantity of parameter is then determined, minimum 0 according to the difference of key word, does not establish the upper limit; Switch parameter then can omit, and can value be also "-force " and "-try ".If value is "-force ", represent no matter whether this statement run succeeded, all by successfully processing; If value is "-try ", if then this statement performs failure, then again perform, until run succeeded.
Step S200, will drive layer command transfer to drive layer perform, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and returning step S100.
Further, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
In order to the operational process of understanding the present invention when automatically testing clearly, be described below by the script file comprising four kinds of different scene type.
Several applicating examples of scene are as follows:
Sample one: common scenarios.Following script realizes call and the on-hook of two mobile phones;
Scene:
Phone1:
Call 13800000001
Phone2:
WaitStr “Incoming Call” 30
Answer
Delay 10
EndCall
Delay 5
Sample two: the scene of given scenario cycle index.Following script realizes 10 calls of two mobile phones, but if wherein once converse failure, then script stops running;
Scene 10:
Phone1:
Call 13800000001
Phone2:
WaitStr "Incoming Call" 30
Answer
Delay 10
EndCall
Delay 5
Sample three: the scene of forced circulation predetermined number of times.Following script realizes 10 calls of two mobile phones, even if wherein converse unsuccessfully, still continues to perform script;
Scene 10 -force:
Phone1:
Call 13800000001
Phone2:
WaitStr "Incoming Call" 30
Answer
Delay 10
EndCall
Delay 5
Sample four: the scene of attempting designated cycle number of times.Call is set up in trial, and converse successfully if set up, then this Scene terminates, and performs follow-up script, if attempt 10 times all unsuccessfully, then script stops performing;
Scene 10 -try:
Phone1:
Call 13800000001
Phone2:
WaitStr "Incoming Call" 30
Answer
Delay 10
EndCall
Delay 5
Visible, in mobile terminal automation testing method of the present invention, each scene laminating mobile phone test business of script file, can realize various mobile phone test business scenario; And writing instruction and writing grammer of script file is simple, and easy tested slip-stick artist understands and uses, and greatly reduces learning cost; Most importantly testing efficiency is high, and Test Engineer writes out 5-8 test case every day and very easily realizes.
Further, as shown in Figure 2, the idiographic flow obtaining the order of driving layer in described step S100 comprises:
Step S101, when detecting that script file is opened, then read scene corresponding to script file;
Step S102, judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then performing step S103, then performing step S104 when not having;
The scene loop number of times of step S103, reading scene, performs step S105;
Step S104, the scene loop number of times of scene is set to 1, performs step S105;
The scene loop number of times of step S105, saving scenario;
Step S106, judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then performing step S107, then performing step S108 when not having;
The scene type of step S107, reading scene, and perform step S109;
Step S108, the scene type of scene is set to common scenarios, and performs step S109;
The scene type of step S109, saving scenario;
Variable in step S110, analyzing script file, and script file is converted sentence by sentence to the order of driving layer.
Further, as shown in Figure 3, comprise according to the idiographic flow driving layer order to carry out test automatically in described step S200:
Step S201, the driving layer execution that will layer order driven to be sent to mobile terminal;
Step S202, judge when the execution result of front wheel driving layer order, when execution result for by time then perform step S203, when execution result be unsuccessfully time then perform step S205;
Step S203, judge whether to reach the scene loop number of times of specifying, then performing step B7 when being, when no, then perform step S204;
Whether step S204, the scene type judging scene are the scene of attempting designated cycle number of times, then performing step S207, when no, then perform step S201 when being;
Step S205, judge that whether the scene type of scene is the scene of forced circulation predetermined number of times, then performing step S206 when being, when no, then perform step S207;
Step S206, judge whether to reach the scene loop number of times of specifying, then performing step S207 when being, when no, then perform step S201;
Step S207, the execution terminating when the order of front wheel driving layer;
Step S208, judge whether next script file, when sometimes then opening next script file and returning step S100.
Based on said method embodiment, present invention also offers a kind of mobile terminal automation testing system, as shown in Figure 4, it comprises:
Obtain and parsing module 100, for when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order;
Judge and control module 200, perform to driving layer for layer command transfer will be driven, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
Further, in described mobile terminal automation testing system, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
Further, in described mobile terminal automation testing system, described acquisition and parsing module 100 specifically comprise:
Scene acquiring unit, for when detecting that script file is opened, then reads scene corresponding to script file;
First judging unit, for judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then starting cycle index acquiring unit, then starts cycle index setting unit when not having;
Cycle index acquiring unit, for reading the scene loop number of times of scene, restarts cycle index storage unit;
Cycle index setting unit, for the scene loop number of times of scene is set to 1, restarts cycle index storage unit;
Cycle index storage unit, for the scene loop number of times of saving scenario;
Second judging unit, for judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then starting scene type acquiring unit, then starts scene type setting unit when not having;
Scene type acquiring unit, for reading the scene type of scene, and starts scene type storage unit;
Scene type setting unit, for the scene type of scene is set to common scenarios, and starts scene type storage unit;
Scene type storage unit, for the scene type of saving scenario;
Resolution unit, for the variable in analyzing script file, and converts the order of driving layer to sentence by sentence by script file.
Further, in described mobile terminal automation testing system, described judgement and control module 200 specifically comprise:
Transmitting element, for performing the driving layer driving layer order to be sent to mobile terminal;
3rd judging unit, for judging the execution result when the order of front wheel driving layer, when execution result for by time then start the 4th judging unit, when execution result be unsuccessfully time then start the 5th judging unit;
4th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element when being, then start the 5th judging unit when no;
5th judging unit, for judging whether the scene type of scene is the scene of attempting designated cycle number of times, then starting stopping performance element, then starting transmitting element when being when no;
6th judging unit, for judging that whether the scene type of scene is the scene of forced circulation predetermined number of times, then starting the 7th judging unit, when no, then start stopping performance element when being;
7th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element, when no, then start transmitting element when being;
Stop performance element, for terminating the execution when the order of front wheel driving layer;
Control module, for having judged whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
In sum, the invention provides a kind of mobile terminal automation testing method and system, method comprises: A, when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order; B, will drive layer command transfer to drive layer perform, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and returning steps A.The present invention can reduce the requirement to tester's programming levels and test scene, reduces testing cost simultaneously, improves testing efficiency.
Should be understood that, application of the present invention is not limited to above-mentioned citing, for those of ordinary skills, can be improved according to the above description or convert, and all these improve and convert the protection domain that all should belong to claims of the present invention.
Claims (8)
1. a mobile terminal automation testing method, is characterized in that, said method comprising the steps of:
A, when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order;
B, will drive layer command transfer to drive layer perform, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and returning steps A.
2. mobile terminal automation testing method according to claim 1, is characterized in that, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
3. plant mobile terminal automation testing method according to claim 2, it is characterized in that, described steps A specifically comprises:
A1, when detecting that script file is opened, then read scene corresponding to script file;
A2, judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then performing steps A 3, then performing steps A 4 when not having;
The scene loop number of times of A3, reading scene, performs steps A 5;
A4, the scene loop number of times of scene is set to 1, performs steps A 5;
The scene loop number of times of A5, saving scenario;
A6, judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then performing steps A 7, then performing steps A 8 when not having;
The scene type of A7, reading scene, and perform steps A 9;
A8, the scene type of scene is set to common scenarios, and performs steps A 9;
The scene type of A9, saving scenario;
Variable in A10, analyzing script file, and script file is converted sentence by sentence to the order of driving layer.
4. plant mobile terminal automation testing method according to claim 3, it is characterized in that, described step B specifically comprises:
B1, the driving layer execution that will layer order driven to be sent to mobile terminal;
B2, judge when the execution result of front wheel driving layer order, when execution result for by time then perform step B3, when execution result be unsuccessfully time then perform step B5;
B3, judge whether to reach the scene loop number of times of specifying, then performing step B7 when being, when no, then perform step B4;
Whether B4, the scene type judging scene are the scene of attempting designated cycle number of times, then performing step B7, when no, then perform step B1 when being;
B5, judge that whether the scene type of scene is the scene of forced circulation predetermined number of times, then performing step B6 when being, when no, then perform step B7;
B6, judge whether to reach the scene loop number of times of specifying, then performing step B7 when being, when no, then perform step B1;
B7, the execution terminating when the order of front wheel driving layer;
B8, judge whether next script file, when sometimes then opening next script file and returning steps A.
5. a mobile terminal automation testing system, is characterized in that, comprising:
Obtain and parsing module, for when detecting that script file is opened, then read the scene loop number of times in script file and scene type, and script file is resolved, obtain driving layer order;
Judge and control module, perform to driving layer for layer command transfer will be driven, corresponding test result is exported after the order of front wheel driving layer is finished, if when the test result that the order of front wheel driving layer is corresponding be by and reach the scene loop number of times when the corresponding scene type of front wheel driving layer order time, then judge whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
6. mobile terminal automation testing system according to claim 5, is characterized in that, described scene type comprises common scenarios, the scene of given scenario cycle index, the scene of forced circulation predetermined number of times and attempts the scene of designated cycle number of times.
7. mobile terminal automation testing system according to claim 6, it is characterized in that, described acquisition and parsing module specifically comprise:
Scene acquiring unit, for when detecting that script file is opened, then reads scene corresponding to script file;
First judging unit, for judging whether the scene that script file is corresponding has the scene loop number of times of specifying, when sometimes then starting cycle index acquiring unit, then starts cycle index setting unit when not having;
Cycle index acquiring unit, for reading the scene loop number of times of scene, restarts cycle index storage unit;
Cycle index setting unit, for the scene loop number of times of scene is set to 1, restarts cycle index storage unit;
Cycle index storage unit, for the scene loop number of times of saving scenario;
Second judging unit, for judging whether the scene that script file is corresponding has the scene type of specifying, when sometimes then starting scene type acquiring unit, then starts scene type setting unit when not having;
Scene type acquiring unit, for reading the scene type of scene, and starts scene type storage unit;
Scene type setting unit, for the scene type of scene is set to common scenarios, and starts scene type storage unit;
Scene type storage unit, for the scene type of saving scenario;
Resolution unit, for the variable in analyzing script file, and converts the order of driving layer to sentence by sentence by script file.
8. mobile terminal automation testing system according to claim 7, it is characterized in that, described judgement and control module specifically comprise:
Transmitting element, for performing the driving layer driving layer order to be sent to mobile terminal;
3rd judging unit, for judging the execution result when the order of front wheel driving layer, when execution result for by time then start the 4th judging unit, when execution result be unsuccessfully time then start the 5th judging unit;
4th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element when being, then start the 5th judging unit when no;
5th judging unit, for judging whether the scene type of scene is the scene of attempting designated cycle number of times, then starting stopping performance element, then starting transmitting element when being when no;
6th judging unit, for judging that whether the scene type of scene is the scene of forced circulation predetermined number of times, then starting the 7th judging unit, when no, then start stopping performance element when being;
7th judging unit, reaching the scene loop number of times of specifying for judging whether, then starting stopping performance element, when no, then start transmitting element when being;
Stop performance element, for terminating the execution when the order of front wheel driving layer;
Control module, for having judged whether next script file, when sometimes then opening next script file and restarting acquisition and parsing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510099845.5A CN104699607A (en) | 2015-03-06 | 2015-03-06 | Automation testing method and system for mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510099845.5A CN104699607A (en) | 2015-03-06 | 2015-03-06 | Automation testing method and system for mobile terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104699607A true CN104699607A (en) | 2015-06-10 |
Family
ID=53346760
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510099845.5A Pending CN104699607A (en) | 2015-03-06 | 2015-03-06 | Automation testing method and system for mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104699607A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117343A (en) * | 2015-09-18 | 2015-12-02 | 厦门美图移动科技有限公司 | Method and device for performing automatic testing based on text |
| CN108376115A (en) * | 2018-01-29 | 2018-08-07 | 数据通信科学技术研究所 | Across the Android platform automated testing method of one kind and system |
| CN108933711A (en) * | 2018-06-29 | 2018-12-04 | 华勤通讯技术有限公司 | The automated testing method and system of terminal device |
| CN112965907A (en) * | 2021-03-11 | 2021-06-15 | 南京爱奇艺智能科技有限公司 | VR APP automatic test method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110022899A1 (en) * | 2009-07-27 | 2011-01-27 | Vitali Greenberg | Producing or executing a script for an operation test of a terminal server |
| CN102841845A (en) * | 2012-07-30 | 2012-12-26 | 广东欧珀移动通信有限公司 | Automatic testing method of Android device software |
| CN103631590A (en) * | 2013-11-29 | 2014-03-12 | 广东明创软件科技有限公司 | Method for editing automated testing script |
| WO2014169565A1 (en) * | 2013-08-21 | 2014-10-23 | 中兴通讯股份有限公司 | Terminal testing method and device |
-
2015
- 2015-03-06 CN CN201510099845.5A patent/CN104699607A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110022899A1 (en) * | 2009-07-27 | 2011-01-27 | Vitali Greenberg | Producing or executing a script for an operation test of a terminal server |
| CN102841845A (en) * | 2012-07-30 | 2012-12-26 | 广东欧珀移动通信有限公司 | Automatic testing method of Android device software |
| WO2014169565A1 (en) * | 2013-08-21 | 2014-10-23 | 中兴通讯股份有限公司 | Terminal testing method and device |
| CN103631590A (en) * | 2013-11-29 | 2014-03-12 | 广东明创软件科技有限公司 | Method for editing automated testing script |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117343A (en) * | 2015-09-18 | 2015-12-02 | 厦门美图移动科技有限公司 | Method and device for performing automatic testing based on text |
| CN108376115A (en) * | 2018-01-29 | 2018-08-07 | 数据通信科学技术研究所 | Across the Android platform automated testing method of one kind and system |
| CN108933711A (en) * | 2018-06-29 | 2018-12-04 | 华勤通讯技术有限公司 | The automated testing method and system of terminal device |
| CN108933711B (en) * | 2018-06-29 | 2021-06-18 | 华勤技术股份有限公司 | Automatic testing method and system for terminal equipment |
| CN112965907A (en) * | 2021-03-11 | 2021-06-15 | 南京爱奇艺智能科技有限公司 | VR APP automatic test method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102819492B (en) | Keyword driven automatic testing frame on basis of Android | |
| US9161238B2 (en) | Mobile device monitoring and testing | |
| CN104699607A (en) | Automation testing method and system for mobile terminal | |
| CN102053911A (en) | Automated testing method and system based on Android and mobile terminal | |
| CN105824544A (en) | Method for starting application program and terminal | |
| CN105261366A (en) | Voice identification method, voice engine and terminal | |
| CN103744784A (en) | Method and system for automatically testing mobile phone applications | |
| CN102298503A (en) | Method and device for displaying contents on mobile terminal list interface | |
| CN101751329B (en) | Method and system for realizing automatic testing | |
| CN105824755A (en) | Automation test method, automation test device and mobile terminal | |
| CN111801731B (en) | Voice control method, voice control device, and computer-executable nonvolatile storage medium | |
| CN103763433A (en) | Method and system for controlling operation of terminal applications | |
| CN104980552A (en) | Method and system for realizing automatic test of Android mobile terminal | |
| CN106095248A (en) | A kind of application program based on mobile terminal is searched and is started method and system | |
| CN104021066A (en) | Mobile terminal operation information recording method, operation method and mobile terminal | |
| CN106227585A (en) | Application program starting method, device and equipment | |
| CN103870123A (en) | Information processing method and electronic equipment | |
| CN106648685A (en) | Processing method and device of intelligent terminal system and intelligent terminal | |
| CN103399814A (en) | Automated testing method and automated testing device | |
| CN106598859A (en) | Appium multi-thread implementation system and method | |
| CN106484609A (en) | Page method of testing and device | |
| CN110162730A (en) | Information processing method, device, computer equipment and storage medium | |
| CN112231206A (en) | Script editing method for application program test, computer readable storage medium and test platform | |
| CN101571922A (en) | Character recognition tool for mobile terminal automation testing and method thereof | |
| CN109344058B (en) | Automatic small program testing method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150610 |
|
| RJ01 | Rejection of invention patent application after publication |