Method, device and system for production testing of servers

Abstract

Embodiments of the present application provide a production test method, a production test device and a production test system of a server. The method comprises: extracting test information of each server in a received current order; determining a historical order having the same configuration information and the same test instruction as the current order based on order information of the current order, to obtain a target historical order, the test instruction being used for testing the test information of the server; and testing the test information of each server in the current order based on a standard file of the target historical order, the standard file being obtained after testing the test information of a first server produced in the target historical order. Through the present application, the problem of large workload and waste of human resources caused by manually checking the first server in each order in the related art is solved.

Description

Technical Field

[0001] This application relates to the field of servers, and more specifically, to a server production testing method, a production testing apparatus, a computer-readable storage medium, and a server production testing system. Background Technology

[0002] With societal development and the increasing informatization of various industries, the demand for servers is growing. Furthermore, the emergence of technologies such as artificial intelligence, metaverse, blockchain, and edge computing has led to diverse requirements for server form factors.

[0003] In server manufacturing plants, customer orders are often split into multiple orders at the production end due to factors such as component and material supply, factory capacity pressure, or discontinuous customer demand. This results in production being carried out in multiple factories and at different times. Alternatively, multiple customer orders with the same configuration and customization requirements may also be scattered across different factories and production periods. To ensure product quality, the first server of each order needs to undergo production testing (i.e., first-run inspection) by production inspection personnel. With increasing capacity pressure, diversified customer customization requirements, and the requirements of smart factory construction, the first-run inspection method urgently needs to be transformed.

[0004] In existing technologies, the first server for each order is usually identified, and after basic functional testing is completed, the server is transported to the first inspection area so that production inspectors can conduct production testing.

[0005] The above method requires checking each order, which is time-consuming. Furthermore, with a large number of small orders, not only is the initial inspection workload heavy, but because some of these orders have the same configuration and instructions, the verification work becomes repetitive, leading to a waste of manpower.

[0006] Therefore, there is an urgent need for a method that can reduce the workload of the first inspection. Summary of the Invention

[0007] This application provides a server production testing method, production testing device, computer-readable storage medium, and server production testing system to at least solve the problem in related technologies that the workload and human resource waste caused by manually checking the first server in each order are large.

[0008] According to one embodiment of this application, a method for production testing of a server is provided, comprising: extracting test information of each server in a received current order, the test information including firmware information, component information, motherboard programming information, backplane programming information, and customization information, wherein the customization information is special parameter information set for the server; determining, based on the order information of the current order, a target historical order having the same configuration information and the same test instructions as the current order, wherein the test instructions are used to test the test information of the server; and testing the test information of each server in the current order based on a standard file of the target historical order, wherein the standard file is obtained after testing the test information of the first server produced in the target historical order.

[0009] In one exemplary embodiment, the order information includes model information, key component information, and configuration number of each server in the current order. The model information is used to characterize the model of each server in the current order, the key component information is used to characterize the relevant information of the key components of each server in the current order, and the configuration number is used to characterize at least the configuration information of each server in the current order.

[0010] In one exemplary embodiment, the model information has the highest priority, and the configuration number has the lowest priority. Based on the order information of the current order, determining historical orders with the same configuration information and the same test instructions as the current order to obtain target historical orders includes: if there is a historical order with the same model information as the current order, determining the historical order with the same model information as the current order as the target historical order; if the target historical order cannot be determined based on the model information of the current order, and there is a historical order with the same key component information as the current order, determining the historical order with the same key component information as the current order as a candidate historical order, and then determining whether to determine the candidate historical order as the target historical order based at least on the test instructions corresponding to the test information of the server in the current order; if the target historical order cannot be determined based on the key component information of the current order, and there is a historical order with the same configuration number as the current order, determining the historical order with the same configuration number as the current order as the candidate historical order, and then determining whether to determine the candidate historical order as the target historical order based at least on the test instructions corresponding to the test information of the server in the current order.

[0011] In one exemplary embodiment, determining whether to designate a candidate historical order as a target historical order, based at least on the test instructions corresponding to the test information of the server in the current order, includes: determining whether the test instructions corresponding to the test information of the server in the current order are the same as the test instructions corresponding to the candidate historical order; if the test instructions corresponding to the test information of the server in the current order are the same as the test instructions corresponding to the candidate historical order, designating the candidate historical order as the target historical order; if the test instructions corresponding to the test information of the server in the current order are different from the test instructions corresponding to the candidate historical order, determining whether the test instructions corresponding to the test information of the server in the current order are related to both the assembly process standards and test requirements of the corresponding server; if the test instructions corresponding to the test information of the server in the current order are not related to both the assembly process standards and test requirements of the corresponding server, designating the candidate historical order as the target historical order.

[0012] In one exemplary embodiment, testing the test information of each server in the current order based on the standard file of the target historical order includes: comparing each standard test information in the standard file of the target historical order with each test information of each server in the current order one by one; if all the standard test information in the standard file of the target historical order passes the comparison with each test information of the target server, the target server is determined to have passed the test, and the target server is one of the servers in the current order; if one of the standard test information in the standard file of the target historical order fails the comparison with the corresponding test information of the target server, the target server is determined to have failed the test.

[0013] In an exemplary embodiment, if a standard test message in the standard file containing the target historical order fails a comparison with a corresponding test message of the target server, and the production testing method determines that the target server test has failed, the production testing method further includes: issuing a warning message to alert the testers.

