Board card interface test method, system and device and storage medium

Abstract

The invention discloses a board card interface testing method, system and device and a storage medium, and is applied to the technical field of servers, and the method comprises the steps: building interface bitmaps corresponding to different board card models in advance; for any board card model, the corresponding interface bitmap carries position parameters which are newly added in the interface configuration file in a state that all universal serial bus interfaces of the board card of the board card model are inserted into the peripheral compared with a state that all universal serial bus interfaces are not inserted into the peripheral; obtaining an interface bitmap corresponding to the model of the board card to be tested; after each universal serial bus interface of the to-be-tested board card is inserted into the peripheral, acquiring an interface configuration file; judging whether the obtained interface configuration file contains various position parameters in the interface bitmap or not; and if yes, determining that the to-be-tested board card passes the interface insertion test. By applying the scheme of the invention, the test method of the board card interface can be effectively carried out, and the test efficiency and the success rate are guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of servers, and in particular to a test method, system, equipment and storage medium for a board interface. Background Art

[0002] At present, when testing the USB (Universal Serial Bus) interface of a board, it is necessary to do so manually, which is increasingly costly. In addition, during the process of deep customization by customers and continuous product iteration, the design pattern of the board is also rapidly updated and iterated. Testing through manual operation has natural disadvantages in terms of complexity and one-time test success rate, and product upgrades also require extremely high operator memory.

[0003] In addition, the current USB interface test process before the server leaves the factory requires that after the USB flash drive is inserted during the USB test phase, a baseline USB configuration file is generated for the first test machine of the order, and the subsequent machines of the order are fully compared and tested with the USB configuration file of the first machine. If the USB configuration file is consistent with the USB configuration file produced by the first machine, the test passes, and if it is inconsistent, an error is reported. In such a scheme, if the first machine is abnormal, the configuration file will also be abnormal, which will cause a large number of machines to be tested using an incorrect standard.

[0004] In summary, how to effectively test the board interface and ensure the test efficiency and success rate is a technical problem that technicians in this field urgently need to solve. Summary of the invention

[0005] The purpose of the present invention is to provide a test method, system, device and storage medium for a board card interface, so as to effectively perform the test method for the board card interface and ensure the test efficiency and success rate.

[0006] In order to solve the above technical problems, the present invention provides the following technical solutions:

[0007] In a first aspect, the present invention provides a method for testing a board interface, comprising:

[0008] Pre-establishing interface bitmaps corresponding to different board models; wherein, for any board model, the corresponding interface bitmap carries the board of the board model, when each universal serial bus interface is plugged into a peripheral device, compared to a state where each universal serial bus interface is not plugged into a peripheral device, a newly added position parameter in the interface configuration file;

[0009] Determine the model of the board to be tested, and obtain the established interface bitmap corresponding to the model of the board to be tested;

[0010] After each universal serial bus interface of the board to be tested is plugged into a peripheral device, obtaining an interface configuration file of the board to be tested;

[0011] Determine whether the interface configuration file obtained contains various position parameters in the interface bitmap corresponding to the model of the board to be tested;

[0012] If yes, it is determined that the board to be tested has passed the interface insertion test.

[0013] On the other hand, after determining that the interface configuration file obtained does not include various position parameters in the interface bitmap corresponding to the model of the board to be tested, the method further includes:

[0014] Based on the obtained interface configuration file, determine each problematic interface;

[0015] Wherein, for any universal serial bus interface of the board to be tested, when any position parameter in the interface bitmap used to reflect the difference between the universal serial bus interface after the peripheral device is inserted and before the peripheral device is inserted does not appear in the interface configuration file obtained, the universal serial bus interface is determined as a problematic interface;

[0016] For each problematic interface, logically disable the problematic interface and re-enable it after the logical disablement;

[0017] Return to execute the operation of obtaining the interface configuration file of the board to be tested.

[0018] On the other hand, it also includes:

[0019] Before executing the operation of logically disabling each problematic interface and re-enabling the problematic interface after the logical disabling, determining whether a preset repeated test condition is satisfied;

[0020] If the condition is satisfied, then for each problematic interface, the operation of logically disabling the problematic interface and re-enabling the problematic interface after the logical disabling is performed;

[0021] If not, the test of the board to be tested is terminated.

[0022] On the other hand, the interface bitmaps corresponding to different board models are pre-established, including:

[0023] For any board model, when no peripheral is inserted into each universal serial bus interface of the board model, an interface configuration file of the board is obtained as an initial interface configuration file of the board, and an interface rate file of the board is obtained as an initial interface rate file of the board;

[0024] When a peripheral device is inserted into the ath universal serial bus interface of the board, a current interface configuration file of the board is obtained, and a position parameter newly added to the current interface configuration file compared with the initial interface configuration file is used as a position parameter corresponding to the ath universal serial bus interface;

[0025] When the ath universal serial bus interface of the board is plugged into a peripheral device, a current interface rate file of the board is obtained, and a numbering parameter newly added to the current interface rate file compared with the initial interface rate file is used as a numbering parameter corresponding to the ath universal serial bus interface; wherein a is a positive integer and ranges from 1 to n in sequence; and n is the total number of universal serial bus interfaces of the board of the board model;

[0026] After a is sequentially changed from 1 to n, the position parameter and number parameter corresponding to each universal serial bus interface are obtained as the interface bitmap corresponding to the board model;

[0027] After determining that the board to be tested has passed the interface insertion test, the method further includes:

[0028] The rate configuration file of the board to be tested is obtained, and based on the interface bitmap corresponding to the model of the board to be tested, the interface rate test of the board to be tested is performed.

[0029] On the other hand, obtaining the rate configuration file of the board to be tested, and performing an interface rate test of the board to be tested based on an interface bitmap corresponding to the model of the board to be tested, including:

[0030] For each universal serial bus interface of the board to be tested, obtaining a number parameter corresponding to the universal serial bus interface from an interface bitmap corresponding to the model of the board to be tested;

