Test procedure verification method and device for multiple models of products

Abstract

This invention provides a method and apparatus for verifying test programs for multiple product models, relating to the field of product testing technology. The invention can acquire target production information of the product to be tested; based on the target production information, determine the target product model and target test program data, including common test items, dedicated test items, and the correspondence between dedicated test items and product models; and test the product to be tested based on the target product model and target test program data to obtain test program verification results. By splitting the test program into common and dedicated test items, and integrating test programs for different product models, a single target test program data is used to adapt to all product models, significantly shortening the program development time caused by frequent test program updates and reducing the error rate of program upgrades, thereby ensuring the timeliness and reliability of production line production.

Description

Technical Field

[0001] The present invention relates to the technical field of product testing, and in particular to a method and device for verifying a testing program for multiple models of products. Background Art

[0002] With the advancement of Sip (System in Package) packaging technology, Dies (dices after wafer cutting, i.e. unpackaged chips or bare chips) from different wafer fabs, different wafer process nodes, different chip design companies, etc. are packaged in the same plastic package. From the product side, the same package can achieve rapid product upgrades and iterations through the combination of different chip categories, different wafer models, different wafer processes, etc., to meet diverse market needs. However, from the perspective of the packaging production process, every minor change will lead to a new product, and a corresponding new ATE (Automatic Test Equipment) test program must be developed.

[0003] Currently, when upgrading a version of the test program, the programs corresponding to each product model must be upgraded simultaneously; omissions and errors are prone to occur during the upgrade process; even if there are no omissions, there will be a problem of a long upgrade cycle, which will have a great impact on project progress, production line stocking, product quality, etc. Summary of the invention

[0004] The purpose of the present invention is to provide a test program verification method and device for multiple models of products, so as to shorten the program development time caused by frequent updates of the test program and reduce the error rate of the test program upgrade, thereby ensuring the timeliness and reliability of production line production.

[0005] In a first aspect, the present invention provides a test program verification method for multiple models of products, comprising:

[0006] Obtain target production information of the product to be tested;

[0007] According to the target production information, determine the target product model and target test program data of the product to be tested, the target test program data includes common test items, special test items and the corresponding relationship between special test items and product models; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products;

[0008] According to the target product model and target test program data, the product to be tested is tested to obtain the test program verification result.

[0009] Further, according to the target production information, the target product model and target test program data of the product to be tested are determined, including:

[0010] Determine the target product model of the product to be tested according to the correspondence between the target production information and the preset production information and the product model;

[0011] The target test program data corresponding to the target production information is searched and obtained from a preset test program database or a cloud server.

[0012] Furthermore, the target test program data also includes test item execution order information; according to the target product model and the target test program data, the product to be tested is tested to obtain the test program verification result, including:

[0013] According to the test item execution sequence information, the test items in the target test program data are tested in turn on the product to be tested; among them, when executing to the current special test item, based on the correspondence between the special test item and the product model, it is determined whether the current special test item corresponds to the target product model. If so, the current special test item is executed.

[0014] Furthermore, the above method also includes:

[0015] If not, skip the current dedicated test item and proceed to the next test item.

[0016] Furthermore, before testing each test item in the target test program data on the product to be tested in sequence according to the test item execution sequence information, the method further includes:

[0017] Determine whether the product to be tested is successfully connected and obtain the determination result;

[0018] When the judgment result is yes, the step of testing each test item in the target test program data is executed in sequence on the product to be tested according to the test item execution sequence information.

[0019] In a second aspect, the present invention further provides a test program verification device for multiple models of products, comprising:

[0020] An acquisition module, used to acquire target production information of the product to be tested;

[0021] A determination module is used to determine the target product model and target test program data of the product to be tested according to the target production information, wherein the target test program data includes common test items, special test items, and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products;

[0022] The test module is used to test the product to be tested according to the target product model and target test program data to obtain the test program verification result.

[0023] Furthermore, the target test program data also includes test item execution sequence information; the test module is specifically used to: test each test item in the target test program data on the test product in turn according to the test item execution sequence information; wherein, when executing to the current special test item, based on the correspondence between the special test item and the product model, determine whether the current special test item corresponds to the target product model, and if so, execute the current special test item.

[0024] Furthermore, the above device also includes:

[0025] A judgment module is used to judge whether the connection to the product to be tested is successful and obtain a judgment result;

[0026] The test module is also used to execute the steps of testing each test item in the target test program data in sequence on the product to be tested according to the test item execution sequence information when the judgment result of the judgment module is yes.