[0014] In one exemplary embodiment, the production testing method further includes: if, based on the order information of the current order, no target historical order with the same configuration information and the same test instructions as the current order is identified, testing the first server produced in the current order is performed based on the test information and test instructions of the first server produced in the current order.

[0015] According to another embodiment of this application, a server production testing apparatus is provided, comprising: an extraction unit, configured to extract test information of each server in a received current order, the test information including firmware information, component information, motherboard programming information, backplane programming information, and customization information, wherein the customization information is special parameter information set for the server; a determination unit, configured to determine, based on the order information of the current order, a historical order having the same configuration information and the same test instructions as the current order, thereby obtaining a target historical order, wherein the test instructions are used to test the test information of the server; and a first testing unit, configured to test the test information of each server in the current order based on a standard file of the target historical order, wherein the standard file is obtained after testing the test information of the first server produced in the target historical order.

[0016] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to execute the steps of any of the method embodiments at runtime.

[0017] According to one embodiment of this application, a server production testing system is also provided, including a memory, a server production testing device, and a computer program stored on the memory and executable on the server production testing device. When the server production testing device executes the computer program, it implements the steps of any of the server production testing methods described above.

[0018] This application utilizes a cleverly designed automatic order identification and merging mechanism to identify target historical orders that share the same configuration information and test instructions as the current order. Based on the standard files of the target historical orders, the test information for each server in the current order is tested. This eliminates the need for initial testing of the first server produced in the current order, thereby improving the efficiency and reducing the workload of initial testing. This solves the problem of high workload and wasted human resources caused by manual inspection of the first server in each order in related technologies. Furthermore, the automated testing of the test information for each server in the current order reduces human error rates and ensures high accuracy of the test information for each server in the current order. Attached Figure Description

[0019] Figure 1 A hardware structure block diagram of a mobile terminal for implementing a production testing method for a server, according to an embodiment of this application, is shown.

[0020] Figure 2 This is a flowchart illustrating a server production testing method according to an embodiment of this application;

[0021] Figure 3 This is a schematic diagram of a process for determining a target historical order according to an embodiment of this application;

[0022] Figure 4 This is a flowchart illustrating a specific server production testing method according to an embodiment of this application;

[0023] Figure 5 This is a flowchart illustrating another specific server production testing method according to an embodiment of this application;

[0024] Figure 6 This is a schematic diagram of the structure of a server production testing apparatus according to an embodiment of this application.

[0025] The above figures include the following reference numerals:

[0026] 102. Processor; 104. Memory; 106. Transmission device; 108. Input / output device. Detailed Implementation

[0027] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0029] First-run inspection: During server production at the factory, each order requires identifying the first server produced as the standard, which is called the first unit. This first unit serves as a reference for testing, and all other servers in the order are compared to it. Servers with discrepancies will trigger errors during testing. This first-run inspection ensures consistency in assembly, firmware, settings, and other information across the same order, guaranteeing uniform shipments. The manual inspection of the first unit is called the first-run inspection. This inspection checks whether the first unit meets the customer's requirements, based on the server assembly process and customized specifications.

[0030] Test instructions: These include the process standards and testing requirements for server assembly. Servers are assembled according to general process standards during production and tested according to the requirements of the test instructions during testing.

[0031] The methods and embodiments provided in this application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1This is a hardware structure block diagram of a mobile terminal for a server production testing method according to an embodiment of this application. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0032] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the server production testing method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0033] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0034] This embodiment provides a production testing method for a server running on the aforementioned mobile terminal. Figure 2 This is a flowchart of a server production testing method according to an embodiment of this application, such as... Figure 2 As shown, the production testing method for this server includes the following steps:

[0035] Step S202: Extract the test information of each server in the received current order. The test information includes firmware information, component information, motherboard programming information, backplane programming information, and customization information. The customization information is the special parameter information of the server set.

[0036] Specifically, during server production at the factory, the first unit of each order requires manual inspection to ensure server quality. This initial inspection involves checking various types of information (i.e., testing information), typically including firmware information, component information, motherboard programming information, backplane programming information, and customization information. Within a server, firmware generally includes BIOS (Basic Input / Output System), BMC (Baseboard Management Controller), CMOS (Complementary Metal-Oxide-Semiconductor, used to store BIOS settings), and OS (Operating System). The OS is used to manage and schedule server software, hardware, and data resources.

[0037] The specific process for extracting the test information of each server in the current order in step S202 above can be as follows:

[0038] 1) Summarize all candidate test information for various types of servers and categorize the candidate test information. For example, candidate test information can be checked one by one according to firmware, components, boards, customization information, BMCWeb, etc., to ensure the universality of the final extracted server test information.

[0039] 2) Classify candidate test information in another dimension, such as automated classification, to identify all candidate test information that can be checked automatically; to identify all candidate test information that can only be checked manually due to technical limitations; and to identify all candidate test information that requires special attention to draw the testers' attention.

[0040] 3) The test information of the finalized current order is processed into text, so that the test results can be texted through the system command line or a separately developed tool, which facilitates order comparison and manual analysis.

[0041] In other words, the server test information in step S202 above is test information that can be checked automatically.

