CN107229554A - Mobile terminal stability test method and device - Google Patents
Mobile terminal stability test method and device Download PDFInfo
- Publication number
- CN107229554A CN107229554A CN201610175981.2A CN201610175981A CN107229554A CN 107229554 A CN107229554 A CN 107229554A CN 201610175981 A CN201610175981 A CN 201610175981A CN 107229554 A CN107229554 A CN 107229554A
- Authority
- CN
- China
- Prior art keywords
- testing time
- exception
- file
- exception record
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Probability & Statistics with Applications (AREA)
- Evolutionary Biology (AREA)
- Bioinformatics & Computational Biology (AREA)
- Life Sciences & Earth Sciences (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present invention provides a kind of mobile terminal stability test method and device, and methods described includes：The exception record file of mobile terminal described in timing receipt；Data in the exception record file are stored in database by rule；Data generation anomaly trend figure in the database, and real-time exhibition.The present invention can realize automatic record, without additional manual operation, be capable of the precise time of recording exceptional generation in real time, and being capable of real-time exhibition anomaly trend figure.
Description
Technical field
The present invention relates to system testing technical field, more particularly to a kind of mobile terminal stability test method and device.
Background technology
With the development of mobile communication technology, mobile terminal product increasingly enriches, and function becomes increasingly complex, and the frequency of release is more and more faster, causes the R＆D cycle to shorten., it is necessary to by ensureing the quality and performance of product to the test of mobile terminal, while the testing efficiency of mobile terminal, control testing cost must be improved again, need constantly to accumulate measuring technology for this, improve testing level in R＆D process.
The probability that serious problems occur in unit interval is the topmost stability indicator of mobile terminal project, and this requires the exception that record occurs in real time, and the information of record is standardized, and finally all data are put together and do statistics and analysis.It is the exception occurred by manual record mobile terminal in existing technology and does statistical analysis, the time occurred extremely by manual record in test process and species, and data are periodically collected, classify by professional and summarized, issue changing trend diagram.
During the present invention is realized, inventor has found at least there is following technical problem in the prior art：
In actual mobile terminal project testing, tester needs to record these exceptions in real time, because progress parallel with operational trials is, it is necessary to expend substantial amounts of manpower and time.Simultaneously as each team's target service is different with demand, and the usable samples limited amount being collected into, and it is not statistical uncertainty really for the abnormal correct time occurred.
The content of the invention
A kind of method and device for mobile terminal stability test that the present invention is provided, can realize automatic record, without additional manual operation；All can be counted in survey mobile phone；It is capable of the precise time of recording exceptional generation in real time, and being capable of real-time exhibition anomaly trend figure.
In a first aspect, the present invention provides a kind of mobile terminal stability test method, including：
The exception record file of mobile terminal described in timing receipt；
Data in the exception record file are stored in database by rule；
Data generation anomaly trend figure in the database, and real-time exhibition.
Alternatively, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception, and the data by the exception record file are stored in database by rule to be included：Data in the exception record file are stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
Alternatively, the database includes project table, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
Alternatively, the data by the exception record file are stored in database by rule includes：When database is that exception record file is stored in database by space-time first, exception record file is stored in database again when database non-NULL, wherein exception record file is stored in into database again includes：The exception record file of identical version information is stored in database again, and the exception record file of different editions information is stored in database again.
Alternatively, it is described to be stored in exception record file in database first, and that the exception record file of different editions information is stored in into operating procedure in database again is identical, including：
The version information and filename of the exception record file are inserted into the project table of database；
The test time started of each testing time node in the exception record file and test end time and corresponding item record ID are inserted into testing time table；
The abnormal information and testing time node ID of each testing time node of each exception record file are inserted into exception table.
Alternatively, it is described the exception record file of identical version information is stored in database again to include：
Search the last old exception record file preserved；
The new abnormal log file of contrast and old exception record file, judge whether two exception record files have inclusion relation；
If two exception record files do not have inclusion relation, then preserve new abnormal log file, the last upload file name for updating the data the item record of storehouse project table uploads file name to be new, and all testing time nodes in new file and the corresponding abnormal information of the testing time node are inserted respectively into the corresponding testing time table of database and exception table；
If two exception record files have inclusion relation, new abnormal log file is preserved, old exception record file is deleted, updated the data the last upload file name of the item record in the project table of storehouse and upload file name to be new；
The position of the corresponding testing time node in new abnormal log file is found according to the position of old last testing time node of exception record file, it is newly test end time of the abnormal log file in the testing time node of the position to update the data the test end time of the testing time node in the testing time table in storehouse；
Additional abnormal information in testing time node described in new abnormal log file is inserted into exception table；
The testing time node that will be increased newly in new abnormal log file, and abnormal information in these testing time nodes insert corresponding testing time table and exception table respectively.
Alternatively, it is described to judge whether two exception record files include with inclusion relation：
When only one of which testing time node in old exception record file, it is equal to the test time started of first testing time node of old exception record file when the test time started of first testing time node in new abnormal log file, when the test end time of first testing time node of new exception log file is more than or equal to the test end time of old first testing time node of exception record file, two exception record files have inclusion relation, otherwise without inclusion relation；
When the testing time node number in old exception record file is more than 1, it is respectively equal to the test time started and test end time of first testing time node of old exception record file when the test time started and test end time of first testing time node in new abnormal log file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, during the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position, two exception record files have inclusion relation, otherwise do not have inclusion relation.
Alternatively, the data generation anomaly trend figure in the database includes：
Abnormal number sum occurs for all mobile terminals of the same version information of data acquisition in the database, i.e., total abnormal number；
The testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；
The abscissa of the tendency chart is beta version number, and ordinate is average exceptional value,
Average exceptional value=total abnormal number/total testing time.
Alternatively, the tendency chart screening conditions include total sample size, total testing time and Exception Type.
Second aspect, the present invention provides a kind of mobile terminal stability test device, including：
Receiving unit, the exception record file for mobile terminal described in timing receipt；
Storage unit, for the data in the exception record file to be stored in database by rule；
Generation unit, anomaly trend figure, and real-time exhibition are generated for the data in the database.
Alternatively, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception, the storage unit, for the data in the exception record file to be stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
Alternatively, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception, the storage unit, for the data in the exception record file to be stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
Alternatively, the database includes project table, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
Alternatively, the storage unit is used to, when database is that exception record file is stored in database by space-time first, be stored in exception record file in database again when database non-NULL.
Alternatively, the storage unit includes：First insertion module, the project table for the version information and filename of the exception record file to be inserted into database；
Second insertion module, for the test time started of each testing time node in the exception record file and test end time and corresponding item record ID to be inserted into testing time table；
3rd insertion module, for the abnormal information and testing time node ID of each testing time node of each exception record file to be inserted into exception table.
Alternatively, the storage unit includes：
Searching modul, the old exception record file for searching last preservation；
Judge module, for contrasting new abnormal log file and old exception record file, judges whether two exception record files have inclusion relation；
First preserving module, for when two exception record files do not have inclusion relation, then preserve new abnormal log file, the last upload file name for updating the data the item record of storehouse project table uploads file name to be new, and all testing time nodes in new file and the corresponding abnormal information of the testing time node are inserted respectively into the corresponding testing time table of database and exception table；
Second preserving module, for when two exception record files have inclusion relation, preserving new abnormal log file, deletes old exception record file, updates the data the last upload file name of the item record in the project table of storehouse and uploads file name to be new；The position of the corresponding testing time node in new abnormal log file is found according to the position of old last testing time node of exception record file, it is newly test end time of the abnormal log file in the testing time node of the position to update the data the test end time of the testing time node in the testing time table in storehouse；Additional abnormal information in testing time node described in new abnormal log file is inserted into exception table；The testing time node that will be increased newly in new abnormal log file, and abnormal information in these testing time nodes insert corresponding testing time table and exception table respectively.
Alternatively, the judging unit is used for,
When only one of which testing time node in old exception record file, it is equal to the test time started of first testing time node of old exception record file when the test time started of first testing time node in new abnormal log file, when the test end time of first testing time node of new exception log file is more than or equal to the test end time of old first testing time node of exception record file, judge that two exception record files have inclusion relation, otherwise without inclusion relation；
When the testing time node number in old exception record file is more than 1, it is respectively equal to the test time started and test end time of first testing time node of old exception record file when the test time started and test end time of first testing time node in new abnormal log file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, during the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position, judge that two exception record files have inclusion relation, otherwise do not have inclusion relation.
Alternatively, the generation unit includes：
First acquisition module, the abnormal number sum that all mobile terminals for the same version information of data acquisition in the database occur, i.e., total abnormal number；
Second acquisition module, for the testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；
Tendency chart drafting module, for being abscissa with beta version number, average exceptional value is that ordinate draws tendency chart, wherein averagely exceptional value=total abnormal number/total testing time.
Alternatively, the tendency chart screening conditions include total sample size, total testing time and Exception Type.
A kind of mobile terminal stability test method and device provided in an embodiment of the present invention, can realize automatic record, without additional manual operation；All can be counted in survey mobile phone；It is capable of the precise time of recording exceptional generation in real time, and being capable of real-time exhibition anomaly trend figure.
Brief description of the drawings
Fig. 1 is the flow chart of one embodiment of the invention mobile terminal stability test method；
Fig. 2 is the flow chart of another embodiment of the present invention mobile terminal stability test method；
Fig. 3 is the structural representation of one embodiment of the invention mobile terminal stability test device.
Embodiment
To make the purpose, technical scheme and advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only a part of embodiment of the invention, rather than whole embodiments.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art are obtained under the premise of creative work is not made belongs to the scope of protection of the invention.
The present invention provides a kind of mobile terminal stability test method, as shown in figure 1, methods described includes：
The exception record file of mobile terminal described in S11, timing receipt；
S12, the data in the exception record file are stored in database by rule；
S13, the data generation anomaly trend figure in the database, and real-time exhibition.
A kind of mobile terminal stability test method provided in an embodiment of the present invention, can realize automatic record, without additional manual operation；All can be counted in survey mobile phone；It is capable of the precise time of recording exceptional generation in real time, and being capable of real-time exhibition anomaly trend figure.
The specific workflow of the present invention is as shown in Fig. 2 mainly include：
Step S21：Abnormality monitoring, abnormal backstage is installed in mobile terminal and monitors instrument, for carrying out abnormal information collection, in test process, all kinds of exceptions such as monitoring of software, hardware, wherein the exception includes in the handset starting stage：Kernel is abnormal（Kernel fault）, framework it is abnormal（Application error）, app it is abnormal（Software anomaly）And modem is abnormal（Modem is abnormal）.
Step S22：By in the exception record file of the mobile terminal exception record listened to mobile terminal, wherein the exception record file is made up of a series of test node, a new test node can be generated when mobile terminal is restarted under normal circumstances.Each test node includes three parts：Version information, testing time node and abnormal information, wherein version information include：Hardware version, mobile terminal sequence number, the version information of buildNumber mobile phones（Mainly there are engineering name, android version numbers, compiled version number, CPVersion CP version number）, extraInfo branch informations and gms information.Testing time node includes test time started and test end time, and start can generate first test node to mobile terminal for the first time, restart once or deletion record file can also regenerate a new test node.Abnormal information includes a series of abnormal nodes, and each abnormal nodes include the abnormal time occurred, the type of exception, abnormal description information, wherein when the abnormal time occurred refers to abnormal generation, the time is recorded on mobile terminal.The version information of each test node of same exception record file is consistent.
Step S23：Judge whether the uplink time of arrival exception record file, the uplink time of exception record file is set, when the time reaching the uplink time of exception record file, then perform step S24：Exception record file is uploaded onto the server, step S21 is otherwise jumped to and proceeds abnormality monitoring.
Step S24：Exception record file is uploaded onto the server in the time timing that exception record file according to setting is uploaded.
Step S25：After server receives exception record file, the data in exception record file are saved in database by rule.Data in the exception record file are stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
The form that database preserves the data in exception record file mainly includes project table（Comprising version information, hardware information, engineering information, handset serial etc.）, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
Server is received after data, and the data in exception record file are stored in database by rule, and for the efficient and real-time of page presentation, the mode of server saves data is：File combination database.The data in exception record file are stored in into database by rule includes：When database is that exception record file is stored in database by space-time first, exception record file is stored in database again when database non-NULL, wherein exception record file is stored in into database again includes：The exception record file of identical version information is stored in database again, and the exception record file of different editions information is stored in database again.
When database is space-time, for the processing of the first time preservation of exception record file：
1）After exception record file is uploaded onto the server, whole exception record file is parsed, the version information of exception record file is obtained, testing time node listing, the corresponding exception list of each testing time node.
2）The version information of the exception record file is inquired about to the project table of database as querying condition.Now database is seen for sky, thus project table for sky, and it is sky to return to item record.
3）By project information（The version information of exception record file）And the file name of the exception record file is inserted into project table, the path of the exception record file can be obtained according to the filename of the project information and the exception record file, the exception record file can be found by the path.
4）By the test time started of all testing time nodes of each test node of exception record file and test end time and the 3rd）Item record ID in step is inserted into testing time table, and the last test timing node ID of renewal item table is the testing time node ID being currently inserted into.
5）If currently the corresponding exception list of testing time node is sky, the 4th is jumped to）The next testing time node of step processing.Otherwise the 6th is jumped to）Step, the exception list that the abnormal information of current testing time node is inserted.
6）The information of each abnormal nodes of the abnormal information and current testing time node ID are inserted into exception table.
Second for exception record file and follow-up preservation processing：
1）After exception record file is uploaded onto the server, whole exception record file is parsed, the version information of exception record file is obtained, testing time node listing, the corresponding abnormal information of each testing time node.
2）The version information of the exception record file is inquired about to the project table of database as querying condition.HardwareVersion+ SN+ buildNumber+ extraInfo are inquired about to the project table of database as the querying condition of combination.If the exception record file of new a version and mobile phone, i.e., the corresponding item record not with the querying condition of the combination, then handled according to the preserving type of the first time of exception record file in database.If the exception record file of same version and mobile phone, i.e., the item record in unique one project table corresponding with the querying condition of the combination is found in database, then into the 3rd）Step.
3）According to the 2nd）The filename of project information and exception record file in the item record found in step, the path for the exception record file once uploaded onto the server on server end is found, find the exception record file of last time, and the version information of a upper exception record file is obtained according to same analysis mode, testing time node listing, the corresponding abnormal information of each testing time node.
4）The content of the new abnormal log file this time to be preserved and the last old exception record file preserved is contrasted, judges whether two exception record files have inclusion relation.When new abnormal log file and old exception record file meet following condition, two exception record files have inclusion relation, otherwise without inclusion relation.
Condition（1）The testing time number of nodes of new exception log file is more than or equal to the testing time number of nodes of old exception record file.
Condition（2）When the testing time node number of old exception record file is 1, first testing time node of new abnormal log file and old exception record file is compared, the test time started of first testing time node of new exception log file is equal to the test time started of first testing time node of old exception record file, and the test end time of first testing time node of new exception log file is more than or equal to the test end time of first testing time node of old exception record file.
When the testing time node number of old exception record file is more than 1, the test time started and test end time of first testing time node in new exception log file are respectively equal to the test time started and test end time of first testing time node of old exception record file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position.
5）When new abnormal log file and old exception record file do not have inclusion relation, then new abnormal log file is preserved in server end, update the data file name of the last upload file name of item record corresponding in the project table of storehouse for new abnormal log file.All testing time nodes and the abnormal information corresponding with the testing time node in new abnormal log file are inserted respectively into corresponding testing time table and exception table.
6）When new abnormal log file and old exception record file have inclusion relation, then new abnormal log file is preserved in server end, and old exception record file is deleted, update the data file name of the last upload file name of item record corresponding in the project table of storehouse for new abnormal log file.Last test timing node ID in database project table finds the record of database testing time table, the position of the corresponding testing time node in new abnormal log file is found according to the position of last testing time node of old exception record file, the test end time of this record in database testing time table is updated to test end time of the new abnormal log file in the testing time node of the position.Old exception record file last corresponding exception table of testing time node is searched, additional abnormal information in new abnormal log file correspondence testing time node is inserted into the exception table.For the newly-increased testing time node of new abnormal log file, and the abnormal information in these newly-increased testing time nodes, corresponding testing time table and exception table are inserted respectively.
Step S26：Page real-time exhibition, web page provides intuitively tendency chart and shown, the abnormal number sum of all mobile terminals generation of the same version information of data acquisition in database, i.e., total abnormal number；The testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；The abscissa of the tendency chart is beta version number, and ordinate is average exceptional value, average exceptional value=total abnormal number/total testing time.The page real-time exhibition of the tendency chart only takes out data from database and makes the tendency chart, so can just accomplish in real time when handling the testing time node and the exception record file of millions of of several ten million bars.The tendency chart can check from product, two dimensions of hardware, and there is provided the filter condition such as engineering, sample size and testing time threshold value, species.Wherein, the filter condition of total sample size, the test data of Individual mobile terminal can be filtered to be set to a rational value；The filter condition of total testing time, by setting rational value to filter the test data of short time.For the filter condition of Exception Type, the abnormal problem that different team may pay close attention to is different, and the abnormal tendency chart of different type can be drawn by carrying out statistics for different types of abnormal data, to meet the demand of different team.The average exceptional value upper limit that initialization system each stage should reach, can be with the average anomalous variation situation of observing system by tendency chart, and whether reaches the requirement of the average exceptional value in corresponding stage, with the stability state of attention location system.
Step S27：When date of arrival time reporting the transmission time, collected data are collected, and are sending mail daily, different addressees are set, receive the anomaly trend figure of the test event of configuration.
Step S28：When the time, which reaches weekly, sends the time, collected data are collected, and are sending mail weekly, different addressees are set, receive the anomaly trend figure of the test event of configuration.
The embodiment of the present invention also provides a kind of mobile terminal stability test device, and as shown in Figure 3, described device includes：
Receiving unit 31, the exception record file for mobile terminal described in timing receipt；
Storage unit 32, for the data in the exception record file to be stored in database by rule；
Generation unit 33, anomaly trend figure, and real-time exhibition are generated for the data in the database.
A kind of mobile terminal stability test device provided in an embodiment of the present invention, can realize automatic record, without additional manual operation；All can be counted in survey mobile phone；It is capable of the precise time of recording exceptional generation in real time, and being capable of real-time exhibition anomaly trend figure.
Alternatively, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception, the storage unit, for the data in the exception record file to be stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
Alternatively, the database includes project table, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
Alternatively, the storage unit 32 is used to, when database is that exception record file is stored in database by space-time first, be stored in exception record file in database again when database non-NULL.
Alternatively, the storage unit 32 includes：
First insertion module, the project table for the version information and filename of the exception record file to be inserted into database；
Second insertion module, for the test time started of each testing time node in the exception record file and test end time and corresponding item record ID to be inserted into testing time table；
3rd insertion module, for the abnormal information and testing time node ID of each testing time node of each exception record file to be inserted into exception table.
Alternatively, the storage unit 32 includes：
Searching modul, the old exception record file for searching last preservation；
Judge module, for contrasting new abnormal log file and old exception record file, judges whether two exception record files have inclusion relation；
First preserving module, for when two exception record files do not have inclusion relation, then preserve new abnormal log file, the last upload file name for updating the data the item record of storehouse project table uploads file name to be new, and all testing time nodes in new file and the corresponding abnormal information of the testing time node are inserted respectively into the corresponding testing time table of database and exception table；
Second preserving module, for when two exception record files have inclusion relation, preserving new abnormal log file, deletes old exception record file, updates the data the last upload file name of the item record in the project table of storehouse and uploads file name to be new；The position of the corresponding testing time node in new abnormal log file is found according to the position of old last testing time node of exception record file, it is newly test end time of the abnormal log file in the testing time node of the position to update the data the test end time of the testing time node in the testing time table in storehouse；Additional abnormal information in testing time node described in new abnormal log file is inserted into exception table；The testing time node that will be increased newly in new abnormal log file, and abnormal information in these testing time nodes insert corresponding testing time table and exception table respectively.
Alternatively, the judging unit, for when only one of which testing time node in old exception record file, it is equal to the test time started of first testing time node of old exception record file when the test time started of first testing time node in new abnormal log file, when the test end time of first testing time node of new exception log file is more than or equal to the test end time of old first testing time node of exception record file, judge that two exception record files have inclusion relation, otherwise without inclusion relation；
When the testing time node number in old exception record file is more than 1, it is respectively equal to the test time started and test end time of first testing time node of old exception record file when the test time started and test end time of first testing time node in new abnormal log file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, during the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position, judge that two exception record files have inclusion relation, otherwise do not have inclusion relation.
Alternatively, the generation unit 33 includes：
First acquisition module, the abnormal number sum that all mobile terminals for the same version information of data acquisition in the database occur, i.e., total abnormal number；
Second acquisition module, for the testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；
Tendency chart drafting module, for being abscissa with beta version number, average exceptional value is that ordinate draws tendency chart, wherein averagely exceptional value=total abnormal number/total testing time.
Alternatively, the tendency chart screening conditions include total sample size, total testing time and Exception Type.
It is described above; only embodiment of the invention, but protection scope of the present invention is not limited thereto, any one skilled in the art the invention discloses technical scope in; the change or replacement that can be readily occurred in, should all be included within the scope of the present invention.Therefore, protection scope of the present invention should be defined by scope of the claims.
Claims (18)
1. a kind of mobile terminal stability test method, it is characterised in that including：
The exception record file of mobile terminal described in timing receipt；
Data in the exception record file are stored in database by rule；
Data generation anomaly trend figure in the database, and real-time exhibition.
2. mobile terminal stability test method according to claim 1, it is characterized in that, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception,
The data by the exception record file are stored in database by rule to be included：Data in the exception record file are stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
3. mobile terminal stability test method according to claim 2, it is characterised in that the database includes project table, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
4. mobile terminal stability test method according to claim 3, it is characterised in that the data by the exception record file are stored in database by rule to be included：When database is that exception record file is stored in database by space-time first, exception record file is stored in database again when database non-NULL, wherein exception record file is stored in into database again includes：The exception record file of identical version information is stored in database again, and the exception record file of different editions information is stored in database again.
5. mobile terminal stability test method according to claim 4, it is characterised in that described to be stored in exception record file in database first, and that the exception record file of different editions information is stored in into operating procedure in database again is identical, including：
The version information and filename of the exception record file are inserted into the project table of database；
The test time started of each testing time node in the exception record file and test end time and corresponding item record ID are inserted into testing time table；
The abnormal information and testing time node ID of each testing time node of each exception record file are inserted into exception table.
6. mobile terminal stability test method according to claim 4, it is characterised in that described the exception record file of identical version information is stored in into database again to include：
Search the last old exception record file preserved；
The new abnormal log file of contrast and old exception record file, judge whether two exception record files have inclusion relation；
If two exception record files do not have inclusion relation, then preserve new abnormal log file, the last upload file name for updating the data the item record of storehouse project table uploads file name to be new, and all testing time nodes in new file and the corresponding abnormal information of the testing time node are inserted respectively into the corresponding testing time table of database and exception table；
If two exception record files have inclusion relation, new abnormal log file is preserved, old exception record file is deleted, updated the data the last upload file name of the item record in the project table of storehouse and upload file name to be new；
The position of the corresponding testing time node in new abnormal log file is found according to the position of old last testing time node of exception record file, it is newly test end time of the abnormal log file in the testing time node of the position to update the data the test end time of the testing time node in the testing time table in storehouse；
Additional abnormal information in testing time node described in new abnormal log file is inserted into exception table；
The testing time node that will be increased newly in new abnormal log file, and abnormal information in these testing time nodes insert corresponding testing time table and exception table respectively.
7. mobile terminal stability test method according to claim 6, it is characterised in that described to judge whether two exception record files include with inclusion relation：
When only one of which testing time node in old exception record file, it is equal to the test time started of first testing time node of old exception record file when the test time started of first testing time node in new abnormal log file, when the test end time of first testing time node of new exception log file is more than or equal to the test end time of old first testing time node of exception record file, two exception record files have inclusion relation, otherwise without inclusion relation；
When the testing time node number in old exception record file is more than 1, it is respectively equal to the test time started and test end time of first testing time node of old exception record file when the test time started and test end time of first testing time node in new abnormal log file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, during the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position, two exception record files have inclusion relation, otherwise do not have inclusion relation.
8. the mobile terminal stability test method according to any one of claim 1-7, it is characterised in that the data generation anomaly trend figure in the database includes：
Abnormal number sum occurs for all mobile terminals of the same version information of data acquisition in the database, i.e., total abnormal number；
The testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；
The abscissa of the tendency chart is beta version number, and ordinate is average exceptional value,
Average exceptional value=total abnormal number/total testing time.
9. mobile terminal stability test method according to claim 8, it is characterised in that the tendency chart screening conditions include total sample size, total testing time and Exception Type.
10. a kind of mobile terminal stability test device, it is characterised in that including：
Receiving unit, the exception record file for mobile terminal described in timing receipt；
Storage unit, for the data in the exception record file to be stored in database by rule；
Generation unit, anomaly trend figure, and real-time exhibition are generated for the data in the database.
11. mobile terminal stability test device according to claim 10, it is characterized in that, the exception record file includes multiple test nodes, and each test node includes version information, testing time node and abnormal information, and the version information of each test node is identical；The testing time node includes test time started and test end time；The abnormal information includes the description of the abnormal time occurred, abnormal type and exception, the storage unit, for the data in the exception record file to be stored in database according to the version information of the exception record file, and identical data do not repeat to preserve.
12. mobile terminal stability test device according to claim 11, it is characterised in that the database includes project table, testing time table and exception table；The version information that the project table includes exception record file is recorded, the testing time table includes the one of project belonged to record in project table each test time started and test end time in the test time started of the testing time node of exception record file and the record of test end time, the testing time table；The abnormal information that the exception table includes exception record file is recorded；The testing time section for one of them testing time node that abnormal information record in each exception table belongs in testing time table.
13. mobile terminal stability test device according to claim 12, it is characterized in that, the storage unit is used to, when database is that exception record file is stored in database by space-time first, be stored in exception record file in database again when database non-NULL.
14. mobile terminal stability test device according to claim 13, it is characterised in that the storage unit includes：
First insertion module, the project table for the version information and filename of the exception record file to be inserted into database；
Second insertion module, for the test time started of each testing time node in the exception record file and test end time and corresponding item record ID to be inserted into testing time table；
3rd insertion module, for the abnormal information and testing time node ID of each testing time node of each exception record file to be inserted into exception table.
15. mobile terminal stability test device according to claim 13, it is characterised in that the storage unit includes：
Searching modul, the old exception record file for searching last preservation；
Judge module, for contrasting new abnormal log file and old exception record file, judges whether two exception record files have inclusion relation；
First preserving module, for when two exception record files do not have inclusion relation, then preserve new abnormal log file, the last upload file name for updating the data the item record of storehouse project table uploads file name to be new, and all testing time nodes in new file and the corresponding abnormal information of the testing time node are inserted respectively into the corresponding testing time table of database and exception table；
Second preserving module, for when two exception record files have inclusion relation, preserving new abnormal log file, deletes old exception record file, updates the data the last upload file name of the item record in the project table of storehouse and uploads file name to be new；The position of the corresponding testing time node in new abnormal log file is found according to the position of old last testing time node of exception record file, it is newly test end time of the abnormal log file in the testing time node of the position to update the data the test end time of the testing time node in the testing time table in storehouse；Additional abnormal information in testing time node described in new abnormal log file is inserted into exception table；The testing time node that will be increased newly in new abnormal log file, and abnormal information in these testing time nodes insert corresponding testing time table and exception table respectively.
16. mobile terminal stability test device according to claim 15, it is characterized in that, the judging unit, for when only one of which testing time node in old exception record file, it is equal to the test time started of first testing time node of old exception record file when the test time started of first testing time node in new abnormal log file, when the test end time of first testing time node of new exception log file is more than or equal to the test end time of old first testing time node of exception record file, judge that two exception record files have inclusion relation, otherwise do not have inclusion relation；
When the testing time node number in old exception record file is more than 1, it is respectively equal to the test time started and test end time of first testing time node of old exception record file when the test time started and test end time of first testing time node in new abnormal log file, and the test time started of last testing time node of old exception record file is identical with the test time started of the testing time node at new abnormal log file opposite position, during the test end time for the testing time node that the test end time of last testing time node of old exception record file is less than or equal at new abnormal log file opposite position, judge that two exception record files have inclusion relation, otherwise do not have inclusion relation.
17. the mobile terminal stability test device according to any one of claim 10-16, it is characterised in that the generation unit includes：
First acquisition module, the abnormal number sum that all mobile terminals for the same version information of data acquisition in the database occur, i.e., total abnormal number；
Second acquisition module, for the testing time sum of all testing time nodes of all mobile terminals of the same version information of data acquisition in the database, i.e. total testing time；
Tendency chart drafting module, for being abscissa with beta version number, average exceptional value is that ordinate draws tendency chart, wherein averagely exceptional value=total abnormal number/total testing time.
18. mobile terminal stability test device according to claim 17, it is characterised in that the tendency chart screening conditions include total sample size, total testing time and Exception Type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610175981.2A CN107229554A (en) | 2016-03-25 | 2016-03-25 | Mobile terminal stability test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610175981.2A CN107229554A (en) | 2016-03-25 | 2016-03-25 | Mobile terminal stability test method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107229554A true CN107229554A (en) | 2017-10-03 |
Family
ID=59931713
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610175981.2A Pending CN107229554A (en) | 2016-03-25 | 2016-03-25 | Mobile terminal stability test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107229554A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108197951A (en) * | 2017-12-28 | 2018-06-22 | 广州美诚汇信息科技有限公司 | A kind of cosmetics license responsibility is honoured an agreement monitor supervision platform and method |
| CN108363659A (en) * | 2018-02-23 | 2018-08-03 | 青岛海信移动通信技术股份有限公司 | A kind of method and device of processing electronic equipment exception |
| CN108459956A (en) * | 2017-11-29 | 2018-08-28 | 平安科技（深圳）有限公司 | Test report automatic management method, apparatus, equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101197694A (en) * | 2006-12-04 | 2008-06-11 | 中兴通讯股份有限公司 | Central statistics and processing system and method for communication system log |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic test method and device |
| US20120185735A1 (en) * | 2011-01-19 | 2012-07-19 | Oracle International Corporation | System and method for determining causes of performance problems within middleware systems |
| CN105068930A (en) * | 2015-08-07 | 2015-11-18 | 天津市康凯特软件科技有限公司 | Intelligent analysis method and device for test generation data of mobile terminal |
| CN105159820A (en) * | 2015-09-06 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Transmission method and device of system log data |
| CN105335277A (en) * | 2014-06-27 | 2016-02-17 | 可牛网络技术（北京）有限公司 | Fault information processing method and device as well as terminal |
-
2016
- 2016-03-25 CN CN201610175981.2A patent/CN107229554A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101197694A (en) * | 2006-12-04 | 2008-06-11 | 中兴通讯股份有限公司 | Central statistics and processing system and method for communication system log |
| US20120185735A1 (en) * | 2011-01-19 | 2012-07-19 | Oracle International Corporation | System and method for determining causes of performance problems within middleware systems |
| CN102419727A (en) * | 2011-09-30 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Automatic test method and device |
| CN105335277A (en) * | 2014-06-27 | 2016-02-17 | 可牛网络技术（北京）有限公司 | Fault information processing method and device as well as terminal |
| CN105068930A (en) * | 2015-08-07 | 2015-11-18 | 天津市康凯特软件科技有限公司 | Intelligent analysis method and device for test generation data of mobile terminal |
| CN105159820A (en) * | 2015-09-06 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Transmission method and device of system log data |
Non-Patent Citations (1)
| Title |
|---|
| 石盛林: "《质量管理理论方法与实践》", 31 January 2014 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108459956A (en) * | 2017-11-29 | 2018-08-28 | 平安科技（深圳）有限公司 | Test report automatic management method, apparatus, equipment and storage medium |
| WO2019104918A1 (en) * | 2017-11-29 | 2019-06-06 | 平安科技（深圳）有限公司 | Automatic test report management method and apparatus, device and storage medium |
| CN108197951A (en) * | 2017-12-28 | 2018-06-22 | 广州美诚汇信息科技有限公司 | A kind of cosmetics license responsibility is honoured an agreement monitor supervision platform and method |
| CN108363659A (en) * | 2018-02-23 | 2018-08-03 | 青岛海信移动通信技术股份有限公司 | A kind of method and device of processing electronic equipment exception |
| CN108363659B (en) * | 2018-02-23 | 2021-06-29 | 青岛海信移动通信技术股份有限公司 | Method and device for processing abnormity of electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107832196B (en) | Monitoring device and monitoring method for abnormal content of real-time log | |
| US5946372A (en) | Apparatus and method for testing digital communications circuits | |
| CN103246595B (en) | Application management method, device, server and terminating unit | |
| CN103425750A (en) | Cross-platform and cross-application log collecting system and collecting managing method thereof | |
| US20100058122A1 (en) | Apparatus, system, and method for automated error priority determination of call home records | |
| CN111367760B (en) | Log collection method and device, computer equipment and storage medium | |
| CN105574096A (en) | Method and system for obtaining, uploading and analyzing log information | |
| CN107229554A (en) | Mobile terminal stability test method and device | |
| CN103490937A (en) | Method and device for filtering monitoring data | |
| CN102957550A (en) | System and method for alarming based on log detection | |
| CN107870859B (en) | Large-batch comparison test method and system | |
| CN113472858B (en) | Buried point data processing method and device and electronic equipment | |
| CN111224807B (en) | Distributed log processing method, device, equipment and computer storage medium | |
| CN115220995A (en) | Agent probe-based micro-service full-link analysis method | |
| CN101222351A (en) | Method and device for acquiring performance data files | |
| CN111309696A (en) | Log processing method and device, electronic equipment and readable medium | |
| CN106487852B (en) | Method, device, terminal equipment and system for realizing client file synchronization | |
| CN105337748A (en) | Log file collection method and system, server, and service cluster controlling apparatus | |
| CN109582504A (en) | A kind of data reconstruction method and device for apple equipment | |
| CN107391551B (en) | Web service data analysis method and system based on data mining | |
| CN111984844B (en) | Automatic map filling method and system based on big data | |
| CN112988828B (en) | Message pushing method and electronic equipment | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN104679894A (en) | Acquisition method of operation and maintenance data in ERP (Enterprise Resource Planning) system | |
| CN113656210A (en) | Processing method and device for error reporting information, server and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171003 |
|
| RJ01 | Rejection of invention patent application after publication |