[0027] In a third aspect, the present invention further provides an ATE device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the computer program, the test program verification method for multiple models of products of the first aspect is implemented.

[0028] In a fourth aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is run by a processor, the test program verification method for multiple models of products of the first aspect is executed.

[0029] A test program verification method and device for a multi-model product provided by an embodiment of the present invention can obtain target production information of the product to be tested; determine the target product model and target test program data of the product to be tested based on the target production information, the target test program data including common test items, special test items and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of product, and the special test items are applicable to some product models of the same type of product; according to the target product model and the target test program data, the product to be tested is tested to obtain the test program verification result. In this way, by splitting the test program into two categories, common test items and special test items, the test programs of different product models are integrated together, and one target test program data is used to adapt all product models, the delivery time and error rate impact caused by the upgrade and maintenance of the test programs of different models of the same type of products is effectively reduced, the program development time caused by the frequent update of the test program is greatly shortened, and the error rate of the program upgrade is reduced, thereby ensuring the timeliness and reliability of the production line. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 A test program verification and release process provided by an embodiment of the present invention;

[0032] Figure 2 A flowchart of a test program verification method for multiple models of products provided by an embodiment of the present invention;

[0033] Figure 3 A schematic diagram of a program architecture provided by an embodiment of the present invention;

[0034] Figure 4 A schematic diagram of the structure of a test program verification device for multiple models of products provided by an embodiment of the present invention;

[0035] Figure 5 A schematic diagram of the structure of an ATE device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0036] The technical solution of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0037] ATE test program can realize FT (Final Test, chip finished product test / chip final test), CP (Chip Probing, wafer test) and other tests. Figure 1As shown in the figure, the test program verification and release process includes all the links required from program triggering upgrade to factory verification completion and importing into mass production. The test program verification and release process involves the collaboration efficiency of two parties (program developers and program receivers). Links 1, 2, and 3 shown in the dotted box are indispensable parts to ensure the correctness of the program during the program upgrade process. They are also time-consuming parts and all require the use of ATE equipment for program verification. Link 1 mainly involves the demand conversion, demand verification, code implementation and verification in the laboratory of the program change initiator. Conventional demand verification is expected to take about 3 working days (actual upgrades may take longer, which will not be discussed here); Link 2 involves program verification of the program receiver and involves cross-departmental (or cross-company) cooperation issues. During the implementation process, production line scheduling and other issues are taken into consideration. The general verification cycle is about 3 working days; Link 3 mainly verifies the stability of the program during mass production environment and batch product testing, etc. It is fully implemented in accordance with mass production standards and is expected to take 4 working days; In addition to the above links 1, 2, and 3, the time spent on the remaining links is relatively scattered, but also relatively fixed, usually taking 1 working day.

[0038] Under the existing test program verification method (i.e. the current conventional solution), with the diversification of product models, the time for program release will increase significantly. Figure 1 Taking the release process as an example, for each additional product model, the program change and upgrade time increases by (3+3+4)=10 working days.

[0039] Assuming that the probability of introducing risk with each program change is 1% (the actual value may be higher than this, this is just an example), and assuming that the same product project has n product models, the development cycle and risk rate of each upgrade will change as follows:

[0040] n=1: Development time=1+(3+3+4)×1=11 working days;

[0041] Error rate = 1%;

[0042] n=2: Development time = 1+(3+3+4)×2=21 working days; increase from the last time (i.e. n=1): 91%;

[0043] Error rate = 100% - (100% - 1%) ^ 2 = 1.99%;

[0044] n=3: Development time = 1+(3+3+4)×3=31 working days; increase from the last time: 48%;

[0045] Error rate = 100% - (100% - 1%)^3 = 2.97%;

[0046] n=4: Development time=1+(3+3+4)×4=41 working days; increase from the last time: 32%;

[0047] Error rate = 100% - (100% - 1%)^4 = 3.94%;

[0048] n=5: Development time=1+(3+3+4)×5=51 working days; increase from the last time: 24%;

[0049] Error rate = 100% - (100% - 1%) ^ 5 = 4.90%;

[0050] …

[0051] From the above calculation, it can be seen that if one product model is upgraded according to the conventional plan, as the number of product models increases, the product development time will become longer and longer, and the errors introduced during the development process will also become higher and higher. Comparing n=5 and n=1, it is found that the development cycle has increased by nearly 4.6 times and the error rate has increased by 4.9 times, which has a serious impact on the production progress and quality of the product.

[0052] The above example is only a drill for a program upgrade. Generally speaking, the same project may have an average of at least three program change requests per year, which will require more development time and human resources.