[0042] In practical applications, the server models and other specifications required in the same order are generally identical. Therefore, multiple servers in the same order can have the same testing information. That is, the testing information for each server in the same order is identical. This further ensures that the servers in the same order are consistent after production.

[0043] Step S204: Based on the order information of the current order, determine the historical order that has the same configuration information and the same test instructions as the current order, and obtain the target historical order. The test instructions are used to test the test information of the server.

[0044] Specifically, the configuration information mentioned above can be related configuration information of the server. For example, the model and version information of the CPU (Central Processing Unit) in the server, the system information installed on the server, the server's memory information, and the running memory information, etc.

[0045] Step S206: Based on the standard file of the target historical order, test the test information of each server in the current order. The standard file is obtained after testing the test information of the first server produced in the target historical order.

[0046] In the aforementioned server production testing method, a target historical order with the same configuration information and test instructions as the current order is identified based on the order information of the current order. In other words, since the target historical order and the current order have the same configuration information and test instructions, they can be considered as the same order. Therefore, the standard file obtained from testing the first server in the target historical order can be used as the standard for testing the server information in the current order. This application, through a cleverly designed automatic order identification and merging mechanism, identifies the target historical order with the same configuration information and test instructions as the current order. Based on the standard file of the target historical order, the test information of each server in the current order is tested. This eliminates the need for initial testing of the first server produced in the current order, thereby improving the efficiency and reducing the workload of initial testing. This solves the problem of large workload and wasted human resources caused by manual inspection of the first server in each order in related technologies. Furthermore, by automating the testing of the test information of each server in the current order, the human error rate is reduced, ensuring a high accuracy of the test information for each server in the current order.

[0047] The execution entity for the above steps can be a mobile terminal, but is not limited to this. In practical applications, a first-time inspection software query system can be designed, and this system can be applied to the aforementioned server production testing method. Furthermore, the first-time inspection software query system can run on the aforementioned mobile terminal. Because the first-time inspection software query system will have a corresponding human-computer interaction interface, it provides better interaction for testers (i.e., first-time inspection personnel), further ensuring that the operation steps of the test process are relatively simple for testers.

[0048] The execution order of steps 202 and S204 can be interchanged; that is, step 204 can be executed first, and then step S202 can be executed.

[0049] In some embodiments, the order information in step S204 includes model information, key component information, and configuration number of each server in the current order. The model information represents the model of each server in the current order, the key component information represents the relevant information of key components of each server in the current order, and the configuration number represents at least the configuration information of each server in the current order. Subsequently, based on the priority order of the model information, key component information, and configuration number in the order information, target historical orders with the same configuration information and test instructions as the current order can be determined from multiple dimensions. This further ensures that target historical orders with the same configuration information and test instructions as the current order can be determined more accurately, and the probability of determining target historical orders with the same configuration information and test instructions as the current order is relatively high, reducing the probability of failure in determining target historical orders with the same configuration information and test instructions as the current order.

[0050] In the above embodiments, the model information of each server in the current order can be the customer's server requirement information, that is, the customer's original requirement information for the current order.

[0051] In the above embodiments, the key component information of each server in the current order can be the key material information used when the server is manufactured on the production side, such as the key materials required for assembling the server, such as the CPU, motherboard, BMC, etc., which is some information that can reveal the relevant configuration information of the server.

[0052] In the above embodiments, the configuration number of each server in the current order can be information reflecting the relevant configuration of the server.

[0053] To further identify target historical orders with the same configuration information and test instructions as the current order from multiple dimensions, in some specific implementation processes, step S204 may also include steps S2042, S2044, and S2046:

[0054] Step S2042 above: If there is a historical order with the same model information as the current order, the historical order with the same model information as the current order is identified as the target historical order;

[0055] Step S2044 above: If the target historical order cannot be determined based on the model information of the current order, and there is a historical order with the same key component information as the current order, the historical order with the same key component information as the current order is determined as a candidate historical order, and then, based at least on the test instructions corresponding to the test information of the server in the current order, it is determined whether to determine the candidate historical order as the target historical order.

[0056] Step S2046 above: If the target historical order cannot be determined based on the key component information of the current order, and there is a historical order with the same configuration number as the current order, the historical order with the same configuration number as the current order is determined as the candidate historical order, and then, based at least on the test instructions corresponding to the test information of the server in the current order, it is determined whether to determine the candidate historical order as the target historical order.

[0057] In one specific embodiment of this application, such as Figure 3 As shown, for target historical orders that have the same configuration information and test instructions as the current order, it can be determined from different dimensions whether a target historical order with the same configuration information and test instructions exists. As test instructions are continuously upgraded, some updated test instructions do not involve the process requirements and testing requirements for server assembly. To expand the scope of merged orders, a judgment can be made based on the requirements of the test instructions. If the test instructions do not change the process requirements and testing requirements for server assembly, they can also be judged as the same batch of orders. Specifically:

[0058] 1) Order Splitting: In actual server production, when the number of servers for a current order is large, the server production side will split the current order into multiple sub-orders, distributing these sub-orders to multiple different factories for simultaneous production. For this scenario, a target historical order with the same configuration information and testing instructions can be identified based on whether the customer's original requirements (i.e., the model information of the current order) are consistent with the original requirements of historical orders. For example, if the original requirements of the current order are the same as those of a historical order, then the customization requirements and testing instructions of that historical order will also be the same. Therefore, that historical order can be identified as the target historical order.