[0031] Determining the type of the universal serial bus interface based on the number parameter corresponding to the universal serial bus interface;

[0032] Based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, an interface rate test result of the universal serial bus interface is determined.

[0033] On the other hand, based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, determining the interface rate test result of the universal serial bus interface includes:

[0034] When the universal serial bus interface is of the first type, if the acquired rate configuration file of the board to be tested contains a first data row and a second data row carrying a number parameter of the universal serial bus interface, and the first data row carries a first numerical value, and the second data row carries a second numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed;

[0035] When the universal serial bus interface is of the second type, if the acquired rate configuration file of the board to be tested contains a first data row carrying a numbering parameter of the universal serial bus interface, and the first data row carries a first numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed.

[0036] On the other hand, it also includes:

[0037] After performing the interface rate test on the board to be tested, each universal serial bus interface in the board to be tested that fails the interface rate test is regarded as a problem interface;

[0038] For each problematic interface, logically disable the problematic interface and re-enable it after the logical disablement;

[0039] Return to the operation of obtaining the rate configuration file of the board to be tested, and performing an interface rate test of the board to be tested based on the interface bitmap corresponding to the model of the board to be tested.

[0040] In a second aspect, the present invention provides a test system for a board interface, comprising:

[0041] An interface bitmap establishment module is used to pre-establish interface bitmaps corresponding to different board models; wherein, for any board model, the corresponding interface bitmap carries a board of the board model, when each universal serial bus interface is plugged into a peripheral device, compared to a state where each universal serial bus interface is not plugged into a peripheral device, a position parameter newly added in the interface configuration file;

[0042] An interface bitmap acquisition module, used to determine the model of the board to be tested, and to acquire the established interface bitmap corresponding to the model of the board to be tested;

[0043] An interface configuration file acquisition module, used for acquiring the interface configuration file of the board to be tested after each universal serial bus interface of the board to be tested is plugged into a peripheral device;

[0044] The interface insertion test judgment module is used to judge whether the interface configuration file obtained contains various position parameters in the interface bitmap corresponding to the model of the board to be tested; if yes, it is determined that the board to be tested has passed the interface insertion test.

[0045] In a third aspect, the present invention provides a test device for a board interface, comprising:

[0046] Memory for storing computer programs;

[0047] The processor is used to execute the computer program to implement the steps of the board interface testing method as described above.

[0048] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the board interface testing method as described above are implemented.

[0049] The technical solution provided by the embodiment of the present invention is applied, considering that different board models have different design patterns, therefore for each board model, in the present application scheme, an interface bitmap corresponding to the board model is pre-established. For any board model, the corresponding interface bitmap carries the position parameter newly added in the interface configuration file when each universal serial bus interface of the board model is inserted into the state of the peripherals, compared to the state when each universal serial bus interface is not inserted into the peripherals. In other words, the interface bitmap established by the present application scheme can effectively reflect the board of the model, each universal serial bus interface is reflected in the configuration file after the peripherals are inserted compared to the difference before the peripherals are inserted, and the interface insertion test is subsequently realized based on the interface bitmap, and the reliability is very high, and the interface bitmap is usually error-free. For the board to be tested, after determining the model of the board to be tested, the interface bitmap corresponding to the model of the board to be tested can be obtained. Afterwards, it is necessary to obtain the interface configuration file of the board to be tested after each universal serial bus interface of the board to be tested is inserted into the peripheral hardware, and then determine whether the interface configuration file obtained includes the various position parameters in the interface bitmap corresponding to the model of the board to be tested. Under normal circumstances, in the interface configuration file obtained, the various position parameters in the interface bitmap should be included, so it can be determined that the board to be tested has passed the interface insertion test, that is, each universal serial bus interface of the board to be tested has passed the interface insertion test. And it can be seen that compared to the traditional scheme, a large amount of human-computer interaction operations are required, and the present application scheme only needs to pre-establish the interface bitmap corresponding to different board models, and then the test of the board to be tested can be efficiently completed, without the need for staff to perform human-computer interaction operations, it is also not easy to make mistakes, and the test efficiency and success rate are guaranteed.

[0050] In summary, in the solution of the present application, the board interface can be tested effectively, ensuring the test efficiency and success rate. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0052] Figure 1 A flow chart of a method for testing a board interface provided by a specific embodiment of the present invention;

[0053] Figure 2 A schematic diagram of a design architecture for testing a board interface provided by a specific implementation of the present invention;

[0054] Figure 3 A comparative schematic diagram of interface configuration files in a specific implementation manner of the present invention;

[0055] Figure 4 A schematic diagram of comparing interface rate files in a specific implementation manner of the present invention;

[0056] Figure 5 A schematic diagram of an interface bitmap in a specific implementation manner of the present invention;

[0057] Figure 6 A schematic diagram of the structure of a board interface test system provided by a specific embodiment of the present invention;

[0058] Figure 7 A schematic diagram of the structure of a board interface test device provided by a specific embodiment of the present invention;

[0059] Figure 8 The present invention is a schematic diagram of the structure of a computer-readable storage medium. DETAILED DESCRIPTION

[0060] The core of the present invention is to provide a test method for a board card interface, which can effectively perform the test method for the board card interface and ensure the test efficiency and success rate.

[0061] In order to enable those skilled in the art to better understand the scheme of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0062] Please refer to Figure 1 , Figure 1 The present invention provides a flow chart of a method for testing a board interface in accordance with a specific embodiment of the present invention. The method for testing a board interface may include the following steps:

[0063] Step S101: pre-establishing interface bitmaps corresponding to different board models.

[0064] Among them, for any board model, the corresponding interface bitmap carries the board of the board model, and when each universal serial bus interface is inserted with peripherals, compared with the state where none of the universal serial bus interfaces are inserted with peripherals, the newly added position parameters in the interface configuration file.

