Embedded board testing method, device, computer equipment and storage medium

The method addresses inefficiencies in embedded board card testing by automating the execution of test scripts across multiple interfaces, improving testing speed and efficiency by utilizing updated code to perform comprehensive driver interface tests on embedded board cards.

CN118093295BActive Publication Date: 2025-03-25GUANGZHOU YIHUI INFORMATION TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202311708349.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-12-13
Publication Date
2025-03-25
Estimated Expiration
2043-12-13

AI Technical Summary

Technical Problem

Current embedded board card testing methods are inefficient due to the lack of unified hardware and performance testing frameworks, leading to reduced testing speed when multiple board cards are tested individually.

Method used

A method that detects code updates in a repository, deploys the updated code to a test board card, connects it to a pre-configured test framework, and executes predefined test scripts across multiple interfaces to obtain comprehensive test results, thereby improving testing efficiency by combining driver interface tests.

Benefits of technology

This approach enhances testing efficiency by automating the execution of test scripts across multiple interfaces, reducing the time required for testing multiple board cards and improving the detection of driver-related issues.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118093295B_ABST
    Figure CN118093295B_ABST
Patent Text Reader

Abstract

The present application relates to an embedded board test method, device, computer equipment and storage medium. When code update information is detected in a code warehouse, the updated code is obtained from the code warehouse, and the updated code is deployed to a test board. The test board is connected to each drive interface of a preset test frame. The test board executes each drive test combination in a preset test script based on the updated code and each drive interface, obtains each drive test result of each drive test combination through each drive interface, and obtains the test result of the test board according to each drive test result. Compared with the traditional method of only testing each interface of each board one by one, this solution connects each drive interface of the test board to the test frame, and when a code update is detected, the drive test item combination of each interface in the test board is automatically executed using the updated code, so as to realize the combined test of each board drive interface and improve the test efficiency of the test board.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of testing technology, and in particular to an embedded board testing method, device, computer equipment, storage medium and computer program product. Background Art

[0002] With the development of computer technology, embedded development has become the mainstream development method in the computer field. In the process of embedded board development, embedded boards need to be tested. In a system, there are many embedded boards, and currently embedded boards are usually tested one by one. However, the parameters such as hardware and performance test framework of different boards are not unified. When testing each interface of multiple boards one by one, the test efficiency will be reduced.

[0003] Therefore, the current embedded board testing method has the defect of low testing efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide an embedded board testing method, device, computer equipment, computer readable storage medium and computer program product that can improve testing efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides an embedded board testing method, the method comprising:

[0006] Detecting code update information in a code repository, and obtaining updated code from the code repository;

[0007] Determine the corresponding test board according to the code update information, and deploy the updated code to the test board; connect the test board to each drive interface of the preset test frame; the test board is used to execute each drive test item combination in the preset test script according to the updated code and each drive interface in the preset test frame;

[0008] The driving test results of the driving test item combinations are obtained through the driving interfaces, and the test results of the test board are obtained according to the driving test results.

[0009] In one embodiment, determining the corresponding test board according to the code update information includes:

[0010] Obtaining program firmware information corresponding to the code update information;

[0011] The corresponding board information is determined according to the program firmware information, and the test board corresponding to the code update information is obtained according to the board information.

[0012] In one embodiment, deploying the updated code to the test board includes:

[0013] Compiling the updated code to obtain compiled code;

[0014] The compiled code is deployed to the test board through a file transfer protocol.

[0015] In one embodiment, deploying the updated code to the test board includes:

[0016] Deploy the updated code to the test board, and after the test board is restarted, determine the drive interface test items and drive function test items to be tested corresponding to each drive interface according to each drive interface connected between the test board and the test frame, and obtain each drive test item combination according to each drive interface test item and each drive function test item;

[0017] Execute each of the drive interface test items and each of the drive function test items to obtain each drive test result.

[0018] In one embodiment, obtaining the test result of the test board according to the drive test results includes:

[0019] For each driving test result, if the driving test result is detected to be abnormal, determining an associated driving test item combination of the driving test item combination corresponding to the driving test result; the associated driving test item combination indicates that there is at least one driving test item combination with the driving test item combination corresponding to the driving test result that has the same driving test item;

