Testing method, device, system, electronic device and storage medium

Abstract

The present disclosure relates to core board detection field, and in particular to a test method, device, system, electronic device and storage medium. According to the technical solution provided by the present disclosure embodiment, by defining a plurality of test schemes configured for different types of core boards in a configuration file, and importing the test scheme defined by the configuration file into a test system when a test program is started, when the core board to be tested is tested, the corresponding test scheme is found according to the test scheme ID bound to the core board to be tested, and the core board to be tested is tested using the test scheme, and the test process is automatically carried out according to the test scheme content, on the one hand, owing to avoiding manual operation in the test process, thereby improving the accuracy of the test, on the other hand, realizing that the test program does not need to be modified and only needs to be executed by a test program to perform a plurality of test schemes. The technical purpose of using different schemes to test the core board to be tested of different types or the same type is improved, thereby improving the reusability of the test program. In addition, the user can add, delete, modify the relevant content of the test scheme in the description file as needed, thereby improving the flexibility and scalability of the test software.

Description

Technical Field

[0001] The present disclosure relates to the field of core board detection, and in particular to a testing method, device, system, electronic equipment and storage medium. Background Art

[0002] The main control core board (hereinafter referred to as the core board) typically includes a processor, random access memory chip, read-only memory chip, power supply chip, crystal oscillator, printed circuit board, and peripheral resistors and capacitors. The core board is the core control component of an embedded control system and the brain of the control system, providing functions such as input signal acquisition, program calculation, data storage, and control signal output. The core board has a wide range of applications, including power communications, industrial fields, smart home, and nearly all industries requiring electronic equipment.

[0003] To ensure product quality, core board modules undergo rigorous factory testing, which is completed by a product testing system that includes test fixtures and test software.

[0004] The existing process of factory testing the core board through the test system is as follows.

[0005] The existing test tooling leads the core board pins to the tooling terminals. The tooling equipment baseboard provides power for the core board. The core board is written with a solidified test program. Testers use multimeters, oscilloscopes, power meters and other equipment to measure the signals at the tooling terminals and determine whether the core board is qualified or unqualified based on the output signal of the core board.

[0006] Existing test software is generally installed on a host computer, which communicates directly with the core board installed on the test fixture through a serial port. The tester clicks to start the test through the test software, and the test software sends a command to start the test to the core board. After receiving the start command, the solidified test program on the core board initializes the hardware interface. After that, the tester clicks on the signal types that need to be tested in sequence, and the test software sends a command to test the signal to the core board. The core board executes the command and outputs a signal for the tester to measure. After the measurement is completed, the tester clicks on the next signal type until the test of all signal types is completed. After all test items are completed, the tester clicks to end the test, and the test software sends a stop command to the core board, and the core board stops outputting signals.

[0007] The factory testing of existing core boards has the following problems:

[0008] 1. The test software has poor reusability and cannot configure multiple test solutions for different types of core boards.

[0009] 2. The test software has poor flexibility and scalability, and the test command content is fixed. Modifying and adding test commands requires modifying the test software source code, resulting in problems such as difficulty in modifying the test software and multiple versions.

[0010] 3. The test error rate is high. Since the test steps require a lot of manual operations, it is easy to produce abnormal behaviors such as misoperation and misjudgment, resulting in inaccurate test results.

[0011] How to make up for the above defects existing in the existing factory testing of core boards is a problem that needs to be solved urgently. Summary of the Invention

[0012] In order to solve the problems in the related art, the embodiments of the present disclosure provide a testing method, apparatus, system, electronic device and storage medium.

[0013] In a first aspect, an embodiment of the present disclosure provides a test system for a core board, the test system comprising: a host computer and a test fixture; the host computer is loaded with a first test program, the test fixture comprises a control board, and the control board is loaded with a second test program; the host computer is communicatively connected to one or more core boards to be tested through one or more test fixtures;

[0014] The host computer imports one or more first configuration files through the first test program; wherein the first configuration files include description parameters of the test scheme and one or more test items, the description parameters include a test scheme ID, and the test items include test commands;

[0015] The host computer generates a test solution set according to the first configuration file using the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other;

[0016] The host computer creates one or more test fixture instances corresponding to the one or more test fixtures through the first test program;

[0017] Execute a test operation on the core board to be tested in each test tool instance, wherein the test operation on the core board to be tested includes: obtaining a test scheme ID of the core board to be tested connected to the current test tool; searching for a test scheme corresponding to the test scheme ID in the test scheme set; and sending a test command in a test item of the found test scheme to the current test tool so as to test the core board to be tested by the current test tool;

[0018] The test tool is configured to receive a test command sent by the host computer through the control board after establishing a communication connection with the host computer, and test the core board to be tested according to the test command and using the second test program.

[0019] According to an embodiment of the present disclosure, the host computer is respectively connected to one or more of the test fixtures for communication via Ethernet;

[0020] The creating one or more test fixture instances corresponding to the one or more test fixtures includes:

[0021] The host computer imports a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, and the configuration information includes a test fixture serial number and a test fixture IP address;

[0022] One or more test jig instances corresponding to the one or more test jigs are created according to the second configuration file; wherein the jig serial number and the test jig IP address of each test jig instance are different from each other.

[0023] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes:

[0024] Obtain the serial number ID of the core board to be tested connected to the current test fixture.

[0025] According to an embodiment of the present disclosure, the host computer is connected to the barcode scanner, and the test scheme ID of the core board to be tested connected to the current test fixture is obtained, and the serial number ID of the core board to be tested connected to the current test fixture is obtained, including:

[0026] The serial number QR code of the core board to be tested is scanned by the barcode scanner to obtain the test solution ID of the core board to be tested and the serial number ID of the core board to be tested.

[0027] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes:

[0028] The host computer receives an execution result corresponding to a test command in a test item of the test plan, sent by the current test tool, wherein the execution result includes a test result, or test return data and a test result, and the test result includes a test success and a test failure;

[0029] Saving the test return data in the execution result, and determining the final test result according to the test result in the execution result;

[0030] After the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

[0031] According to an embodiment of the present disclosure, determining a final test result according to the test result in the execution result includes:

[0032] When the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

[0033] According to an embodiment of the present disclosure, the testing system further includes:

[0034] The host computer exports the test record data through the first test program and forms a table file in Excel format.

[0035] According to an embodiment of the present disclosure, the test command includes one or more of the following parameters: a test command string, input parameters of the test command, a matching rule of a test command return result, a test command return result, and a content description of the test command;

[0036] The description parameters also include one or more of the following: test plan name, test plan description information and operator information.

[0037] According to an embodiment of the present disclosure, the test tool is respectively connected to the host computer and the core board to be tested via Ethernet, or the test tool is connected to the core board to be tested via a serial port and is connected to the host computer via Ethernet.

[0038] According to an embodiment of the present disclosure, the one or more core boards to be tested are communicated with a third test program, and the test commands include: a first type of test command and a second type of test command, wherein the first type of test command is defined as being processed by the test tool and not forwarded to the core board to be tested, and the second type of test command is defined as being forwarded to the core board to be tested by the test tool, so that the test command is processed by the core board to be tested through the third test program;

[0039] The step of testing the core board to be tested according to the test command and using the second test program includes:

[0040] Determine the type of the test command by the second test program; when the test command is a first type test command, forward the test command to the core board to be tested, and wait for the execution result of the test command by the core board to be tested; when the test command is a second type test command, process the test command, and return the execution result of the test command to the host computer; wherein the execution result includes the test result, or the test return data and the test result, and the test result includes a test success and a test failure;

[0041] While waiting for the execution result of the test command by the core board to be tested, if the waiting times out or the test result received by the core board to be tested for the test command is a test failure, the execution result of the test failure is returned to the host computer; if the test result received by the core board to be tested for the test command is a test success, the execution result of the test success is returned to the host computer; if the test return data of the test command by the core board to be tested is received, the test return data is returned to the host computer.

[0042] According to an embodiment of the present disclosure, the test fixture further comprises: a connecting device and a core board fixing device;

[0043] The connecting device includes a first connecting device and a second connecting device; the first connecting device is configured to connect the control board to the core board to be tested for communication; the second connecting device is configured to connect the control board to the host computer for communication;

[0044] The core board fixing device is configured to fix the core board to be tested on the first connecting device, so that the core board to be tested is communicatively connected to the control board through the first connecting device.

[0045] According to an embodiment of the present disclosure, the first connecting device includes a connecting cable, a probe board and a spring probe; the core board fixing device includes a crimping block, a fixing column and a crimping handle;

[0046] The test fixture further comprises: a test fixture box;