[0053] Based on this, an embodiment of the present invention provides a test program verification method and device for multiple models of products, which adopts a new program architecture solution and uses one program to adapt (be compatible with) all product models, thereby effectively reducing the impact of delivery time and error rate caused by program upgrades and maintenance of different models of the same type of products.

[0054] To facilitate understanding of this embodiment, a test program verification method for multiple models of products disclosed in an embodiment of the present invention is first introduced in detail.

[0055] The embodiment of the present invention provides a test program verification method for multiple models of products, which can be executed by ATE equipment and is suitable for Figure 1 The steps 1, 2, and 3 in the program verification process are required. Figure 2 The flowchart of a test program verification method for multiple models of products is shown, and the method mainly includes the following steps S210 to S230:

[0056] Step S210, obtaining target production information of the product to be tested.

[0057] The production information of the product may be information used in order placement or factory transfer orders, such as production batch number, order identification, and process flow identification. The production information of the product to be tested is referred to as target production information. The product to be tested may be, but is not limited to, a packaged chip.

[0058] Step S220, based on the target production information, determine the target product model and target test program data of the product to be tested, the target test program data including common test items, special test items and the correspondence between special test items and product models; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products.

[0059] In this embodiment, Figure 3 As shown, the test program is divided into two parts: the common part (corresponding to the common test items) and the unique part (corresponding to the special test items). The common part refers to the items that need to be tested for all product models, and the test content is exactly the same. The unique part means that for different product models, there will be different test requirements, and the test items corresponding to these different test requirements are the unique part. In order to achieve compatibility, a correspondence between special test items and product models can be established based on product models, such as establishing a program-product model correspondence table. Figure 3 The correspondence between the special test items and product models shown in the table includes: product model 1 corresponds to test item A, product model 2 corresponds to test item B, product model 3 corresponds to test item C, product model 4 corresponds to test item D, product model 5 corresponds to test item E, and product model 6 corresponds to test item F. In addition to the re-architecting of the program, the production information is also strictly mapped with the program-product model correspondence table, so that after the program is released, no human intervention is required, and the content to be tested can be automatically selected according to the actual product work order and other production information during the test process. It should be noted that both public test items and special test items can be one or more.

[0060] In some possible embodiments, the above step S220 may include: determining the target product model of the product to be tested according to the correspondence between the target production information and the preset production information and the product model; and searching for the target test program data corresponding to the target production information from a preset test program database or a cloud server. The test program database may be a local database of the ATE device. The cloud server may be connected to the ATE device for communication, and issue the required target test program data based on a data acquisition request sent by the ATE device, the data acquisition request carrying the target production information.

[0061] Step S230, testing the product to be tested according to the target product model and the target test program data to obtain a test program verification result.

[0062] In this embodiment, Figure 3As shown, the unique part needs to be selected for execution according to the production information, and whether to execute the test items of the unique part can be selected by matching the product model, while for the common part, all product models must execute it. Based on this, in some possible embodiments, the above-mentioned target test program data also includes test item execution order information; based on this, step S230 may include: according to the test item execution order information, the test items in the target test program data are tested in sequence for the product to be tested; wherein, when executing to the current special test item, according to the correspondence between the special test item and the product model, it is determined whether the current special test item corresponds to the target product model, if it corresponds, the current special test item is executed; if it does not correspond, the current special test item is skipped and the next test item is executed. When executing to the current public test item, the current public test item is directly tested.

[0063] In specific implementation, each test item can be marked with a test item label, which is used to indicate whether the test item is a public test item or a special test item. In this way, based on the test item label, it can be determined whether the current test item to be executed is a special test item. If the current test item is a special test item, it can be determined whether the current special test item corresponds to the target product model, thereby realizing the selection and execution of the special test item.

[0064] A test program verification method for a multi-model product provided by an embodiment of the present invention can obtain target production information of the product to be tested; determine the target product model and target test program data of the product to be tested based on the target production information, the target test program data including common test items, special test items and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of product, and the special test items are applicable to some product models of the same type of product; according to the target product model and the target test program data, the product to be tested is tested to obtain a test program verification result. In this way, by splitting the test program into two categories, common test items and special test items, the test programs of different product models are integrated together, and one target test program data is used to adapt all product models, the delivery time and error rate impact caused by the upgrade and maintenance of the test programs of different models of the same type of products is effectively reduced, the program development time caused by the frequent update of the test program is greatly shortened, and the error rate of the program upgrade is reduced, thereby ensuring the timeliness and reliability of production line production.