[0020] Obtaining an associated drive test result corresponding to the associated drive test item combination;

[0021] When it is detected that the associated drive test result is abnormal, it is determined that the test result of the test board is that a drive test item combination corresponding to the drive test result and the same drive test item in the associated drive test item combination are abnormal.

[0022] In one embodiment, after deploying the updated code to the test board, the method further includes:

[0023] If it is detected that the test time of the test board for the drive test item combination is greater than a preset threshold, the test of the test board is stopped.

[0024] In a second aspect, the present application provides an embedded board testing device, the device comprising:

[0025] An acquisition module, used to detect code update information in a code repository and acquire updated code from the code repository;

[0026] A test module is used to determine the corresponding test board according to the code update information, and deploy the updated code to the test board; the test board is connected to each drive interface of the preset test frame; the test board is used to execute each drive test item combination in the preset test script according to the updated code and each drive interface in the preset test frame;

[0027] The determination module is used to obtain each drive test result of each drive test item combination through each drive interface, and obtain the test result of the test board according to each drive test result.

[0028] In a third aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0029] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0030] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0031] The above-mentioned embedded board test method, device, computer equipment, storage medium and computer program product, when detecting code update information in the code warehouse, obtain the updated code from the code warehouse, deploy the updated code to the test board, the test board is connected to each drive interface of the preset test frame, the test board executes each drive test combination in the preset test script based on the updated code and each drive interface, obtains each drive test result of each drive test combination through each drive interface, and obtains the test result of the test board according to each drive test result. Compared with the traditional method of only testing each interface of each board one by one, this scheme connects each drive interface of the test board with the test frame, and when detecting a code update, uses the updated code to automatically execute the drive test item combination of each interface in the test board, so as to realize the combined test of each board drive interface and improve the test efficiency of the test board. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An application environment diagram of an embedded board test method in an embodiment;

[0033] Figure 2A schematic diagram of a flow chart of an embedded board testing method in one embodiment;

[0034] Figure 3 A schematic diagram of a flow chart of an embedded board testing method in another embodiment;

[0035] Figure 4 A structural block diagram of an embedded board test device in one embodiment;

[0036] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] The embedded board test method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the test board communicates with the server through the network, and the test board is connected to the test frame through a corresponding type of drive interface. The data storage system can store the data that the server needs to process. The data storage system can be integrated on the server, or it can be placed on the cloud or other network servers. When the server detects a code update, the updated code can be deployed to the test board, so that the test board can execute the corresponding test script in conjunction with the corresponding test frame, test each drive interface, and the server can obtain the test results corresponding to the test board and analyze the test results. Among them, the server can be implemented with an independent server or a server cluster consisting of multiple servers.

[0039] In one embodiment, Figure 2 As shown, a method for testing an embedded board is provided. Figure 1 The server in the example is used to illustrate the following steps:

[0040] Step S202: Detect code update information in the code repository, and obtain updated code from the code repository.

[0041] Among them, the server may include a code management server, in which a code management repository, also called a code repository, is deployed, so that developers can submit iterative updated code to the above code management repository. The server can be a Gitlab Runner server, specifically a CI (Continuous Integration) / CD (Continuous Delivery / Deployment) compilation and deployment server. CI refers to the automatic integration of changed code into the code repository, and the verification and construction of the code through automated testing, compilation, and building processes, so as to quickly discover and resolve code problems. CI helps to speed up the speed and quality of code delivery and improve the collaboration efficiency of the development team. CD refers to the automatic deployment of CI-verified code to the corresponding test board to achieve faster delivery and response to needs.

[0042] After the server detects the code update information in the code repository, it can obtain the updated code from the code repository, so that the server can test the test board of the embedded system based on the updated code.

[0043] Step S204, determine the corresponding test board according to the code update information, and deploy the updated code to the test board; connect the test board to each driver interface of the preset test frame; the test board is used to execute each driver test item combination in the preset test script according to the updated code and each driver interface in the preset test frame.