[0065] The present application solution usually tests the USB interface of the board to be tested, so the interface bitmap established is also the USB interface bitmap, that is, the USB map. And considering that different board models have different design patterns, for each board model, it is necessary to establish an interface bitmap corresponding to the board model, that is, to establish a full USB map. In addition, it is understandable that in the process of product update and iteration, when a new board model appears, a new interface bitmap can be established for the new board model. Please refer to Figure 2 , all interface bitmaps can be stored in the database.

[0066] The interface bitmap reflects the board of the corresponding model. The difference in the interface configuration file when each USB interface is plugged into a peripheral device and when none of the USB interfaces is plugged into a peripheral device can be used to test the board to be tested based on the interface bitmap.

[0067] When establishing the interface bitmaps corresponding to different board models, there can be multiple specific implementation methods as long as they can meet the functional requirements of this application. For example, in one scenario, for any board model, the interface configuration file of the board can be obtained when no peripherals are inserted into each universal serial bus interface of the board model, as the initial interface configuration file of the board. When the ath universal serial bus interface of the board is inserted into a peripheral, the current interface configuration file of the board is obtained, and the position parameters newly added to the current interface configuration file compared to the initial interface configuration file are used as the position parameters corresponding to the ath universal serial bus interface. After a is sequentially taken from 1 to n, the position parameters corresponding to each universal serial bus interface can be obtained, and these position parameters are used as the interface bitmap corresponding to the board model.

[0068] For example, in a specific implementation of the present invention, step S101 may include:

[0069] For any board model, when no peripheral is inserted into each universal serial bus interface of the board model, an interface configuration file of the board is obtained as an initial interface configuration file of the board, and an interface rate file of the board is obtained as an initial interface rate file of the board;

[0070] When the ath universal serial bus interface of the board is plugged into a peripheral device, a current interface configuration file of the board is obtained, and a position parameter newly added to the current interface configuration file compared with the initial interface configuration file is used as a position parameter corresponding to the ath universal serial bus interface;

[0071] When the ath universal serial bus interface of the board is plugged into a peripheral device, the current interface rate file of the board is obtained, and the numbering parameter newly added to the current interface rate file compared with the initial interface rate file is used as the numbering parameter corresponding to the ath universal serial bus interface; wherein a is a positive integer and ranges from 1 to n in sequence; and n is the total number of universal serial bus interfaces of the board model;

[0072] After a takes values ​​from 1 to n in sequence, the position parameter and number parameter corresponding to each universal serial bus interface are obtained as the established interface bitmap corresponding to the board model.

[0073] And in this implementation manner, after determining that the board to be tested has passed the interface insertion test, the method may also include: obtaining a rate configuration file of the board to be tested, and performing an interface rate test on the board to be tested based on an interface bitmap corresponding to the model of the board to be tested.

[0074] In this implementation, the interface bitmap carries not only the position parameter of each USB interface but also the number parameter of each USB interface, so that the interface rate test of the board to be tested can be performed based on the interface bitmap.

[0075] Specifically, in this implementation, a certain board model is used as an example for explanation. For this model of board, it is necessary to obtain the interface configuration file of the board as the initial interface configuration file of the board when none of the USB interfaces of the board is plugged into any peripheral device. The interface configuration file of the board reflects the location information of each USB interface. Of course, in some specific occasions, the interface configuration file may also carry some other information of the USB interface, which does not affect the implementation of the present invention. In one implementation, when none of the USB interfaces of this model of board is plugged into any peripheral device, the path ls / sys / bus / usb / devices / is printed to obtain the initial interface configuration file.

[0076] When the first USB interface of the board is plugged into a peripheral device, the path ls / sys / bus / usb / devices / can also be printed to obtain the current interface configuration file of the board. Then, the interface configuration file is compared with the initial interface configuration file to determine the position parameters newly added to the interface configuration file compared to the initial interface configuration file as the position parameters corresponding to the first universal serial bus interface.

[0077] For easier understanding, please refer to Figure 3 , is a comparative diagram of interface configuration files. And, Figure 3 The left side is a partial schematic diagram of the initial interface configuration file, and the right side is a partial schematic diagram of the interface configuration file obtained after the USB interface at the upper right front position of the board (for example, recorded as the first USB interface) is plugged into a peripheral. It can be seen that the interface configuration file obtained after the first USB interface is plugged into the peripheral has four more position parameters (1-4.3; 1-4.3:1.0; 2-4.3; 2-4.3:1.0) compared to the initial interface configuration file. These four position parameters are the position parameters corresponding to the first universal serial bus interface in this example.

[0078] Based on the same principle, when the peripheral device inserted into the first USB interface of the board is removed and the peripheral device is inserted into the second USB interface of the board, the path ls / sys / bus / usb / devices / can also be printed to obtain the current interface configuration file of the board, and then the interface configuration file can be compared with the aforementioned initial interface configuration file to determine the newly added position parameters of the interface configuration file compared with the initial interface configuration file as the position parameters corresponding to the second universal serial bus interface. Similarly, after a is taken from 1 to n in sequence, the position parameters corresponding to each universal serial bus interface can be obtained.

[0079] In this implementation, when no peripherals are inserted into any USB interface of the board, in addition to obtaining the interface configuration file of the board, it is also necessary to obtain the interface rate file of the board as the initial interface rate file of the board. The interface rate file of the board reflects the rate information of each USB interface. Of course, in some specific occasions, the interface rate file may also carry some other information of the USB interface. In one implementation, when no peripherals are inserted into any USB interface of this model of board, the interface rate file can be obtained by printing the path lsusb-t as the initial interface rate file.

[0080] When the first USB interface of the board is plugged into a peripheral device, the path lsusb–t can also be printed to obtain the current interface rate file of the board. Then, the interface rate file can be compared with the aforementioned initial interface rate file to determine the numbering parameters newly added to the current interface rate file compared to the initial interface rate file, as the numbering parameters corresponding to the first universal serial bus interface. The numbering parameters usually include the Vendor ID and the Product ID. By placing the numbering parameters into USBmap, when the interface rate test is performed later, the line where the numbering parameters are located can be found from the corresponding interface rate file based on the numbering parameters in USBmap, and then the interface rate file can be determined to be qualified, that is, whether the corresponding USB interface has passed the interface rate test.