[0059] 2) Key Component Information & Test Instructions: For current orders that differ from the customer's original requirements, the key component information of the current order can be used to identify target historical orders with the same configuration information and test instructions. If the key component information of a historical order is consistent with that of the current order, it indicates that the two orders have the same configuration information. If the configuration information is identical, further judgment is made based on whether the test instructions are identical and whether server assembly process requirements and testing requirements are involved.

[0060] 3) Configuration Number & Test Instructions: If, based on the key component information and test instructions, a target historical order with the same configuration information and test instructions as the current order cannot be identified, the configuration number of the current order can be used to match historical orders with the same configuration information. This method can identify historical orders with alternative materials or substitution relationships. If such historical orders exist, further judgment is made based on whether the test instructions are the same and whether they involve server assembly process requirements and testing requirements.

[0061] The above three methods can match target historical orders with the same configuration information and the same test instructions based on priority, further realizing the multi-dimensional and high-probability identification of target historical orders with the same configuration information and the same test instructions as the current order.

[0062] In a specific implementation, step S2046 can also be implemented through the following steps: determining whether the test instructions corresponding to the test information of the server in the current order are the same as the test instructions corresponding to the candidate historical orders; if the test instructions corresponding to the test information of the server in the current order are the same as the test instructions corresponding to the candidate historical orders, the candidate historical order is determined as the target historical order; if the test instructions corresponding to the test information of the server in the current order are not the same as the test instructions corresponding to the candidate historical orders, determining whether the test instructions corresponding to the test information of the server in the current order are related to the assembly process standards and test requirements of the corresponding server; if the test instructions corresponding to the test information of the server in the current order are not related to the assembly process standards and test requirements of the corresponding server, the candidate historical order is determined as the target historical order. In this embodiment, when the test instructions in the candidate historical order are the same as the test instructions corresponding to each server in the current order, a target historical order with the same configuration information and the same test instructions as the current order is determined, so the candidate historical order can be determined as the target historical order. If the test instructions in the candidate historical order are different from the test instructions corresponding to each server in the current order, the decision on whether to identify the candidate historical order as the target historical order is made by checking whether the test instructions corresponding to each server in the current order are related to the assembly process standards and testing requirements of the server. This further ensures that the target historical order with the same configuration information and the same test instructions as the current order can be identified efficiently and with a high probability.

[0063] To further improve the efficiency of testing the test information of each server in the current order and to further reduce the workload of testing, in one embodiment of this application, step S206 can also be implemented by steps S2062, S2064 and S2066:

[0064] Step S2062 above: Compare each standard test information in the standard file of the target historical order with each test information of the server in the current order one by one.

[0065] Step S2064 above: If all the standard test information in the standard file of the target historical order is compared with all the test information of the target server and passes, it is determined that the target server has passed the test and the target server is one of the servers in the current order.

[0066] Step S2066 above: If a standard test information in the standard document containing the target historical order fails to pass the comparison with the corresponding test information of the target server, it is determined that the target server test has failed.

[0067] In practical applications, the testing is not limited to comparing the standard files of the target historical orders with the test information of each server in the current order one by one. Alternatively, automated scripts can be designed to execute corresponding test instructions, thereby testing the test information of each server in the current order. This further ensures the accuracy of the test results for the test information of each server in the current order.

[0068] In one specific embodiment, the production testing method of this application may further include step S208: if a standard test information in the standard file of the aforementioned target historical order fails to pass the comparison with the corresponding test information of the aforementioned target server, after determining that the target server test has failed, an early warning message is issued to notify the tester. In this way, after receiving the early warning message, the tester can manually check and retest or confirm the test information of the target server, further ensuring that the servers of the same order are consistent, and further improving the accuracy of testing the test information of the servers of the current order.

[0069] In the above embodiments, when testers receive warning information, they can also make reverse adjustments to the automated testing process according to the specific situation, thereby further improving the accuracy of testing the test information of each server for the current order.

[0070] Of course, in practical applications, a periodic sampling strategy can also be set. This way, through the feedback from periodic sampling, the test information in the testing process and the matching strategy of the target historical orders can be continuously and automatically tested. Through this positive feedback mechanism, the coverage of server production testing can be increased and the accuracy and effectiveness of server production testing can be improved.

[0071] The production testing method of this application may further include step S210, where, if no target historical order with the same configuration information and test instructions as the current order is identified based on the order information of the current order, the first server produced in the current order is tested based on the test information and test instructions of the first server produced in the current order. In other words, if no target historical order with a first server to be checked is found, the test instructions of the first server produced in the current order are used to test its corresponding test information, thus further ensuring the consistency of servers within the same order.

[0072] Of course, after matching a target historical order with a first-time inspection capability, and testing the test information of each server in the current order based on the standard documents of the target historical order, it is also possible to test whether the current order underwent a manual first-time inspection, and the test results of testing the test information of each server in the current order based on the standard documents of the target historical order. All test results are then fed back to the first-time inspection software query system. If no target historical order with a first-time inspection capability is matched, it is also necessary to test the test information of the first server produced in the current order through a manual first-time inspection. The test results and the method of manual first-time inspection are both fed back to the first-time inspection software query system.

[0073] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0074] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the server production testing method of this application will be described in detail below with reference to specific embodiments.