[0065] In order to improve the test efficiency, before testing each test item in the target test program data for the product to be tested in sequence according to the test item execution sequence information, it is possible to first determine whether the ATE device is successfully connected to the product to be tested to obtain a judgment result; when the judgment result is yes, the steps of testing each test item in the target test program data for the product to be tested in sequence according to the test item execution sequence information are executed; when the judgment result is no, the steps of testing each test item in the target test program data for the product to be tested in sequence according to the test item execution sequence information are not executed, and a reminder that the product was not successfully connected can also be issued to remind the user to reconnect the product to be tested to the ATE device.

[0066] The embodiment of the present invention integrates different product model programs into one test program, and redefines the test program: from the original one-to-one correspondence between program and product model, to one program corresponding to multiple product models. This method mainly solves the problem of long development cycle and easy introduction of errors in frequent modifications during program upgrade and change.

[0067] Compared with the conventional solutions at this stage, the development cycle and error rate corresponding to the method provided in this embodiment are simply calculated as follows:

[0068] n=1: Development time=1+(3+3+4)×1=11 working days; Compared with the original: the same;

[0069] Error rate = 1%; compared with the original: the same;

[0070] n=2:Development time=1+(3+3+4)×1=11 working days;Compared with the original: save 47.6%;Error rate=100%-(100%-1%)^1=1%;Reduced by 0.99%;

[0071] n=3: Development time = 1+(3+3+4)×1=11 working days; compared with the original: saving 64.5%; Error rate = 100%-(100%-1%)^1=1%; reduced by 1.97% compared with the original;

[0072] n=4:Development time=1+(3+3+4)×1=11 working days; compared with the original: saving 73.2%;

[0073] Error rate = 100% - (100% - 1%) ^ 1 = 1%; compared with the original, it is reduced by 2.94%;

[0074] n=5: Development time=1+(3+3+4)×1=11 working days; compared with the original: saving 78.4%; Error rate=100%-(100%-1%)^1=1%; reduced by 3.90% compared with the original;

[0075] …

[0076] It can be seen from the calculation that the development time and error rate of the method provided in this embodiment will not change with the increase of product models. Compared with the conventional solutions at this stage, the development time is saved more obviously with the increase of product models, and the error rate is also reduced more obviously with the increase of product models.

[0077] In summary, the test program verification method for multiple models of products provided in the embodiment of the present invention can be used for the test program addition, change, upgrade and release process of multiple models of products, which can greatly shorten the product test program development cycle, improve efficiency without introducing additional costs and quality risks, and also reduce the error rate of program upgrades.

[0078] Corresponding to the above-mentioned test program verification method for multiple models of products, the embodiment of the present invention also provides a test program verification device for multiple models of products, see Figure 4 A schematic diagram of the structure of a test procedure verification device for multiple models of products is shown, the device comprising:

[0079] An acquisition module 401 is used to acquire target production information of the product to be tested;

[0080] Determination module 402, used to determine the target product model and target test program data of the product to be tested according to the target production information, the target test program data including common test items, special test items and the correspondence between the special test items and the product model; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products;

[0081] The testing module 403 is used to test the product to be tested according to the target product model and the target test program data to obtain the test program verification result.

[0082] A test program verification device for a multi-model product provided by an embodiment of the present invention can obtain target production information of the product to be tested; determine the target product model and target test program data of the product to be tested based on the target production information, the target test program data including common test items, special test items and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of product, and the special test items are applicable to some product models of the same type of product; according to the target product model and the target test program data, the product to be tested is tested to obtain a test program verification result. In this way, by splitting the test program into two categories, common test items and special test items, the test programs of different product models are integrated together, and one target test program data is used to adapt all product models, the delivery time and error rate impact caused by the upgrade and maintenance of the test programs of different models of the same type of products is effectively reduced, the program development time caused by the frequent update of the test program is greatly shortened, and the error rate of the program upgrade is reduced, thereby ensuring the timeliness and reliability of the production line.

[0083] Furthermore, the above-mentioned determination module 402 is specifically used to: determine the target product model of the product to be tested according to the correspondence between the target production information and the preset production information and product model; and search for target test program data corresponding to the target production information from a preset test program database or a cloud server.

[0084] Furthermore, the above-mentioned target test program data also includes test item execution sequence information; the test module 403 is specifically used to: test each test item in the target test program data on the product to be tested in turn according to the test item execution sequence information; wherein, when executing to the current special test item, based on the correspondence between the special test item and the product model, determine whether the current special test item corresponds to the target product model, and if so, execute the current special test item.