[0081] For easier understanding, please refer to Figure 4 , is a comparison diagram of interface rate files. And, Figure 4The left side is a partial schematic diagram of the initial interface rate file, and the right side is a partial schematic diagram of the interface rate file obtained after the USB interface at the upper right front position of the board (for example, recorded as the first USB interface) is plugged into a peripheral. It can be seen that the interface rate file obtained after the first USB interface is plugged into the peripheral has 2 more lines than the initial interface rate file. One line has a Vendor ID of 2 and a Product ID of 25, which means that the newly added numbering parameter in this line can be expressed as 2.25, and the other line has a Vendor ID of 2 and a Product ID of 26, which means that the newly added numbering parameter in this line can be expressed as 2.26. In other words, 2.25 and 2.26 are the numbering parameters corresponding to the first universal serial bus interface in this example.

[0082] Based on the same principle, when the peripheral device inserted into the first USB interface of the board is removed and the peripheral device is inserted into the second USB interface of the board, the path ls lsusb–t can also be printed to obtain the current interface rate file of the board, and then the interface rate file can be compared with the aforementioned initial interface rate file to determine the number parameter newly added to the interface rate file compared with the initial interface rate file as the position parameter corresponding to the second universal serial bus interface. Similarly, after a is taken from 1 to n in sequence, the number parameter corresponding to each universal serial bus interface can be obtained.

[0083] It can be seen that after a is sequentially changed from 1 to n, in this implementation, the position parameters and number parameters corresponding to each universal serial bus interface can be obtained as the interface bitmap corresponding to the board model. Figure 3 For example, for the USB port in the upper right front position, the number parameters are 2.25 and 2.26, and the position parameters are 1-4.3; 1-4.3:1.0; 2-4.3 and 2-4.3:1.0. Figure 5 , which is an interface bitmap established in a specific implementation method. Figure 5 The 8 corresponding USB interfaces in the figure show the number parameters and position parameters respectively, forming the interface bitmap of the specific board model.

[0084] In addition, it should be noted that the commonly used USB interfaces are usually USB3.0 and USB2.0. For different USB interfaces, the number of number parameters and position parameters are different. Figure 5 In the example, USB3.0 has 4 position parameters and 2 number parameters, while USB2.0 has 2 position parameters and 1 number parameter, so Figure 5 In the example, the missing data for USB2.0 is not filled in.

[0085] In the traditional scheme, the test content is very simple, and the difference between the USB3.0 interface and the USB2.0 interface is not considered for testing. As long as the USB disk or mouse is simply inserted and the USB disk can be read or the mouse can be moved, it is considered that the USB interface is normal, that is, the interface rate test of the USB interface will not be performed. In this implementation, the interface rate test of the board to be tested is further performed, that is, the interface rate test of each USB interface is performed, so that the USB interface with abnormal interface rate can be effectively determined, and the detection reliability of the solution of the present application is further improved.

[0086] Step S102: Determine the model of the board to be tested, and obtain the established interface bitmap corresponding to the model of the board to be tested.

[0087] After the server is powered on, the board interface test can be automatically executed through a pre-written program. During execution, the model of the board to be tested needs to be determined. For example, the model of the board to be tested can be obtained through the ipmitool fru | grep "ard PartNumber" command. After obtaining the model of the board to be tested, the interface bitmap corresponding to the model of the board to be tested can be obtained from the database.

[0088] Step S103: After all the USB interfaces of the board to be tested are plugged with peripherals, an interface configuration file of the board to be tested is obtained.

[0089] When carrying out the test of the board to be tested, it is necessary to insert peripheral hardware into each USB interface of the board to be tested. In practical applications, each peripheral hardware can be a USB flash drive usually, which is convenient for implementation. Of course, other USB peripheral hardware can be used according to actual needs in other specific occasions. At this time, the interface configuration file of the board to be tested can be obtained, for example, the path ls / sys / bus / usb / devices / is printed, and the current interface configuration file under the path can be obtained. In addition, it is understandable that, since each universal serial bus interface of the board to be tested is inserted into peripheral hardware at this time, the interface configuration file of the board to be tested obtained in step S103, under normal circumstances, can carry each position parameter of each USB interface.

[0090] Step S104: Determine whether the acquired interface configuration file contains various position parameters in the interface bitmap corresponding to the model of the board to be tested. If yes, execute step S105.

[0091] Step S105: Determine whether the board to be tested has passed the interface insertion test.

[0092] The interface configuration file obtained in step S103 can be compared with the interface bitmap corresponding to the model of the board to be tested, so as to determine whether the interface configuration file obtained contains the various position parameters in the interface bitmap. Figure 5 For example, the USB interface at the upper right front position of the device, normally, the interface configuration file obtained needs to include the position parameters 1-4.3; 1-4.3:1.0; 2-4.3 and 2-4.3:1.0. Similarly, for Figure 5 For USB interfaces at other positions in the interface bitmap, the interface configuration file obtained in step S103 should also include various position parameters of these USB interfaces.

[0093] If the interface configuration file obtained contains various position parameters in the interface bitmap corresponding to the model of the board to be tested, it means that the board to be tested has passed the interface insertion test, that is, it means that each USB interface of the board to be tested has currently read the inserted peripherals, so each USB interface has passed the interface insertion test. On the contrary, if the interface configuration file obtained does not contain various position parameters in the interface bitmap corresponding to the model of the board to be tested, it means that the interface insertion test of one or more USB interfaces has not passed. At this time, an error log can be output, and the error log can carry the position of the failed USB interface to prompt the staff to perform maintenance.

[0094] In a specific implementation of the present invention, after determining that the acquired interface configuration file does not contain various position parameters in the interface bitmap corresponding to the model of the board to be tested, it also includes:

[0095] Based on the obtained interface configuration files, identify each problematic interface;

[0096] Wherein, for any universal serial bus interface of the board to be tested, when any position parameter in the interface bitmap used to reflect the difference between the universal serial bus interface after the peripheral device is inserted and before the peripheral device is inserted does not appear in the acquired interface configuration file, the universal serial bus interface is determined as a problematic interface;

[0097] For each problematic interface, logically disable the problematic interface and then re-enable it after logically disabling it;

[0098] Returns the operation of obtaining the interface configuration file of the board to be tested.

[0099] In this implementation manner, if the acquired interface configuration file does not contain various position parameters in the interface bitmap corresponding to the model of the board to be tested, the test is not terminated immediately, but further attempts are made.

[0100] Specifically, each problematic interface will be identified based on the interface configuration file obtained. Figure 5 This interface bitmap is used as an example to illustrate that, for example, for the USB interface at the upper right front of the board to be tested, in the interface configuration file obtained, position parameters 1-4.3; 1-4.3:1.0; 2-4.3 can be found, but there is no 2-4.3:1.0, so it can be determined that the USB interface at the upper right front of the board to be tested is a problematic interface. Similarly, based on the interface configuration file obtained, each problematic interface can be determined by comparing the interface bitmap.

[0101] In this implementation, for each problem interface, these problem interfaces will be logically disabled, and after the logical disablement, they will be re-enabled, and then the operation of executing step S103 will be returned to re-acquire the interface configuration file of the board to be tested, so as to re-test. This is to take into account that in some cases, the determined problem interface is not a fault, but an occasional error caused by factors such as interference, so that the USB interface is determined as a problem interface, and it can be checked by re-enabling after logical disablement. Therefore, in this implementation, each problem interface is logically disabled and re-enabled after logical disablement, and some problem interfaces may be correctly identified, which makes it possible to return to the operation of executing step S103, and the interface configuration file of the board to be tested that is re-acquired has the relevant position parameters corresponding to the problem interface in the interface bitmap, that is, after re-judgment, the problem interface can be inserted into the test through the interface. It can be seen that this implementation effectively reduces the probability of false detection and improves the detection reliability of the present application scheme.

[0102] In addition, there are many specific implementations for logically disabling the problematic interface and re-enabling it after logical disabling. For example, in one implementation, an interface enable / disable file can be opened through an instruction. For example, in one case, the interface enable / disable file is created or opened through the instruction vi 99-disable-usb.rules (if the interface enable / disable file does not exist, it is created first and then opened). Then, the content in the enable / disable file can be modified, and the USB interface can be reloaded, so that each problematic interface can be logically disabled. For example, in one case, specifically in the interface enable / disable file, add "ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="****", ATTRS{idProduct}=="****", RUN+=" / bin / sh -c'echo 0 > / sys / bus / usb / devices / %k / authorized", where **** needs to be filled in with the number parameters of each problematic interface, that is, fill in the Vendor ID and Product ID of each problematic interface. Then execute the reload udev rules: udevadm control–reload-rules, at which time each problematic interface is disabled. After disabling, you can wait for a certain period of time, such as 30 seconds, and then delete the interface enable / disable file, and reload the USB interface, so that each USB interface can be re-enabled. For example, in one case, specifically, the interface enable / disable file is deleted through the command rm 99-disable-usb.rules, and then udevadm is executed again. control–reload-rules, at this time, each USB port is re-enabled, and can be verified again, that is, the interface insertion test of the board to be tested is performed again. It can be seen that through the above operation, the process of logically disabling the problem interface and re-enabling it after logical disabling is realized in a relatively simple and convenient manner.

[0103] Furthermore, in a specific embodiment of the present invention, it may also include:

[0104] Before executing the operation of logically disabling the problem interface and re-enabling the problem interface after the logical disabling for each problem interface, determining whether a preset repeated test condition is met;

[0105] If the condition is satisfied, then for each problematic interface, an operation of logically disabling the problematic interface and re-enabling the problematic interface after the logical disabling is performed;

[0106] If not satisfied, the test of the board to be tested is terminated.

[0107] This implementation method takes into account that if a certain USB interface is indeed faulty, even if the interface insertion test of the board to be tested is repeated for many times as described in the above implementation method, the USB interface still cannot pass the interface insertion test. In this regard, a repeated test condition is set in this implementation method. Before the operation of logically disabling the problem interface and re-enabling it after logical disabling, it is necessary to first determine whether the preset repeated test condition is satisfied. If satisfied, the operation of logically disabling and re-enabling each problem interface will be performed, otherwise the test of the board to be tested can be directly terminated.

[0108] The specific content of the repeated test condition can be set and adjusted according to actual needs. For example, the number of repeated executions can be counted, that is, each time the operation of logically disabling and re-enabling the problem interface is performed once, the count value is increased by 1. If the count value does not reach the set number of times threshold, it can be determined that the repeated test condition is met. On the contrary, if the count value does not reach the set number of times threshold, it can be determined that the repeated test condition is not met. In another case, when a problem interface determined this time is still a problem interface when it is executed next time, it can be determined that the repeated test condition is not met.

[0109] In a specific implementation of the present invention, obtaining a rate configuration file of a board to be tested, and performing an interface rate test of the board to be tested based on an interface bitmap corresponding to the model of the board to be tested may specifically include:

[0110] For each universal serial bus interface of the board to be tested, obtaining a number parameter corresponding to the universal serial bus interface from an interface bitmap corresponding to the model of the board to be tested;

[0111] Determining the type of the universal serial bus interface based on the number parameter corresponding to the universal serial bus interface;

[0112] Based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, an interface rate test result of the universal serial bus interface is determined.