[0044] The code update information may include relevant information of the updated code, such as the location of the updated code, the content of the updated code, and the program firmware information to which the updated code belongs. Since the embedded system may include a variety of hardware, there may be a variety of test boards. The server may determine the corresponding test board according to the code update information, thereby determining the board that needs to be retested.

[0045] Among them, since the above-mentioned test board can include multiple types, when determining the corresponding test board, the server can first obtain the program firmware information corresponding to the code update information. Among them, the program firmware information represents the information of the program firmware to which the changed code belongs, and the program firmware information can be installed on the corresponding board, so the program firmware information can correspond to the board information one by one, and the server can determine the corresponding board information based on the program firmware information, wherein the board information can include the number, model and type of the embedded board, and the server can obtain the test board corresponding to the code update information according to the board information.

[0046] After the code in the above code warehouse is updated, the server can start the process of retesting the above determined test board. After the server determines the corresponding test board, the updated code can be deployed to the above test board. Among them, the above test board can be connected to the corresponding test frame, and a plurality of drive interfaces are provided in the test frame. Corresponding to the plurality of drive interfaces on the test board, the plurality of drive interfaces in the test board can be connected to the plurality of drive interfaces in the preset test frame, and one test frame can be connected to one test board. The test board is pre-deployed with a corresponding preset test script, and the preset test script can include a variety of test schemes for the above test board, which can include tests for the drive interface and tests for the drive function. After the server deploys the above updated code to the test board, the test board can execute each combination of drive test items in the above preset test script. Among them, the drive test item can be a test for a certain drive interface or a certain drive function. Since the operation of each drive interface and drive function requires other interfaces or functions to work together, the preset test script can include a combination of drive test items consisting of multiple drive test items. Among them, each driver test item combination includes at least two driver test items that have an operation dependency relationship. For example, a certain function of the test board requires the coordinated implementation of two driver test items A and B, and a certain function requires the coordinated implementation of two driver test items B and C. The server can set A and B as a driver test item combination, and set B and C as a driver test item combination, so that the test board can test the above-mentioned driver test item combinations in combination with the updated code and the preset driver interfaces in the test frame when executing the above-mentioned preset test script.

[0047] Step S206, obtaining each driving test result of each driving test item combination through each driving interface, and obtaining the test result of the test board according to each driving test result.

[0048] Wherein, each drive interface of the above-mentioned test frame can be connected to the server, and the test board executes the preset test script, and after testing each drive test item combination, the corresponding drive test result can be generated, and the server can obtain each drive test result corresponding to each drive test item combination through the above-mentioned drive interface. Wherein, the server can also be a test server, and the server can monitor the test process of the above-mentioned test board in real time through the drive interface in the test frame, and can also realize functions such as result collection and abnormality detection. After the server obtains the above-mentioned drive test results, the test results of the test board can be obtained according to each drive test result.

[0049] Among them, the same drive test items may exist in each drive test item combination corresponding to the above-mentioned drive test results. When a drive test result is abnormal, since its corresponding drive test item combination contains multiple drive test items, the server can combine multiple drive test results corresponding to multiple drive test item combinations containing at least one identical drive test item to determine whether the above-mentioned identical drive test item has an abnormality, and then obtain the test result of the test board.

[0050] In addition, in some embodiments, the server can also collect and organize the above test results after all tests are completed, and package them and send them to the terminal data processing system of the administrator. The terminal data processing system can analyze the received test results, form a test report, and send the report and the program firmware used to test the above test board to the software developer, for example, by email. Thereby, the developer can further analyze the test board based on the above test report and program firmware to confirm whether there is a problem with the above updated code. Among them, the server directly packages the firmware and the corresponding test report and sends it to the developer, omitting the process of manually relying on code compilation, packaging and testing when the product version is released, thereby improving the test efficiency.

[0051] In the above-mentioned embedded board test method, when code update information is detected in the code warehouse, the updated code is obtained from the code warehouse, the updated code is deployed to the test board, the test board is connected to each drive interface of the preset test frame, the test board executes each drive test combination in the preset test script based on the updated code and each drive interface, obtains each drive test result of each drive test combination through each drive interface, and obtains the test result of the test board according to each drive test result. Compared with the traditional method of only testing each interface of each board one by one, this scheme connects each drive interface of the test board with the test frame, and when a code update is detected, automatically executes the drive test item combination of each interface in the test board using the updated code, realizes the combined test of each board drive interface, and improves the test efficiency of the test board.

