Test result processing method, device, system and storage medium

By automatically extracting and analyzing log information on the mobile terminal and creating a problem sheet, the problem of low processing efficiency of terminal MTBF test results in the prior art is solved, and automated processing is realized, improving work efficiency and the accuracy of problem sheets.

CN114257534BInactive Publication Date: 2024-11-26BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011018949.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-24
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In the prior art, the processing efficiency of terminal MTBF test results is low. When the test fails, log information needs to be manually exported and problem sheets are created, resulting in reduced work efficiency.

Method used

When the MTBF test result of the mobile terminal fails, log information is automatically extracted, exception information is analyzed, and problem list is created based on the exception information. Automatically process it through the log analysis subsystem and problem tracking subsystem, and store and resend data to ensure the problem. Single creation was successful.

Benefits of technology

Improve the work efficiency of testers and developers, and saves time for manual processing by automated processing of MTBF test results, ensuring that problem orders can be accurately created and tracked.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114257534B_ABST
    Figure CN114257534B_ABST
Patent Text Reader

Abstract

The present application discloses a test result processing method, device, system and storage medium, which is executed by a mobile terminal, and includes: extracting the log information of the terminal when the mean time between failures (MTBF) test result is a failure; analyzing the abnormal information in the log information; and creating a problem ticket according to the abnormal information in the log information. The technical solution provided by the embodiment of the present application can automatically extract the log information of the mobile terminal for analysis when the MTBF test result of the mobile terminal is a failure, obtain the abnormal information, and automatically create a problem ticket based on the abnormal information, which effectively improves the work efficiency of testers and developers.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to the field of terminal testing technology, and more particularly to a test result processing method, device, system and storage medium. Background Art

[0002] MTBF, or Mean Time Between Failures, is an indicator for measuring the reliability of a terminal.

[0003] In the prior art, the MTBF test of the terminal requires multiple test machines to perform the MTBF test. The tester will check whether the test result is successful. If successful, a success interface will be displayed, and if failed, a failure interface will be displayed. Then the tester will take the failed machine to the computer, export the log information, manually create a problem ticket, and then submit it to the corresponding developer to handle the problem, which greatly reduces work efficiency. Summary of the invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a test result processing method, device, system and storage medium to improve the work efficiency of testers and developers.

[0005] In a first aspect, an embodiment of the present application provides a test result processing method, the method comprising:

[0006] When a mean time between failures (MTBF) test result of the mobile terminal is failure, extracting log information of the mobile terminal;

[0007] Analyze abnormal information in the log information;

[0008] Create a problem ticket based on the exception information uploaded in the log information.

[0009] Optionally, the analyzing the abnormal information in the log information includes:

[0010] The abnormal information in the log information is associated with the identification information of the mobile terminal.

[0011] The identification information of the mobile terminal includes: a software version number or an International Mobile Equipment Identity number of the mobile terminal.

[0012] Optionally, the method further includes storing the abnormal information in the log information and the associated identification information in a database.

[0013] Optionally, the testing method further includes:

[0014] When the issue ticket creation fails, the log analysis subsystem extracts the data from the database and resends it to the JIRA system to recreate the issue ticket.

[0015] In a second aspect, an embodiment of the present application provides a test result processing method, the method comprising:

[0016] When the mean time between failures (MTBF) test result of the mobile terminal is a failure, the mobile terminal extracts its own log information and sends it to the log analysis subsystem;

[0017] The log analysis subsystem receives the log information, analyzes the abnormal information in the log information, and uploads it to the problem tracking subsystem;

[0018] The problem tracking subsystem creates a problem ticket based on the abnormal information in the log information. Optionally, the method further includes:

[0019] When the problem ticket creation fails, the problem tracking subsystem notifies the log analysis subsystem;

[0020] The log analysis subsystem extracts the abnormal information in the log information from the database and sends it to the problem tracking subsystem again;

[0021] The problem tracking subsystem recreates the problem ticket according to the abnormal information in the received log information.

[0022] In a third aspect, an embodiment of the present application provides a test result processing device, characterized in that the device includes:

[0023] A log extraction module is used to extract the log information of the terminal when the mean time between failures (MTBF) test result is a failure;

[0024] A log analysis module, used to analyze abnormal information in the log information;

[0025] The problem ticket creation module is used to create a problem ticket based on the uploaded exception information in the log information.

[0026] In a fourth aspect, an embodiment of the present application provides a mobile terminal, which includes a test result processing device as described in the third aspect.

[0027] In a fifth aspect, the embodiments of the present application provide a test result processing system, the system comprising a mobile terminal, a log analysis subsystem and a problem tracking subsystem, the mobile terminal being used to extract log information of the terminal when the mean time between failures (MTBF) test result is a failure;

[0028] The log analysis subsystem is used to receive log information from the mobile terminal, analyze abnormal information in the log information, and send the abnormal information to the problem tracking subsystem;

[0029] The problem tracking subsystem is used to receive the exception information from the log analysis subsystem and create a problem ticket based on the exception information.

[0030] In a sixth aspect, the embodiments of the present application provide a mobile terminal, including a processor, a memory and a display; the memory contains instructions executable by the processor so that the processor executes: the testing method of the above-mentioned terminal.

[0031] In a seventh aspect, the embodiments of the present application provide a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned test result processing method when executed.

[0032] Beneficial effects:

[0033] The test result processing method of the present application, when monitoring the failure of the terminal MTBF test, extracts the log information of the mobile terminal, analyzes the abnormal information in the log information; and creates a problem ticket according to the abnormal information. The embodiment of the present application monitors the MTBF test results by the mobile terminal itself, and extracts the log information for analysis to create a problem ticket when the test result is a failure, which effectively saves the working time of the testers and improves the working efficiency of the testers and developers. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0035] Figure 1 A flow chart showing a method for processing test results according to an embodiment of the present application is shown;

[0036] Figure 2 A flow chart showing a test result processing method according to another embodiment of the present application is shown;

[0037] Figure 3 A flow chart showing a test result processing method according to another embodiment of the present application is shown;

[0038] Figure 4 A structural block diagram of a test result processing device according to an embodiment of the present application is shown;

[0039] Figure 5 A structural block diagram of a test result processing device according to another embodiment of the present application is shown;

[0040] Figure 6A structural block diagram of a test result processing device according to another embodiment of the present application is shown;

[0041] Figure 7 A structural block diagram of a mobile terminal according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0042] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0043] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0044] Please refer to Figure 1 , which shows a flow chart of a test result processing method that can be applied to the embodiment of the present application. The test result processing method is executed by a mobile terminal, and the method includes:

[0045] S40, when the mean time between failures MTBF test result of the mobile terminal is failure, extracting log information of the mobile terminal;

[0046] Among them, MTBF, or Mean Time Between Failures, is an indicator to measure the reliability of the terminal. The unit is "hours". It reflects the time quality of the product and is an ability of the product to maintain its function within a specified time. Specifically, it refers to the average working time between two adjacent failures.

[0047] The MTBF test content can include voice calls, short messages, browser surfing, phone book operations, etc. You can set a monkey test of a certain duration (24h\48h\72h, etc.). You can connect to WiFi during the test. It is usually used to test system stability issues. When the MTBF test result is a failure, the log information in the terminal is extracted.

[0048] S60, analyzing abnormal information in the log information;

[0049] Specifically, the abnormal information in the log can be said to include abnormal information of voice calls, short messages, multimedia messages, browser Internet access, phone book operations, etc.

[0050] S80: Create a problem ticket based on the abnormal information in the log information.

[0051] Among them, the problem ticket refers to a document for tracking problems. Usually, after the tester finds a problem during the test of the mobile phone, he will create a document for tracking the problem and attach the log information during the test process. According to the field to which the problem belongs, it will be assigned to the developer of the module of the corresponding function for processing. Specifically, the problem ticket is created according to the abnormal information in the log information. The problem ticket can be created separately according to the corresponding test items. For example, the voice call problem ticket, the browser Internet problem ticket, the phone book operation problem ticket, etc. can also be merged into a whole problem ticket for R&D personnel to view. For example, when the tester tests the phone call function, he finds that the call cannot be connected. At this time, a problem ticket will be created, including the problem ticket number: 00001, the problem ticket title: The mobile phone voice call function is abnormal and the call cannot be connected; voice module: xx phone (i.e. the developer's contact information or email address); xx designated processing personnel: xx (i.e. the developer of the module of the corresponding function). For example, a problem ticket can be created based on the abnormal information in the log information of the browser Internet in the log information, so that the developer responsible for the browser Internet can track and solve the problem of the browser module.

[0052] Through the above method steps, when the MTBF test result of the mobile terminal is a failure, the log information of the mobile terminal can be automatically extracted, and the exception information in the log information can be obtained through log information analysis, and a problem ticket is automatically created based on the exception information, so that the developer corresponding to the problem ticket can track the problem corresponding to the exception information, which effectively improves the work efficiency of testers and developers.

[0053] It should be noted that although the operations of the method of the present invention are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0054] Please refer to Figure 2 , which shows a flow chart of a test result processing method proposed in an embodiment of the present application. The method can be implemented by a test result processing system. The method includes:

[0055] S40: When the mean time between failures (MTBF) test result of the mobile terminal is failure, the log extraction module in the mobile terminal extracts log information of the mobile terminal.

[0056] The mobile terminal includes mobile phones, tablet computers, PADs, etc., which are not limited here. Taking the mobile terminal as a mobile phone as an example, a monkey test of a certain duration (24h\48h\72h, etc.) can be set. When the test result is a failure, determine whether the monkey process is stopped. Under normal circumstances, after the preset test time (for example, 24h), the monkey process continues to run, and the test result is success. If the monkey process stops during the period, it will be considered an exception, and the test result is failure. When the test result is a failure, the log information can be extracted by triggering the bugreport (a program that feeds back bug logs) service in the mobile phone. The triggering extraction method is, for example, adb shell bugreport. After the log extraction module extracts the log information of the mobile terminal, it sends the log information to the log analysis subsystem.

[0057] S60, the log analysis subsystem receives the log information, analyzes the abnormal information in the log information, and uploads it to the problem tracking subsystem; the log analysis subsystem may be, for example, an ELK (Elasticsearch Logstash Kibana) system.

[0058] By automatically analyzing the uploaded log information, the type of problem, exception summary (key error log), number of times, and problem details can be displayed in a table format. The extracted log information, exception information / abnormal information can be compressed and then uploaded to the problem tracking subsystem via wifi.

[0059] S80: The problem tracking subsystem creates a problem ticket according to the abnormal information in the log information. The problem tracking subsystem may be, for example, a JIRA system.

[0060] The JIRA system is an issue ticket tracking system. Testers can create issue tickets through the JIRA system, and track issues with corresponding developers through issue tickets to solve problems corresponding to abnormal information.

[0061] This embodiment may further include S20, the mobile terminal monitoring a test result of a mean time between failures MTBF.

[0062] For example, by configuring a monitoring module in the mobile terminal and monitoring the MTBF test results through the monitoring module, the work efficiency of testers and developers can be further improved, and the working time of testers can be saved. Specifically, when the test machine performs the mean time between failures MTBF test on the mobile terminal, the monitoring module of the mobile terminal will monitor the test results of the test machine. When the test failure result is monitored, a control instruction is sent to the log extraction module to extract the log information, and then analyze the abnormal information in the log information.

[0063] Through the test result processing method of this embodiment, when the MTBF test failure of the mobile terminal is monitored, the log information of the terminal when the MTBF test result is a failure is extracted, and the abnormal information in the log information is analyzed and uploaded; and it is saved in the database; then this information is sent to the problem tracking subsystem to automatically create a problem ticket, which is convenient for the developer corresponding to the problem ticket to handle, greatly improving the work efficiency of testers and developers.

[0064] Based on the above embodiments, a log extraction module may be configured in the mobile terminal, a log analysis module may be configured in the log analysis subsystem, a problem ticket creation module may be configured in the problem tracking subsystem, and the like.

[0065] Based on the above examples, please refer to Figure 3 , which shows a flow chart of a test result processing method that can be applied to the embodiment of the present application. The test result processing method also includes:

[0066] S70: storing the abnormal information in the log information and its associated identification information in a database.

[0067] In this embodiment, the International Mobile Equipment Identity (IMEI), software version, abnormal log information, problems corresponding to the abnormal log, etc. of the corresponding mobile terminal are obtained and stored in the database;

[0068] By associating the abnormal information in the log information with the software version number and IMEI number of the terminal, R&D personnel can quickly find the corresponding mobile terminal and the problems that occur in the mobile terminal, which greatly improves the work efficiency of testers and developers.

[0069] In the above embodiment, the test result processing method may further include:

[0070] S90. When the problem ticket creation fails, the log analysis subsystem extracts data from the database and resends it to the problem tracking subsystem to recreate the problem ticket.

[0071] In this embodiment, the log analysis subsystem extracts data from the database and resends it to the problem tracking subsystem to recreate the problem ticket. If the problem ticket creation fails due to some reason, such as network instability, the log analysis subsystem will extract the data from the database and resend it at least once to create the problem ticket, thus solving the problem of problem ticket creation failure due to network instability.

[0072] Further, refer to Figure 4, which shows a schematic diagram of the structure of a test result processing device to which the embodiment of the present application can be applied. The test result processing device can be set in a mobile terminal. The test result processing device includes:

[0073] The log extraction module 40 is used to extract the log information of the mobile terminal when the mean time between failures MTBF test result is failure;

[0074] Among them, MTBF, or Mean Time Between Failures, is an indicator to measure the reliability of the terminal. The unit is "hours". It reflects the time quality of the product and is an ability of the product to maintain its function within a specified time. Specifically, it refers to the average working time between two adjacent failures.

[0075] The MTBF test content can include voice calls, short messages, browser surfing, phone book operations, etc. You can set a monkey test for a certain duration (24h\48h\72h, etc.). You can connect to WiFi during the test. It is usually used to test system stability issues. When the MTBF test result is a failure, the log information in the terminal is extracted.

[0076] The log analysis module 60 is used to analyze abnormal information in the log information;

[0077] Specifically, the abnormal information in the log information may include abnormal information of voice calls, short messages, multimedia messages, browser surfing, phone book operations, etc.

[0078] The problem ticket creation module 80 is used to create a problem ticket based on the uploaded abnormal information in the log information.

[0079] Among them, the problem ticket refers to a document for tracking problems. Usually, after the tester finds a problem during the test of the mobile phone, he will create a document for tracking the problem and attach the log information during the test process. According to the field to which the problem belongs, it will be assigned to the developer of the module of the corresponding function for processing. Specifically, the problem ticket is created according to the abnormal information in the log information. The problem ticket can be created separately according to the corresponding test items. For example, the voice call problem ticket, the browser Internet problem ticket, the phone book operation problem ticket, etc. can also be merged into a whole problem ticket for R&D personnel to view. For example, when the tester tests the phone call function, he finds that the call cannot be connected. At this time, a problem ticket will be created, including the problem ticket number: 00001, the problem ticket title: The mobile phone voice call function is abnormal and the call cannot be connected; voice module: xx phone (i.e. the developer's contact information or email address); xx designated processing personnel: xx (i.e. the developer of the module of the corresponding function). For example, a problem ticket can be created based on the abnormal information in the log information of the browser Internet in the log information, so that the developer responsible for the browser Internet can track and solve the problem of the browser module.

[0080] The test result processing device of this embodiment, when the MTBF test fails, extracts the log information at the time of the test failure through the log extraction module 40, analyzes the abnormal information in the log information by the log analysis module 60, and automatically creates a problem ticket based on the abnormal information by the problem ticket creation module 80, so that the technical person in charge corresponding to the problem ticket can track the problem easily, which greatly improves the work efficiency of testers and developers.

[0081] Please refer to Figure 5 , which shows a test result processing system that can be applied to the embodiments of the present application, the system includes: a mobile terminal, a log analysis subsystem and a problem tracking subsystem.

[0082] The mobile terminal is used to extract the log information of the terminal when the mean time between failures MTBF test result is a failure; for example, the mobile terminal can extract the log information of the terminal when the mean time between failures MTBF test result is a failure through the log extraction module;

[0083] The log analysis subsystem is used to receive log information from the mobile terminal, analyze abnormal information in the log information, and send the abnormal information to the problem tracking subsystem; for example, the log analysis subsystem can analyze the abnormal information in the log information through a log analysis module.

[0084] The problem tracking subsystem is used to create a problem ticket based on the abnormal information received from the log analysis subsystem. For example, the problem tracking subsystem can create a problem ticket based on the abnormal information through a problem ticket creation module.

[0085] The mobile terminal of this embodiment may also include a monitoring module 20 for monitoring the MTBF test result of the terminal; the monitoring module monitors the success or failure of the test result when the test machine is performing the MTBF test, mainly monitoring the terminal that fails the test. Taking the terminal as a mobile phone as an example, a monkey test of a certain duration (24h\48h\72h, etc.) can be set. When the test result is a failure, it is determined whether the monkey process is stopped. Under normal circumstances, after the preset test time (for example, 24h), the monkey process keeps running, and the test result is success. If the monkey process stops during the period, it will be considered as an abnormality, and the test result is failure. When the test result is a failure, the bugreport (a program for feedback bug logs) service in the mobile phone can be triggered by the monitoring module to extract log information. The triggering extraction method is, for example, adb shellbugreport. The configuration of the monitoring module makes this application more automated, further improving the work efficiency of testers and developers.

[0086] Based on the above embodiment, the system may further include a transmission module 50, which is configured in the mobile terminal and is used to compress the log information extracted in the log extraction module and send it to the log analysis module. As the running time increases, the log information will become more and more, occupying more space. In order to save space, the historical files can also be compressed.

[0087] Based on the above embodiment, the system further includes: a storage module 70 and a reconstruction module 90. The storage module 70 and the reconstruction module 90 can be configured in the log analysis subsystem.

[0088] The storage module 70 is used to store the abnormal information and the associated identification information in the log information into a database;

[0089] The reconstruction module 90 is used to, when the problem ticket creation fails, extract data from the database by the log analysis subsystem and resend it to the problem tracking subsystem to recreate the problem ticket.

[0090] In certain scenarios, such as network instability and failure to create a problem ticket, the ELK system will retrieve the data from the database and resend it at least once, notifying the problem ticket creation module of the JIRA system to create the problem ticket, thus solving the problem of failure to create a problem ticket due to network instability.

[0091] The test result processing system provided in this embodiment, when the monitoring module of the mobile terminal detects that the MTBF test fails, issues an instruction to the log extraction module to extract log information. After the log extraction is completed, the transmission module compresses the extracted log and can upload it to the log analysis module in the log analysis subsystem via wifi. The log analysis module processes the log information, obtains the IMEI number, software version, abnormal log information, module to which the abnormal log belongs, etc. of the corresponding mobile terminal, and saves it in the database.

[0092] Then, this information is sent to the problem ticket creation module of the problem tracking subsystem. The problem tracking subsystem will create a problem ticket for the corresponding module problem based on the received data for tracking the problem.

[0093] After the problem ticket is successfully created, the problem ticket creation module can send an indication message to the log analysis module that the problem ticket has been successfully created; if the creation fails, the log analysis subsystem will retrieve the data from the database and resend it to the problem ticket creation module 80 of the problem tracking subsystem to recreate the problem ticket.

[0094] The above-mentioned embodiment of the present application can automatically create a problem ticket, which is convenient for establishing associations with developers corresponding to the problem ticket, and effectively improves the work efficiency of testers and developers.

[0095] The present application also provides a mobile terminal. Figure 7 A schematic diagram of the structure of a mobile terminal to which the present application embodiment can be applied is shown in FIG. Figure 7 As shown, the mobile terminal 300 includes a central processing unit (CPU) 301, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 302 or the program loaded from the storage part 308 to the random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the system 300 are also stored. The CPU 301, the ROM 302 and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0096] The following components are connected to the I / O interface 305: an input section 1006 including a keyboard, a mouse, etc.; an output section 307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 308 including a hard disk, etc.; and a communication section 309 including a network interface card such as a LAN card, a modem, etc. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to the I / O interface 305 as needed. A removable medium 311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 310 as needed, so that a computer program read therefrom is installed into the storage section 308 as needed.

[0097] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a different order from the order marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0098] The units or modules involved in the embodiments of the present application may be implemented in software or hardware. The modules described may also be provided in a processor. For example, they may be described as follows: a processor includes a log extraction module, a log analysis module, and a problem ticket creation module. The names of these units or modules do not, in certain cases, constitute limitations on the units or modules themselves. For example, the log extraction module may also be described as a "module for extracting log information."

[0099] As another aspect, the present application further provides a computer-readable storage medium, which may be the computer-readable storage medium included in the software installation device described in the above embodiment; or may be a computer-readable storage medium that exists independently and is not installed in the device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the software installation method described in the present application.

[0100] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the present application.

Claims

1. A test result processing method, characterized in that: The method is executed by a mobile terminal, and the method includes: When a mean time between failures (MTBF) test result of the mobile terminal is failure, extracting log information of the mobile terminal; Analyze abnormal information in the log information; Creating a problem ticket based on the abnormal information in the log information; The analyzing the abnormal information in the log information includes: Associating the abnormal information in the log information with the identification information of the mobile terminal; The abnormal information in the log information includes abnormal information of voice calls, short messages, multimedia messages, browser surfing, and phone book operations.

2. The test result processing method according to claim 1, characterized in that: The identification information of the mobile terminal includes: a software version number or an International Mobile Equipment Identity number of the mobile terminal.

3. The test result processing method according to claim 1, characterized in that: The method further comprises: The abnormal information in the log information and the associated identification information are stored in a database.

4. A test result processing method, characterized in that: The method comprises: When the mean time between failures (MTBF) test result of the mobile terminal is failure, the mobile terminal extracts its own log information and sends it to the log analysis subsystem; The log analysis subsystem receives the log information, analyzes the abnormal information in the log information, and uploads it to the problem tracking subsystem; The problem tracking subsystem creates a problem ticket based on the abnormal information in the log information; The method further comprises: Storing the abnormal information in the log information and its associated identification information in a database; The abnormal information in the log information includes abnormal information of voice calls, short messages, multimedia messages, browser surfing, and phone book operations.

5. The test result processing method according to claim 4, characterized in that: The method further comprises: When the problem ticket creation fails, the problem tracking subsystem notifies the log analysis subsystem; The log analysis subsystem extracts the abnormal information in the log information from the database and sends it to the problem tracking subsystem again; The problem tracking subsystem recreates the problem ticket according to the abnormal information in the received log information.

6. A test result processing device, characterized in that: The device is arranged in a mobile terminal, and comprises: A log extraction module, used to extract log information of the mobile terminal when the mean time between failures (MTBF) test result is a failure; A log analysis module, used to analyze abnormal information in the log information; The problem ticket creation module is used to create a problem ticket based on the uploaded abnormal information in the log information; A storage module, used to store the abnormal information in the log information and its associated identification information in a database; The abnormal information in the log information includes abnormal information of voice calls, short messages, multimedia messages, browser surfing, and phone book operations.

7. A mobile terminal, characterized in that: The mobile terminal includes the test result processing device according to claim 6.

8. A test result processing system, characterized in that: The system includes a mobile terminal, a log analysis subsystem and a problem tracking subsystem. The mobile terminal is used to extract log information of the mobile terminal when the mean time between failures (MTBF) test result is failure; The log analysis subsystem is used to receive log information from the mobile terminal, analyze abnormal information in the log information, and send the abnormal information to the problem tracking subsystem; The problem tracking subsystem is used to create a problem ticket based on the abnormal information received from the log analysis subsystem; The log analysis subsystem is used to store abnormal information in the log information and its associated identification information in a database; The abnormal information in the log information includes abnormal information of voice calls, short messages, multimedia messages, browser surfing, and phone book operations.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: The computer program is used for: the test result processing method according to any one of claims 1 to 5.