[0075] This embodiment relates to a specific method for production testing of a server, such as... Figure 4 As shown, it includes the following steps:

[0076] Step S1: Extract test information from each server in the received current order;

[0077] First, based on the scope of the initial inspection content, all candidate test information for each server can be listed. Second, all candidate test information is categorized. Distinguishing candidate test information according to different categories facilitates the expansion of subsequent candidate test information. Finally, the selected test information is transcribed into text, either through system commands or by developing proprietary tools, providing convenient raw data support for the subsequent automated inspection mechanism.

[0078] As products are continuously updated, the testing information required for inspection is constantly expanding, from assembly information to firmware information and configuration information. With the increasing refinement of component identification and testing, cable connection information can also be added. Through this in-depth identification of testing information, the goal of refined first-run inspection can be achieved.

[0079] The test information in the production testing method of this application is easily expandable, which can meet the requirements of continuous product evolution and meet the agile development of the first inspection of the server production end.

[0080] Step S2: Based on the order information of the current order, determine the target historical order that has the same configuration information and the same test instructions as the current order; for example, the target historical order with the same configuration information and the same test instructions as the current order can be determined by querying the database of the first inspection software query system.

[0081] By identifying the relationships between configuration information and test instructions across different factories and orders, target historical orders with identical configuration information and test instructions can be identified from different dimensions. First, consistency with upstream original orders can be checked based on the customer's original requirements. Second, the consistency of key components can be used to identify candidate historical orders with identical configuration information. If the key component information is the same, the configuration information is also consistent. For candidate historical orders with the same configuration information as the current order, the test instructions are then checked for consistency. Finally, since some materials are substitutable during order production, identical configuration information can be identified from the perspective of the order's configuration number. This maintained identification relationship can match candidate historical orders with identical configuration information.

[0082] During processing, this method automatically prompts the first-run inspection personnel whether the current order needs to be inspected. Based on the extraction of test information, and with identical configuration information and test instructions, the system can determine whether a similar order has been produced and inspected by the first runner, based on the inspection history of previous orders. In this way, orders are automatically merged, improving the efficiency of the first-run inspection and enhancing accuracy through automated processing.

[0083] Step S3: As Figure 5 As shown, once the target historical order is identified—that is, if the target historical order exists in the database of the first inspection software—the system automatically verifies the test information of each server in the current order based on the standard file of the target historical order. During the verification process, it is determined whether the verification of each server is successful. If the verification of all servers is successful, the order is considered complete. If the verification of any target server fails, a warning message is issued to prompt the testers to intervene manually and handle the situation.

[0084] If the target historical order is not identified, a manual first-run inspection is performed on the first server produced in the current order. The inspection record and related results are then updated in the database of the first-run inspection software query system.

[0085] Simultaneously, a manual first-run inspection is performed on the first server produced in the current order. This involves checking the first test information, the second test information, and so on, until the Nth test information is checked. Once the first-run inspection is complete, a standard file is generated. Based on this standard file, the test information of the other servers in the current order is checked one by one until the order is completed.

[0086] Step S4: Based on the order merging records and feedback from the server production end, perform data analysis on the first merging effect and optimize the merging strategy.

[0087] The inspection strategy is optimized periodically based on order merging records and manual sampling data. For example, the coverage percentage of order merging is checked based on order merging records. The inspection mechanism is optimized and the scope of merged orders is expanded by analyzing unmerged orders. Secondly, the effectiveness of merged orders is checked through gray-scale testing based on manual sampling results.

[0088] This embodiment also provides a server production testing apparatus, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0089] Figure 6 This is a schematic diagram of the structure of a server production testing apparatus according to an embodiment of this application, as shown below. Figure 6 As shown, the production testing apparatus includes:

[0090] Extraction unit 62 is used to extract test information of each server in the received current order. The test information includes firmware information, component information, motherboard programming information, backplane programming information and customization information. The customization information is the special parameter information of the server set.

[0091] Specifically, during server production at the factory, the first unit of each order requires manual inspection to ensure server quality. This initial inspection involves checking various types of information (i.e., testing information), typically including firmware information, component information, motherboard programming information, backplane programming information, and customization information. Within a server, firmware generally includes BIOS, BMC, CMOS, and OS. The OS is used to manage and schedule server software, hardware, and data resources.

[0092] The specific process of extracting test information from each server in the current order within the above extraction unit can be as follows:

[0093] 1) Summarize all candidate test information for various types of servers and categorize the candidate test information. For example, candidate test information can be checked one by one according to firmware, components, boards, customization information, BMCWeb, etc., to ensure the universality of the final extracted server test information.

[0094] 2) Classify candidate test information in another dimension, such as automated classification, to identify all candidate test information that can be checked automatically; to identify all candidate test information that can only be checked manually due to technical limitations; and to identify all candidate test information that requires special attention to draw the testers' attention.

[0095] 3) The test information of the finalized current order is processed into text, so that the test results can be texted through the system command line or a separately developed tool, which facilitates order comparison and manual analysis.

[0096] In other words, the server test information in the above extraction unit is test information that can be checked automatically.

[0097] In practical applications, the server models and other specifications required in the same order are generally identical. Therefore, multiple servers in the same order can have the same testing information. That is, the testing information for each server in the same order is identical. This further ensures that the servers in the same order are consistent after production.

[0098] The determining unit 64 is used to determine, based on the order information of the current order, a historical order that has the same configuration information and the same test instructions as the current order, and obtain the target historical order. The test instructions are used to test the test information of the server.

[0099] Specifically, the configuration information mentioned above can be related to the server's configuration information. For example, the CPU model and version information, the system information installed on the server, the server's memory information, and its running memory information, etc.

[0100] The first test unit 66 is used to test the test information of each of the servers in the current order based on the standard file of the target historical order. The standard file is obtained after testing the test information of the first server produced in the target historical order.

[0101] In the aforementioned server production testing device, a cleverly designed automatic order identification and merging mechanism identifies target historical orders with the same configuration information and test instructions as the current order. Based on the standard file of the target historical order, the test information of each server in the current order is tested. This eliminates the need for initial testing of the first server in the current order, thereby improving the efficiency and reducing the workload of initial testing. This solves the problem of high workload and wasted human resources caused by manual inspection of the first server in each order in related technologies. Furthermore, the automated testing of the test information of each server in the current order reduces human error rates and ensures a high accuracy of the test information for each server in the current order.

[0102] In some embodiments, the order information includes model information, key component information, and configuration number of each server in the current order. The model information represents the model of each server in the current order, the key component information represents the relevant information of key components of each server in the current order, and the configuration number represents at least the configuration information of each server in the current order. Subsequently, based on the priority order of the model information, key component information, and configuration number in the order information, target historical orders with the same configuration information and test instructions as the current order can be determined from multiple dimensions. This further ensures that target historical orders with the same configuration information and test instructions as the current order can be determined more accurately, and the probability of determining target historical orders with the same configuration information and test instructions as the current order is relatively high, reducing the probability of failure in determining target historical orders with the same configuration information and test instructions as the current order.

[0103] In the above embodiments, the model information of each server in the current order can be the customer's server requirement information, that is, the customer's original requirement information for the current order.

[0104] In the above embodiments, the key component information of each server in the current order can be the key material information used when the server is manufactured on the production side, such as the key materials required for assembling the server, such as the CPU, motherboard, BMC, etc., which is some information that can reveal the relevant configuration information of the server.

[0105] In the above embodiments, the configuration number of each server in the current order can be information reflecting the relevant configuration of the server.

[0106] In order to further identify target historical orders that have the same configuration information and the same test instructions as the current order from multiple dimensions, in some specific implementation processes, the above-mentioned determining unit includes a first determining module, a second determining module, and a third determining module. The first determining module is used to determine the historical order with the same model information as the current order as the target historical order when there is a historical order with the same model information as the current order. The second determining module is used to determine the historical order with the same key component information as the current order as a candidate historical order when the target historical order cannot be determined based on the model information of the current order, and there is a historical order with the same key component information as the current order, and then determines whether to determine the candidate historical order as the target historical order based at least on the test instructions corresponding to the test information of the server in the current order. The third determining module is used to determine the historical order with the same configuration number as the current order as the candidate historical order when the target historical order cannot be determined based on the key component information of the current order, and there is a historical order with the same configuration number as the current order, and then determines whether to determine the candidate historical order as the target historical order based at least on the test instructions corresponding to the test information of the server in the current order.

[0107] In one specific embodiment of this application, such as Figure 3As shown, for target historical orders that have the same configuration information and test instructions as the current order, it can be determined from different dimensions whether a target historical order with the same configuration information and test instructions exists. As test instructions are continuously upgraded, some updated test instructions do not involve the process requirements and testing requirements for server assembly. To expand the scope of merged orders, a judgment can be made based on the requirements of the test instructions. If the test instructions do not change the process requirements and testing requirements for server assembly, they can also be judged as the same batch of orders. Specifically:

[0108] 1) Order Splitting: In actual server production, when the number of servers for a current order is large, the server production side will split the current order into multiple sub-orders, distributing these sub-orders to multiple different factories for simultaneous production. For this scenario, a target historical order with the same configuration information and testing instructions can be identified based on whether the customer's original requirements (i.e., the model information of the current order) are consistent with the original requirements of historical orders. For example, if the original requirements of the current order are the same as those of a historical order, then the customization requirements and testing instructions of that historical order will also be the same. Therefore, that historical order can be identified as the target historical order.

[0109] 2) Key Component Information & Test Instructions: For current orders that differ from the customer's original requirements, the key component information of the current order can be used to identify target historical orders with the same configuration information and test instructions. If the key component information of a historical order is consistent with that of the current order, it indicates that the two orders have the same configuration information. If the configuration information is identical, further judgment is made based on whether the test instructions are identical and whether server assembly process requirements and testing requirements are involved.

[0110] 3) Configuration Number & Test Instructions: If, based on the key component information and test instructions, a target historical order with the same configuration information and test instructions as the current order cannot be identified, the configuration number of the current order can be used to match historical orders with the same configuration information. This method can identify historical orders with alternative materials or substitution relationships. If such historical orders exist, further judgment is made based on whether the test instructions are the same and whether they involve server assembly process requirements and testing requirements.

[0111] The above three methods can match target historical orders with the same configuration information and the same test instructions based on priority, further realizing the multi-dimensional and high-probability identification of target historical orders with the same configuration information and the same test instructions as the current order.

