CN103634441A - Method and device for testing mobile terminal - Google Patents
Method and device for testing mobile terminal Download PDFInfo
- Publication number
- CN103634441A CN103634441A CN201210303898.0A CN201210303898A CN103634441A CN 103634441 A CN103634441 A CN 103634441A CN 201210303898 A CN201210303898 A CN 201210303898A CN 103634441 A CN103634441 A CN 103634441A
- Authority
- CN
- China
- Prior art keywords
- mobile terminal
- tested
- daily record
- journal file
- random order
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a method and device for testing a mobile terminal and belongs to the field of a computer and communication. The method comprises the following steps: starting a mobile terminal to be tested to carry out a random event corresponding to a random command; obtaining a log generated when the mobile terminal to be tested is carrying out the random event corresponding to the random command; and analyzing whether fault occurs when the mobile terminal to be tested carries out the random event corresponding to the random command based on the obtained log. The device comprises a starting module, an obtaining module and an analyzing module. The method and device for testing the mobile terminal are capable of improving the efficiency of testing the mobile terminal.
Description
Technical field
The present invention relates to computer and the communications field, particularly a kind of method of testing mobile terminal and device.
Background technology
Along with the fast development of the communication technology, mobile phone obtains user and is widely used, and in order to protect user's interests and to make user use more easily mobile phone, mobile phone manufacturer needs mobile phone to test before mobile phone dispatches from the factory, the hidden danger that may exist to test out mobile phone.
At present, mobile phone test personnel are by PC(Personal Computer, personal computer) main frame is connected by data wire with mobile phone to be tested, open mobile phone to be tested, then on PC main frame, manually mobile phone to be tested is tested, and test out mobile phone to be tested and whether have FC(Force Close, positive closing) and ANR(Application Not Responding, application program is without response) mistake.Wherein, it should be noted that: the mobile phone that manual test is to be tested, the efficiency of test is very low.
Summary of the invention
In order to improve the efficiency of testing mobile terminal, the invention provides a kind of method and device of test terminal.Described technical scheme is as follows:
A method for testing mobile terminal, described method comprises:
Start mobile terminal to be tested and carry out chance event corresponding to random order;
Obtain the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order;
According to mobile terminal to be tested described in the described log analysis obtaining, when carrying out chance event corresponding to described random order, whether make a mistake.
Described startup mobile terminal to be tested is carried out chance event corresponding to random order, comprising:
Send and order to mobile terminal to be tested at random, make described mobile terminal to be tested produce and carry out chance event corresponding to described random order.
Describedly obtain the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order, comprising:
Send log acquisition order to described mobile terminal to be tested;
Receive the journal file that described mobile terminal to be tested sends when stopping carrying out chance event corresponding to described random order, described journal file comprises the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order.
Described in the log analysis obtaining described in described basis, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order, comprising:
Article one daily record statement comprising from described journal file starts scanning, judges in the daily record statement of described scanning whether comprise that application program is without response ANR and/or fatal abnormal Fatal Exception;
If the daily record statement of described scanning comprises keyword ANR, determine that ANR mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order;
If the daily record statement of described scanning comprises keyword Fatal Exception, determine that positive closing FC mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order.
Described in the log analysis obtaining described in described basis, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order, also comprises:
If do not comprise keyword ANR and Fatal Exception in the daily record statement of described scanning, judge in described journal file whether also have the not daily record statement of scanning, if also existed, scan next daily record statement.
The described article one daily record statement comprising from described journal file also comprises before starting scanning:
Convert described journal file to journal file that each physical line comprises a daily record statement.
Described startup mobile terminal to be tested also comprises before carrying out chance event corresponding to random order:
Remove the daily record of described mobile terminal records to be tested.
After described in the log analysis obtaining described in described basis, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order, also comprise:
If described mobile terminal to be tested makes a mistake, from described journal file, obtain and store described wrong corresponding daily record statement.
The described daily record statement that obtains and store described wrong correspondence, comprising:
Create a blank test result file;
If there is ANR mistake in described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword ANR, by described, comprise that the daily record statement of keyword ANR is stored in described test result file;
If there is FC mistake in described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword Fatal Exception, by described, comprise that the daily record statement of keyword Fatal Exception is stored in described test result file.
After described in the log analysis obtaining described in described basis, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order, also comprise:
Judge testing time corresponding to described mobile terminal to be tested, if testing time corresponding to described mobile terminal to be tested is less than preset times, increase testing time corresponding to described mobile terminal to be tested, restart described mobile terminal to be tested.
A device for testing mobile terminal, described device comprises:
Start module, for starting mobile terminal to be tested, carry out chance event corresponding to random order;
Acquisition module, the daily record producing when carrying out chance event corresponding to described random order for obtaining described mobile terminal to be tested;
Whether analysis module, make a mistake when carrying out chance event corresponding to described random order for mobile terminal to be tested described in the log analysis obtaining described in basis.
Described startup module, specifically for sending random order to mobile terminal to be tested, makes described mobile terminal to be tested produce and carry out chance event corresponding to described random order.
Described acquisition module comprises:
Transmitting element, for sending log acquisition order to described mobile terminal to be tested;
Receiving element, the journal file sending when stopping carrying out chance event corresponding to described random order for receiving described mobile terminal to be tested, described journal file comprises the daily record that described mobile terminal to be tested produces when chance event corresponding to the described random order of execution.
Described analysis module comprises:
The first scanning element, starts scanning for article one daily record statement comprising from described journal file, judges in the daily record statement of described scanning whether comprise that application program is without response ANR and/or fatal abnormal Fatal Exception;
The first determining unit, if comprise keyword ANR for the daily record statement of described scanning, determines that ANR mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order;
The second determining unit, if comprise keyword Fatal Exception for the daily record statement of described scanning, determines that positive closing FC mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order.
Described analysis module also comprises:
The second scanning element, if do not comprise keyword ANR and Fatal Exception for the daily record statement of described scanning, judges in described journal file whether also have the not daily record statement of scanning, if also existed, scans next daily record statement.
Described device also comprises:
Modular converter, for converting described journal file to journal file that each physical line comprises a daily record statement.
Described device also comprises:
Remove module, for removing the daily record of described mobile terminal records to be tested.
Described device also comprises:
Memory module if made a mistake for described mobile terminal to be tested, obtains and stores described wrong corresponding daily record statement from described journal file.
Described memory module comprises:
Creating unit, for creating a blank test result file;
The first memory cell if there is ANR mistake for described mobile terminal to be tested, reads the daily record statement that comprises keyword ANR from described journal file, by described, comprises that the daily record statement of keyword ANR is stored in described test result file;
The second memory cell, if there is FC mistake for described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword Fatal Exception, by described, comprise that the daily record statement of keyword Fatal Exception is stored in described test result file.
Described device also comprises:
Judge module, for judging testing time corresponding to described mobile terminal to be tested, if testing time corresponding to described mobile terminal to be tested is less than preset times, increase testing time corresponding to described mobile terminal to be tested, restart described mobile terminal to be tested.
In embodiments of the present invention, start mobile terminal to be tested and carry out chance event corresponding to random order, obtain the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random, whether the mobile terminal to be tested according to the log analysis obtaining makes a mistake when execution is ordered corresponding chance event at random, so realize and automatically mobile terminal being tested, improve the efficiency of testing mobile terminal.
Accompanying drawing explanation
Fig. 1 is the method flow diagram of a kind of testing mobile terminal of providing of the embodiment of the present invention 1;
Fig. 2 is the method flow diagram of a kind of testing mobile terminal of providing of the embodiment of the present invention 2;
Fig. 3 is the apparatus structure schematic diagram of a kind of testing mobile terminal of providing of the embodiment of the present invention 3.
Embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing, embodiment of the present invention is described further in detail.
Embodiment 1
As shown in Figure 1, the embodiment of the present invention provides a kind of method of testing mobile terminal, comprising:
Step 101: start mobile terminal to be tested and carry out chance event corresponding to random order;
Step 102: obtain the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random;
Step 103: whether the mobile terminal to be tested according to the log analysis obtaining makes a mistake when execution is ordered corresponding chance event at random.
Wherein, above-mentioned steps 101, can be specially:
Send and order to mobile terminal to be tested at random, make mobile terminal to be tested produce and carry out chance event corresponding to random order.
Wherein, above-mentioned steps 102, can be specially:
Send log acquisition order to mobile terminal to be tested;
Receive the journal file that mobile terminal to be tested sends when stopping carrying out chance event corresponding to random order, this journal file comprises the daily record that mobile terminal to be tested produces when carrying out chance event corresponding to random order.
Wherein, above-mentioned steps 103, can be specially:
Article one daily record statement comprising from this journal file starts scanning, whether comprises fatal abnormal of keyword ANR and/or Fatal Exception(in the daily record statement of judgement scanning);
If the daily record statement of scanning comprises keyword ANR, determine that ANR mistake occurs mobile terminal to be tested when execution is ordered corresponding chance event at random;
If the daily record statement of scanning comprises keyword Fatal Exception, determine that FC mistake occurs mobile terminal to be tested when execution is ordered corresponding chance event at random.
Further, above-mentioned steps 103, can also comprise:
If do not comprise keyword ANR and Fatal Exception in the daily record statement of scanning, judge in this journal file whether also have the not daily record statement of scanning, if also existed, scan next daily record statement.
Further, article one daily record statement comprising from this journal file also comprises before starting scanning:
Convert this journal file to journal file that each physical line comprises a daily record statement.
Further, before carrying out above-mentioned steps 101, can also comprise:
Remove the daily record of mobile terminal records to be tested.
Further, after executing above-mentioned steps 103, can also comprise:
If mobile terminal to be tested makes a mistake, from this journal file, obtain and store the daily record statement of this mistake correspondence.
Wherein, the above-mentioned daily record statement that obtains and store this mistake correspondence, comprising:
Create a blank test result file;
If there is ANR mistake in mobile terminal to be tested, from this journal file, read the daily record statement that comprises keyword ANR, the daily record statement that comprises keyword ANR is stored in test result file;
If there is FC mistake in mobile terminal to be tested, from this journal file, read the daily record statement that comprises keyword Fatal Exception, the daily record statement that comprises keyword Fatal Exception is stored in test result file.
Further, after executing above-mentioned steps 103, can also comprise:
Judge testing time corresponding to mobile terminal to be tested, if testing time corresponding to mobile terminal to be tested is less than preset times, increase the testing time that mobile terminal to be tested is corresponding, restart mobile terminal to be tested.
In embodiments of the present invention, start mobile terminal to be tested and carry out chance event corresponding to random order, obtain the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random, whether the mobile terminal to be tested according to the log analysis obtaining makes a mistake when execution is ordered corresponding chance event at random, so realize and automatically mobile terminal being tested, improve the efficiency of testing mobile terminal.
Embodiment 2
As shown in Figure 2, the embodiment of the present invention provides a kind of method of testing mobile terminal, comprising:
Step 201: remove the daily record of mobile terminal records to be tested, and start chance event corresponding to the random order of mobile terminal execution to be tested;
Particularly, PC main frame sends removes daily record order to mobile terminal to be tested, and mobile terminal to be tested receives removes daily record order, removes the daily record of self having recorded; PC main frame sends and orders to mobile terminal to be tested at random, and mobile terminal to be tested receives this and orders at random, produces and carry out chance event corresponding to this random order.
Wherein, random order can be Monkey order.Between PC main frame and mobile terminal to be tested, by data wire, be connected, when mobile terminal to be tested starts, PC main frame starts to carry out this step.
Wherein, in mobile terminal to be tested, comprise that one for the journal file of log, the form of this journal file can be txt(text document) form, after the removing daily record order that mobile terminal reception PC main frame to be tested sends, empty this journal file, to realize, remove the daily record of self having recorded.
Wherein, mobile terminal to be tested is in carrying out the process of chance event corresponding to random order, in the real-time journal file that produces daily record and the log recording of generation is comprised at self of meeting.
Wherein, if there is FC mistake in mobile terminal to be tested in the process of carrying out chance event corresponding to random order, stop carrying out chance event corresponding to random order, and daily record statement corresponding to the FC mistake of generation is recorded in the journal file self comprising, and this daily record statement comprises fatal abnormal of keyword Fatal Exception().
Wherein, if there is ANR mistake in mobile terminal to be tested in the process of carrying out chance event corresponding to random order, stop carrying out chance event corresponding to random order, and daily record statement corresponding to the ANR mistake of generation is recorded in the journal file self comprising, and this daily record statement comprises keyword ANR.
Wherein, if mobile terminal to be tested, in the process of carrying out chance event corresponding to random order, FC mistake and/or ANR mistake does not occur, when executing chance event corresponding to random order, automatically stop.
Step 202: obtain the journal file of mobile terminal to be tested, this journal file comprises the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random;
Particularly, PC main frame sends log acquisition order to mobile terminal to be tested, mobile terminal to be tested receives this log acquisition order and when stopping carrying out chance event corresponding to random order, the journal file of self record is sent to PC main frame, and PC main frame receives this journal file.
Wherein, first PC main frame sends removes daily record order to mobile terminal to be tested, send and order to mobile terminal to be tested at random again, then send log acquisition order to mobile terminal to be tested, so mobile terminal to be tested is carried out the operation of removing daily record, execute the operation of removing daily record, then carry out chance event corresponding to random order, then when stopping carrying out chance event corresponding to random order, send the journal file that self comprises to PC main frame.
Step 203: convert the journal file of mobile terminal records to be tested to journal file that each physical line comprises a daily record statement;
Particularly, PC main frame converts the journal file of mobile terminal records to be tested to journal file that each physical line comprises a daily record statement by existing daily record transfer algorithm.
Wherein, all not in lines, each daily record statement all links together the daily record statement that the journal file of mobile terminal records to be tested comprises; And in the present embodiment, convert the journal file of mobile terminal records to be tested to journal file that each physical line comprises a daily record statement, thereby distinguish every daily record statement that journal file comprises.
Step 204: whether the mobile terminal to be tested according to the log file analysis of conversion makes a mistake when execution is ordered corresponding chance event at random;
Particularly, article one daily record statement that PC main frame comprises from the journal file of changing starts scanning, in the daily record statement of judgement scanning, whether comprises keyword ANR and/or Fatal Exception; If the daily record statement of scanning comprises keyword ANR, determine that ANR mistake occurs mobile terminal to be tested when execution is ordered corresponding chance event at random; If the daily record statement of scanning comprises keyword Fatal Exception, determine that FC mistake occurs mobile terminal to be tested when execution is ordered corresponding chance event at random; If do not comprise keyword ANR and Fatal Exception in the daily record statement of scanning, in the journal file of judgement conversion, whether also there is the not daily record statement of scanning, if also existed, scan next statement.
Wherein, when scanning repeats above-mentioned analysis process after next statement, until analyze mobile terminal to be tested, make a mistake, or till while scanning the daily record statement that the journal file of complete conversion comprises.
Wherein, in the present embodiment, distinguish each daily record statement that journal file comprises, each then journal file being comprised daily record statement is lined by line scan and analyzes, and so improves and analyzes the efficiency whether mobile terminal to be tested makes a mistake.
Step 205: if mobile terminal to be tested makes a mistake, obtain and store the daily record statement of this mistake correspondence from the journal file of conversion.
Particularly, PC main frame creates a blank test result file, if there is ANR mistake in mobile terminal to be tested, from the journal file of conversion, read the daily record statement that comprises keyword ANR, read the daily record statement that current scanning comprises keyword ANR, the daily record statement that comprises keyword ANR is stored in test result file; If there is FC mistake in mobile terminal to be tested, from the journal file of conversion, read the daily record statement that comprises key point Fatal Exception, read the daily record statement that current scanning comprises keyword Fatal Exception, the daily record statement that comprises key point Fatal Exception is stored in test result file.
Further, after the daily record statement of the mistake correspondence that mobile terminal to be tested is occurred is stored in test result file, can printing test destination file.
Further, judge testing time corresponding to mobile terminal to be tested, if the testing time that mobile terminal to be tested is corresponding is less than preset times, increase the testing time that mobile terminal to be tested is corresponding, restart mobile terminal to be tested, then return to step 201 and restart to carry out.
Wherein, if testing time corresponding to mobile terminal to be tested is more than or equal to preset times, stop mobile terminal to be tested to test.The initial value of the number of times of the test that mobile terminal to be tested is corresponding can be 1 etc.
Wherein, increase the operation of the testing time that mobile terminal to be tested is corresponding, can be specially:
Testing time corresponding to mobile terminal to be tested increased to 1 etc.
Wherein, it should be noted that: the tester of mobile terminal can judge which module that mobile terminal to be tested comprises according to the daily record statement of the mistake correspondence of storing in test result file has occurred problem.
In embodiments of the present invention, start mobile terminal to be tested and carry out chance event corresponding to random order, obtain the journal file of mobile terminal to be tested, this journal file comprises the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random, convert this journal file to journal file that each physical line comprises a daily record statement, according to the journal file of conversion, determine whether mobile terminal to be tested makes a mistake when execution is ordered corresponding chance event at random, so realize and automatically mobile terminal being tested, improve the efficiency of testing mobile terminal, wherein, convert the journal file of mobile terminal to be tested to journal file that each physical line only includes a daily record statement, thereby distinguish every daily record statement that journal file comprises, each that journal file is comprised daily record statement is lined by line scan and analyzes, and so improves and analyzes the efficiency whether mobile terminal to be tested makes a mistake.
Embodiment 3
As shown in Figure 3, the embodiment of the present invention provides a kind of device of testing mobile terminal, comprising:
Whether analysis module 303, for making a mistake when in execution, this orders corresponding chance event at random according to the log analysis obtaining mobile terminal to be tested.
Wherein, start module 301, specifically for sending random order to mobile terminal to be tested, make mobile terminal to be tested produce and carry out chance event corresponding to this random order.
Wherein, acquisition module 302 comprises:
Transmitting element, for sending log acquisition order to mobile terminal to be tested;
Receiving element, for receiving mobile terminal to be tested when stopping carrying out the journal file sending when this orders corresponding chance event at random, this journal file comprises the daily record that mobile terminal to be tested produces when this orders corresponding chance event at random in execution.
Wherein, analysis module 303 comprises:
The first scanning element, starts scanning for article one daily record statement comprising from this journal file, in the daily record statement of judgement scanning, whether comprises keyword ANR and/or Fatal Exception;
The first determining unit, if comprise keyword ANR for the daily record statement of scanning, determines that ANR mistake occurs when this orders corresponding chance event at random in execution mobile terminal to be tested;
The second determining unit, if comprise keyword Fatal Exception for the daily record statement of scanning, determines that positive closing FC mistake occurs when this orders corresponding chance event at random in execution mobile terminal to be tested.
Further, analysis module 303 also comprises:
The second scanning element, if do not comprise keyword ANR and Fatal Exception for the daily record statement of scanning, judges in this journal file whether also have the not daily record statement of scanning, if also existed, scans next daily record statement.
Further, this device also comprises:
Modular converter, for converting this journal file to journal file that each physical line comprises a daily record statement.
Further, this device also comprises:
Remove module, for removing the daily record of mobile terminal records to be tested.
Further, this device also comprises:
Memory module if made a mistake for mobile terminal to be tested, obtains and stores the daily record statement of this mistake correspondence from this journal file.
Wherein, memory module comprises:
Creating unit, for creating a blank test result file;
The first memory cell if there is ANR mistake for mobile terminal to be tested, reads the daily record statement that comprises keyword ANR from this journal file, and the daily record statement that comprises keyword ANR is stored in test result file;
The second memory cell, if there is FC mistake for mobile terminal to be tested, from this journal file, read the daily record statement that comprises keyword Fatal Exception, the daily record statement that comprises keyword Fatal Exception is stored in test result file.
Wherein, this device also comprises:
Judge module, for the testing time that judges that mobile terminal to be tested is corresponding, if testing time corresponding to mobile terminal to be tested is less than preset times, increases the testing time that mobile terminal to be tested is corresponding, restarts mobile terminal to be tested.
In embodiments of the present invention, start mobile terminal to be tested and carry out chance event corresponding to random order, obtain the journal file of mobile terminal to be tested, this journal file comprises the daily record that mobile terminal to be tested produces when execution is ordered corresponding chance event at random, convert this journal file to journal file that each physical line comprises a daily record statement, according to the journal file of conversion, determine whether mobile terminal to be tested makes a mistake when execution is ordered corresponding chance event at random, so realize and automatically mobile terminal being tested, improve the efficiency of testing mobile terminal, wherein, convert the journal file of mobile terminal to be tested to journal file that each physical line only includes a daily record statement, thereby distinguish every daily record statement that journal file comprises, each that journal file is comprised daily record statement is lined by line scan and analyzes, and so improves and analyzes the efficiency whether mobile terminal to be tested makes a mistake.
It should be noted that: the device of a kind of testing mobile terminal that above-described embodiment provides is when testing mobile terminal, only the division with above-mentioned each functional module is illustrated, in practical application, can above-mentioned functions be distributed and by different functional modules, completed as required, the internal structure that is about to device is divided into different functional modules, to complete all or part of function described above.In addition, above-described embodiment provides the device of testing mobile terminal and the embodiment of the method for testing mobile terminal to belong to same design, and its specific implementation process refers to embodiment of the method, repeats no more here.
One of ordinary skill in the art will appreciate that all or part of step that realizes above-described embodiment can complete by hardware, also can come the hardware that instruction is relevant to complete by program, described program can be stored in a kind of computer-readable recording medium, the above-mentioned storage medium of mentioning can be read-only memory, disk or CD etc.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (20)
1. a method for testing mobile terminal, is characterized in that, described method comprises:
Start mobile terminal to be tested and carry out chance event corresponding to random order;
Obtain the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order;
According to mobile terminal to be tested described in the described log analysis obtaining, when carrying out chance event corresponding to described random order, whether make a mistake.
2. the method for claim 1, is characterized in that, described startup mobile terminal to be tested is carried out chance event corresponding to random order, comprising:
Send and order to mobile terminal to be tested at random, make described mobile terminal to be tested produce and carry out chance event corresponding to described random order.
3. the method for claim 1, is characterized in that, described in obtain the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order, comprising:
Send log acquisition order to described mobile terminal to be tested;
Receive the journal file that described mobile terminal to be tested sends when stopping carrying out chance event corresponding to described random order, described journal file comprises the daily record that described mobile terminal to be tested produces when carrying out chance event corresponding to described random order.
4. method as claimed in claim 3, is characterized in that, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order described in the log analysis obtaining described in described basis, comprising:
Article one daily record statement comprising from described journal file starts scanning, judges in the daily record statement of described scanning whether comprise that application program is without response ANR and/or fatal abnormal Fatal Exception;
If the daily record statement of described scanning comprises keyword ANR, determine that ANR mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order;
If the daily record statement of described scanning comprises keyword Fatal Exception, determine that positive closing FC mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order.
5. method as claimed in claim 4, is characterized in that, whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order described in the log analysis obtaining described in described basis, also comprises:
If do not comprise keyword ANR and Fatal Exception in the daily record statement of described scanning, judge in described journal file whether also have the not daily record statement of scanning, if also existed, scan next daily record statement.
6. method as claimed in claim 4, is characterized in that, the described article one daily record statement comprising from described journal file also comprises before starting scanning:
Convert described journal file to journal file that each physical line comprises a daily record statement.
7. the method as described in claim 1 to 6 any one claim, is characterized in that, described startup mobile terminal to be tested also comprises before carrying out chance event corresponding to random order:
Remove the daily record of described mobile terminal records to be tested.
8. the method as described in claim 3 to 6 any one claim, is characterized in that, after whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order described in the log analysis obtaining described in described basis, also comprises:
If described mobile terminal to be tested makes a mistake, from described journal file, obtain and store described wrong corresponding daily record statement.
9. method as claimed in claim 8, is characterized in that, described in obtain and store described wrong corresponding daily record statement, comprising:
Create a blank test result file;
If there is ANR mistake in described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword ANR, by described, comprise that the daily record statement of keyword ANR is stored in described test result file;
If there is FC mistake in described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword Fatal Exception, by described, comprise that the daily record statement of keyword Fatal Exception is stored in described test result file.
10. the method as described in claim 1 to 6 any one claim, is characterized in that, after whether mobile terminal to be tested makes a mistake when carrying out chance event corresponding to described random order described in the log analysis obtaining described in described basis, also comprises:
Judge testing time corresponding to described mobile terminal to be tested, if testing time corresponding to described mobile terminal to be tested is less than preset times, increase testing time corresponding to described mobile terminal to be tested, restart described mobile terminal to be tested.
The device of 11. 1 kinds of testing mobile terminals, is characterized in that, described device comprises:
Start module, for starting mobile terminal to be tested, carry out chance event corresponding to random order;
Acquisition module, the daily record producing when carrying out chance event corresponding to described random order for obtaining described mobile terminal to be tested;
Whether analysis module, make a mistake when carrying out chance event corresponding to described random order for mobile terminal to be tested described in the log analysis obtaining described in basis.
12. devices as claimed in claim 11, is characterized in that,
Described startup module, specifically for sending random order to mobile terminal to be tested, makes described mobile terminal to be tested produce and carry out chance event corresponding to described random order.
13. devices as claimed in claim 11, is characterized in that, described acquisition module comprises:
Transmitting element, for sending log acquisition order to described mobile terminal to be tested;
Receiving element, the journal file sending when stopping carrying out chance event corresponding to described random order for receiving described mobile terminal to be tested, described journal file comprises the daily record that described mobile terminal to be tested produces when chance event corresponding to the described random order of execution.
14. devices as claimed in claim 13, is characterized in that, described analysis module comprises:
The first scanning element, starts scanning for article one daily record statement comprising from described journal file, judges in the daily record statement of described scanning whether comprise that application program is without response ANR and/or fatal abnormal Fatal Exception;
The first determining unit, if comprise keyword ANR for the daily record statement of described scanning, determines that ANR mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order;
The second determining unit, if comprise keyword FatalException for the daily record statement of described scanning, determines that positive closing FC mistake occurs described mobile terminal to be tested when carrying out chance event corresponding to described random order.
15. devices as claimed in claim 14, is characterized in that, described analysis module also comprises:
The second scanning element, if do not comprise keyword ANR and FatalException for the daily record statement of described scanning, judges in described journal file whether also have the not daily record statement of scanning, if also existed, scans next daily record statement.
16. devices as claimed in claim 14, is characterized in that, described device also comprises:
Modular converter, for converting described journal file to journal file that each physical line comprises a daily record statement.
17. devices as described in claim 11 to 16 any one claim, is characterized in that, described device also comprises:
Remove module, for removing the daily record of described mobile terminal records to be tested.
18. devices as described in claim 13 to 16 any one claim, is characterized in that, described device also comprises:
Memory module if made a mistake for described mobile terminal to be tested, obtains and stores described wrong corresponding daily record statement from described journal file.
19. devices as claimed in claim 18, is characterized in that, described memory module comprises:
Creating unit, for creating a blank test result file;
The first memory cell if there is ANR mistake for described mobile terminal to be tested, reads the daily record statement that comprises keyword ANR from described journal file, by described, comprises that the daily record statement of keyword ANR is stored in described test result file;
The second memory cell, if there is FC mistake for described mobile terminal to be tested, from described journal file, read the daily record statement that comprises keyword Fatal Exception, by described, comprise that the daily record statement of keyword Fatal Exception is stored in described test result file.
20. devices as described in claim 11 to 16 any one claim, is characterized in that, described device also comprises:
Judge module, for judging testing time corresponding to described mobile terminal to be tested, if testing time corresponding to described mobile terminal to be tested is less than preset times, increase testing time corresponding to described mobile terminal to be tested, restart described mobile terminal to be tested.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210303898.0A CN103634441B (en) | 2012-08-24 | 2012-08-24 | A kind of method and device for testing mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210303898.0A CN103634441B (en) | 2012-08-24 | 2012-08-24 | A kind of method and device for testing mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103634441A true CN103634441A (en) | 2014-03-12 |
| CN103634441B CN103634441B (en) | 2018-04-27 |
Family
ID=50215053
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210303898.0A Active CN103634441B (en) | 2012-08-24 | 2012-08-24 | A kind of method and device for testing mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103634441B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301136A (en) * | 2014-09-11 | 2015-01-21 | 青岛海信电器股份有限公司 | Method and equipment for reporting and processing fault information |
| CN104768218A (en) * | 2015-04-23 | 2015-07-08 | 上海斐讯数据通信技术有限公司 | Mobile phone registration debugging method and system |
| CN105005526A (en) * | 2015-05-26 | 2015-10-28 | 广东欧珀移动通信有限公司 | Information reminding method and mobile terminal |
| CN105068930A (en) * | 2015-08-07 | 2015-11-18 | 天津市康凯特软件科技有限公司 | Intelligent analysis method and device for test generation data of mobile terminal |
| CN105988818A (en) * | 2015-03-06 | 2016-10-05 | 展讯通信(天津)有限公司 | Bug automatic debugging system and method |
| CN106155884A (en) * | 2015-03-31 | 2016-11-23 | 展讯通信（上海）有限公司 | A kind of log analysis method and system |
| CN106155885A (en) * | 2015-03-31 | 2016-11-23 | 展讯通信（上海）有限公司 | A kind of full-automatic test system and method for testing |
| CN106598804A (en) * | 2016-11-29 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | Abnormality processing method and apparatus |
| CN108052452A (en) * | 2017-12-29 | 2018-05-18 | 北京酷我科技有限公司 | The visual optimization method that a kind of daily record is checked and accepted |
| CN108062257A (en) * | 2017-12-28 | 2018-05-22 | 北京奇虎科技有限公司 | A kind of method and system for handling stack information |
| CN115563910A (en) * | 2022-11-24 | 2023-01-03 | 英诺达(成都)电子科技有限公司 | UPF command execution method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6622298B1 (en) * | 2000-02-03 | 2003-09-16 | Xilinx, Inc. | Method and apparatus for testing software having a user interface |
| CN101945155A (en) * | 2010-09-03 | 2011-01-12 | 展讯通信（上海）有限公司 | Method and terminal device for capturing terminal debugging information in real-time manner |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic test method and device |
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
-
2012
- 2012-08-24 CN CN201210303898.0A patent/CN103634441B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6622298B1 (en) * | 2000-02-03 | 2003-09-16 | Xilinx, Inc. | Method and apparatus for testing software having a user interface |
| CN101945155A (en) * | 2010-09-03 | 2011-01-12 | 展讯通信（上海）有限公司 | Method and terminal device for capturing terminal debugging information in real-time manner |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic test method and device |
| CN103577313A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Mobile terminal application program testing method and device |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301136B (en) * | 2014-09-11 | 2018-06-19 | 青岛海信电器股份有限公司 | Fault information reporting and the method and apparatus of processing |
| CN104301136A (en) * | 2014-09-11 | 2015-01-21 | 青岛海信电器股份有限公司 | Method and equipment for reporting and processing fault information |
| CN105988818A (en) * | 2015-03-06 | 2016-10-05 | 展讯通信(天津)有限公司 | Bug automatic debugging system and method |
| CN106155884A (en) * | 2015-03-31 | 2016-11-23 | 展讯通信（上海）有限公司 | A kind of log analysis method and system |
| CN106155885A (en) * | 2015-03-31 | 2016-11-23 | 展讯通信（上海）有限公司 | A kind of full-automatic test system and method for testing |
| CN104768218A (en) * | 2015-04-23 | 2015-07-08 | 上海斐讯数据通信技术有限公司 | Mobile phone registration debugging method and system |
| CN104768218B (en) * | 2015-04-23 | 2019-11-12 | 上海斐讯数据通信技术有限公司 | A kind of mobile telephone registration adjustment method and system |
| CN105005526A (en) * | 2015-05-26 | 2015-10-28 | 广东欧珀移动通信有限公司 | Information reminding method and mobile terminal |
| CN105068930A (en) * | 2015-08-07 | 2015-11-18 | 天津市康凯特软件科技有限公司 | Intelligent analysis method and device for test generation data of mobile terminal |
| CN106598804A (en) * | 2016-11-29 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | Abnormality processing method and apparatus |
| CN108062257A (en) * | 2017-12-28 | 2018-05-22 | 北京奇虎科技有限公司 | A kind of method and system for handling stack information |
| CN108052452A (en) * | 2017-12-29 | 2018-05-18 | 北京酷我科技有限公司 | The visual optimization method that a kind of daily record is checked and accepted |
| CN115563910A (en) * | 2022-11-24 | 2023-01-03 | 英诺达(成都)电子科技有限公司 | UPF command execution method, device, equipment and storage medium |
| CN115563910B (en) * | 2022-11-24 | 2023-02-03 | 英诺达(成都)电子科技有限公司 | UPF command execution method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103634441B (en) | 2018-04-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103634441A (en) | Method and device for testing mobile terminal | |
| CN105611330B (en) | Smart television maintenance method and system, server and mobile terminal | |
| CN107273280A (en) | A kind of log processing method, device, electronic equipment and storage medium | |
| CN101930400B (en) | SDK (Software Development Kit) automatic test system and method | |
| CN104699598A (en) | Automatic testing method, device, equipment and system | |
| CN102479084A (en) | Method and device for acquiring log by Android terminal | |
| CN112744115B (en) | Information processing method, device and system of electric automobile and processor | |
| CN104572422A (en) | Memory monitoring achievement method based on startup and shutdown of Linux system | |
| CN106537351B (en) | Method for the power failure in diagnostic wireless communication equipment | |
| CN105929697A (en) | Maintenance method of smart home, device and terminal | |
| CN103441861A (en) | Method and device for generating data records | |
| CN104113440A (en) | Method and system for intelligently monitoring operation state of home gateway | |
| CN109254922A (en) | A kind of automated testing method and device of server B MC Redfish function | |
| CN105022694A (en) | Test case generation method and system for mobile terminal test | |
| CN108738059B (en) | WIFI module testing method and device | |
| CN104346410A (en) | Method and equipment for monitoring terminal equipment | |
| CN100403838C (en) | Fault information collection system and method | |
| CN101672879B (en) | Automatic diagnostic device and method of electronic products | |
| CN202713533U (en) | TV diagnosis and maintenance system and TV | |
| CN107153539A (en) | A kind of file interface system | |
| CN108763097A (en) | Automated testing method, device, electronic equipment, storage medium | |
| CN104424098B (en) | A kind of application testing method and device | |
| CN105840433B (en) | Wind turbine generator system point inspection information management system and wind turbine generator system point inspection management system | |
| CN111045934A (en) | Page analysis method, device, client, storage medium and electronic equipment | |
| CN101533369A (en) | Method for checking start-up procedure and device thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |