TWI384362B - Method of viewing test log file and computer program product using the method - Google Patents

Description

Test method for testing log files and computer program production using this method Product

The present invention relates to a method for viewing a test record file, and more particularly to a method for viewing a test record file and a computer program product using the same.

In order to ensure the stability of the shipped products, computer system developers will test the computer system that will be shipped, and by checking the test log file, you can check whether the computer system to be shipped is working well to filter the products that are not working properly. Ensure that the computer system can run stably after shipment, including whether to pass the WHQL (Windows Hardware Quality Labs) certification.

Taking HP as an example, after designing and developing a new computer system, the computer system developed by it will be handed over to the downstream foundry to mass-produce, and the operating system and related operating system of the computer system will be related. The soft system is distributed as a system image to the foundry. In order to maintain the quality of its brand, the OEM must test the product before shipment, and this test can be carried out using the HP report program developed by it. When executing this test program, the system image of the computer system will be read and the driver in the system image will be tested. The test results will be recorded in the window test log (wtl) file format. In the file. The foundry can check the wtl file to detect if the driver has an error and report the error message to the computer system developer to correct the error. Driver.

In the current environment, to view this wtl file, you must use the Driver Test Manager Log Viewer (hereinafter referred to as DTM Log Viewer) provided by Microsoft. The DTM Log Viewer must be installed before use, and when it is used to open the contents of the test log file, the length of the test log file is relatively lengthy. The testers must check their contents one by one to check whether all the drivers have passed the test, which is extremely inconvenient in the inspection work. On the other hand, the above-mentioned viewing operation is very time consuming, and in the long-term work, the tester is likely to be in a state of fatigue. If the tester is tired, the tester will ignore it for a while and ignore a few drivers that have not passed the test.

In view of this, the present invention provides a method for checking a test record file. After setting a corresponding flag value for the information in the test record file, the content of the test record file is displayed by scanning the corresponding flag value.

The invention provides a computer program product which can be executed by loading a computer program into a computer system to quickly and systematically display the contents of the test record file.

The present invention provides a method for inspecting a test record file, which is suitable for viewing a test record file including a plurality of sets of test information, wherein each set of test information includes driver information, at least one file information and test result information, and the view method includes the following steps. First, depending on the type of information and the type of test results Define several flag values. Then, according to the type of information and the type of test results, the driver information, each file information, and the flag value of each test result information are set. Then, the viewing condition is obtained, wherein the viewing condition corresponds to at least one flag value. Finally, the driver information, file information, or test result information set to the flag value corresponding to the viewing condition is displayed.

In an embodiment of the present invention, the method for inspecting the log file further includes the following steps: a. Searching for a specific tag in the test log file. b. Get the string corresponding to the specific tag. c. When the string does not conform to a specific string composed of a plurality of specific symbols, the information type of the defined string is driver information, file information or test result information according to the order in which the specific labels are arranged in the test record file. d. Repeat steps a. through c. until all the specific tags in the test log are searched.

In an embodiment of the invention, the step of defining a plurality of flag values according to the type of information and the type of test result includes the following steps. The combination information type and the type of test result are arranged to determine the number of flag values and define the contents of each flag value.

In an embodiment of the present invention, the step of setting each driver information, each file information, and a flag value to which each test result information belongs includes the following steps. If the information type is driver information and the corresponding test result type is passed, it is set to the first flag value. If the type of information is file information, and the corresponding test result type is passed, the second flag value is set. If the type of information is test result information, and the corresponding test result type is passed, set to the third flag value. If the information type is driven Program information, and the corresponding test result type is not passed, set to the fourth flag value. If the type of information is file information and the corresponding test result type is not passed, set to the fifth flag value. If the type of information is test result information, and the corresponding test result type is not passed, set to the sixth flag value.

In an embodiment of the invention, the viewing conditions include filtering the correct driver information, displaying all driver information, displaying the file information details, and not displaying the file information details.

In an embodiment of the invention, the step of obtaining the viewing condition comprises the following steps. A user interface including a first checkbox and a second checkbox is displayed. Determining whether the first checkbox is checked to determine the viewing conditions includes filtering the correct driver information or displaying all driver information. It is judged whether the second check box is checked to determine the viewing condition, including displaying the file information details or not displaying the file information details.