[0047] The crimping block and the crimping handle are connected by threads, the crimping handle is movably connected to the fixing column, and the fixing column is arranged on the upper side of the upper panel of the test fixture box;

[0048] The control board is arranged at the bottom of the test fixture box, and the probe board is fixed to the lower side of the upper panel of the test fixture box by screws, with the back of the probe board facing upward and the front facing downward, wherein the front of the probe board is connected to the control board through the connecting cable, and the probe contact on the back of the probe board contacts one end of the spring probe, and the other end of the spring probe extends out of the upper panel of the test fixture box so as to contact the contact of the core board to be tested; wherein, the probe board matches the core board to be tested, and different types of core boards to be tested correspond to different probe boards, and when the crimping handle is pressed down, the spring probe is compressed, thereby realizing the connection between the probe board and the core board to be tested, and when the crimping handle is lifted, the spring probe pops up, thereby disconnecting the probe board from the core board to be tested.

[0049] According to an embodiment of the present disclosure, the second connection device includes an Ethernet port, and the second connection device is configured to connect the control board to the host computer and the core board to be tested through the Ethernet port for communication;

[0050] Alternatively, the second connection device is configured to connect the control board to the host computer for communication via the Ethernet port, and the first connection device is configured to connect the control board to the core board to be tested for communication via a serial port.

[0051] In a second aspect, an embodiment of the present disclosure provides a testing method for a core board, which is applied to a host computer, wherein the host computer is respectively connected to one or more core boards to be tested through one or more test fixtures, and a first test program is loaded on the host computer. The testing method includes:

[0052] Importing one or more first configuration files through the first test program; wherein the first configuration files include description parameters of the test plan and one or more test items, the description parameters include a test plan ID, and the test items include test commands;

[0053] generating a test solution set according to the first configuration file by the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other;

[0054] creating one or more test fixture instances corresponding to the one or more test fixtures through the first test program;

[0055] A test operation on the core board to be tested is performed in each test tool instance, and the test operation on the core board to be tested includes: obtaining the test scheme ID of the core board to be tested connected to the current test tool; searching for the corresponding test scheme in the test scheme set according to the test scheme ID; and sending the test commands in the test items of the found test scheme to the current test tool, so that the core board to be tested is tested by the current test tool.

[0056] According to an embodiment of the present disclosure, the host computer is respectively connected to one or more test fixtures via Ethernet, and the step of creating one or more test fixture instances corresponding to the one or more test fixtures includes:

[0057] Importing a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, the configuration information including a test fixture serial number and a test fixture IP address;

[0058] One or more test jig instances corresponding to the one or more test jigs are created according to the second configuration file; wherein the jig serial number and the test jig IP address of each test jig instance are different from each other.

[0059] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes:

[0060] Obtain the serial number ID of the core board to be tested connected to the current test fixture.

[0061] According to an embodiment of the present disclosure, the host computer is connected to the barcode scanner, and the test scheme ID of the core board to be tested connected to the current test fixture is obtained, and the serial number ID of the core board to be tested connected to the current test fixture is obtained, including:

[0062] The serial number QR code of the core board to be tested is scanned by the barcode scanner to obtain the test solution ID of the core board to be tested and the serial number ID of the core board to be tested.

[0063] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes:

[0064] Receive an execution result corresponding to a test command in a test item of the test plan sent by the current test tool, wherein the execution result includes a test result, or test return data and a test result, wherein the test result includes a test success and a test failure;

[0065] Saving the test return data in the execution result, and determining the final test result according to the test result in the execution result;

[0066] After the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

[0067] According to an embodiment of the present disclosure, determining the final test result according to the test result in the execution result includes:

[0068] When the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

[0069] According to an embodiment of the present disclosure, the testing method further includes:

[0070] The test record data is exported through the first test program and formed into a table file in Excel format.

[0071] In a third aspect, an embodiment of the present disclosure provides a testing device for a core board, which is provided in a host computer, wherein the host computer is respectively connected to one or more core boards to be tested through one or more test fixtures, and a first test program is loaded on the host computer. The testing device includes:

[0072] A first configuration file importing module is configured to import one or more first configuration files through the first test program; wherein the first configuration file includes description parameters of a test plan and one or more test items, the description parameters include a test plan ID, and the test items include test commands;

[0073] a test solution set generating module, configured to generate a test solution set according to the first configuration file using the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other;

[0074] a test tool instance creation module, configured to create one or more test tool instances corresponding to the one or more test tools through the first test program;

[0075] A test execution module, the test execution module includes: a test scheme ID acquisition module, which is configured to obtain the test scheme ID of the core board to be tested connected to the current test tool in each test tool instance; a test scheme search module, which is configured to search for the test scheme corresponding to it in the test scheme set according to the test scheme ID; a test command sending module, which is configured to send the test commands in the test items of the found test scheme to the current test tool, so that the core board to be tested is tested by the current test tool.

[0076] According to an embodiment of the present disclosure, the test tool instance creation module includes:

[0077] A second configuration file importing module is configured to import a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, and the configuration information includes a test fixture serial number and a test fixture IP address;

[0078] The instance generation module is configured to create one or more test tool instances corresponding to the one or more test tools according to the second configuration file; wherein the tool serial number and test tool IP address of each test tool instance are different from each other.

[0079] According to an embodiment of the present disclosure, the test execution module further includes:

[0080] The module for obtaining the serial number ID of the core board to be tested is configured to obtain the serial number ID of the core board to be tested connected to the current test fixture.

[0081] According to an embodiment of the present disclosure, the test execution module further includes:

[0082] a test command execution result processing module configured to receive an execution result corresponding to a test command in a test item of the test scheme sent by the current test tool, the execution result including a test result, or test return data and a test result, the test result including a test success and a test failure; save the test return data in the execution result, and determine a final test result based on the test result in the execution result;

[0083] A test record data generation module is configured to generate test record data of the core board to be tested according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data after the test of the core board to be tested is completed; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

[0084] According to an embodiment of the present disclosure, the testing device further includes:

[0085] The test record data export module is configured to export the test record data through the first test program and form a table file in Excel format.

[0086] In a fourth aspect, an embodiment of the present disclosure provides an electronic device, comprising a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the test method described in any one of the second aspects.

[0087] In a fifth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implements the test method described in any one of the second aspects.

[0088] In a sixth aspect, an embodiment of the present disclosure provides a computer program product, comprising a computer program, which implements the testing method described in any one of the second aspects when executed by a processor.

[0089] According to the technical solution provided by the embodiment of the present disclosure, by defining a plurality of test schemes configured for different types of core boards in a configuration file, and importing the test scheme defined by the configuration file into the test system when the test program is started, when the core board to be tested is tested, the corresponding test scheme is found according to the test scheme ID bound to the core board to be tested, and the core board to be tested is tested using the test scheme, and the test process is automatically carried out according to the test scheme content, on the one hand, owing to avoiding manual operation in the test process, thereby improving the accuracy of the test, on the other hand, realizing that the test program does not need to be modified and only a strategy of executing multiple test schemes through a test program can be used to test the core board to be tested of different types or the same type using different schemes for the technical purpose, thereby improving the reusability of the test program. In addition, the user can add, delete, modify the relevant content of the test scheme in the description file as needed, thereby improving the flexibility and scalability of the test software.

[0090] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Other features, objectives and advantages of the present disclosure will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0092] Figure 1 A structural block diagram of a test system for a core board according to an embodiment of the present disclosure is shown;

[0093] Figure 2 A structural block diagram of another test system for a core board according to an embodiment of the present disclosure is shown;

[0094] Figure 3 A schematic diagram showing the data structure of a first configuration file according to an embodiment of the present disclosure;

[0095] Figure 4 A schematic diagram showing the data structure of a second configuration file according to an embodiment of the present disclosure;

[0096] Figure 5 Shown based on Figure 1 A structural block diagram of another test system for the core board when the host computer is connected to a barcode scanner;

[0097] Figure 6 Shown based on Figure 2 A structural block diagram of another test system for the core board when the host computer is connected to a barcode scanner;

[0098] Figure 7 A structural block diagram of a test fixture for a core board according to an embodiment of the present disclosure is shown;

[0099] Figure 8 A schematic diagram showing a test fixture for a core board according to an embodiment of the present disclosure is shown;

[0100] Figure 9 A front view schematic diagram of a probe card in a specific embodiment of the present disclosure is shown;

[0101] Figure 10 A schematic diagram of the reverse side of a probe card in a specific embodiment of the present disclosure is shown;

[0102] Figure 11 A flow chart showing a method for testing a core board according to an embodiment of the present disclosure is shown;