[0052] In one embodiment, deploying the updated code to the test board includes: compiling the updated code to obtain compiled code; and deploying the compiled code to the test board through a file transfer protocol.

[0053] In this embodiment, after the server obtains the updated code from the code repository, the updated code can be deployed to the corresponding test board. For example, after obtaining the above-mentioned updated code, the server can compile the above-mentioned updated code to obtain the compiled code. Among them, after the above-mentioned updated code is compiled, it can become an executable state. In addition, the server can deploy the compiled code to the test board through a preset protocol. Specifically, the above-mentioned preset protocol can be an FTP (File Transfer Protocol) protocol, and the above-mentioned server can be a GitLab Runner server, that is, the GitLab Runner server can pull the latest code, compile the code, and then deploy the above-mentioned compiled code to the test board through the file transfer protocol.

[0054] Through this embodiment, the server can automatically pull the latest code and compile it after the code is changed, and then deploy it to the test board, so that the test board can start the corresponding test process, thereby improving the test efficiency of the test board in the embedded system.

[0055] In one embodiment, the updated code is deployed to the test board, including: deploying the updated code to the test board, and after the test board is restarted, determining each drive interface test item and each drive function test item to be tested corresponding to each drive interface according to each drive interface connected to the test frame by the test board, and obtaining each drive test item combination according to each drive interface test item and each drive function test item; executing each drive interface test item and each drive function test item to obtain each drive test result.

[0056] In the present embodiment, the above-mentioned server can deploy the updated code to the test board, and the test board can restart the test board after the updated code deployment is completed, and start the corresponding test process. Wherein, the above-mentioned test board can be connected to multiple drive interfaces in the test frame, and each drive interface can have a corresponding interface type and interface function, and the test board can perform corresponding tests on each drive interface connected to the test frame. For example, the test board can obtain the interface information of each drive interface connected to the test frame, and then the test board can determine the corresponding drive interface test items and each drive function test items to be tested according to the above-mentioned drive interfaces. Wherein, the drive interface test item can be a test for the data transmission capability of the drive interface, such as whether the corresponding type of data can be transmitted normally; the drive function test item can be a test for the drive function that can be realized by the drive interface, such as whether a function of the above-mentioned drive interface that needs to be used in the test board can operate normally.

[0057] The test board can obtain multiple drive test item combinations based on the above drive interface test items and drive function test items. The test board can execute the drive interface test items and drive function test items in the above drive test item combinations according to the preset test script to obtain the drive test results of each drive interface.

[0058] Specifically, the server can unify the drive interface through the test frame, that is, the commonly used drive bus type interface can be uniformly set in the test frame. Among them, the interfaces set on the above test frame include but are not limited to uart (Universal Asynchronous Receiver / Transmitter), can (Controller Area Network, Controller Area Network Bus) and network interfaces. The above test frame can be fixed as a docking carrier for board test, and different test boards can connect their own drive interfaces with the corresponding drive interfaces in the test frame, so that the test board can perform various tests on the drive interface by calling the corresponding drive interface in the test frame during the execution of the preset test script. In addition, the server can also be connected to the test frame through the above drive interface, thereby realizing the monitoring of the drive test process and the collection of test results. Among them, the server can be connected to multiple test frames, and multiple test frames can be connected to corresponding test boards respectively, so that the server can perform concurrent tests on multiple test boards in the embedded system at the same time, so as to locate abnormalities or obtain uniform performance test results of the test boards by comparing the test results of each test board in parallel.

[0059] Through this embodiment, the server can combine the test frame and the various drive interfaces contained in the test board to determine the drive interfaces and corresponding drive functions that need to be tested, so that the test board can automatically execute the test process based on the above-mentioned drive test items that need to be tested, thereby improving the test efficiency of the test board in the embedded system.