[0113] In this implementation, during the interface rate test, for each USB interface of the board to be tested, it is necessary to obtain the number parameter corresponding to the USB interface from the interface bitmap of the model of the board to be tested. Figure 5 Take this interface bitmap as an example to illustrate. For example, for the USB interface at the front upper right position of the board to be tested, in the interface bitmap, you can find the number parameter 2.25 and the number parameter 2.25 corresponding to the USB interface, and then you can determine that the USB interface is of USB3.0 type. Figure 5In the example, for the USB interface at the lower left front of the board to be tested, the number parameter 3.31 corresponding to the USB interface can be found in the interface bitmap. Since there is only one number parameter, it can be determined that the USB interface is of USB2.0 type.

[0114] For any USB interface, it is necessary to determine the interface rate test result of the USB interface based on its type and the obtained rate configuration file of the board to be tested to ensure the reliability of the obtained interface rate test result.

[0115] In a specific implementation of the present invention, based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, determining the interface rate test result of the universal serial bus interface may specifically include:

[0116] When the universal serial bus interface is of the first type, if the acquired rate configuration file of the board to be tested contains a first data row and a second data row carrying a number parameter of the universal serial bus interface, and the first data row carries a first numerical value, and the second data row carries a second numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed;

[0117] When the universal serial bus interface is of the second type, if the rate configuration file of the board to be tested obtained contains a first data row carrying the numbering parameter of the universal serial bus interface, and the first data row carries a first numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed.

[0118] In this implementation, when the USB interface is of the first type, that is, the USB interface is of the USB3.0 type, it is necessary to determine whether there is a first data row and a second data row carrying the serial number parameter of the USB interface in the acquired rate configuration file of the board to be tested, and it is required that the first data row carries a first value and the second data row carries a second value. The first value is usually set to 480M, and the second value is usually set to 5000M. Figure 4 Taking the right side as an example, it can be seen that in the first data row carrying the number parameter 2.26, it carries the first value 480M, and in the second data row carrying the number parameter 2.25, it carries the second value 5000M.

[0119] When the universal serial bus interface is of the second type, it means that the universal serial bus interface is of USB2.0 type. Therefore, it is necessary to determine whether there is a first data row carrying the numbering parameters of the universal serial bus interface in the rate configuration file of the board to be tested, and the first data row is required to carry the first value 480M.

[0120] In a specific embodiment of the present invention, it also includes:

[0121] After the interface rate test of the board to be tested is performed, each universal serial bus interface in the board to be tested that fails the interface rate test is regarded as a problem interface;

[0122] For each problematic interface, logically disable the problematic interface and then re-enable it after logically disabling it;

[0123] Return to execute the operation of obtaining the rate configuration file of the board to be tested, and performing the interface rate test of the board to be tested based on the interface bitmap corresponding to the model of the board to be tested.

[0124] This implementation method takes into account that when any USB interface does not provide interface speed testing, the USB interface can also be used as a problem interface. For each problem interface, the problem interface can also be logically disabled and re-enabled after logical disabling to deal with some occasional interference, thereby effectively reducing the probability of false detection and improving the detection reliability of the solution of the present application.

[0125] By logically disabling each problematic interface and then re-enabling it, the rate configuration file of the board to be tested can be re-acquired, and then the interface rate test of the board to be tested can be performed again based on the interface bitmap corresponding to the model of the board to be tested.

[0126] In addition, it is understandable that when re-testing the interface rate test of the board to be tested, statistics of repeated tests can also be set, for example, the number of repeated executions can also be counted to determine whether it is necessary to continue to re-test the interface rate test of the board to be tested. Figure 2 In the example, the same count value can be shared for the interface rate test and the interface insertion test of the board to be tested. That is to say, whether it is during the interface insertion test that the problem interface needs to be logically disabled and re-enabled, or during the interface rate test that the problem interface needs to be logically disabled and re-enabled, the count value will be increased. When the count value does not reach the set number of times, the test is allowed to continue. Otherwise, the test will not continue but will be ended directly.

[0127] The technical solution provided by the embodiment of the present invention is applied, considering that different board models have different design patterns, therefore for each board model, in the present application scheme, an interface bitmap corresponding to the board model is pre-established. For any board model, the corresponding interface bitmap carries the position parameter newly added in the interface configuration file when each universal serial bus interface of the board model is inserted into the state of the peripherals, compared to the state when each universal serial bus interface is not inserted into the peripherals. In other words, the interface bitmap established by the present application scheme can effectively reflect the board of the model, each universal serial bus interface is reflected in the configuration file after the peripherals are inserted compared to the difference before the peripherals are inserted, and the interface insertion test is subsequently realized based on the interface bitmap, and the reliability is very high, and the interface bitmap is usually error-free. For the board to be tested, after determining the model of the board to be tested, the interface bitmap corresponding to the model of the board to be tested can be obtained. Afterwards, it is necessary to obtain the interface configuration file of the board to be tested after each universal serial bus interface of the board to be tested is inserted into the peripheral hardware, and then determine whether the interface configuration file obtained includes the various position parameters in the interface bitmap corresponding to the model of the board to be tested. Under normal circumstances, in the interface configuration file obtained, the various position parameters in the interface bitmap should be included, so it can be determined that the board to be tested has passed the interface insertion test, that is, each universal serial bus interface of the board to be tested has passed the interface insertion test. And it can be seen that compared to the traditional scheme, a large amount of human-computer interaction operations are required, and the present application scheme only needs to pre-establish the interface bitmap corresponding to different board models, and then the test of the board to be tested can be efficiently completed, without the need for staff to perform human-computer interaction operations, it is also not easy to make mistakes, and the test efficiency and success rate are guaranteed.

[0128] In summary, in the solution of the present application, the board interface can be tested effectively, ensuring the test efficiency and success rate.

[0129] Corresponding to the above method embodiment, the embodiment of the present invention further provides a test system for a board interface, which can be referred to in correspondence with the above.

[0130] See also Figure 6 , the test system of the board interface may include:

[0131] The interface bitmap establishment module 601 is used to establish the interface bitmaps corresponding to different board models in advance; wherein, for any board model, the corresponding interface bitmap carries the board model, when each universal serial bus interface is plugged into a peripheral device, compared with the state where each universal serial bus interface is not plugged into a peripheral device, the position parameters newly added in the interface configuration file;