[0103] Figure 12 A flow chart showing a test operation of a core board to be tested according to an embodiment of the present disclosure is shown;

[0104] Figure 13 A flow chart showing another method for testing a core board according to an embodiment of the present disclosure is shown;

[0105] Figure 14 A flow chart showing another method for testing a core board according to an embodiment of the present disclosure is shown;

[0106] Figure 15 A structural block diagram of a testing device for a core board according to an embodiment of the present disclosure is shown;

[0107] Figure 16 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0108] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0109] In the present disclosure, it should be understood that terms such as "include" or "have" are intended to indicate the presence of features, numbers, steps, actions, components, parts, or combinations thereof disclosed in the present specification, and are not intended to exclude the possibility that one or more other features, numbers, steps, actions, components, parts, or combinations thereof exist or are added.

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

[0111] As mentioned above, factory testing of core boards is a crucial step in ensuring their quality, performance, and stability. However, existing methods and equipment for factory testing core boards have numerous problems, which severely impact the efficiency, accuracy, and reliability of factory testing, and thus fail to ensure product quality and performance stability.

[0112] In order to improve the efficiency, accuracy and reliability of core board factory testing and ensure the stability of product quality and performance, the inventors of the present invention have carefully studied and considered, optimized and improved the existing core board testing system from multiple dimensions, and provided a set of efficient, low-cost, highly reusable and accurate testing system.

[0113] From the perspective of test software, the present invention adopts a design that applies the test software to the upper, middle and lower layers of the host computer, control board and core board respectively, breaking through the two-layer design of the existing test software that is only applied to the host computer and core board. When the core board to be tested is tested, the control board can not only provide the core board with various interface resources required for testing, but also flexibly control the relevant parameters of the core board through test commands, such as: controlling the power-on status and startup mode of the core board, selecting the communication method between the control board and the core board, and providing necessary status support for the pins of the core board, etc. The test indicators are more comprehensive and meet different test conditions. Compared with the existing test process in which the core board to be tested is powered by the tooling equipment baseboard and the core board to be tested is in a fixed state after power-on, it is more flexible and controllable, thereby meeting the diversified testing of the core board to be tested in different application scenarios.

[0114] Further, test scheme in the present disclosure is not defined inside test program, but test scheme part is separated from test program, defined separately by configuration file, by defining the multiple test schemes configured for different types of core boards in configuration file, and the test scheme defined by this configuration file is imported into test system when test program starts, when core board to be tested is tested, according to the test scheme ID bound with core board to be tested, find corresponding test scheme, and use this test scheme to test core board to be tested, test flow is automatically carried out according to test scheme content, on the one hand, owing to avoiding the manual operation in test process, thereby improving the accuracy of test, on the other hand, realize that test program need not be modified only need to use different schemes to test core board to be tested of different types or the same type by the strategy of executing multiple test schemes of a test program, improve the reusability of test program. In addition, user can add, delete, modify the relevant content of the test scheme in description file as needed, even can add the custom extended command that meets certain format requirement to realize personalized test demand in configuration file, thereby improving flexibility and the extensibility of test software.

[0115] From the test hardware aspect, the test fixture hardware of the disclosed embodiment adopts modular design. The fixture hardware also includes a probe plate and a spring probe in addition to the control board. The core board to be tested is connected to the control board by the probe plate and the spring probe, and the probe plate can be disassembled and replaced. The type of the probe plate determines the type of the fixture. When testing different types of core boards, it is only necessary to replace the corresponding probe plate. After replacing the appropriate probe plate, the same fixture hardware can test various types of core boards, avoiding the need for each core board in the prior art to redevelop the test fixture, solving the problems of high cost, long cycle, and difficult maintenance. In addition, the test fixture also includes a crimping block, a fixed column and a crimping handle for fixing the core board to be tested. The test fixture hardware of the disclosed embodiment is simple and practical to implement, reducing manufacturing and maintenance costs. Further, multiple test fixtures can be connected in parallel with a host computer via Ethernet, so that on the one hand the problem of unstable communication caused by serial port connection is avoided, and the reliability, safety and compatibility of test communication are improved. On the other hand, multiple core boards can be tested simultaneously by connecting a host computer and multiple test fixtures in parallel, saving the number of host computers and reducing operating steps, thereby improving test efficiency.

[0116] Figure 1 A structural block diagram of a test system for a core board according to an embodiment of the present disclosure is shown. Figure 2 FIG. 1 shows a structural block diagram of another test system for a core board according to an embodiment of the present disclosure. Figure 1 and Figure 2 The test systems shown in the figure all include: a host computer and a test fixture, wherein the host computer is loaded with a first test program, and the test fixture includes a control board, wherein the control board is loaded with a second test program; the difference is that, Figure 1 The host computer shown is connected to a test fixture, so it can be connected to a core board to be tested (not shown in the figure); Figure 2 The host computer shown is connected to multiple test fixtures ( Figure 2 In the figure, three are taken as an example) and are connected in parallel, so they can respectively correspond to and communicate with multiple core boards to be tested (not shown in the figure).

[0117] for Figure 1 and Figure 2 The host computer in the test system shown, according to an embodiment of the present disclosure, can be set as follows: when the first test program is started, one or more first configuration files can be imported through the loaded first test program; wherein the first configuration file is used to define the specific content of the test plan. Generally speaking, one first configuration file can define one test plan.

[0118] The first configuration file may include but is not limited to descriptive parameters of the test plan and one or more test items. The descriptive parameters may include but are not limited to the test plan ID. The test plan ID is used to uniquely identify the test plan, and each test plan has a unique test plan ID. The descriptive parameters may also include but are not limited to one or more of the following: test plan name, test plan description information, and operator information.

[0119] Among them, the test scheme name is generally named after the core board name, model, purpose, etc., the test scheme description information is generally used to record the detailed content, modification process and other information of the test scheme, and the operator information is used to facilitate the query of the modifier information. The test items include but are not limited to test commands, and the test commands include but are not limited to one or more of the following parameters: test command string, test command input parameters, test command return result matching rules, test command return result and test command content description; wherein, the test command string is a string used to perform a specific test operation, such as: the test command for resetting the core board to be tested is Reset; the input parameters of the test command are additional information passed to the test command to affect its behavior or operation, and taking Reset as an example, when the input parameters of the test command are 0, it means pulling the level down, and when they are 1, it means pulling the level up; the test command return result is the result or output returned when the test command is executed, which can be a numerical value (such as a status code), a string, a Boolean value or other data type, depending on the nature and purpose of the test command; the input parameters of the test command and the test command return result can be either string constants or variables starting with '@'. The matching rules of the test command return results are the conditions for determining whether the test of the test item is successful. The matching rules can be used to determine whether the return result matches a string constant or a string variable. The test is considered successful only when the string of the return result strictly meets the matching rules. The content description of the test command is a detailed description of the function, purpose, execution method and expected results of the test command, which is intended to help users or developers understand how to use the command and how the command helps to complete specific test tasks. In addition, the test item may also include a test item serial number. When executing a specific test plan, the test commands of the test items can be executed in sequence according to the test item serial numbers of the test items described in the test plan, and the test results of each item can be determined.