[0112] In a specific implementation, the second or third determining module may further include a first determining submodule, a second determining submodule, a third determining submodule, and a fourth determining submodule. The first determining submodule is used to determine whether the test instruction corresponding to the server's test information in the current order is the same as the test instruction corresponding to the candidate historical order. The second determining submodule is used to determine the candidate historical order as the target historical order if the test instruction corresponding to the server's test information in the current order is the same as the test instruction corresponding to the candidate historical order. The third determining submodule is used to determine whether the test instruction corresponding to the server's test information in the current order is related to the assembly process standards and test requirements of the corresponding server if the test instruction corresponding to the server's test information in the current order is different from the test instruction corresponding to the candidate historical order. The fourth determining submodule is used to determine the candidate historical order as the target historical order if the test instruction corresponding to the server's test information in the current order is unrelated to the assembly process standards and test requirements of the corresponding server. In this embodiment, if the test instructions in the candidate historical order are identical to the test instructions corresponding to each server in the current order, then the target historical order with the same configuration information and test instructions as the current order is identified, and thus the candidate historical order can be designated as the target historical order. If the test instructions in the candidate historical order differ from those corresponding to each server in the current order, the decision to designate the candidate historical order as the target historical order is further made by checking whether the test instructions corresponding to each server in the current order are related to the server assembly process standards and testing requirements. This further ensures that the target historical order with the same configuration information and test instructions as the current order can be identified efficiently and with a high probability.

[0113] To further improve the efficiency of testing the test information of each server in the current order and to further reduce the testing workload, in one embodiment of this application, the first testing unit includes a comparison module, a fourth determination module, and a fifth determination module. The comparison module compares each standard test information in the standard file of the target historical order with each test information of each server in the current order. The fourth determination module determines that the target server has passed the test, and that the target server is one of the servers in the current order, if all comparisons between the standard test information in the standard file of the target historical order and the test information of the target server are successful. The fifth determination module determines that the target server has failed the test, if one standard test information in the standard file of the target historical order fails the comparison with the corresponding test information of the target server.

[0114] In practical applications, the testing is not limited to comparing the standard files of the target historical orders with the test information of each server in the current order one by one. Alternatively, automated scripts can be designed to execute corresponding test instructions, thereby testing the test information of each server in the current order. This further ensures the accuracy of the test results for the test information of each server in the current order.

[0115] In one specific embodiment, the production testing apparatus of this application may further include an issuing unit, used to issue a warning message after determining that the target server test has failed when a standard test message in the standard file of the aforementioned target historical order fails to pass a comparison with the corresponding test message of the aforementioned target server. This is to alert the tester, so that after receiving the warning message, the tester can manually check or retest or confirm the test message of the target server, further ensuring that the servers of the same order are consistent and further improving the accuracy of testing the test message of the servers of the current order.

[0116] In the above embodiments, when testers receive warning information, they can also make reverse adjustments to the automated testing process according to the specific situation, thereby further improving the accuracy of testing the test information of each server for the current order.

[0117] Of course, in practical applications, a periodic sampling strategy can also be set. This way, through the feedback from periodic sampling, the test information in the testing process and the matching strategy of the target historical orders can be continuously and automatically tested. Through this positive feedback mechanism, the coverage of server production testing can be increased and the accuracy and effectiveness of server production testing can be improved.

[0118] The production testing apparatus of this application may further include a second testing unit, used to test the first server produced in the current order, based on the test information and test instructions of the first server produced in the current order, when no target historical order with the same configuration information and test instructions as the current order is identified based on the order information of the current order. In other words, if no target historical order with the first server to be checked is found, the test instructions of the first server produced in the current order are used to test its corresponding test information, thus further ensuring the consistency of servers within the same order.

[0119] Of course, after matching a target historical order with a first-time inspection capability, and testing the test information of each server in the current order based on the standard documents of the target historical order, it is also possible to test whether the current order underwent a manual first-time inspection, and the test results of testing the test information of each server in the current order based on the standard documents of the target historical order. All test results are then fed back to the first-time inspection software query system. If no target historical order with a first-time inspection capability is matched, it is also necessary to test the test information of the first server produced in the current order through a manual first-time inspection. The test results and the method of manual first-time inspection are both fed back to the first-time inspection software query system.

[0120] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0121] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when it is run.

[0122] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0123] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0124] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0125] Embodiments of this application also provide a server production testing system. The production testing system includes a memory, a server production testing apparatus, and a computer program stored in the memory and executable on the server production testing apparatus. When the server production testing apparatus executes the computer program, it implements the steps of any of the aforementioned server production testing methods.

[0126] The aforementioned production testing system includes a server production testing device. This production testing device can be used to execute any of the aforementioned server production testing methods. The production testing method of this application, through a cleverly designed automatic order identification and merging mechanism, identifies target historical orders with the same configuration information and test instructions as the current order. Based on the standard file of the target historical order, the test information of each server in the current order is tested. This eliminates the need for initial testing of the first server in the current order, thereby improving the efficiency and reducing the workload of initial testing. This solves the problem in related technologies where manual inspection of the first server in each order results in a large workload and waste of human resources. Furthermore, by automating the testing of the test information of each server in the current order, the human error rate is reduced, ensuring a high accuracy of the test information for each server in the current order.

