Machine data file processing method suitable for integrated circuit testing
By reading and parsing machine test data files line by line, storing and managing them in a classified manner, the problem of large amount of test data in integrated circuits is solved, the testing efficiency and reliability are improved, and the data processing process is simplified.
Patent Information
- Application Number
- CN202311833400.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-27
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2043-12-27
Smart Images

Figure CN117825918B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a method, in particular to a machine data file processing method suitable for integrated circuit testing. Background Art
[0002] With the rapid development of integrated circuit (IC) technology, the integration of digital circuits has been continuously improved, and a number of highly integrated integrated circuits such as FPGA (Field Programmable Gate Array) and CPU (Central Processing Unit) have emerged. When testing such integrated circuits, more complex tests are required, which generates more test data.
[0003] In order to make the test results more accurate, multiple rounds of testing are often required for integrated circuits, and the amount of test data generated is growing. In order to improve test efficiency, each test is often conducted on multiple machines at the same time. After each test step is completed, all machine data will be cross-stored. Each test generally executes dozens, hundreds or even more test steps, so a large number of test data files will be generated after each test is completed.
[0004] Since the test files are relatively large, the analysis, comparison, archiving, and review of the test data require a lot of manpower and time costs, which makes it difficult to meet the test and analysis needs of integrated circuits. Summary of the invention
[0005] The purpose of the present invention is to overcome the deficiencies in the prior art and provide a machine data file processing method suitable for integrated circuit testing, which can effectively analyze and process the test data of the integrated circuit and improve the efficiency and reliability of the integrated circuit testing.
[0006] According to the technical solution provided by the present invention, a method for processing machine data files suitable for integrated circuit testing, the method for processing machine test data files comprising:
[0007] Loading a machine test data file, wherein the machine test data file includes at least one test case data unit, each test case data unit includes a test case first data block representing test case information and a test case second data block representing test result information, the test case first data block includes a test case header string and a test unit data block, and the test case second data block includes a test result data block;
[0008] Each test case data unit in the machine test data file is read line by line to extract line test data information in the machine test data file line by line, wherein:
[0009] When the extracted row test data information is located in the first data block of the test case, the basic data information of the current row test data information is determined by parsing, wherein the basic data information of the row test data information includes a test case code, a test unit title, a test data row or a test machine code;
[0010] According to the test machine code, the basic data information determined by the analysis is cached into a temporary file, wherein the temporary file includes a test case header, a test unit header, and test line data corresponding to the test machine code;
[0011] Based on the test result data block, the temporary files are classified and numbered, and transferred to the folder PASS indicating that the test passed, or the folder FAIL indicating that the test failed;
[0012] Repeat the above-mentioned line-by-line reading and parsing processing steps until all the line test data information in the machine test data file is read and parsed.
[0013] The test case header string includes the test case header "Device#:" identifier and the test case code, wherein:
[0014] The test case code is located after the "Device#:" identifier in the test case header, and the test case code corresponds to the test machine code Site one by one.
[0015] For any test unit data block, it includes the test unit title, test unit name and test data block, where:
[0016] The test unit title includes the test number Number, the test machine code Site and the test name TestName.
[0017] The data in the test data block are arranged in the order according to the test unit title.
[0018] The test result data block includes a result title and a result data row corresponding to the result title, wherein:
[0019] The result title includes the test machine coding site, test pass status, and the number of times the test was executed;
[0020] The number of result data rows is consistent with the number of test machine encoding sites in the test unit data block.
[0021] For temporary files storing basic data information, each temporary file has a unique number, and the number of temporary files increases from 0;
[0022] Save each temporary file with the corresponding test machine code site, test results, test code, and unique code.
[0023] After extracting and parsing all the line test data information in the machine test data file, data reading and parsing statistics are performed to obtain data reading and parsing statistical information, where:
[0024] The data reading and parsing statistical information includes the total file size, the number of file lines, the total number of circuits tested, the number of circuits that passed, the number of circuits that failed and / or the total parsing time.
[0025] When parsing the row test data information, the parsing includes:
[0026] For the extracted row test data information, determining the type of the row test data information, wherein the type of the row test data information is a test case start row, a test unit start row, a test data row, a test result data block start row, or a test result data row;
[0027] Based on the determined type of the row test data information, a processing step is performed to obtain basic data information of the current row test data information.
[0028] When judging the type of the row test data information, when the test case header "Device#:" identifier is identified, the type of the row test data information is judged as the test case start row, and the case start flag isTest is configured to True, otherwise, the case start flag isTest is configured to False, wherein,
[0029] When processing the test data information of the row determined as the start row of the test case, the start value and the end value of the test case code are parsed;
[0030] For the identified test case header "Device#:" identifier and the parsed test case code, save the data before the test case header "Device#:" identifier into the string m_titleData, and set the test result start flag isResult to False
[0031] Clear the temporary data string tmpStr, the encoding hash table curDut, and the temporary data hash table numtmpstr.
[0032] Test data information for the rows read and extracted, including:
[0033] When the use case start flag isTest is True and the test unit title is recognized, the current row of test data information is the test unit start row;
[0034] Parse the row test data information, find the data columns corresponding to "Number of tests", "Site of test machine code" and "Test Name", and save the row test data information into the temporary string tmpStr.
[0035] When the row test data information is determined to be a test data row, the corresponding test code, test machine code and test name are parsed according to the position of the column parsed from the start row of the test unit, and it is determined whether the obtained test machine code exists in the hash table curDut, where:
[0036] If the obtained test machine code Site does not exist in the hash table curDut, the test machine code Site and the corresponding unique code Site are stored in the hash table curDut, and a DataInfo instance object is created, and the pointer of the DataInfo instance object is stored in the hash table m_dataInfoMap, so as to use the DataInfo instance object to save the current test machine code Site, unique code and test code, and create a temporary file to save the corresponding test machine test data, and save the temporary data string tmpStr and the current row data in the temporary file, and save the temporary data string tmpStr to the hash table numtmpstr;
[0037] If the obtained test machine code Site is already in the hash table curDut, then find the unique code according to the current test machine code Site, and then find the pointer to the corresponding DataInfo instance object through the unique code, and check whether the temporary data string tmpStr corresponding to the unique code in the temporary hash table numtmpstr is equal to the current temporary data string tmpStr. If not, update the temporary data string tmpStr in the hash table numtmpstr, and write the new temporary data string tmpStr into the temporary file, and then store the current data in the temporary file of its test data.
[0038] The advantages of the present invention are as follows: the loaded machine test data file is processed by reading it line by line and parsing it after reading, so that the machine test data file can be analyzed, compared, archived and reviewed, thereby effectively analyzing and processing the test data of the integrated circuit, and improving the efficiency and reliability of the integrated circuit test. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 The present invention is a flowchart of an embodiment of the processing method.
[0040] Figure 2 A flow chart of an embodiment of parsing and processing test data information of the present invention.
[0041] Figure 3 This is an implementation example of the DataInfo instance object of the present invention.
[0042] Figure 4 This is an embodiment of the machine test data file of the present invention. DETAILED DESCRIPTION
[0043] The present invention will be further described below in conjunction with specific drawings and embodiments.
[0044] In order to effectively analyze and process the test data of the integrated circuit and improve the efficiency and reliability of the integrated circuit test, a method for processing a machine test data file suitable for the integrated circuit test is provided. In one embodiment of the present invention, the method for processing the machine test data file includes:
[0045] Loading a machine test data file, wherein the machine test data file includes at least one test case data unit, each test case data unit includes a test case first data block representing test case information and a test case second data block representing test result information, the test case first data block includes a test case header string and a test unit data block, and the test case second data block includes a test result data block;
[0046] Each test case data unit in the machine test data file is read line by line to extract line test data information in the machine test data file line by line, wherein:
[0047] When the extracted row test data information is located in the first data block of the test case, the basic data information of the current row test data information is determined by parsing, wherein the basic data information of the row test data information includes a test case code, a test unit title, a test data row or a test machine code Site;
[0048] According to the test machine code, the basic data information determined by the analysis is cached into a temporary file, wherein the temporary file includes a test case header, a test unit header, and test line data corresponding to the test machine code;
[0049] Based on the test result data block, the temporary files are classified and numbered, and transferred to the folder PASS indicating that the test passed, or the folder FAIL indicating that the test failed;
[0050] Repeat the above-mentioned line-by-line reading and parsing processing steps until all the line test data information in the machine test data file is read and parsed.
[0051] As can be seen from the above description, the machine test data file is a data file generated by testing the same integrated circuit. The machine test data file is generally in text format. The generation method and format of the machine test data file can be consistent with the existing ones. Figure 4 An embodiment of a machine test data file is shown in FIG. The machine test data file can be loaded by means commonly used in the technical field. The loaded machine test data file generally includes at least one test case data unit. The number of test case data units is related to the process of testing the integrated circuit.
[0052] Each test case data unit includes a test case first data block representing the test case information and a test case second data block representing the test result information, the test case first data block includes a test case header string and a test unit data block, and the test case second data block includes a test result data block; that is, for a test case, there will be a corresponding test case data unit, and the test case data unit will simultaneously include a test case header string, several test unit data blocks and a test result data block. Generally, the test unit data block follows the test case header string, and the test result data block is generally located after the test unit data block.
[0053] In one embodiment of the present invention, the test case header string includes a test case header "Device#:" identifier and a test case code, wherein:
[0054] The test case code is located after the "Device#:" identifier in the test case header, and the test case code corresponds to the test machine code Site one by one.
[0055] Generally, the test case header string is located at the starting position of a test case. After the test case header string is the test unit data block, which is used to identify the corresponding test data under the current test case. Specifically, the test case header string includes the test case header "Device#:" identifier and the test case code. The test case code is located in the test case header "Device#:" identifier. For example, when a test case header string is: "Device#:128-132", it represents that the start code of the current test case is 128 and the end code is 132.
[0056] In specific implementation, the test case code corresponds to the test machine code Site one by one; for example, the test machine codes obtained by parsing the test data are 0, 1, 2, 4, and 5, that is, when there are 6 test machines, the corresponding test case codes are 128, 129, 130, 131, and 132, that is, when the test case code is 128, the corresponding test machine is 0. For other corresponding situations, please refer to the description here.
[0057] In one embodiment of the present invention, any test unit data block includes a test unit title, a test unit name and a test data block, wherein:
[0058] The test unit title includes the test number Number, the test machine code Site and the test name TestName.
[0059] The data in the test data block are arranged in the order according to the test unit title.
[0060] For each test case data unit, each test unit data block generally has the same format, such as a test unit title, a test unit name, and a test data block. The test unit title is the title of the test unit data block. The test number Number, the test machine code Site, and the test name TestName in the test unit title are located in the same line. When the test number Number, the test machine code Site, and the test name TestName are detected or identified, it can be considered that the test unit data block has begun.
[0061] The test unit title is the beginning of a test unit data block, and the test unit name indicates that the following data blocks all belong to the current test unit data block. Generally, the test unit name is located on the next line of the test unit title. A test unit data block can contain multiple unit test names and corresponding test data blocks, that is, a group of corresponding test data blocks are contained under a test unit name.
[0062] The data in the test data block is arranged in order according to the test unit title, such as the test number Number in the first column, the test machine code Site in the second column, and the test name Test Name in the fourth column. When parsing the test data block, the data in the first column represents the current test number Number, the data in the second column represents the test machine code Site, and the data in the fourth column represents the test name Test Name. In this way, the test data in the test data block can be parsed.
[0063] In one embodiment of the present invention, the test result data block includes a result title and a result data row corresponding to the result title, wherein:
[0064] The result title includes the test machine coding site, test pass status, and the number of times the test was executed;
[0065] The number of result data rows is consistent with the number of test machine encoding sites in the test unit data block.
[0066] Specifically, the test result data block is used to indicate the test status of the current test case during the test. In order to facilitate reading and distinction, the test result data block must include a result header, that is, the result header is used to indicate the beginning of the test result data block and the meaning of the result data. The result header generally includes the test machine code Site, test pass status, and the number of test executions.
[0067] The result data row corresponds to the structure title, specifically, the content of the result data row includes the data of the test machine coding Site, the data of the test pass status, and the data of the test result test number. For example, a result data row can be "0, 0, 216", and the specific corresponding relationship is: the "0" in the first column indicates the test machine coding Site, the "0" in the second column indicates that the test pass status is successful, and the "216" in the third column indicates that the number of times the test is executed is 216. When the number of rows in the result data row is consistent with the number of test machine codes in the test unit data block, the test result corresponding to the test machine coding Site can be obtained.
[0068] For the above test case data unit, Figure 1 A processing method of an embodiment is shown in the figure. For the above test case data unit, a method of reading and parsing line by line is generally adopted. When reading line by line, line test data information can be obtained, and then the line test data information is parsed. In an embodiment of the present invention, when parsing the line test data information, the parsing includes:
[0069] For the extracted row test data information, determining the type of the row test data information, wherein the type of the row test data information is a test case start row, a test unit start row, a test data row, a test result data block start row, or a test result data row;
[0070] Based on the determined type of the row test data information, a processing step is performed to obtain basic data information of the current row test data information.
[0071] From the above description, it can be seen that any row test data information has corresponding data features. Therefore, when parsing, it is necessary to first determine the type of the current row test data information, and then perform corresponding parsing and post-parsing processing steps according to the determined row test data information type, so as to obtain the basic data information of the row test data information. Figure 2 The type of test data information of the determination row and the specific process of parsing and processing according to the type are explained in detail.
[0072] In one embodiment of the present invention, when determining the type of the row test data information, when the test case header "Device#:" identifier is identified, the type of the row test data information is determined to be a test case start row, and the case start flag isTest is configured to True, otherwise, the case start flag isTest is configured to False, wherein,
[0073] When processing the test data information of the row determined as the start row of the test case, the start value and the end value of the test case code are parsed;
[0074] For the identified test case header "Device#:" identifier and the parsed test case code, save the data before the test case header "Device#:" identifier into the string m_titleData, and set the test result start flag isResult to False;
[0075] Clear the temporary data string tmpStr, the encoding hash table curDut, and the temporary data hash table numtmpstr.
[0076] Specifically, it can be seen from the above description that the test case header string has specific information, that is, it contains the "Device#:" identifier. When it is identified by existing commonly used means, the type of the line test data information can be determined as the test case start line. At this time, the test case start flag isTest can be configured to True, otherwise, the test case start flag isTest is configured to False. After the "Device#:" identifier is identified, the data before the "Device#:" identifier is saved in the string m_titleData. The data before the "Device#:" identifier is generally the engineering information before the test case. In addition, the start code and end code can be saved in temporary variables devstart and devend.
[0077] In specific implementation, the coding hash table curDut is used to store the parsed test machine coding Site and its corresponding unique code, ensuring that the same test machine coding Site in the test data block is assigned a unique code only once, and creating a unique DataInfo instance.
[0078] The temporary data hash table numtmpstr is used to store unique codes and common temporary data such as test unit titles, unit test names, spaces, etc. corresponding to the test data of the test machine. It is used to ensure that the common data and format of the original data are retained when each test machine is stored separately.
[0079] In one embodiment of the present invention, the row test data information read and extracted includes:
[0080] When the test case start flag isTest is True and the test unit title is recognized, the current row of test data information is the test unit start row;
[0081] Parse the row test data information, find the data columns corresponding to "Number of tests", "Site of test machine code" and "Test Name", and save the row test data information into the temporary string tmpStr.
[0082] As can be seen from the above description, the test unit header also has specific information. Therefore, the row test data information can be parsed to determine whether it is the start row of the test unit. The specific parsing method can be selected according to needs, based on the ability to parse the row test data information.
[0083] In one embodiment of the present invention, when the row test data information is determined to be a test data row, the corresponding test number, test machine code Site and test name are parsed according to the position of the column parsed from the start row of the test unit, and it is determined whether the obtained test machine code Site exists in the hash table curDut, wherein:
[0084] If the obtained test machine code Site does not exist in the hash table curDut, the test machine code Site and the corresponding unique code are stored in the hash table curDut, and a DataInfo instance object is created, and the pointer of the DataInfo instance object is stored in the hash table m_dataInfoMap, so as to use the DataInfo instance object to save the current test machine code Site, unique code and test number, and create a temporary file to save the corresponding test machine test data, and save the temporary data string tmpStr and the current row data in the temporary file, and save the temporary data string tmpStr to the hash table numtmpstr;
[0085] If the obtained test machine code Site is already in the hash table curDut, then find the unique number according to the current test machine code Site, and then find the pointer to the corresponding DataInfo instance object through the unique number, and check whether the temporary data string tmpStr corresponding to the unique code in the temporary hash table numtmpstr is equal to the current temporary data string tmpStr. If not, update the temporary data string tmpStr in the hash table numtmpstr, and write the new temporary data string tmpStr into the temporary file, and then store the current data in the temporary file of its test data.
[0086] As can be seen from the above description, since the data is read line by line, after the test case start line and the test unit start line are determined, if the test data in the line that is read immediately is data information, it is a test data line. When it is determined that the test machine code does not exist in the hash table curDut, the test machine code Site in the hash table curDut can be directly compared, that is, the hash table curDut has a search function, and can directly determine whether the corresponding test machine code Site exists in the table.
[0087] The DataInfo instance object can be created by using the commonly used technical means in this technical field. Figure 3 An embodiment of a DataInfo instance object is shown in FIG. 1 , wherein the DataInfo instance object includes a unique code, a test machine code Site, a test code, a test result, and a temporary file name.
[0088] During the line-by-line reading process, as long as it is not the test case start line, the test unit start line, or the test result data block start line, the current line data information is generally the test data line; and when the test result data block start line is identified, the subsequent information is generally considered to be the test result data line. During the line-by-line reading of the test result data line, if the test case start line and the test unit start line are not identified, the current line test data is still considered to be the test result data line.
[0089] From the composition of the test result data block, it can be seen that when the result title is recognized, it is considered to enter the test result data block. The result title includes the test machine code Site, the test pass status, and the number of times the test is executed. After the result title is recognized, the temporary data string tmpStr is cleared, and the row of data is saved in the temporary data string tmpStr temporary string, the test result start flag isResult flag is set to True, and the use case start flag isTest flag is set to False.
[0090] If the test result start flag isResult is True, determine whether the current data row is a test result data row. If so, parse the corresponding test machine code Site and test pass status, and find the unique code corresponding to the test machine according to the hash table curDut, as well as the corresponding DataInfo instance object, save the temporary data string tmpStr and the row test data of the current row to a temporary file, and rename it: unique code.txt, and store its unique code in the m_passDataInfoIndx or m_failDataInfoIndx list according to the test result (0 or 1), which is used to count successful or failed test machine codes.
[0091] If the row test data is not the above data, the data will be stored in the temporary data string tmpStr, and then continue to read the next row of data.
[0092] In one embodiment of the present invention, for temporary files storing basic data information, each temporary file has a unique number, and the number of the temporary files increases from 0;
[0093] Save each temporary file and the corresponding test machine code, test results, test code, and unique code into the corresponding DataInfo instance object.
[0094] In specific implementation, different test cases have the same test machine code Site, but different test codes, that is, the test code corresponds to the test machine code Site. After the unique code is generated by assignment, a unique number for each temporary file can be obtained, and the code of the test machine code Site is unique, so the number of each temporary file is also unique, and the number of temporary files increases from 0.
[0095] In addition, in one embodiment of the present invention, after extracting and parsing all the row test data information in the machine test data file, data reading and parsing statistics are performed to obtain data reading and parsing statistical information, wherein:
[0096] The data reading and parsing statistical information includes the total file size, the number of file lines, the total number of circuits tested, the number of circuits that passed, the number of circuits that failed and / or the total parsing time.
[0097] Specifically, the number of test cases is the same as the total number of circuits tested.
[0098] In specific implementation, when processing the machine test data file, the relevant information can also be displayed and output, such as the input of the machine test data file, the file and test result information, etc.; the parsed results are displayed in the file and test result information area; the file and test result information area can be divided into seven small parts: the total test machine number list, the PASS test machine number list, the FAIL test machine number list, the file information, the PASS test machine number file list, the FAIL test machine number file list, and the detailed number list, specifically:
[0099] Total test machine number list, this area displays all parsed test numbers in the currently parsed test data file, and is displayed in the order of the test data in the file;
[0100] PASS test machine number list, only displays all the passed test codes in the current test file;
[0101] The FAIL test machine number list only displays all the test codes that failed in the current test file;
[0102] The file information display area displays the relevant information of the current machine test file, including the total file size, the total number of data lines in the file, the total number of circuits tested, the number of circuits that passed, the number of circuits that failed, and the total parsing time of the file;
[0103] The PASS test machine number file list displays the mapping relationship between all temporary number file names that have passed the test and the corresponding test numbers. The specific format is: number file name--test code, for example: 00001.txt--128.
[0104] The FAIL test machine number file list displays the mapping relationship between all temporary number file names that failed the test and the corresponding test numbers. The specific format is: number file name--test code, for example: 00002.txt--129.
[0105] The detailed number list shows the test data temporary number, the corresponding test machine code Site and test result information parsed in sequence. The specific format is: unique code-test code--Pass / Fail, for example: 1--128--Pass, or, 2--129--Fail, where the unique code corresponds to the temporary number file one by one.
[0106] In specific implementation, after the above analysis process, the operation step of modifying the code can also be performed, and the modification of the code includes: PASS tube core code modification and FAIL tube core code modification;
[0107] PASS tube core modification code modification is mainly responsible for modifying and saving all test codes and data that have passed the test; the PASS tube core code modification area consists of 5 parts: code change operation bar, code modification list, error list, and single project modification and saving;
[0108] The code change operation bar provides single code modification and batch code modification functions, as well as displays related information such as the total data volume, modified data, and remaining data; the code modification list is mainly used to display the test code items that have been modified, and the displayed data format is: file number name--original test code--new test code; for example: 00001.txt--128--P100; the code modification list also provides the function of clearing the current modified items and selecting the modified items individually. After clearing, you can re-modify the code and other functions; the error list mainly displays error information such as individual modification format errors; individual item modification, you can modify the code of the selected items in the code modification list individually; save, if the code list is empty, save all PASS test data, if the code list is not empty, only save the corresponding test data in the list.
[0109] The FAIL die code modification area is mainly responsible for modifying and saving all test codes and data that have not passed the test; the FAIL die code modification area consists of 5 parts: code change operation bar, number modification list, single item modification, single item deletion and save; the functions of code change operation bar, code modification list, single item modification and save are the same as those of the PASS area; single item deletion provides the modified item selected in the number list, and after deletion, it can be re-encoded.
[0110] The PASS or FAIL statistics are provided by the m_passDataInfoIndx list and the m_failDataInfoIndx list. The interface finds the corresponding DataInfo object based on the unique coding item in the above list, and displays the corresponding temporary coding file and test coding in the interface. When the user modifies a single item, the new coding and unique coding are saved to QMap<int,QString> m_passModifyfile or QMap<int,QString> In the m_failModifyfile variable, if batch modification is performed, the program will perform sequential cyclic modifications based on the set starting value, step value, and number to be modified, and save the modification results to the corresponding variables. For example, if the starting value is 100, the step value is 2, and the number to be modified is 2, then the new modified codes are 100 and 102.
[0111] The test data is reorganized and saved, and its output file name format is: original file name_ALL_PASS.txt, original file name_ALL_FAIL.txt; both output files retain the engineering information in the header of the original data file; the test data part is stored in sequence according to its unique number based on the test case. Each test case only contains multiple test unit data blocks of one machine and one test result data block.
[0112] When reorganizing and saving data, there are: Check whether there are modified items in the corresponding modifyfile variable of PASS or FAIL status. If there are, create the corresponding output file, write the project information in the saved m_titleData into the file header, and then write the data in the corresponding temporary file into the output file in the order of the unique code of the modified file. If there is no modification, save all PASS and FAIL temporary file data into the corresponding output data file in the order of the unique code.
Claims
1. A method for processing machine data files suitable for integrated circuit testing, characterized in that: The machine data file processing method comprises: Loading a machine test data file, wherein the machine test data file includes at least one test case data unit, each test case data unit includes a test case first data block representing test case information and a test case second data block representing test result information, the test case first data block includes a test case header string and a test unit data block, and the test case second data block includes a test result data block; Each test case data unit in the machine test data file is read line by line to extract line test data information in the machine test data file line by line, wherein: When the extracted row test data information is located in the first data block of the test case, the basic data information of the current row test data information is determined by parsing, wherein the basic data information of the row test data information includes a test case code, a test unit title, a test data row or a test machine code Site; According to the test machine code, the basic data information determined by the analysis is cached into a temporary file, wherein the temporary file includes the test case header, the test unit header and the test line data corresponding to the test machine code Site; Based on the test result data block, the temporary files are classified and numbered, and transferred to the folder PASS indicating that the test passed, or the folder FAIL indicating that the test failed; Repeat the above-mentioned line-by-line reading and parsing processing steps until all the line test data information in the machine test data file is read and parsed; The test case header string includes the test case header "Device#:" identifier and the test case code, wherein: The test case code is located after the "Device#:" identifier in the test case header, and the test case code corresponds to the test machine code Site one by one; When parsing the row test data information, the parsing includes: For the extracted row test data information, determining the type of the row test data information, wherein the type of the row test data information is a test case start row, a test unit start row, a test data row, a test result data block start row, or a test result data row; Based on the determined type of the row test data information, a processing step is performed to obtain basic data information of the current row test data information; When judging the type of the row test data information, when the test case header "Device#:" identifier is identified, the type of the row test data information is judged as the test case start row, and the case start flag isTest is configured to True, otherwise, the case start flag isTest is configured to False, where, When processing the test data information of the row determined as the start row of the test case, the start value and the end value of the test case code are parsed; For the identified test case header "Device#:" identifier and the parsed test case code, save the data before the test case header "Device#:" identifier into the string m_titleData, and set the test result start flag isResult to False; Clear the temporary data string tmpStr, the encoding hash table curDut, and the temporary data hash table numtmpstr; Test data information for the rows read and extracted, including: When the use case start flag isTest is True and the test unit title is recognized, the current row of test data information is the test unit start row; Parse the row test data information, find the data columns corresponding to "Number of tests", "Site of test machine code" and "Test name TestName", and save the row test data information into the temporary string tmpStr; When the row test data information is determined to be a test data row, the corresponding test number Number, test machine code Site and test name Test Name are parsed according to the position of the column parsed from the start row of the test unit, and it is determined whether the obtained test machine code Site exists in the hash table curDut, where: If the obtained test machine code Site does not exist in the hash table curDut, the test machine code Site and the corresponding unique code are stored in the hash table curDut, and a DataInfo instance object is created, and the pointer of the DataInfo instance object is stored in the hash table m_dataInfoMap, so as to use the DataInfo instance object to save the current test machine code Site, unique code and test number Number, and create a temporary file to save the corresponding test machine test data, and save the temporary data string tmpStr and the current row data in the temporary file, and save the temporary data string tmpStr to the hash table numtmpstr; If the acquired test machine code Site is already in the hash table curDut, then find the unique code according to the current test machine code Site, and then find the pointer of the corresponding DataInfo instance object through the unique code, and check whether the temporary data string tmpStr corresponding to the unique code in the temporary hash table numtmpstr is equal to the current temporary data string tmpStr. If not, update the temporary data string tmpStr in the hash table numtmpstr, and write the new temporary data string tmpStr into the temporary file, and then store the current data into the temporary file of its test data; For temporary files storing basic data information, each temporary file has a unique code, and the unique code of the temporary file increases from 0; Save each temporary file and the corresponding test machine code Site, test results, test times Number, and unique code to the corresponding DataInfo instance object.
2. The method for processing machine data files suitable for integrated circuit testing according to claim 1, characterized in that: For any test unit data block, it includes the test unit title, test unit name and test data block, where: The test unit title includes the test number Number, the test machine code Site and the test name Test Name. The data in the test data block are arranged in the order according to the test unit title.
3. The machine data file processing method suitable for integrated circuit testing according to claim 2, characterized in that: The test result data block includes a result title and a result data row corresponding to the result title, wherein: The result title includes the test machine coding site, test pass status, and the number of times the test was executed; The number of result data rows is consistent with the number of test machine encoding sites in the test unit data block.
4. The machine data file processing method suitable for integrated circuit testing according to claim 1, characterized in that: After extracting and parsing all the line test data information in the machine test data file, data reading and parsing statistics are performed to obtain data reading and parsing statistical information, where: The data reading and parsing statistical information includes the total file size, the number of file lines, the total number of circuits tested, the number of circuits that passed, the number of circuits that failed and / or the total parsing time.