In an embodiment of the invention, the step of displaying the driver information, the file information, or the test result information set to the flag value corresponding to the viewing condition includes the following steps. If the viewing condition is to display all driver information and not to display the details of the file information, the search and display are set to the first flag value, the third flag value, the fourth flag value, and the sixth in the test record file. All information about the flag value.

In an embodiment of the invention, the step of displaying the driver information, the file information, or the test result information set to the flag value corresponding to the viewing condition includes the following steps. Search and display in the test if the viewing condition is to display all driver information and display the details of the file information. All information in the log file set to the first flag value, the second flag value, the third flag value, the fourth flag value, the fifth flag value, and the sixth flag value.

In an embodiment of the invention, the step of displaying the driver information, the file information, or the test result information set to the flag value corresponding to the viewing condition includes the following steps. If the viewing condition is to filter the correct driver information and not display the file information details, search and display all the information set in the test log file as the fourth flag value and the sixth flag value. .

In an embodiment of the invention, the step of displaying the driver information, the file information, or the test result information set to the flag value corresponding to the viewing condition includes the following steps. If the viewing condition is to filter the correct driver information and display the file information details, search and display all the information set in the test log file as the fourth flag value and the fifth flag value.

In an embodiment of the invention, the test record file described above conforms to a window test log (wtl) file format.

In an embodiment of the present invention, the step of defining a plurality of flag values according to the type of information and the type of test result includes standard formatting of the test record file.

The present invention provides a computer program product that can be loaded via a computer system to perform the following steps. First, a test record file including a plurality of sets of test information is provided, wherein each set of test information includes driver information, at least one file information and test result information. Next, multiple flag values are defined according to the type of information and the type of test result. And, according to the type of information and the type of test results, each driver information and each file information are set to And the flag value of each test result information. Then, the viewing condition is obtained, wherein the viewing condition corresponds to at least one flag value. Finally, the driver information, file information, or test result information set to the flag value corresponding to the viewing condition is displayed.

According to the invention, a plurality of flag values are defined according to the type of the information and the type of the test result, and according to the type of the information and the type of the test result, the flag values of the driver information, the file information and the test result information in the test record file are set. After obtaining the viewing condition through the user interface, the appropriate information is extracted from the test record file by searching for the flag value corresponding to the viewing condition. In this way, not only can the search action be completed quickly, but also the information required by the user can be displayed systematically, thereby improving the convenience of viewing the test record file.

The above described features and advantages of the present invention will be more apparent from the following description.

In view of this, in order to enable the tester to view the test record file more easily and quickly, the present invention proposes a view method, which can be executed in the form of a computer program product. In order to clarify the content of the present invention, the following specific examples are given as examples in which the present invention can be implemented.

In order to ensure the quality of the products, computer system operators will test their products before shipment, and the generated test files can be used to provide testers with the correct function of the computer system. In general, there are many types of test software, and the format of the test record file generated is not the same, but the following It is described in the test log file conforming to the window test log (wtl) file format. Figure 1A is a schematic diagram of a test log file segment. Referring to FIG. 1A, the test log file 100 has a plurality of sets of test information (for example, test information 110) corresponding to each driver, and each set of test information includes driver information, at least one file information, and test result information.

2 is a flow chart of a method for viewing a test record file according to an embodiment of the invention. Referring to FIG. 1A and FIG. 3, as shown in FIG. 1A, each group of test information is a paragraph, so that the driver information, the file information, and the test result information in the test information cannot be clearly distinguished. Therefore, first, in step S201, the test record file 100 is formatted in a standard manner, and the driver information, the file information, the test result, and other information in the test result are sequentially processed, and the process is processed. It will be as shown in Figure 1B.

Figure 1B is a schematic diagram of a test log file segment. Referring to FIG. 1B, after the line feed processing, the driver information, file information, and test results in the test results are clearly separated to facilitate subsequent processing. Taking test information 110 as an example, test information 110 includes three parts, paragraph 101, paragraph 102, and paragraph 103. In paragraph 101, a dividing line consisting of a plurality of "=" characters is included. In the next paragraph 102, the driver information and other information not related to the driver test results are mainly recorded. In paragraph 103, the file information and the corresponding test result information are included. Since the driver includes more than one file, paragraph 103 will contain several file information and corresponding test result information. And continue in the segment After falling 103 is another set of test information.

As described above, it can be found that the driver information, the file information, and the test result information in the test log file are displayed in a specific arrangement order. Further, after the dividing line is the driver information, and until the next dividing line is the file information and test result information corresponding to the driver information. According to this, when the required information is extracted from the test record file, the obtained string can be judged as driver information, file information or test result information according to a specific arrangement order.

The description of the following embodiment will be made by taking the test log file 100 of the inspection view 1B as an example. Referring to FIG. 1B and FIG. 2, a lot of information not related to the driver test result is also recorded in the test log file 100 (for example, "<rti id="489564857"/>" in paragraph 102, "<ctx id= "230571217"/>"), so the necessary information will be retrieved from the test log file 100 before being reviewed. Therefore, in step S202, a specific tag is searched for in the test log file 100, and the specific tag is, for example, "UserText" in FIG. 1B. Next, in step S203, the string corresponding to the specific tag is obtained, that is, the string between the quotation marks "" after "UserText". For example, when "UserText" in paragraph 101 is searched, a string consisting of "=" characters will be obtained, and when "UserText" in paragraph 102 is found, "Checking Mobile Intel" will be obtained. (R)45 Express Chipset Family" string.

Next, when step S204 is performed, when the obtained string does not conform to a specific string composed of a plurality of specific symbols, the specific label is measured. The order of the records in the test record, and the information type of the defined string is driver information, file information or test result information. In this embodiment, since the string consisting of "=" characters is a separation line for separating the test information of each group, and is not necessary information for viewing the driver, the specific symbol is defined here as a character "= "." When the extracted string is not a specific string consisting of the character "=", the information type of the string is defined according to the order in which the corresponding specific label is arranged in the test record file 100.

According to the arrangement sequence illustrated in FIG. 1B, after the string consisting of the character "=" is obtained, the information type of the next string obtained immediately is defined as the driver information. Then continue to search for a specific tag and obtain a number of strings, then the definition string is the file information or test result information related to the driver information. The action of defining the type of information of the obtained string in a set of test information is completed until the string consisting of the character "=" is obtained again.

For example, after searching for the "UserText" in the paragraph 101 and obtaining the string consisting of the "=" character, since the obtained string matches the specific string, the string will not be used in step S204. Make a definition. However, it is assumed that the currently searched for "UserText" in paragraph 102 corresponds to the string "Checking Mobile Intel(R) 45 Express Chipset Family". First, it is judged that the string is not a string consisting of the character "=". Then, since it has been determined that the "UserText" in the paragraph 101 corresponds to a specific string, and the "UserText" of the paragraph 102 is arranged in the first specific label after the "UserText" of the paragraph 101, the string "Checking Mobile Intel" (R)45 Express Chipset Family" will be defined as the driver Information. Similarly, it is assumed that the string corresponding to each "UserText" of paragraph 103 is obtained, and the type of information (for example, file information or test result information) may be defined according to the order in which they are arranged.

After each time a string is obtained and it is judged whether or not the information type is to be defined, it is necessary to determine whether all the specific tags in the test record file 100 have been searched as shown in step S205. If the result of the determination is "NO", the process returns to step S202, and steps S202 to S205 are repeatedly executed until all the specific tags are searched for.

The function of repeatedly performing steps S202 to S205 is to filter information that is not related to checking the driver result. In other words, when all the specific tags in the test log file 100 are searched for (that is, when the decision result in the step S205 is "YES"), all the information related to the driver in the test log file 100 will be extracted. In this embodiment, the result of the extraction is temporarily stored in the memory. FIG. 3 is a schematic diagram of obtaining information related to the test driver test result from the test record file 100.

Referring to FIG. 3, it must first be noted that FIG. 3 is a simple representation of each piece of information obtained from the test record file 100 in a corresponding type of information. That is, FIG. 3 is merely a simplified illustration for convenience of explanation, and is not an actual result produced by analyzing the test log file 100. As shown in FIG. 3, all of the information shown in FIG. 3 will be arranged in a particular order in the test log file 100. That is, after each driver information, the corresponding file information and test result information will appear. The information in Figure 3 is the string taken from the test log file 100 (including the driver name and category, file name and location, etc.), which can be read by the tester. Whether this driver or its own file has an error.

Next, please return to step S205 of FIG. 2, and when the determination result is "Yes", then, as shown in step S206, the corresponding flag value is set for the necessary information temporarily stored in the memory, so as to facilitate searching and displaying. Information needed. In the present embodiment, several kinds of flag values have been defined in advance based on the type of information and the type of test result. For example, by arranging and combining the types of information and the types of test results, the number of flag values can be determined and the contents of each flag value can be defined. In general, the types of test results can be divided into three types of information types (ie, driver information, file information, and test result information) in the test record file 100. Flag value (first flag value, second flag value, third flag value, fourth flag value, fifth flag value, and sixth flag value).

The results of one of the permutations and combinations are shown in Table 1:

Therefore, in this embodiment, step S206 will set the flag value of each driver information, each file information, and each test result information temporarily stored in the memory according to the content of Table 1. Please refer to Table 1 and Figure 3, taking the information 310 and 330 as an example. The information type belongs to the driver information, and the corresponding test result type is passed, so it will be set as the first flag. Value (for example, the flag value "11").

For example, if information 311, 313, 315, 321, 331 and 333 are used as the example, the information type belongs to the file information, and the corresponding test result type is passed, so it will be set as the second flag value (for example, the flag value " twenty one"). If the information 312, 314, 316, 322, 332 and 334 are taken as an example, the information type belongs to the test result information, and the corresponding test result type is passed, so it will be set as the third flag value (for example, the flag value) "31").

Then, taking the information 320 as an example, the information type belongs to the driver information, and the corresponding test result type is unpassed (including the file information 323, 325 corresponding to the test result information 324, 326 that does not pass), and thus will be set. It is the fourth flag value (for example, the flag value "12"). Taking information 323 and 325 as an example, the type of information belongs to the file information, and the corresponding test result type is unsuccessful, so it will be defined as the fifth flag value (for example, the flag value "22"). If information 324 and 326 are taken as an example, the information type is test result information, and the corresponding test result type is not passed, so it will be defined as the sixth flag value (for example, the flag value "32"). This allows different flag values to be used to separate various information belonging to different test results.

It should be noted that the content of the flag value used above is a numerical value defined for convenience of explanation, and those who know the ordinary knowledge of the technology can naturally be modified accordingly. However, it is also within the scope of the embodiments of the present invention as long as the types of different test results and different types of information can be distinguished.

After the flag value of each piece of information is set, step S207 is next performed to obtain the viewing condition. Among them, the viewing conditions include filtering the correct driver information, displaying all driver information, displaying the file information details and The combination of the four cases of file information details is not displayed. Different viewing conditions correspond to at least one flag value (this will be explained later). In this embodiment, the viewing condition is obtained by displaying a user interface including the first core block and the second core block. 4 is a schematic diagram of a user interface of the embodiment. Referring to FIG. 4, in the embodiment, the user interface 400 includes a display area 401, a first check box 402, and a second check box 403. The display area 401 is configured to display the driver information corresponding to the viewing condition. File information or test result information. Among them, the check box 402 corresponds to the filtering of the correct driver information and the display of all the driver information; the check box 403 is corresponding to the display of the file information details and the display of the file information details. A prompt text is displayed next to the check boxes 402 and 403 for the tester to select. However, the user interface 400 is intended to be illustrative and is not intended to limit the scope of the invention.

In this embodiment, when the check box 402 is checked, the viewing condition may include filtering the correct driver information; otherwise, if the check box 402 is not checked, the viewing condition may include displaying all driver information. . In addition, if the check box 403 is checked, the viewing condition may include displaying the file information details; otherwise, if the check box 403 is not checked, the viewing condition may include not displaying the file information details.

The tester can check the checkboxes 402 and 403 as needed. The check box of the check boxes 402, 403 will correspond to different viewing conditions, so the results displayed in the display area 401 are also different.

After the user accesses the user interface 400 to obtain the viewing condition, step S208 is next performed to display the setting as the corresponding viewing condition. Driver information, file information, or test result information. Here, the flag values corresponding to the respective viewing conditions and the flag values corresponding to the search viewing conditions are displayed together, and the results of the related information are displayed:

First, if the first checkbox 202 and the second checkbox 203 are not checked, the view condition is to display all driver information and not to display the file information details. In the present embodiment, such viewing conditions correspond to the flag value "11", the flag value "31", the flag value "12", and the flag value "32", so in step S208, it will be in memory. The body searches for all the information set to the flag value "11", the flag value "31", the flag value "12", and the flag value "32" (ie, the information 310, 312, 314, 316 of FIG. 3, 320, 322, 324, 326, 330, 332, and 334), and the above information is displayed on the display area 401.

Second, if the first checkbox 202 is unchecked and the second checkbox 203 is checked, the view condition is to display all driver information and display the file information detail, that is, display all the contents in the memory. News. In this embodiment, such viewing conditions correspond to the flag value "11", the flag value "21", the flag value "31", the flag value "12", the flag value "22", and the flag. The value is "32". Therefore, in step S208, the search is set to the flag value "11", the flag value "21", the flag value "31", the flag value "12", the flag value "23", and the flag value " All the information of 32" (ie, information 310, 311, 312, 313, 314, 315, 316, 320, 321, 322, 323, 324, 325, 326, 330, 331, 332, 333 and 334 of Figure 3), The above information is displayed on the display area 401.

Third, if the first core block 202 is checked and the second core block 203 Not checked, indicating that the viewing condition is to filter the correct driver information and not to display the file information details. In the present embodiment, such a viewing condition corresponds to the flag value "12" and the flag value "32", so in step S208, the search is set to the flag value "12" and the flag value "32". All the information (ie, information 320, 324, and 326 of FIG. 3) is displayed in the display area 401. Accordingly, the tester can view all the wrong drivers in the display area 401.

Fourth, if both the first core block 202 and the second core block 203 are checked, the viewing condition is to filter the correct driver information and display the file information details. In this embodiment, such viewing conditions correspond to "12" and the flag value "22", so in step S208, all information that is set to "12" and the flag value "22" is searched (ie, The information 320, 323 and 325) of FIG. 3, and the above information is displayed on the display area 401.

At this point, the tester can set the viewing condition through the user interface 400, and only the information meeting the viewing condition is displayed in the display area 401. Thereby, the tester can easily despise the required information from the display area 401, thereby reducing the time required to view the test record file, and improving the convenience of viewing the test record file, thereby reducing the probability of human error.

In addition, the present invention also provides a computer program product for performing the above-mentioned test record file review method. The computer program product is basically composed of a plurality of code segments (for example, establishing an organization chart program). Code segment, signing form code segment, setting code segment, and deploying code segment), and after the code segment is loaded into the computer system and executed, the inspection method of the test record file can be completed. step. The computer program product provided by the embodiment of the present invention can be directly executed without installation, and the corresponding information in the test record file can be viewed according to the tester's setting, so that the tester can quickly and conveniently view the required data. It also avoids the inconvenience caused by the installation program.

In summary, the method for inspecting the test record file of the embodiment of the present invention and the computer program product using the method define a plurality of flag values according to the type of the information and the type of the test result, and according to the type of information corresponding to The type of test results, setting the flag information of each driver information, each file information and each test result information, and the tester can set the viewing condition through the user interface, and the viewing condition corresponds to at least one flag value to display the corresponding View driver information, file information, or test result information for the flag value of the condition. In this way, the tester can check the information that meets the viewing conditions by setting the viewing conditions, thereby improving the convenience of viewing the test record file and reducing the occurrence of human error.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.

100‧‧‧ test record file

110‧‧‧Test Information

Paragraph 101~103‧‧‧

S201-S208‧‧‧ steps of a method for inspecting a test record file according to an embodiment of the present invention

310~316, 320~326, 330~334‧‧‧Information

400‧‧‧User interface

401‧‧‧ display area

402, 403‧‧‧Checkbox

FIG. 1A is a schematic diagram of a test record file segment according to an embodiment of the invention.

FIG. 1B is a test record file according to an embodiment of the invention. Schematic diagram of the fragment.

2 is a flow chart of a method for viewing a test record file according to an embodiment of the invention.

FIG. 3 is a schematic diagram of obtaining information related to the test driver test result from the test record file.

4 is a schematic diagram of a user interface according to an embodiment of the invention.

S201~S208‧‧‧ steps of the inspection method for the test record file according to an embodiment of the present invention

Claims (24)

A test record file is adapted to view a test record file including a plurality of sets of test information, wherein each set of test information includes a driver program information, at least one file information and a test result information, and the method includes: Defining a plurality of flag values for the type of the test result and the type of the test result; setting the driver information, each of the file information, and the respective test result information according to the type of the information and the type of the test result a flag value; obtaining a viewing condition, wherein the viewing condition corresponds to at least one of the flag values; and displaying the driver information and the file information set to the flag values corresponding to the viewing condition, Or information about the test results. The method for inspecting the test record file described in claim 1 further includes: a. searching for a specific tag in the test record file; b. obtaining a string corresponding to the specific tag; c. When the string does not match a specific string composed of a plurality of specific symbols, the information type of the string is defined as the driver information, the file information, or the order of the specific label in the test record file. The test result information; and d. repeating the steps a. to c. until all the specific tags in the test record file are searched. The method for inspecting a test record file as described in claim 1, wherein a plurality of flags are defined according to the type of the information and the type of the test result The step of value includes: arranging the combination of the information category and the type of the test result to determine the number of the flag values and defining the content of each of the flag values. For the inspection method of the test record file described in claim 1, wherein the steps of setting the driver information, each of the file information, and the flag value of each of the test result information include: The information type is the driver information, and when the type of the test result is passed, the first flag value is set; if the information type is the file information, and the corresponding test result type is passed, the setting is set. a second flag value; if the information type is the test result information, and the corresponding test result type is passed, set to a third flag value; if the information type is the driver information, and corresponding When the type of the test result is not passed, the value is set to a fourth flag value; if the information type is the file information, and the type of the test result is not passed, the value is set to a fifth flag value; If the information type is the test result information, and the corresponding test result type is not passed, it is set to a sixth flag value. For the inspection method of the test record file described in claim 4, the inspection condition includes filtering the correct driver information, displaying all driver information, displaying the file information details, and not displaying the file information details. The method for inspecting a test record file as described in claim 5, wherein the step of obtaining the inspection condition comprises: Displaying a user interface including a first check box and a second check box; determining whether the first check box is checked to determine the view condition includes filtering the correct driver information or displaying all drivers Information; and determining whether the second checkbox is checked to determine whether the view condition includes displaying the file information detail or not displaying the file information detail. The method for inspecting a test record file as described in claim 6 wherein the step of displaying the driver information, the file information, or the test result information set to the flag values corresponding to the viewing condition includes If the viewing condition is to display all driver information and not displaying the file information detail, the search and display is set in the test log file as the first flag value, the third flag value, and the fourth flag. All information about the value and the sixth flag value. The method for inspecting a test record file as described in claim 6 wherein the step of displaying the driver information, the file information, or the test result information set to the flag values corresponding to the viewing condition includes If the viewing condition is to display all the driver information and display the file information detail, the search and display is set in the test record file as the first flag value, the second flag value, and the third flag. All information of the value, the fourth flag value, the fifth flag value, and the sixth flag value. For example, the inspection record file of the test record mentioned in item 6 of the patent application scope The method for displaying the driver information, the file information, or the test result information set to the flag values corresponding to the viewing condition includes: if the viewing condition is filtering the correct driver information and not displaying When the file information is detailed, all information that is set to the fourth flag value and the sixth flag value in the test record file is searched for and displayed. The method for inspecting a test record file as described in claim 6 wherein the step of displaying the driver information, the file information, or the test result information set to the flag values corresponding to the viewing condition includes : If the viewing condition is to filter the correct driver information and display the file information detail, search and display all the information set in the test record file as the fourth flag value and the fifth flag value. The method for inspecting a test record file as described in claim 1, wherein the test record file conforms to a Windows Test Log (WTL) file format. The method for checking a test record file according to the first aspect of the patent application, wherein before the defining the flag values according to the type of the information and the type of the test result, the method further comprises: standard formatting the test record file. A computer program product loaded by a computer system to perform the following steps: providing a test record file including a plurality of sets of test information, wherein each set of test information includes a driver information, at least one file information, and a test knot Information; defining a plurality of flag values according to a type of information and a test result type; setting each of the driver information, each of the file information, and each of the information types according to the type of the information and the type of the test result The flag value to which the test result information belongs; obtaining a view condition, wherein the view condition corresponds to at least one of the flag values; and displaying the driver set to the flag values corresponding to the view condition Information, the file information, or information about the test results. The computer program product of claim 13, wherein the program further comprises: a. searching for a specific tag in the test record file; b. obtaining a string corresponding to the specific tag; c. When the string does not match a specific string composed of a plurality of specific symbols, the information type of the string is defined as the driver information and the file information according to the order in which the specific label is arranged in the test record file. Or the test result information; and d. Repeat the steps a. to c. until all the specific tags in the test record are searched. The computer program product of claim 13, wherein the program defines a plurality of flag values according to the type of the information and the type of the test result, including arranging and combining the information type and the type of the test result to determine the The number of flag values and defines the content of each of these flag values. A computer program product as described in claim 13 of the patent application, The program includes the information of the driver, each of the file information, and the flag value of each of the test result information, including if the information type is the driver information, and the test result is corresponding to the test result. When the type is passed, it is set to a first flag value. If the information type is the file information, and the corresponding test result type is passed, the second flag value is set, if the information type is the test The result information is set to a third flag value when the type of the test result is passed, and is set to a fourth if the information type is the driver information and the type of the test result is not passed. The flag value, if the information type is the file information, and the corresponding test result type is not passed, set to a fifth flag value, and if the information type is the test result information, and the corresponding test When the result type is not passed, it is set to a sixth flag value. For example, the computer program product described in claim 16 includes the following conditions: filtering the correct driver information, displaying all driver information, displaying the details of the file information, and not displaying the details of the file information. The computer program product of claim 17, wherein the program, when the viewing condition is obtained, includes displaying a user interface including a first verification block and a second verification block, and determining the first Check whether the check box is checked to determine whether the view condition includes filtering the correct driver information or displaying all driver information, and determining whether the second check box is checked to determine the view condition including displaying the file information details. Or do not display the details of the file information. A computer program product as described in claim 18, The program includes displaying the driver information, the file information, or the test result information corresponding to the flag values corresponding to the viewing condition, including if the viewing condition is to display all driver information and not displaying When the file information is detailed, all information that is set to be the first flag value, the third flag value, the fourth flag value, and the sixth flag value in the test record file is searched for and displayed. The computer program product of claim 18, wherein the program includes the driver information, the file information, or the test result information that is set to the flag values corresponding to the viewing condition, including If the viewing condition is to display all the driver information and display the file information details, the search and display is set in the test record file as the first flag value, the second flag value, and the third flag. All information of the value, the fourth flag value, the fifth flag value, and the sixth flag value. The computer program product of claim 18, wherein the program includes the driver information, the file information, or the test result information that is set to the flag values corresponding to the viewing condition, including If the viewing condition is to filter the correct driver information and not display the file information details, search and display all the information set in the test log file as the fourth flag value and the sixth flag value. The computer program product of claim 18, wherein the program includes the driver information, the file information, or the test result information that is set to the flag values corresponding to the viewing condition, including If the viewing condition is to filter the correct driver information and display the file information details, the search and display is set to be in the test log file. All information of the fourth flag value and the fifth flag value. The method for inspecting a test record file as described in claim 13 wherein the test record file conforms to a window test log file format. The method for checking a test record file according to claim 13 , wherein before the defining the flag values according to the type of the information and the type of the test result, the method further comprises: standard formatting the test record file.