[0120] Figure 3The following diagram shows the data structure of the first configuration file of the embodiment of the present disclosure. Taking the first configuration file using the JSON data format as an example, the file is named detectsolutions.json, where solutionID is the test solution ID; solutionName is the test solution name; solutionDesc is the test solution description; operator is the operator information; and solutionItems is the test items. Figure 3 Lists a test item. Each test item parameter includes: idx (the test item number), command (the test command string), args (the test command input parameters), expectation (the matching rule for the test command's return result), returnformat (the test command's return result), and description (the description of the test command's content). If multiple test items are defined in the first configuration file, solutionItems includes multiple sets of test item parameters.

[0121] According to an embodiment of the present disclosure, the host computer may also be configured to generate a test scenario set according to the first configuration file using the loaded first test program, wherein the test scenario IDs of the test scenarios in the test scenario set are different from each other. In a specific implementation, when generating the test scenario set, keywords such as the test scenario ID and the test scenario name may be checked and matched to determine whether duplicate additions are made. After checking that the keywords are correct, the test scenario-related content described in the first configuration file is stored in a database to generate a test scenario set list, in which each list item may be a test scenario.

[0122] According to an embodiment of the present disclosure, the host computer may also be configured to create one or more test fixture instances corresponding to the one or more test fixtures using the loaded first test program. In a specific implementation, the created test fixture instances correspond one-to-one to the connected test fixtures.

[0123] like Figure 1 As shown in , if the host computer is connected to a test fixture, a test fixture instance corresponding to the test fixture needs to be created; Figure 2As shown, the host computer is connected to three test jigs, and three corresponding test jig instances need to be created. Each jig instance can be distinguished by the relevant information of the corresponding test jig. In a specific example, the host computer is respectively connected to one or more of the test jigs via Ethernet. In this case, each test jig has its own IP address. Therefore, the host computer can use the IP address of the test jig to associate with a specific test jig instance, so as to distinguish the multiple test jig instances created. When creating an instance, the host computer can import a second configuration file in advance when the loaded first test program is started, wherein the second configuration file contains configuration information of one or more test jigs, and the configuration information includes the test jig serial number and the test jig IP address. Figure 4 Schematic diagram of the data structure of the second configuration file of the embodiment of the present disclosure is shown. Figure 4 As shown, the second configuration file uses the JSON data format as an example. The second configuration file is named config.json and uses "Clients" to identify the data of the test fixture. Clients can contain data of multiple test fixtures ( Figure 4 Take three test fixtures as an example for explanation), where the data of each test fixture includes: "id" is the test fixture serial number, and "ip" is the test fixture IP address, which cannot be repeated.

[0124] After importing the second configuration file, the host computer creates each test fixture instance according to the configuration information of each test fixture in the second configuration file. Each instance can be implemented by a thread. After creation, the operations in each instance can be executed independently and in parallel without interfering with each other. The method provided by the embodiment of the present disclosure, which creates a corresponding fixture instance according to the imported configuration file containing test fixture information, can facilitate users to add, delete, and modify the number, IP address, and serial number of fixtures in the configuration file without changing the test program, thereby testing the core board more flexibly and efficiently.

[0125] According to the embodiment of the present disclosure, after each test fixture instance is created, each test fixture instance can independently test the core board to be tested to which it corresponds, and perform the test operation on the core board to be tested in each test fixture instance. By encapsulating the operation of testing the core board to be tested in the corresponding test fixture instance, since the operations in each instance can be executed independently and in parallel without interfering with each other, it is possible to achieve the purpose of simultaneously connecting multiple test fixtures in parallel through a host computer to test multiple core boards to be tested at the same time, thereby improving the test efficiency.

[0126] Specifically, the test operation of the core board to be tested includes: obtaining the test scheme ID of the core board to be tested connected to the current test fixture; searching for the test scheme corresponding to it in the test scheme set according to the test scheme ID; sending the test command in the test item of the found test scheme to the current test fixture, so as to test the core board to be tested by the current test fixture. Wherein, the "current test fixture" mentioned in the test operation refers to the test fixture corresponding to the currently running test fixture instance.

[0127] When designing how to match the core board to be tested with a specific test plan, the inventor of the present invention found that: if the serial number ID of the core board to be tested is matched with a specific test plan, then the serial number ID of each core board to be tested needs to be input and saved in advance for matching with the serial number ID of the scanned core board to be tested, so as to correspond to the specific test plan. In this way, it is necessary to maintain a database corresponding to the serial number ID and the test plan. The amount of data is huge and maintenance is difficult, which invisibly increases more manual operations. This not only easily leads to abnormal behaviors such as misoperation and misjudgment, but also causes problems such as inaccurate test results. Alternatively, the correspondence process between the two is fixed in the test program, which in turn requires modification of the test program when testing other core boards for which the serial number ID is not entered, reducing the reusability of the test software.

[0128] After research and thinking, the inventor of the present invention creatively matched the test plan ID with the specific test plan and integrated the test plan ID into the serial number QR code of each core board, using the test plan ID as an index parameter to determine which specific test process to execute when the core board leaves the factory.

[0129] In the prior art, the serial number QR code of core board is a kind of special QR code for identifying and tracking core board identity, contains the contents such as serial number ID and manufacturer information, is generally printed on its surface, and user can intuitively see and scan it.Like this, can according to the test requirement of specific each core board, the test scheme ID corresponding to the test scheme that meets this test requirement is fused in the serial number QR code of core board, after obtaining test scheme ID by scanning this serial number QR code, according to searching the corresponding test scheme in pre-stored test scheme set, core board is tested.Test scheme ID is fused in the mode in the serial number QR code of each core board, when specifically realizing, directly generate the serial number QR code comprising serial number ID and test scheme ID by manufacturer when shipping from the factory and be printed on core board, the configuration file for describing test scheme can also be generated by manufacturer when shipping from the factory and be packaged together with test program for test personnel to directly use, in some cases, can only be modified appropriately according to test requirement, it is simple and convenient to implement and not prone to error when corresponding test scheme.

[0130] In addition, this method of binding the test scheme ID to each core board to determine the specific test process is more effective than the method of determining the specific test process by the serial number ID of the core board. In some cases, different core boards may use the same test scheme, and the test scheme ID is used to correspond to the specific core board, which can simplify the corresponding rules, reduce the amount of data and save database expenses. In addition, there is no need for testers to input the serial number ID of each core board to be tested on the host computer in advance, so there is no need to maintain the database corresponding to the serial number ID and the test scheme, which simplifies the test steps. At the same time, there is no need to make any modifications to the test program, thereby improving the test efficiency and the reusability of the test software.

[0131] When obtaining the test solution ID of the core board to be tested connected to the current test fixture, according to an embodiment of the present disclosure, the test solution ID of the core board to be tested can be obtained by scanning the serial number QR code of the core board to be tested with a barcode scanner connected to the host computer. At the same time, the serial number ID of the core board to be tested can also be obtained in this way. The obtained serial number ID of the core board to be tested is used to identify the test record data of each core board generated after the test is completed, and is used to determine whether the test command to read the core board ID is executed successfully during the test. Based on Figure 1 and Figure 2 , Figure 5 and Figure 6 The corresponding block diagrams show the structure of two other test systems for the core board when the host computer is connected to the barcode scanner.

[0132] After finding the test plan corresponding to the obtained test plan ID based on the test plan set, the test commands for each test item can be automatically sent to the current test tool in sequence according to the test item number in the test plan, and the test results of each test item can be determined. After all test items in the test plan are completed, the tester is notified through a pop-up window or other means.

[0133] for Figure 1 and Figure 2 The test tooling in the test system shown, according to an embodiment of the present disclosure, can be configured to: after establishing a communication connection with the host computer, receive the test command sent by the host computer through the control board, and test the core board to be tested according to the test command and using the second test program.

[0134] The second test program loaded in the control board of the test tool involved in the embodiment of the present disclosure is used to process the test commands sent by the host computer and other test-related operations, such as: establishing a connection with the host computer and the core board to be tested.

[0135] Before the host computer sends the test command to the test tooling, and before the test tooling receives the test command sent by the host computer, it is first necessary to establish a communication connection between the host computer and the test tooling. When the test tooling tests the core board to be tested according to the test command, it also needs to establish a communication connection with the core board to be tested so as to send the relevant test commands to the core board to be tested and receive the test results returned by the core board to be tested.

[0136] For the communication connection mode between the host computer, the test jig and the core board to be tested in the test system of the disclosed embodiment, according to the disclosed embodiment, it can be specifically: the test jig is respectively connected to the host computer and the core board to be tested by Ethernet, or the test jig is connected to the core board to be tested by serial port, and is connected to the host computer by Ethernet. That is to say, both Ethernet communication and serial communication can be used between the test jig and the core board to be tested. When specifically implemented, Ethernet communication can be used by default. If serial communication needs to be used instead, it can be achieved by setting the test command of the core board serial port communication.

[0137] When the test tool is respectively connected to the host computer and the core board to be tested by Ethernet, their Ethernet ports are connected to a network switch. In a specific example, host computer is the server of TCP protocol, and IPv4 address is set to 192.168.3.5, binds and monitors service port 10000, then judges whether there is a request for client to establish a connection, if not, then continue to monitor service port 10000, if so, then establish a connection with it;The IPv4 address of the control panel Ethernet port of test tool is set to 192.168.3.10, 192.168.4.10 and 192.168.5.10 three network segments, wherein 192.168.3.10 address is communicated with host computer, and 192.168.4.10 and 192.168.5.10 address are communicated with core board to be tested. The control panel of test tool actively connects host computer service port as client, if connection is unsuccessful, then attempts to continue to connect, until connection is successful. After the connection is successful, the control board and the host computer can communicate successfully. The IPv4 address of Ethernet port 1 of the core board to be tested is 192.168.4.12, and the IPv4 address of Ethernet port 2 is 192.168.5.12. The core board also acts as the server of the TCP protocol, binds and listens to the service port 20000. The control board actively connects to the core board service port as a client. After the connection is successful, the control board and the core board to be tested can communicate successfully. When multiple test fixtures are connected in parallel with the host computer, the IPv4 address of the Ethernet port of the control board of each test fixture can be set to 192.168.3.11, 192.168.3.12, 192.168.3.13, etc., and then establish connections with the host computer and the core board to be tested respectively.

[0138] After establishing a communication connection with the host computer, the test fixture can receive the test command sent by the host computer through the control board. Specifically, after the test fixture receives the test command sent by the host computer, it first determines the type of the received test command, and then performs different processing according to different command types. Wherein, the test command includes but is not limited to: a first type of test command and a second type of test command, the first type of test command is defined as being processed by the test fixture and not forwarded to the core board to be tested, the control board comprehensively controls the core board through the received first type of test command, both obtains the operating status of the core board, and sets the operating parameters of the core board, can also control the power supply of the core board, set the input level of the core board pin, reset the core board, set the core board to start the boot dial, set the communication interface type, provide ADC acquisition voltage, automatically update the core board online status, etc., to meet different test conditions. The second type of test command is defined as being forwarded to the core board to be tested by the test fixture so that it can be processed by the third test program loaded by the core board to be tested by itself.

[0139] When specifically implemented, the test command can also include the third class test command, such as: custom extension command, as long as it meets certain format requirements, such as: test command line end includes "\r\n" character string, can be added in the first configuration file. For example: can increase the commands related to user accounts such as username, passwd, in order to log into the core board to be tested, so that the test program on the host computer can support user management functions, with the operations such as user registration, password modification, password verification, user deletion; In addition, further can increase the command such as ps (for viewing the command of the process state of the current operation) and top (for the command of the resource occupancy of each process in the real-time display system), in order to view the core board resource occupancy situation. Add which kind of custom extension command, specifically can be determined according to test requirements. For the processing flow of custom extension command, can select the same processing as the second class test command, that is: forwarded to the core board to be tested by the test fixture and processed by it by the third test program, corresponding core board to be tested also needs to support this type of custom extension command.

[0140] Table 1 shows the commands and their functions within the first category of test commands. Table 2 shows the commands and their functions within the second category of test commands. The "SetInterface" command in the second category of test commands is used to set up serial communication on the core board. When the control board and the core board under test communicate via serial ports, the "SetInterface:1\r\n" test command needs to be added to the test plan definition.

[0141] Table 1 First category test commands

[0142]

[0143]

[0144] Table 2 Second category test commands

[0145]

[0146]

[0147] According to an embodiment of the present disclosure, the core board to be tested is tested according to the test command, including: judging the type of the test command, when the test command is a first type test command, forwarding the test command to the core board to be tested, and waiting for the execution result of the test command by the core board to be tested; when the test command is a second type test command, processing the test command, and returning the execution result of processing the test command to the host computer; wherein the execution result includes a test result, or test return data and a test result, and the test result includes a test success and a test failure. When the test result is a test failure, the information of the test failure includes a character string (such as: ERR, TestFailed, etc.) indicating that the test failed, and also includes a failure reason.

[0148] When the test fixture is waiting for the execution result of the test command by the core board to be tested, if the waiting times out or the test result of the test command received by the core board to be tested is a test failure, the execution result of the test failure is returned to the host computer; if the test result of the test command received by the core board to be tested is a test success, the execution result of the test success is returned to the host computer; if the test return data of the test command received by the core board to be tested is returned, the test return data is returned to the host computer. Wherein, the test return data is the intermediate result of the execution of the test command. For example: for the test command "IDCheck\r\n", the core board returns "IDCheck:OK,1151022330030160\r\n" after execution is completed, wherein "1151022330030160" is the test return data, and "OK" indicates that the test is successful.

[0149] According to an embodiment of the present disclosure, the test operation on the core board to be tested executed in each test fixture instance of the host computer further includes:

[0150] The host computer receives the execution result corresponding to the test command in the test item of the test scheme sent by the current test tool, and the execution result includes the test result, or the test return data and the test result, and the test result includes test success and test failure. The test return data in the execution result is saved, and the final test result is determined according to the test result in the execution result. Wherein, the final test result is determined according to the test result in the execution result, including: when the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

[0151] Taking the test command for testing GPIO as an example, the host computer sends the test command "GpioCheck:3000\r\n", where GpioCheck is the command for testing GPIO, and 3000 is the timeout period in milliseconds. To ensure the independence of each packet of data, a carriage return and line feed character "\r\n" must be added to the end of the command. After receiving the command, the control board determines that the command belongs to the second type of test command and needs to forward it to the core board. It then queries whether a connection with the core board is successfully established. If not, it directly returns the error "GpioCheck:TestFailed\r\n" to the host computer. If the core board is online, it forwards the command to the core board and waits for the test result. The core board processes the received test command through the loaded self-test program. If the core board test is successful, it will send "GpioCheck:OK\r\n" to the control board. If the test fails, it will send "GpioCheck:TestFailed\r\n". The control board forwards the test result to the host computer. If the control board does not receive the test result within the timeout period, it will directly send the timeout data "GpioCheck:TimeoutErr\r\n" to the host computer.

[0152] It can be seen from this that after the host computer obtains the test plan ID of the core board to be tested, the host computer and the test tooling do not need to manually click the start, end, test and other buttons to perform operations during the automatic execution of the test plan. Instead, it automatically confirms the current test results and automatically performs the next test in the plan, thereby avoiding abnormal behaviors such as misoperation and misjudgment, solving the problem of inaccurate test results and improving test efficiency.

[0153] After the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data; the first test program saves the test record data in a database. Wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time. Wherein, ESAM (Embedded Secure Access Module) serial number refers to embedded security control module serial number.

[0154] According to an embodiment of the present disclosure, the test system further includes: the host computer exports the test record data through the first test program and forms a spreadsheet file in Excel format, which can be named with the current system time when exported.

[0155] Furthermore, the primary test program installed on the host computer supports summary statistics of test record data. For example, data can be filtered by keywords such as time, batch number, test tool IP address, operator, product model, and order number. Statistics such as test pass rate, test capacity, and average test time are also supported, making data statistics more convenient for querying order details, formulating production plans, and managing factory records. Furthermore, test record data can be uploaded to the MES (Manufacturing Execution System) production management system, further enhancing management convenience.

[0156] The above is a detailed description of the test system of the embodiment of the present disclosure from the perspective of test process execution. The following is a detailed description of the hardware structure of the test tooling in the test system.

[0157] Figure 7 FIG. 1 shows a structural block diagram of a test fixture for a core board according to an embodiment of the present disclosure. Figure 7 As shown, the test fixture includes, in addition to the control board, a connecting device and a core board fixing device. The connecting device includes a first connecting device and a second connecting device; the first connecting device is configured to connect the control board to the core board to be tested for communication; the second connecting device is configured to connect the control board to the host computer for communication; the core board fixing device is configured to fix the core board to be tested on the first connecting device so that the core board to be tested can be connected to the control board for communication via the first connecting device.

[0158] Figure 8 A schematic diagram of a test fixture for a core board according to an embodiment of the present disclosure is shown. In order to describe the connection relationship between the two when the test fixture is used to test the core board to be tested, Figure 8 The core board to be tested is shown in FIG. Figure 8 As shown, the first connecting device in the test fixture includes a connecting cable, a probe board and a spring probe; the core board fixing device includes a crimping block, a fixing column and a crimping handle.

[0159] According to an embodiment of the present disclosure, the test tool further comprises: a test tool fixture box. The test tool fixture box is provided with a power button and a power interface.

[0160] Specifically, the connection relationship between the various parts of the test tooling is as follows: the crimping block and the crimping handle are connected by threads, the crimping handle is movably connected to the fixed column, and the fixed column is arranged on the upper side of the upper panel of the test tooling fixture box; the control panel is arranged at the bottom of the test tooling fixture box.

[0161] The probe plate is fixed to the lower side of the upper panel of the test fixture box by screws, with the back side of the probe plate facing upward and the front side facing downward. Figure 9 A schematic diagram of the front of the probe board in a specific embodiment of the present disclosure is shown. The front of the probe board is connected to the control board via the connecting cable. The connecting cable is connected to the cable plug on the front of the probe board. In a specific example, six 40PIN cables are used to connect the probe board to the control board. In addition, Figure 10 A schematic diagram of the back side of a probe board in a specific embodiment of the present disclosure is shown. The probe contact on the back side of the probe board contacts one end of the spring probe, and the other end of the spring probe extends out of the upper panel of the test fixture box so as to contact the contact of the core board to be tested; wherein, the probe board matches the core board to be tested, and different types of core boards to be tested correspond to different probe boards. When the crimping handle is pressed down, the spring probe is compressed, thereby realizing the connection between the probe board and the core board to be tested. When the crimping handle is lifted, the spring probe pops up, thereby disconnecting the probe board from the core board to be tested. Figure 8 That is, when the crimping handle is pressed down, the core board to be tested is connected to the control board through the spring probe, the probe board and the connecting cable in sequence.

[0162] According to an embodiment of the present disclosure, the second connecting device includes an Ethernet port, and the second connecting device is configured to communicatively connect the control board with the host computer and the core board to be tested through the Ethernet port respectively; or, the second connecting device is configured to communicatively connect the control board with the host computer through the Ethernet port, and the first connecting device is configured to communicatively connect the control board with the core board to be tested through a serial port.

[0163] The test fixture of the embodiment of the present disclosure uses a control board to detect the interface signal of the core board, rather than subjective judgment by the operator, thereby eliminating human judgment errors and improving the accuracy of the test.

[0164] In addition, the control board and housing in the test tooling of the disclosed embodiment are all standard, and the number, position, and definition of the cable plugs connected to the control board are also unified. Therefore, the type of probe board determines the type of tooling. The probe board of the disclosed embodiment adopts a modular design, which is convenient for disassembly and replacement. Different types of core boards have different shapes and numbers of interfaces. When replacing different types of core boards, only the appropriate probe board needs to be replaced, and the test tooling can test various types of core boards without the need to repeatedly arrange the tooling, rewiring, and installing the test program. Thus, it can be compatible with multiple types of core boards, saving manufacturing and maintenance costs.

[0165] The test fixture of the disclosed embodiment not only has a testing function but also a burning function. The core board firmware burning function referred to in the disclosed embodiment means that the test fixture can burn a specific firmware program into the core board. This is a function not available in the test fixtures of the prior art, which generally perform burning through the burning fixture. The integration of the testing and burning functions significantly saves hardware costs.

[0166] The condition for the core board to enter the burning mode is to turn the core board's dial switch to the burning mode and then re-power the core board. After the core board enters the burning mode, test the control board in the tooling and then download the firmware program to the core board via the USB cable.

[0167] Specifically, according to an embodiment of the present disclosure, the core board firmware burning function is implemented by the following steps:

[0168] (1) The control board cuts off the power to the core board.

[0169] (2) The core board's dial is connected to the GPIO of the control board. The control board controls the GPIO output so that the high and low levels of the GPIO output are consistent with the core board's burn mode dial, so that the output level meets the conditions of the core board's burn mode.

[0170] (3) The control board supplies power to the core board.

[0171] (4) Connect the burning USB interface of the core board to the USB interface of the control board via a USB cable, and the control board downloads the core board firmware to the core board via the USB cable.

[0172] (5) After the burning is completed, the control board cuts off the power to the core board.

[0173] Figure 11 A flow chart of a test method for a core board according to an embodiment of the present disclosure is shown. The test method is applied to a host computer. The host computer is connected to one or more core boards to be tested via one or more test fixtures, and a first test program is loaded on the host computer. Figure 11 As shown, the testing method includes the following steps S1110 to S1140:

[0174] In step S1110, one or more first configuration files are imported through the first test program; wherein the first configuration file includes description parameters of the test plan and one or more test items, the description parameters include a test plan ID, and the test items include test commands.

[0175] In step S1120, a test scenario set is generated according to the first configuration file by the first test program, where the test scenario IDs of the test scenarios in the test scenario set are different from each other.

[0176] In step S1130 , one or more test fixture instances corresponding to the one or more test fixtures are created through the first test program.

[0177] According to an embodiment of the present disclosure, the host computer is connected to one or more test fixtures via Ethernet, and step S1130 is specifically performed in the following manner:

[0178] Importing a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, the configuration information including a test fixture serial number and a test fixture IP address;

[0179] One or more test jig instances corresponding to the one or more test jigs are created according to the second configuration file; wherein the jig serial number and the test jig IP address of each test jig instance are different from each other.

[0180] In step S1140 , a test operation on the core board to be tested is performed in each test fixture instance.

[0181] Specifically, Figure 12 A flow chart showing a test operation of a core board to be tested according to an embodiment of the present disclosure is shown as follows: Figure 12 As shown, the test operation on the core board to be tested includes the following steps S1142 to S1147:

[0182] In step S1141 , the test solution ID of the core board to be tested connected to the current test fixture is obtained.

[0183] In step S1142, a corresponding test solution is searched in the test solution set according to the test solution ID.

[0184] In step S1143, the test commands in the test items of the found test solution are sent to the current test tool, so that the core board to be tested is tested by the current test tool.

[0185] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes the following steps S1144:

[0186] In step S1144, the serial number ID of the core board to be tested connected to the current test fixture is obtained.

[0187] Specifically, after obtaining the serial number ID of the core board to be tested, it is necessary to save the serial number ID to a local variable so that it can be used in subsequent operations such as generating test record data or other operations. The variable is different for each test fixture instance. For example, for three test fixture instances, the variable can be set to: serial_no1, serial_no2, and serial_no3.

[0188] In a specific example, the host computer is connected to a barcode scanner, and the obtaining of the test scheme ID of the core board to be tested connected to the current test tooling, and the obtaining of the serial number ID of the core board to be tested connected to the current test tooling, include: scanning the serial number QR code of the core board to be tested by the barcode scanner to obtain the test scheme ID of the core board to be tested and the serial number ID of the core board to be tested.

[0189] According to an embodiment of the present disclosure, the test operation on the core board to be tested further includes the following steps S1145-S1146:

[0190] In step S1145, the execution result corresponding to the test command in the test item of the test plan sent by the current test tool is received, and the execution result includes the test result, or the test return data and the test result, and the test result includes the test success and the test failure; the test return data in the execution result is saved, and the final test result is determined according to the test result in the execution result.

[0191] According to an embodiment of the present disclosure, determining a final test result according to the test result in the execution result includes:

[0192] When the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

[0193] In step S1146, after the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data.

[0194] Among them, the test record data includes the serial number ID of the core board to be tested and the final test result, as well as one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

[0195] After a core board to be tested is tested according to step S1141~S1146 as above, step S1141~S1146 can be recycled and tested to next core board to be tested, until all core boards to be tested are tested.When host computer is in parallel with multiple test fixtures, relevant strategy can be defined in test program to ensure that the test scheme ID and / or the sequence number ID of the current core board to be tested scanned can be correctly obtained by corresponding test fixture instance, such as: by scanning the corresponding core board to be tested successively according to the test fixture sequence number, and after the core board to be tested scanned is all completed test, then the strategy of scanning the next batch of corresponding core boards to be tested successively according to the test fixture sequence number, that is: before scanning the corresponding core board to be tested successively according to the test fixture sequence number, ensure that all test fixtures are all completed and then scanned, so in test program, the test scheme ID and / or the sequence number ID of the core board to be tested scanned can be directly preserved according to the test fixture sequence number, without having to make other judgements. Alternatively, by scanning the corresponding core board to be tested in sequence according to the test fixture sequence number in conjunction with the strategy of clearing the variables of its test scheme ID and / or sequence number ID that will be preserved after the current core board to be tested is completed to be tested. That is: without all test fixtures all completing the test and then scanning, it is necessary to combine the operation of clearing the variables that will preserve test scheme ID and / or sequence number ID after the test is completed, after scanning, it is judged that if the variable is empty, the test scheme ID and / or sequence number ID of the core board to be tested scanned is saved in sequence according to the test fixture sequence number. In this way, it is possible to scan and test the next core board to be tested without having to complete the test, thereby improving test efficiency.

[0196] According to an embodiment of the present disclosure, Figure 13 A flow chart of another method for testing a core board according to an embodiment of the present disclosure is shown. Figure 13 As shown, the testing method further includes step S1150:

[0197] The test record data is exported through the first test program and formed into a table file in Excel format.

[0198] Figure 14 A flow chart of another method for testing a core board according to an embodiment of the present disclosure is shown. The test method is applied to a test fixture, which is respectively connected to a host computer and a core board to be tested, and a second test program is loaded on the control board, such as Figure 14 As shown, the testing method includes the following steps S1410 to S1420:

[0199] In step S1410, after establishing a communication connection with the host computer, a test command sent by the host computer is received.

[0200] According to an embodiment of the present disclosure, the test tool includes an Ethernet interface, and the test tool is respectively communicatively connected to the host computer and the core board to be tested via Ethernet, or the test tool is communicatively connected to the core board to be tested via a serial port and is communicatively connected to the host computer via Ethernet.

[0201] According to an embodiment of the present disclosure, the one or more core boards to be tested are loaded with a third test program, and the test commands include: a first type of test command and a second type of test command, the first type of test command is defined as being processed by the test tooling and not forwarded to the core board to be tested, and the second type of test command is defined as being forwarded by the test tooling to the core board to be tested so that the test command is processed by the core board to be tested through the third test program.

[0202] In step S1420, the core board to be tested is tested according to the test command and using the second test program.

[0203] According to an embodiment of the present disclosure, testing the core board to be tested according to the test command and using the second test program includes:

[0204] The type of the test command is determined by the second test program. When the test command is a first type of test command, the test command is forwarded to the core board to be tested, and the execution result of the test command by the core board to be tested is waited for; when the test command is a second type of test command, the test command is processed, and the execution result of the processing of the test command is returned to the host computer; wherein the execution result includes the test result, or the test return data and the test result, and the test result includes test success and test failure.

[0205] While waiting for the execution result of the test command by the core board to be tested, if the waiting times out or the test result received by the core board to be tested for the test command is a test failure, the execution result of the test failure is returned to the host computer; if the test result received by the core board to be tested for the test command is a test success, the execution result of the test success is returned to the host computer; if the test return data of the test command by the core board to be tested is received, the test return data is returned to the host computer.

[0206] Figure 15The present invention discloses a structured flowchart of a test device for a core board according to an embodiment of the present invention. The test device is arranged on a host computer, and the host computer is respectively connected to one or more core boards to be tested by one or more test fixtures. The host computer is loaded with a first test program, and the test device includes: a first configuration file importing module, which is arranged to import one or more first configuration files through the first test program; wherein the first configuration file includes description parameters and one or more test items of the test scheme, the description parameters include a test scheme ID, and the test item includes a test command; a test scheme set generating module, which is arranged to generate a test scheme set according to the first configuration file through the first test program, and the test scheme IDs of the test schemes in the test scheme set are different from each other; a test fixture instance creating module, which is arranged to create one or more test fixture instances corresponding to the one or more test fixtures through the first test program; specifically, the test fixture instance creating module includes a second configuration file importing module and an instance generating module, and the second configuration file importing module is arranged to import a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, and the configuration information includes a test fixture sequence number and a test fixture IP address. The instance generation module is configured to: create one or more test fixture instances corresponding to the one or more test fixtures according to the second configuration file; wherein the fixture serial number and the test fixture IP address of each test fixture instance are different from each other. The test execution module includes: a test scheme ID acquisition module, which is configured to obtain the test scheme ID of the core board to be tested connected to the current test fixture in each test fixture instance; a test scheme search module, which is configured to search for the test scheme corresponding to it in the test scheme set according to the test scheme ID; a test command sending module, which is configured to send the test command in the test item of the found test scheme to the current test fixture, so as to test the core board to be tested through the current test fixture.

[0207] According to an embodiment of the present disclosure, the test execution module further includes: a serial number ID acquisition module for the core board to be tested, which is configured to acquire the serial number ID of the core board to be tested connected to the current test fixture.

[0208] According to an embodiment of the present disclosure, the test execution module also includes: a test command execution result processing module, which is configured to receive the execution result corresponding to the test command in the test item of the test scheme sent by the current test tooling, the execution result including the test result, or the test return data and the test result, the test result including test success and test failure; save the test return data in the execution result, and determine the final test result based on the test result in the execution result. A test record data generation module, which is configured to generate the test record data of the core board to be tested based on the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data after the test of the core board to be tested is completed; wherein the test record data includes the serial number ID of the core board to be tested and the final test result, as well as one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

[0209] According to an embodiment of the present disclosure, the testing device further includes: a test record data exporting module configured to export the test record data through the first test program and form a spreadsheet file in an Excel format.

[0210] According to the technical solution provided by the embodiment of the present disclosure, by defining a plurality of test schemes configured for different types of core boards in a configuration file, and importing the test scheme defined by the configuration file into the test system when the test program is started, when the core board to be tested is tested, the corresponding test scheme is found according to the test scheme ID bound to the core board to be tested, and the core board to be tested is tested using the test scheme, and the test process is automatically carried out according to the test scheme content, on the one hand, owing to avoiding manual operation in the test process, thereby improving the accuracy of the test, on the other hand, realizing that the test program does not need to be modified and only a strategy of executing multiple test schemes through a test program can be used to test the core board to be tested of different types or the same type using different schemes for the technical purpose, thereby improving the reusability of the test program. In addition, the user can add, delete, modify the relevant content of the test scheme in the description file as needed, thereby improving the flexibility and scalability of the test software.

[0211] Figure 16 FIG. 1 shows a structural block diagram of an electronic device according to an embodiment of the present disclosure. Figure 16 As shown, the electronic device includes a memory and a processor; wherein, the memory is used to store one or more computer instructions, wherein, the one or more computer instructions are executed by the processor to implement the method steps described in any one of the above method embodiments.

[0212] The present disclosure also provides a computer-readable storage medium, which can be included in the electronic device or computer system described in the above embodiments, or can be a standalone computer-readable storage medium not incorporated into the device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to execute the methods described in the present disclosure.

[0213] The present disclosure also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the steps of any method described in the present disclosure are implemented.

[0214] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the invention herein is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also encompasses other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the inventive concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

Claims

1. A test system for a core board, characterized in that, The test system includes: a host computer and a test fixture; the host computer is loaded with a first test program, the test fixture includes a control board, and the control board is loaded with a second test program; the host computer is connected to one or more core boards to be tested through one or more test fixtures; When the first test program is started, the host computer imports one or more first configuration files through the first test program; wherein the first configuration files are used to define specific content of the test plan, and the first configuration files include description parameters of the test plan and one or more test items, the description parameters include a test plan ID, and the test items include test commands; The host computer generates a test solution set according to the first configuration file using the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other; The host computer creates one or more test fixture instances corresponding to the one or more test fixtures through the first test program, wherein each test fixture instance performs a test operation on its corresponding core board to be tested independently and in parallel; Execute a test operation on the core board to be tested in each test tool instance, wherein the test operation on the core board to be tested includes: obtaining a test scheme ID of the core board to be tested connected to the current test tool; searching for a test scheme corresponding to the test scheme ID in the test scheme set; and sending a test command in a test item of the found test scheme to the current test tool so as to test the core board to be tested by the current test tool; The test tool is configured to receive a test command sent by the host computer through the control board after establishing a communication connection with the host computer, and test the core board to be tested according to the test command and using the second test program.

2. The test system according to claim 1, wherein: The host computer is respectively connected to one or more test fixtures for communication via Ethernet; The creating one or more test fixture instances corresponding to the one or more test fixtures includes: The host computer imports a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, and the configuration information includes a test fixture serial number and a test fixture IP address; One or more test jig instances corresponding to the one or more test jigs are created according to the second configuration file; wherein the jig serial number and the test jig IP address of each test jig instance are different from each other.

3. The test system according to claim 1, wherein: The test operation of the core board to be tested also includes: Obtain the serial number ID of the core board to be tested connected to the current test fixture.

4. The test system according to claim 3, characterized in that: The host computer is connected to the barcode scanner, and the test scheme ID of the core board to be tested connected to the current test fixture is obtained, and the serial number ID of the core board to be tested connected to the current test fixture is obtained, including: The serial number QR code of the core board to be tested is scanned by the barcode scanner to obtain the test solution ID of the core board to be tested and the serial number ID of the core board to be tested.

5. The test system according to claim 3, characterized in that: The test operation of the core board to be tested also includes: The host computer receives an execution result corresponding to a test command in a test item of the test plan, sent by the current test tool, wherein the execution result includes a test result, or test return data and a test result, and the test result includes a test success and a test failure; Saving the test return data in the execution result, and determining the final test result according to the test result in the execution result; After the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

6. The test system according to claim 5, characterized in that: Determining the final test result according to the test result in the execution result includes: When the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

7. The test system according to claim 5, characterized in that: The test system further comprises: The host computer exports the test record data through the first test program and forms a table file in Excel format.

8. The test system according to claim 1, wherein: The test command includes one or more of the following parameters: a test command character string, input parameters of the test command, a matching rule of a test command return result, a test command return result, and a content description of the test command; The description parameters also include one or more of the following: test plan name, test plan description information and operator information.

9. The test system according to claim 1, wherein: The test fixture is respectively connected to the host computer and the core board to be tested via Ethernet for communication, or the test fixture is connected to the core board to be tested via a serial port for communication and is connected to the host computer via Ethernet.

10. The test system according to claim 1, wherein: The one or more core boards to be tested are communicated with a third test program, and the test commands include: a first type of test command and a second type of test command, wherein the first type of test command is defined as being processed by the test tool and not forwarded to the core board to be tested, and the second type of test command is defined as being forwarded to the core board to be tested by the test tool, so that the test command is processed by the core board to be tested through the third test program; The step of testing the core board to be tested according to the test command and using the second test program includes: Determine the type of the test command by the second test program; when the test command is a first type test command, forward the test command to the core board to be tested, and wait for the execution result of the test command by the core board to be tested; when the test command is a second type test command, process the test command, and return the execution result of the test command to the host computer; wherein the execution result includes the test result, or the test return data and the test result, and the test result includes a test success and a test failure; While waiting for the execution result of the test command by the core board to be tested, if the waiting times out or the test result received by the core board to be tested for the test command is a test failure, the execution result of the test failure is returned to the host computer; if the test result received by the core board to be tested for the test command is a test success, the execution result of the test success is returned to the host computer; if the test return data of the test command by the core board to be tested is received, the test return data is returned to the host computer.

11. The test system according to claim 1, wherein: The test fixture also includes: a connecting device and a core board fixing device; The connecting device includes a first connecting device and a second connecting device; the first connecting device is configured to connect the control board to the core board to be tested for communication; the second connecting device is configured to connect the control board to the host computer for communication; The core board fixing device is configured to fix the core board to be tested on the first connecting device, so that the core board to be tested is communicatively connected to the control board through the first connecting device.

12. The test system according to claim 11, characterized in that: The first connecting device includes a connecting cable, a probe board and a spring probe; the core board fixing device includes a crimping block, a fixing column and a crimping handle; The test fixture further comprises: a test fixture box; The crimping block and the crimping handle are connected by threads, the crimping handle is movably connected to the fixing column, and the fixing column is arranged on the upper side of the upper panel of the test fixture box; The control board is arranged at the bottom of the test fixture box, and the probe board is fixed to the lower side of the upper panel of the test fixture box by screws, with the back of the probe board facing upward and the front facing downward, wherein the front of the probe board is connected to the control board through the connecting cable, and the probe contact on the back of the probe board contacts one end of the spring probe, and the other end of the spring probe extends out of the upper panel of the test fixture box so as to contact the contact of the core board to be tested; wherein, the probe board matches the core board to be tested, and different types of core boards to be tested correspond to different probe boards, and when the crimping handle is pressed down, the spring probe is compressed, thereby realizing the connection between the probe board and the core board to be tested, and when the crimping handle is lifted, the spring probe pops up, thereby disconnecting the probe board from the core board to be tested.

13. The test system according to claim 11, wherein: The second connection device includes an Ethernet port, and the second connection device is configured to connect the control board to the host computer and the core board to be tested through the Ethernet port for communication; Alternatively, the second connection device is configured to connect the control board to the host computer for communication via the Ethernet port, and the first connection device is configured to connect the control board to the core board to be tested for communication via a serial port.

14. A testing method for a core board, applied to a host computer, characterized in that: The host computer is respectively connected to one or more core boards to be tested via one or more test fixtures, and a first test program is loaded on the host computer. The test method includes: When the first test program is started, one or more first configuration files are imported through the first test program; wherein the first configuration files are used to define specific content of the test plan, and the first configuration files include description parameters of the test plan and one or more test items, the description parameters include a test plan ID, and the test items include test commands; generating a test solution set according to the first configuration file by the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other; Creating one or more test fixture instances corresponding to the one or more test fixtures through the first test program, wherein each test fixture instance independently and in parallel performs a test operation on the corresponding core board to be tested; A test operation on the core board to be tested is performed in each test tool instance, and the test operation on the core board to be tested includes: obtaining the test scheme ID of the core board to be tested connected to the current test tool; searching for the corresponding test scheme in the test scheme set according to the test scheme ID; and sending the test commands in the test items of the found test scheme to the current test tool, so that the core board to be tested is tested by the current test tool.

15. The testing method according to claim 14, characterized in that: The host computer is respectively connected to one or more test fixtures via Ethernet for communication, and the creating of one or more test fixture instances corresponding to the one or more test fixtures includes: Importing a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, the configuration information including a test fixture serial number and a test fixture IP address; One or more test jig instances corresponding to the one or more test jigs are created according to the second configuration file; wherein the jig serial number and the test jig IP address of each test jig instance are different from each other.

16. The testing method according to claim 14, characterized in that: The test operation on the core board to be tested also includes: Obtain the serial number ID of the core board to be tested connected to the current test fixture.

17. The testing method according to claim 16, characterized in that: The host computer is connected to the barcode scanner, and the test scheme ID of the core board to be tested connected to the current test fixture is obtained, and the serial number ID of the core board to be tested connected to the current test fixture is obtained, including: The serial number QR code of the core board to be tested is scanned by the barcode scanner to obtain the test solution ID of the core board to be tested and the serial number ID of the core board to be tested.

18. The testing method according to claim 16, characterized in that: The test operation on the core board to be tested also includes: Receive an execution result corresponding to a test command in a test item of the test plan sent by the current test tool, wherein the execution result includes a test result, or test return data and a test result, wherein the test result includes a test success and a test failure; Saving the test return data in the execution result, and determining the final test result according to the test result in the execution result; After the test of the core board to be tested is completed, the test record data of the core board to be tested is generated according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

19. The testing method according to claim 18, characterized in that: Determining the final test result according to the test result in the execution result includes: When the test results corresponding to all the test commands in the test items of the test scheme are all test successes, the final test result is test success; when the test result corresponding to any test command in the test items of the test scheme is test failure, the test of the core board to be tested is ended, and the final test result is test failure.

20. The testing method according to claim 18, wherein: The test method further comprises: The test record data is exported through the first test program and formed into a spreadsheet file in Excel format.

21. A testing device for a core board, provided on a host computer, characterized in that: The host computer is respectively connected to one or more core boards to be tested via one or more test fixtures, the host computer is loaded with a first test program, and the test device includes: a first configuration file importing module configured to import one or more first configuration files through the first test program when the first test program is started; wherein the first configuration files are used to define specific content of a test plan, the first configuration files including description parameters of the test plan and one or more test items, the description parameters including a test plan ID, and the test items including test commands; a test solution set generating module, configured to generate a test solution set according to the first configuration file using the first test program, wherein the test solution IDs of the test solutions in the test solution set are different from each other; A test fixture instance creation module is configured to create one or more test fixture instances corresponding to the one or more test fixtures through the first test program, wherein each test fixture instance performs a test operation on its corresponding core board to be tested independently and in parallel; A test execution module, the test execution module includes: a test scheme ID acquisition module, which is configured to obtain the test scheme ID of the core board to be tested connected to the current test tool in each test tool instance; a test scheme search module, which is configured to search for the test scheme corresponding to it in the test scheme set according to the test scheme ID; a test command sending module, which is configured to send the test commands in the test items of the found test scheme to the current test tool, so that the core board to be tested is tested by the current test tool.

22. The testing device according to claim 21, characterized in that The test fixture instance creation module includes: A second configuration file importing module is configured to import a second configuration file through the first test program; wherein the second configuration file includes configuration information of the one or more test fixtures, and the configuration information includes a test fixture serial number and a test fixture IP address; The instance generation module is configured to create one or more test tool instances corresponding to the one or more test tools according to the second configuration file; wherein the tool serial number and test tool IP address of each test tool instance are different from each other.

23. The testing device according to claim 21, characterized in that The test execution module also includes: The module for obtaining the serial number ID of the core board to be tested is configured to obtain the serial number ID of the core board to be tested connected to the current test fixture.

24. The testing device according to claim 23, characterized in that The test execution module also includes: a test command execution result processing module configured to receive an execution result corresponding to a test command in a test item of the test scheme sent by the current test tool, the execution result including a test result, or test return data and a test result, the test result including a test success and a test failure; save the test return data in the execution result, and determine a final test result based on the test result in the execution result; A test record data generation module is configured to generate test record data of the core board to be tested according to the serial number ID of the core board to be tested and the final test result, or the serial number ID of the core board to be tested and the final test result and the test return data after the test of the core board to be tested is completed; wherein, the test record data includes the serial number ID of the core board to be tested and the final test result, and one or more of the following: batch number, product model, ESAM serial number, encryption serial number, software version, hardware version, MAC address, IP address, box number and operation time.

25. The testing device according to claim 24, characterized in that The testing device further comprises: The test record data export module is configured to export the test record data through the first test program and form a table file in Excel format.

26. An electronic device, characterized in that: The device comprises a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the testing method according to any one of claims 14 to 20.

27. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by a processor, the testing method according to any one of claims 14 to 20 is implemented.

28. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the testing method according to any one of claims 14 to 20 is implemented.

Images