[0132] The interface bitmap acquisition module 602 is used to determine the model of the board to be tested and acquire the established interface bitmap corresponding to the model of the board to be tested;

[0133] The interface configuration file acquisition module 603 is used to acquire the interface configuration file of the board to be tested after each universal serial bus interface of the board to be tested is plugged into the peripheral device;

[0134] The interface insertion test judgment module 604 is used to judge whether the obtained interface configuration file contains various position parameters in the interface bitmap corresponding to the model of the board to be tested; if so, it is determined that the board to be tested has passed the interface insertion test.

[0135] In a specific embodiment of the present invention, a logic disabling enabling module is further included, which is used to:

[0136] After the interface insertion test determination module 604 determines that the acquired interface configuration file does not contain various position parameters in the interface bitmap corresponding to the model of the board to be tested, each problematic interface is determined based on the acquired interface configuration file;

[0137] Wherein, for any universal serial bus interface of the board to be tested, when any position parameter in the interface bitmap used to reflect the difference between the universal serial bus interface after the peripheral device is inserted and before the peripheral device is inserted does not appear in the acquired interface configuration file, the universal serial bus interface is determined as a problematic interface;

[0138] For each problematic interface, logically disable the problematic interface and then re-enable it after logically disabling it;

[0139] Return to the trigger interface configuration file acquisition module 603.

[0140] In a specific embodiment of the present invention, the logic disabling enabling module is further used for:

[0141] Before executing the operation of logically disabling the problem interface and re-enabling the problem interface after the logical disabling for each problem interface, determining whether a preset repeated test condition is met;

[0142] If the condition is satisfied, then for each problematic interface, an operation of logically disabling the problematic interface and re-enabling the problematic interface after the logical disabling is performed;

[0143] If not satisfied, the test of the board to be tested is terminated.

[0144] In a specific implementation of the present invention, the interface bitmap establishment module 601 is specifically used for:

[0145] For any board model, when no peripheral is inserted into each universal serial bus interface of the board model, an interface configuration file of the board is obtained as an initial interface configuration file of the board, and an interface rate file of the board is obtained as an initial interface rate file of the board;

[0146] When the ath universal serial bus interface of the board is plugged into a peripheral device, a current interface configuration file of the board is obtained, and a position parameter newly added to the current interface configuration file compared with the initial interface configuration file is used as a position parameter corresponding to the ath universal serial bus interface;

[0147] When the ath universal serial bus interface of the board is plugged into a peripheral device, the current interface rate file of the board is obtained, and the numbering parameter newly added to the current interface rate file compared with the initial interface rate file is used as the numbering parameter corresponding to the ath universal serial bus interface; wherein a is a positive integer and ranges from 1 to n in sequence; and n is the total number of universal serial bus interfaces of the board model;

[0148] After a is sequentially changed from 1 to n, the position parameter and number parameter corresponding to each universal serial bus interface are obtained as the interface bitmap corresponding to the board model;

[0149] Also includes interface rate test module for:

[0150] After determining that the board to be tested has passed the interface insertion test, the rate configuration file of the board to be tested is obtained, and the interface rate test of the board to be tested is performed based on the interface bitmap corresponding to the model of the board to be tested.

[0151] In a specific implementation of the present invention, the interface rate test module is specifically used to:

[0152] After determining that the board to be tested has passed the interface insertion test, for each universal serial bus interface of the board to be tested, obtaining a number parameter corresponding to the universal serial bus interface from an interface bitmap corresponding to the model of the board to be tested;

[0153] Determining the type of the universal serial bus interface based on the number parameter corresponding to the universal serial bus interface;

[0154] Based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, an interface rate test result of the universal serial bus interface is determined.

[0155] In a specific embodiment of the present invention, based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, determining the interface rate test result of the universal serial bus interface includes:

[0156] When the universal serial bus interface is of the first type, if the acquired rate configuration file of the board to be tested contains a first data row and a second data row carrying a number parameter of the universal serial bus interface, and the first data row carries a first numerical value, and the second data row carries a second numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed;

[0157] When the universal serial bus interface is of the second type, if the rate configuration file of the board to be tested obtained contains a first data row carrying the numbering parameter of the universal serial bus interface, and the first data row carries a first numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed.

[0158] In a specific embodiment of the present invention, the logic disabling enabling module is further used for:

[0159] After the interface rate test of the board to be tested is performed, each universal serial bus interface in the board to be tested that fails the interface rate test is regarded as a problem interface;

[0160] For each problematic interface, logically disable the problematic interface and then re-enable it after logically disabling it;

[0161] Return to trigger interface rate test module.

[0162] Corresponding to the above method and system embodiments, the embodiments of the present invention further provide a board interface test device, a computer-readable storage medium and a computer program product, which can be referred to in correspondence with the above.

[0163] See also Figure 7 As shown, the device may include:

[0164] Memory 701, used for storing computer programs;

[0165] The processor 702 is used to execute a computer program to implement the steps of the board interface testing method in any of the above embodiments.

[0166] The computer program product includes a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps of the board interface testing method in any of the above embodiments are implemented.

[0167] See also Figure 8The computer readable storage medium 80 stores a computer program 81, and when the computer program 81 is executed by the processor, the steps of the board interface test method in any of the above embodiments are implemented. The computer readable storage medium 80 mentioned here includes RAM (Random Access Memory), memory, ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), register, hard disk, removable disk, or any other form of storage medium known in the technical field.

[0168] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0169] Professionals may further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention, and the description of the above embodiments is only used to help understand the technical solution and its core idea of ​​the present invention. It should be pointed out that for ordinary technicians in the technical field, without departing from the principle of the present invention, the present invention can also be improved and modified in a number of ways, and these improvements and modifications also fall within the scope of protection of the present invention.

Claims