[0085] Furthermore, the test module 403 is also used to: if there is no correspondence, skip the current dedicated test item and continue to execute the next test item.

[0086] Furthermore, the above device also includes:

[0087] A judgment module is used to judge whether the connection to the product to be tested is successful and obtain a judgment result;

[0088] The test module 403 is also used to execute the steps of testing each test item in the target test program data in sequence on the product to be tested according to the test item execution sequence information when the judgment result of the judgment module is yes.

[0089] The implementation principle and technical effects of the device provided in this embodiment are the same as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the aforementioned method embodiment.

[0090] like Figure 5 As shown, an ATE device 500 provided by an embodiment of the present invention includes: a processor 501, a memory 502 and a bus, the memory 502 stores a computer program that can be run on the processor 501, when the ATE device 500 is running, the processor 501 and the memory 502 communicate through the bus, and the processor 501 executes the computer program to implement the above-mentioned test program verification method for multiple models of products.

[0091] Specifically, the memory 502 and the processor 501 can be general-purpose memories and processors, which are not specifically limited here.

[0092] The embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the test program verification method for multiple models of products in the above method embodiment is executed. The computer-readable storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a RAM, a magnetic disk or an optical disk, and other media that can store program codes.

[0093] The term "and / or" herein is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can represent including any one or more elements selected from the set consisting of A, B, and C.

[0094] In all examples shown and described herein, any specific values ​​should be interpreted as merely exemplary and not as limiting, and thus other examples of the exemplary embodiments may have different values.

[0095] The flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and a part of a module, a program segment or 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 box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes 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 box in the block diagram and / or the flowchart, and the combination of the boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0096] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or modules can be electrical, mechanical or other forms.

[0097] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0098] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0099] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A test procedure verification method for multiple models of products, characterized in that: include: Obtain target production information of the product to be tested; Determine the target product model and target test program data of the product to be tested according to the target production information, wherein the target test program data includes common test items, special test items, and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products; The product to be tested is tested according to the target product model and the target test program data to obtain a test program verification result.

2. The method according to claim 1, characterized in that The step of determining the target product model and target test program data of the product to be tested according to the target production information includes: Determining the target product model of the product to be tested according to the target production information and the correspondence between the preset production information and the product model; The target test program data corresponding to the target production information is searched and obtained from a preset test program database or a cloud server.

3. The method according to claim 1, characterized in that The target test program data also includes test item execution order information; the test program verification result is obtained by testing the product to be tested according to the target product model and the target test program data, including: According to the test item execution order information, the test items in the target test program data are tested in sequence on the product to be tested; wherein, when executing to the current special test item, based on the correspondence between the special test item and the product model, it is determined whether the current special test item corresponds to the target product model, and if so, the current special test item is executed.

4. The method according to claim 3, characterized in that The method further comprises: If not, skip the current dedicated test item and continue to execute the next test item.

5. The method according to claim 3, characterized in that: Before testing the test items in the target test program data in sequence on the product to be tested according to the test item execution sequence information, the method further includes: Determine whether the product to be tested is successfully connected and obtain a determination result; When the judgment result is yes, the step of testing each test item in the target test program data in sequence on the product to be tested is executed according to the test item execution sequence information.

6. A test procedure verification device for multiple models of products, characterized in that: include: An acquisition module, used to acquire target production information of the product to be tested; A determination module, used to determine the target product model and target test program data of the product to be tested according to the target production information, wherein the target test program data includes common test items, special test items and the corresponding relationship between the special test items and the product model; the common test items are applicable to all product models of the same type of products, and the special test items are applicable to some product models of the same type of products; The test module is used to test the product to be tested according to the target product model and the target test program data to obtain a test program verification result.

7. The device according to claim 6, characterized in that The target test program data also includes test item execution sequence information; the test module is specifically used to: test each test item in the target test program data on the product to be tested in sequence according to the test item execution sequence information; wherein, when executing to the current special test item, based on the correspondence between the special test item and the product model, determine whether the current special test item corresponds to the target product model, and if so, execute the current special test item.

8. The device according to claim 7, characterized in that The device also includes: A judgment module, used to judge whether the connection to the product to be tested is successful and obtain a judgment result; The test module is also used to execute the step of testing each test item in the target test program data in sequence on the product to be tested according to the test item execution sequence information when the judgment result of the judgment module is yes.

9. An ATE device, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor executes the computer program, the test program verification method for multiple models of products described in any one of claims 1-5 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the test program verification method for multiple models of products according to any one of claims 1 to 5 is executed.

Images