[0127] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0128] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0129] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for production testing of a server, characterized in that, include: Extract the test information of each server in the received current order. The test information includes firmware information, component information, motherboard programming information, backplane programming information, and customization information. The customization information is the special parameter information of the server that is set. Based on the order information of the current order, historical orders with the same configuration information and the same test instructions as the current order are identified to obtain the target historical order. The test instructions are used to test the test information of the server. The order information includes the model information, key component information, and configuration number of each server in the current order. The model information is used to represent the model of each server in the current order. The key component information is used to represent the relevant information of the key components of each server in the current order. The configuration number is used to represent at least the configuration information of each server in the current order. The model information has the highest priority, and the configuration number has the lowest priority. Based on the standard file of the target historical order, the test information of each server in the current order is tested. The standard file is obtained after testing the test information of the first server that produced the target historical order. Based on the order information of the current order, identify historical orders that have the same configuration information and the same test instructions as the current order to obtain target historical orders, including: If a historical order with the same model information as the current order exists, the historical order with the same model information as the current order shall be identified as the target historical order. If the target historical order cannot be determined based on the model information of the current order, and there is a historical order with the same key component information as the current order, the historical order with the same key component information as the current order shall be identified as a candidate historical order. Then, based at least on the test instructions corresponding to the test information of the server in the current order, it shall be determined whether to identify the candidate historical order as the target historical order. If the target historical order cannot be determined based on the key component information of the current order, and there is a historical order with the same configuration number as the current order, the historical order with the same configuration number as the current order shall be determined as the candidate historical order. Then, based at least on the test instructions corresponding to the test information of the server in the current order, it shall be determined whether to determine the candidate historical order as the target historical order.

2. The production testing method according to claim 1, characterized in that, Based at least on the test instructions corresponding to the test information of the server in the current order, determine whether to identify the candidate historical order as the target historical order, including: Determine whether the test instruction corresponding to the test information of the server in the current order is the same as the test instruction corresponding to the candidate historical order; If the test instruction corresponding to the test information of the server in the current order is the same as the test instruction corresponding to the candidate historical order, the candidate historical order will be determined as the target historical order. If the test instructions corresponding to the test information of the server in the current order are different from the test instructions corresponding to the candidate historical order, determine whether the test instructions corresponding to the test information of the server in the current order are related to the assembly process standards and test requirements of the corresponding server. If the test instructions corresponding to the test information of the server in the current order are not related to the assembly process standards and test requirements of the server, the candidate historical order is determined as the target historical order.

3. The production testing method according to claim 1, characterized in that, Based on the standard file of the target historical orders, the test information of each server in the current order is tested, including: Each standard test information in the standard file of the target historical order is compared one by one with each test information of each server in the current order; If all the standard test information in the standard file containing the target historical order passes the comparison with all the test information of the target server, the target server is determined to have passed the test, and the target server is one of the servers in the current order; If a standard test message in the standard file containing the target historical order fails a comparison with the corresponding test message of the target server, the target server test is determined to have failed.

4. The production testing method according to claim 3, characterized in that, If a standard test message in the standard file containing the target historical order fails a comparison with a corresponding test message on the target server, and the target server test fails, the production testing method further includes: Issue an early warning message to alert the testers.

5. The production testing method according to any one of claims 1 to 4, characterized in that, The production testing method also includes: If, based on the order information of the current order, no target historical order with the same configuration information and the same test instructions as the current order is identified, the first server produced in the current order is tested based on the test information and test instructions of the first server produced in the current order.

6. A server production testing apparatus, characterized in that, include: The extraction unit is used to extract the test information of each server in the received current order. The test information includes firmware information, component information, motherboard programming information, backplane programming information, and customization information. The customization information is the special parameter information of the server that is set. The determining unit is configured to determine, based on the order information of the current order, a historical order that has the same configuration information and the same test instructions as the current order, to obtain a target historical order. The test instructions are used to test the test information of the server. The order information includes the model information, key component information, and configuration number of each server in the current order. The model information is used to characterize the model of each server in the current order. The key component information is used to characterize the relevant information of the key components of each server in the current order. The configuration number is used to characterize at least the configuration information of each server in the current order. The model information has the highest priority, and the configuration number has the lowest priority. The first testing unit is used to test the test information of each server in the current order based on the standard file of the target historical order. The standard file is obtained after testing the test information of the first server that produced the target historical order. The determining unit includes: The first determining module is used to determine the historical order with the same model information as the current order as the target historical order when there is a historical order with the same model information as the current order. The second determining module is used to determine, when the target historical order cannot be determined based on the model information of the current order, and there is a historical order with the same key component information as the current order, the historical order with the same key component information as the current order is determined as a candidate historical order, and then, based at least on the test instructions corresponding to the test information of the server in the current order, it is determined whether to determine the candidate historical order as the target historical order. The third determining module is used to determine the candidate historical order when the target historical order cannot be determined based on the key component information of the current order, and there is a historical order with the same configuration number as the current order. Then, based at least on the test instructions corresponding to the test information of the server in the current order, it determines whether to determine the candidate historical order as the target historical order.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the production testing method for the server according to any one of claims 1 to 5.

8. A server production testing system, comprising a memory, a server production testing device, and a computer program stored in the memory and executable on the server production testing device, characterized in that, When the production testing device for the server executes the computer program, it implements the steps of the production testing method for the server according to any one of claims 1 to 5.

Images