1. A method for testing a board interface, characterized in that: include: Pre-establishing interface bitmaps corresponding to different board models; wherein, for any board model, the corresponding interface bitmap carries the board of the board model, when each universal serial bus interface is plugged into a peripheral device, compared to a state where each universal serial bus interface is not plugged into a peripheral device, a newly added position parameter in the interface configuration file; Determine the model of the board to be tested, and obtain the established interface bitmap corresponding to the model of the board to be tested; After each universal serial bus interface of the board to be tested is plugged into a peripheral device, obtaining an interface configuration file of the board to be tested; Determine whether the interface configuration file obtained contains various position parameters in the interface bitmap corresponding to the model of the board to be tested; If yes, it is determined that the board to be tested has passed the interface insertion test.

2. The method for testing a board interface according to claim 1, characterized in that: After determining that the interface configuration file obtained does not include various position parameters in the interface bitmap corresponding to the model of the board to be tested, the method further includes: Based on the obtained interface configuration file, determine each problematic interface; Wherein, for any universal serial bus interface of the board to be tested, when any position parameter in the interface bitmap used to reflect the difference between the universal serial bus interface after the peripheral device is inserted and before the peripheral device is inserted does not appear in the interface configuration file obtained, the universal serial bus interface is determined as a problematic interface; For each problematic interface, logically disable the problematic interface and re-enable it after the logical disablement; Return to execute the operation of obtaining the interface configuration file of the board to be tested.

3. The method for testing a board interface according to claim 2, characterized in that: Also includes: Before executing the operation of logically disabling each problematic interface and re-enabling the problematic interface after the logical disabling, determining whether a preset repeated test condition is satisfied; If the condition is satisfied, then for each problematic interface, the operation of logically disabling the problematic interface and re-enabling the problematic interface after the logical disabling is performed; If not, the test of the board to be tested is terminated.

4. The method for testing a board interface according to claim 1, characterized in that: Pre-establish the interface bitmaps corresponding to different board models, including: For any board model, when no peripheral is inserted into each universal serial bus interface of the board model, an interface configuration file of the board is obtained as an initial interface configuration file of the board, and an interface rate file of the board is obtained as an initial interface rate file of the board; When a peripheral device is inserted into the ath universal serial bus interface of the board, a current interface configuration file of the board is obtained, and a position parameter newly added to the current interface configuration file compared with the initial interface configuration file is used as a position parameter corresponding to the ath universal serial bus interface; When the ath universal serial bus interface of the board is plugged into a peripheral device, a current interface rate file of the board is obtained, and a numbering parameter newly added to the current interface rate file compared with the initial interface rate file is used as a numbering parameter corresponding to the ath universal serial bus interface; wherein a is a positive integer and ranges from 1 to n in sequence; and n is the total number of universal serial bus interfaces of the board of the board model; After a is sequentially changed from 1 to n, the position parameter and number parameter corresponding to each universal serial bus interface are obtained as the interface bitmap corresponding to the board model; After determining that the board to be tested has passed the interface insertion test, the method further includes: The rate configuration file of the board to be tested is obtained, and based on the interface bitmap corresponding to the model of the board to be tested, the interface rate test of the board to be tested is performed.

5. The method for testing a board interface according to claim 4, characterized in that: Acquiring a rate configuration file of the board to be tested, and performing an interface rate test of the board to be tested based on an interface bitmap corresponding to the model of the board to be tested, comprising: For each universal serial bus interface of the board to be tested, acquiring a number parameter corresponding to the universal serial bus interface from an interface bitmap corresponding to the model of the board to be tested; Determining the type of the universal serial bus interface based on the number parameter corresponding to the universal serial bus interface; Based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, an interface rate test result of the universal serial bus interface is determined.

6. The method for testing a board interface according to claim 5, characterized in that: Determining an interface rate test result of the universal serial bus interface based on the type of the universal serial bus interface and the rate configuration file of the board to be tested, including: When the universal serial bus interface is of the first type, if the acquired rate configuration file of the board to be tested contains a first data row and a second data row carrying a number parameter of the universal serial bus interface, and the first data row carries a first numerical value, and the second data row carries a second numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed; When the universal serial bus interface is of the second type, if the acquired rate configuration file of the board to be tested contains a first data row carrying a numbering parameter of the universal serial bus interface, and the first data row carries a first numerical value, then the interface rate test result of the universal serial bus interface is passed, otherwise it is failed.

7. The method for testing a board interface according to claim 5, characterized in that: Also includes: After performing the interface rate test on the board to be tested, each universal serial bus interface in the board to be tested that fails the interface rate test is regarded as a problem interface; For each problematic interface, logically disable the problematic interface and re-enable it after the logical disablement; Return to the operation of obtaining the rate configuration file of the board to be tested, and performing an interface rate test of the board to be tested based on the interface bitmap corresponding to the model of the board to be tested.

8. A board interface testing system, characterized in that: include: An interface bitmap establishment module is used to pre-establish interface bitmaps corresponding to different board models; wherein, for any board model, the corresponding interface bitmap carries a board of the board model, when each universal serial bus interface is plugged into a peripheral device, compared to a state where each universal serial bus interface is not plugged into a peripheral device, a position parameter newly added in the interface configuration file; An interface bitmap acquisition module, used to determine the model of the board to be tested, and to acquire the established interface bitmap corresponding to the model of the board to be tested; An interface configuration file acquisition module, used for acquiring the interface configuration file of the board to be tested after each universal serial bus interface of the board to be tested is plugged into a peripheral device; The interface insertion test judgment module is used to judge whether the interface configuration file obtained contains various position parameters in the interface bitmap corresponding to the model of the board to be tested; if yes, it is determined that the board to be tested has passed the interface insertion test.

9. A test device for a board interface, characterized in that: include: Memory for storing computer programs; A processor is used to execute the computer program to implement the steps of the board interface testing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the board interface testing method according to any one of claims 1 to 7 are implemented.

Images