[0060] In one embodiment, a test result of a test board is obtained according to each drive test result, including: for each drive test result, if the drive test result is detected to be abnormal, determining an associated drive test item combination of the drive test item combination corresponding to the drive test result; the associated drive test item combination represents that there is at least one drive test item combination with the drive test item combination corresponding to the drive test result that has the same drive test item; obtaining an associated drive test result corresponding to the associated drive test item combination; and when the associated drive test result is detected to be abnormal, determining that the test result of the test board is that there is an abnormality between the drive test item combination corresponding to the drive test result and the same drive test item in the associated drive test item combination.

[0061] In this embodiment, the above-mentioned drive test item combination may include multiple combinations, such as at least one drive interface test item and at least one drive function test item, at least two drive interface test items, and at least two drive function test items. The test board performs tests based on each drive test item combination to obtain corresponding drive test results. The server can obtain multiple drive test results corresponding to multiple drive test item combinations.

[0062] The server can determine the test results of the test board based on multiple drive test results, for example, determine which drive test items are abnormal and other information. Wherein, the drive test items in each drive test item combination can be the same or different. For each drive test result, if the server detects that the drive test result is abnormal, the server can determine the drive test item combination corresponding to the drive test result, and the associated drive test item combination corresponding to the drive test item combination. Wherein, the above-mentioned associated drive test item combination indicates that there is at least one drive test item combination with the same drive test item in the drive test item combination corresponding to the drive test result. For example, the above-mentioned drive test item combination includes drive test item A and drive test item B, and another drive test item combination includes drive test item B and drive test item C, then the drive test item combination belongs to the associated drive test item combination of the drive test item combination including A and B. Wherein, there can be at least one associated drive test item combination corresponding to the above-mentioned drive test combination.

[0063] The server can obtain the associated drive test result corresponding to the above-mentioned associated drive test item combination, and detect whether it is abnormal. If the server detects that the above-mentioned associated drive test result is abnormal, the server can determine that the test result of the test board is that the drive test item combination corresponding to the drive test result and the same drive test item in the associated drive test item combination are abnormal. For example, the drive test item combination includes items A and B, and the drive test result is abnormal; the associated drive test item combination includes items B and C, and the associated drive test result is abnormal, then the server can determine that the above-mentioned drive test item B is abnormal.

[0064] Through this embodiment, the server can perform concurrent tests of multiple different combinations on the test board, and thus determine the deep-seated driver problems in the test board by comparing the results of each combination, thereby improving the test efficiency of the test board in the embedded system.

[0065] In one embodiment, after the updated code is deployed to the test board, the method further includes: if it is detected that the test time of the test board for the driver test item combination is greater than a preset threshold, stopping the test board.

[0066] In this embodiment, the above-mentioned server can perform real-time monitoring during the testing process of the test board. The server can monitor the test time of each driver test item combination during the testing of the above-mentioned test board. If the server detects that the test time of the test board on the above-mentioned driver test item combination is greater than a preset threshold, the server can determine that the test of the driver test item combination by the test board has timed out and there is an abnormality in the test board. Then the server can stop testing the above-mentioned test board and continue the test process of other test boards.

[0067] Through this embodiment, the server can monitor the test process of the above-mentioned test board in real time, and actively stop the test process of the timed-out test board when a test timeout is detected, thereby improving the test efficiency of the test board in the embedded system.

[0068] In one embodiment, Figure 3 As shown, Figure 3 The flowchart of the embedded board test method in another embodiment is shown in FIG. In this embodiment, the server may be a GitLab CI / CD Runner server, which is connected to a plurality of test boards and a test rack, wherein each test board is connected to a corresponding test rack via a hardware driver interface; the server may also be a test server, which may monitor the test process of each test board in real time.

[0069] Among them, when the server detects that the developer has submitted changes to the code of a code repository, it can obtain the updated code from the code repository, compile and deploy it to the test board; after the test board is deployed, it can restart and automatically execute the corresponding test script to execute all driver tests in the test plan, such as testing the corresponding combinations of driver test items. Among them, the above-mentioned test frame is uniformly provided with commonly used driver bus interface tests. The test frame is fixed as a docking carrier for board testing, and different boards only need to connect their own interfaces. The above-mentioned test server is responsible for monitoring the drive test process and results, and collecting the data and passing it to the next system for processing. For example, the test board can upload the test results of each test to the server and execute the next test.

[0070] When all tests are completed, the server can collect and organize the test data, and package it and send it to the terminal data processing system. The terminal data processing system can analyze all the data and form a corresponding test report. Then, the report and the program firmware corresponding to the above-mentioned updated code can be sent to the developer, so that the developer can analyze based on the test report to confirm whether there are any problems with the updated code.

[0071] Through the above-mentioned embodiments, the server can connect each drive interface of the test board to the test frame, and when a code update is detected, the server can automatically execute the drive test item combination of each interface in the test board using the updated code, thereby realizing the combined test of each board drive interface and improving the test efficiency of the test board. In addition, by combining each drive test item, the test scheme is flexible and the combination is diverse and comprehensive, thereby improving the efficiency of discovering deep problems; through the test frame, the general hardware communication test interface is unified, so that different test boards can be reused, and through multi-board concurrent testing, the total test time is reduced and the test efficiency is improved. In addition, by collecting the test results and forming a test report through the server, the drive performance test of the test board can be intuitively evaluated through multiple dimensions.

[0072] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0073] Based on the same inventive concept, the embodiment of the present application also provides an embedded board test device for implementing the embedded board test method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more embedded board test device embodiments provided below can refer to the limitations of the embedded board test method above, and will not be repeated here.

[0074] In one embodiment, Figure 4 As shown, an embedded board test device is provided, including: an acquisition module 500, a test module 502 and a determination module 504, wherein:

[0075] The acquisition module 500 is used to detect code update information in the code repository and acquire updated code from the code repository.

[0076] The test module 502 is used to determine the corresponding test board according to the code update information and deploy the updated code to the test board; the test board is connected to each driver interface of the preset test frame; the test board is used to execute each driver test item combination in the preset test script according to the updated code and each driver interface in the preset test frame.

[0077] The determination module 504 is used to obtain each driving test result of each driving test item combination through each driving interface, and obtain the test result of the test board according to each driving test result.

[0078] In one embodiment, the test module 502 is used to obtain program firmware information corresponding to the code update information; determine corresponding board information according to the program firmware information, and obtain a test board corresponding to the code update information according to the board information.

[0079] In one embodiment, the test module 502 is used to compile the updated code to obtain the compiled code; and deploy the compiled code to the test board through the file transfer protocol.

[0080] In one embodiment, the above-mentioned test module 502 is used to test a board, including: deploying the updated code to the test board, and after the test board is restarted, determining each drive interface test item and each drive function test item to be tested corresponding to each drive interface according to each drive interface connected to the test frame, and obtaining each drive test item combination according to each drive interface test item and each drive function test item; executing each drive interface test item and each drive function test item to obtain each drive test result.

[0081] In one embodiment, the above-mentioned determination module 504 is used to determine, for each drive test result, an associated drive test item combination of the drive test item combination corresponding to the drive test result if the drive test result is detected to be abnormal; the associated drive test item combination represents that there is at least one drive test item combination with the drive test item combination corresponding to the drive test result that has the same drive test item; obtain an associated drive test result corresponding to the associated drive test item combination; and when the associated drive test result is detected to be abnormal, determine that the test result of the test board is that there is an abnormality between the drive test item combination corresponding to the drive test result and the same drive test item in the associated drive test item combination.

[0082] In one embodiment, the apparatus further includes: a monitoring module, configured to stop testing the test board if it is detected that the test time of the test board for the drive test item combination is greater than a preset threshold.

[0083] Each module in the above-mentioned embedded board test device can be implemented in whole or in part by software, hardware and their combination. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0084] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as code data and test results. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an embedded board test method is implemented.

[0085] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0086] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the above-mentioned embedded board test method when executing the computer program.

[0087] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned embedded board test method is implemented.

[0088] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the above-mentioned embedded board test method is implemented.

[0089] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0090] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0091] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0092] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for testing an embedded board, characterized in that: The method comprises: Detecting code update information in a code repository, and obtaining updated code from the code repository; Determine the corresponding test board according to the code update information, and deploy the updated code to the test board; the test board is connected to each drive interface of a preset test frame; the deployment of the updated code to the test board includes: deploying the updated code to the test board, and after the test board is restarted, determine each drive interface test item and each drive function test item to be tested corresponding to each drive interface according to each drive interface connected to the test frame by the test board, and obtain each drive test item combination according to each drive interface test item and each drive function test item; execute each drive interface test item and each drive function test item in the each drive test item combination to obtain each drive test result; the drive interface test item is a test for the data transmission capability of the drive interface; the drive function test item is a test for the drive function that can be achieved by the drive interface; The driving test results of each driving test item combination are obtained through each driving interface, and the test result of the test board is obtained according to each driving test result, including: for each driving test result, if the driving test result is detected to be abnormal, determining the associated driving test item combination of the driving test item combination corresponding to the driving test result; the associated driving test item combination represents that there is at least one driving test item combination with the driving test item combination corresponding to the driving test result that has the same driving test item; obtaining the associated driving test result corresponding to the associated driving test item combination; when the associated driving test result is detected to be abnormal, determining that the test result of the test board is that the driving test item combination corresponding to the driving test result and the same driving test item in the associated driving test item combination are abnormal.

2. The method according to claim 1, characterized in that The determining the corresponding test board according to the code update information includes: Obtaining program firmware information corresponding to the code update information; The corresponding board information is determined according to the program firmware information, and the test board corresponding to the code update information is obtained according to the board information.

3. The method according to claim 1, characterized in that The step of deploying the updated code to the test board includes: Compiling the updated code to obtain compiled code; The compiled code is deployed to the test board through a file transfer protocol.

4. The method according to any one of claims 1 to 3, characterized in that: After deploying the updated code to the test board, the method further includes: If it is detected that the test time of the test board for the drive test item combination is greater than a preset threshold, the test of the test board is stopped.

5. An embedded board test device, characterized in that: The device comprises: An acquisition module, used to detect code update information in a code repository and acquire updated code from the code repository; A test module, used to determine the corresponding test board according to the code update information, and deploy the updated code to the test board; the test board is connected to each drive interface of a preset test frame; specifically used to deploy the updated code to the test board, and after the test board is restarted, determine each drive interface test item and each drive function test item to be tested corresponding to each drive interface according to each drive interface connected to the test frame by the test board, and obtain each drive test item combination according to each drive interface test item and each drive function test item; execute each drive interface test item and each drive function test item in the each drive test item combination to obtain each drive test result; the drive interface test item is a test for the data transmission capability of the drive interface; the drive function test item is a test for the drive function that can be achieved by the drive interface; A determination module, used for obtaining each drive test result of each drive test item combination through each drive interface, and obtaining the test result of the test board according to each drive test result, specifically used for: for each drive test result, if the drive test result is detected to be abnormal, determining the associated drive test item combination of the drive test item combination corresponding to the drive test result; the associated drive test item combination represents that there is at least one drive test item combination with the drive test item combination corresponding to the drive test result that has the same drive test item; obtaining the associated drive test result corresponding to the associated drive test item combination; when the associated drive test result is detected to be abnormal, determining that the test result of the test board is that there is an abnormality between the drive test item combination corresponding to the drive test result and the same drive test item in the associated drive test item combination.

6. The device according to claim 5, characterized in that The test module is specifically used for: Obtaining program firmware information corresponding to the code update information; The corresponding board information is determined according to the program firmware information, and the test board corresponding to the code update information is obtained according to the board information.

7. The device according to claim 5, characterized in that The test module is specifically used for: Compiling the updated code to obtain compiled code; The compiled code is deployed to the test board through a file transfer protocol.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Citation Information

Patent Citations

  • Board-card test method and device, readable storage medium and computer equipment

    CN108519934A

  • Test script deployment method, apparatus and device, and readable medium

    CN111858330A

  • Test method, device and equipment and computer readable storage medium

    CN115712032A

  • Board card testing method and device

    CN115840129A