Test order management method and device, electronic equipment and storage medium

Abstract

The invention discloses a test order management method and device, electronic equipment and a storage medium, and relates to the technical field of electrical digital data processing, and the method comprises the steps: carrying out the regular inspection of an order list of to-be-delivered orders, so as to screen out to-be-established orders which do not establish a test item list file and test orders which have established a test item list file, and carrying out the verification of the to-be-established orders. For the to-be-established order, the test items can be selected according to the order information and the test item selection rule, and then the corresponding test item list file is generated according to the selection result, so that the order can be subjected to product testing according to the content of the test item list file, and the problem that the test efficiency is high in the related technology is solved. The technical problems that the test items of the orders are easy to leak or redundancy and the test quality of products is affected in the test items are adjusted according to experience are solved, and the technical effects that the test items are automatically generated, the test items of each order can meet the test requirements of the products, the test efficiency is improved, and the labor cost is reduced are achieved.

Description

Technical Field

[0001] The present application relates to the technical field of electronic digital data processing, and in particular to a test order management method, device, electronic device and storage medium. Background Art

[0002] In the field of server factory production, automated diagnostic software is generally used to detect servers leaving the factory. The diagnostic software divides the server test into multiple test items. The test items required for the platform used by different models are different, and the test items for different types of materials may also be different. When a certain model is inspected and tested, diagnostic tests are performed according to the test item list data of this model (for individual special orders, a test item list can be established according to the order). In related technologies, the test item list can be manually copied with reference to other models during the project development phase, and then the content of the test item list can be adjusted based on experience according to development needs. It is easy to miss some items, and when the initial settings are relatively comprehensive, the test item entries will be too redundant and cannot accurately reflect the test items that have actually been tested for this order. This not only affects the test efficiency, but also causes troubles for log query and problem diagnosis, and urgently needs to be improved. Summary of the Invention

[0003] The present application provides a test order management method, device, electronic device and storage medium to at least solve the technical problem in the related art that adjusting the test items based on experience can easily lead to omissions or redundancies in the test items of the order, thereby affecting the test quality of the product.

[0004] The present application provides a test order management method, comprising: inspecting a list of to-be-delivered orders within a preset time period at preset intervals to identify at least one to-be-delivered order for which a test item list file has not been established and multiple test orders for which test item list files have been established; determining multiple test items for any to-be-delivered order by combining pre-established test item selection rules and order information of any to-be-delivered order; generating a test item list file for any to-be-delivered order using the multiple test items, and modifying any to-be-delivered order for which a test item list file has been established into a test order, until no to-be-delivered order exists in the list of to-be-delivered orders.

[0005] The present application also provides a test order management device, including: an inspection module, used to inspect the list of to-be-delivered orders within a preset time period at preset intervals to identify at least one to-be-built order for which a test item list file has not been established and multiple test orders for which test item list files have been established; a determination module, used to determine multiple test items of any to-be-built order in combination with pre-established test item selection rules and order information of any to-be-built order; a management module, used to generate a test item list file for any to-be-built order using multiple test items, and modify any to-be-built order for which a test item list file has been established into a test order, until no to-be-built order exists in the list of to-be-delivered orders.

[0006] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned test order management methods when executing the computer program.

[0007] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned test order management methods are implemented.

[0008] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned test order management methods when executed by a processor.

[0009] Through this application, by regularly inspecting the order list of orders to be delivered, orders to be built that have not yet established test item list files and test orders that have already established test item list files are screened out. For orders to be built, test items can be selected based on order information and test item selection rules, and then the corresponding test item list file can be generated based on the selection results, so that the order can be tested for product according to the content of the test item list file. This solves the technical problem in related technologies that adjusting the test items based on experience can easily lead to omissions or redundancy in the order's test items, affecting the test quality of the product. It achieves the technical effect of automatic generation of test items, so that the test items of each order can meet the product testing requirements, improve testing efficiency, and reduce labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0011] Figure 1 A flowchart of a test order management method provided in an embodiment of the present application;

[0012] Figure 2 A schematic diagram of the principle of test item selection rules provided according to one embodiment of the present application;

[0013] Figure 3 A schematic diagram illustrating the principles of a test order management method provided according to one embodiment of the present application;

[0014] Figure 4 A schematic diagram of the rule table modification principle provided according to an embodiment of the present application;

[0015] Figure 5A schematic diagram of the structure of a test order management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0017] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0018] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0019] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the test order management method depends, the specific application environment architecture or specific hardware architecture is described herein.

[0020] For example, the architecture applied in the embodiment of the present application may include: an order inspection module and an order test item list generation module.

[0021] The order inspection module can perform regular inspections of orders to be delivered, query orders to be delivered in the most recent period, and for orders to be built that do not have a test item list file, call the order test item list generation module to generate a test item list file for the order to be built; in addition, for test orders that already have a test item list file, first check whether the order time of the test order exceeds a certain period. If so, check whether the machines corresponding to the test order have completed the test. If so, move the test item list file corresponding to the test order to the history directory. For test orders with a shorter time, do not check the corresponding machine status to avoid frequent operations causing greater pressure on the database.

[0022] The order test item list generation module can pre-establish a test item name management table and a test item selection rule table to manage all test items and establish rules for selecting test items; obtain relevant information about the order, such as model, customer, order BOM (Bill of Materials), etc., and then based on the above information, filter out all qualified test items from the rule table, remove duplicates and sort, and finally generate the final required test item list file according to the standard template.

[0023] Based on the above structure, the embodiment of the present application can automatically select appropriate test items for the order and automatically check whether the order has completed the test, reducing manual pressure, improving testing efficiency, facilitating problem tracing, and realizing intelligent order management.

[0024] The embodiment of the present application provides a test order management method, such as Figure 1 As shown, the test order management method includes the following steps:

[0025] In step S101 , a list of to-be-delivered orders within a preset period is inspected at preset intervals to identify at least one to-be-delivered order for which no test item list file has been established and a plurality of test orders for which test item list files have been established.

[0026] During the actual implementation process, the present application can be implemented to regularly inspect orders that have not yet been delivered. For example, multiple fixed inspection times are set every day, so that when the inspection time arrives, all orders in the list of orders to be delivered can be identified to query whether there is a specifically named file representing the test item list file in the test item list directory, such as a file named listid_n. If the file is identified, it is determined to be a test order, and if it is not identified, it is determined to be an order to be created.

[0027] Among them, in order to reduce the amount of data for each inspection and speed up the inspection, the embodiment of the present application can only inspect the most recent period of time each time, such as orders within 5 days.

[0028] Furthermore, according to the orders to be created and the test orders, the embodiments of the present application can implement different management solutions.

[0029] Through scheduled inspections, recent orders can be automatically imported, and then test orders that have established test item list files, are in the testing process, and are waiting to be established orders without established test item list files can be found. This avoids manual searches that may cause misjudgments or duplication of work, and reduces labor costs.

[0030] Optionally, in one embodiment of the present application, after inspecting the list of pending orders within a preset time period at preset intervals, it also includes: if no test order is identified in the list of pending orders, obtaining multiple historical test orders obtained during the last inspection; confirming the corresponding order delivery date based on the order information of multiple historical test orders, and using the order delivery date to confirm whether there is at least one historical test order whose delivery date is after the current inspection time; if there is at least one historical test order, generating an order recognition error reminder.

[0031] It is understandable that in the event of errors in order identification, if the problem is not discovered in time, it may affect the arrangement of a large number of orders in batches.

[0032] In order to avoid the above problems, the embodiments of the present application can combine historical data backtracking with automated inspection logic to achieve active early warning of test order identification omissions or identification failures.

[0033] The embodiment of the present application can scan the current list of pending orders to verify whether it contains records marked as test orders. If no test order is identified, the historical data backtracking mechanism is triggered to extract all historical test order information within the last inspection cycle, parse its preset delivery time (such as order creation time, promised delivery date, etc.), and build a delivery timeline to compare the delivery date of the historical test order with the current inspection timestamp: if there is a test order with a future delivery date, it is determined that the system has missed identifying the test order in the current pending delivery list, and an order recognition error reminder is generated; if there is no test order with a future delivery date, it is determined that the historical test order has expired and no intervention is required.

[0034] When a reminder is triggered, the embodiment of the present application can also automatically record an exception log and push it to the operation and maintenance management platform or alarm queue.

[0035] The embodiments of the present application can combine the double-layer verification of real-time data and historical status to avoid missed test orders due to problems such as instantaneous data synchronization delays and label omissions; through dynamic comparison of delivery timestamps, it is compatible with complex scenarios such as periodic test orders and long-term unclosed orders, reducing the maintenance cost of static rule configuration; integrating the integrated process of alarm generation, log recording, and notification distribution, reducing the frequency of manual inspections and shortening fault response time.

[0036] Optionally, in one embodiment of the present application, after identifying at least one order to be established for which a test item list file has not been established, it also includes: matching a historical test item list file that meets preset conditions in a historical directory based on the order information of any order to be established; and using the historical test item list file as a test item list file for any order to be established.

[0037] In some embodiments, for customers with whom we frequently cooperate, the order contents of their multiple orders may be consistent. In this case, repeatedly selecting test items will waste computing resources. The embodiments of the present application can match historical test item list files based on order information, thereby directly calling historically generated test item list files to speed up data processing.

[0038] In step S102, a plurality of test items of any order to be created are determined by combining pre-built test item selection rules and order information of any order to be created.

[0039] In related technologies, there may be cases where test items are missing. For example, some test items are not required during project development but are required during production. For example, after a certain model has been produced for a period of time, the server shipped to Customer A needs to run a customized diagnostic program customized by Customer A. However, the test item list for this model does not contain the corresponding CUSTOMER test item, resulting in the omission of the customized diagnostic program customized by Customer A, which may cause customer complaints.

[0040] There may also be redundant test items. For example, the test item list is comprehensive and includes all test items. Although a judgment is generally made in the code, and test items that are not needed for the test model are skipped after entering the test item details, all test items in the test item list will be displayed in the test item test details. When the GPU (Graphics Processing Unit) model is actually shipped without a GPU, the test item details will still display the test items for the GPU stress test. When querying the log, some analysis is required, such as the difference between the start and end time of the test item, or the log information printed by this test item, and then it is determined that the test items for the GPU stress test have not been actually tested. In addition, different customers require different test items. Suppose customer A needs test item A and customer B needs test item B. A certain model happens to be shipped to customers A and B. If the test item list is designed to include both test item A and test item B, the log seen by customer B will also include test item A, which will affect the customer experience.

[0041] In order to avoid the above problems, the embodiments of the present application can combine the test item selection rules and the separate order information of each order to realize the automated extraction of customized test items, so as to avoid errors and omissions and improve the user experience.

[0042] As a possible implementation method, for the order to be created, the embodiment of the present application can select corresponding test items to facilitate the subsequent generation of a test item list file.

[0043] Among them, order information may include customer information, material type, material quantity, machine information, etc. The test item selection rules can be determined according to the application party. For example, when applied to server testing, the selection rules may include whether the test items comply with the principle of reasonable resource allocation, whether the technical specifications match, whether the test permissions match the order information, etc.

[0044] Optionally, in one embodiment of the present application, multiple test items for any order to be established are determined in combination with pre-built test item selection rules and order information of any order to be established, including: based on the order information of any order to be established, using the test item selection rules to traverse the pre-built rule table to match multiple candidate test items for any order to be established; deleting duplicate test items from the multiple candidate test items to obtain multiple test items.

[0045] In some embodiments, order information can be used to match in a pre-built rule table, and successfully matched test items can be used as candidate test items until all order information is matched. Duplicate test items are found from multiple candidate test items and deleted, thereby obtaining multiple test items.

[0046] For example, an embodiment of the present application can first construct a rule table that meets the server testing requirements. The rule table covers all test items required for server testing, such as hardware compatibility testing, performance benchmark testing, etc. The rule table can also include associated test items, execution priority and other content.

[0047] The test item selection rule can be understood as the judgment criteria when using order information to match the test items in the rule table.

[0048] The embodiment of the present application can parse order information to extract key fields such as customers, materials, machines, etc.

[0049] The key fields are used to match in the rule table, and the test item selection rules are used to determine whether a match can be made, thereby obtaining candidate test items.

[0050] The embodiment of the present application improves the matching speed through conditional precompilation, and it is actually measured that a thousand-level rule table can be traversed in milliseconds; when a new server model or test requirement is added, it is only necessary to update the rule table instead of modifying the code to achieve dynamic adaptation; after deduplication, repeated execution of the same test items is avoided, saving test environment resources; the rule table is configured through the management interface, lowering the operation threshold for operation and maintenance personnel; in addition, the embodiment of the present application can also record the triggering status of each rule and the change history of the test item to support auditing and problem backtracking.

[0051] Optionally, in one embodiment of the present application, the test item selection rules include: skipping candidate test items that do not meet preset effectiveness conditions; using the model to match the first candidate test item when the order information contains model information or the model meets the preset fuzzy matching conditions; using the customer to match the second candidate test item when the order information contains customer information or the customer's customer information meets the preset exact matching conditions; matching the third candidate test item based on the material code and / or material type when the order information contains material code and / or material type; matching the fourth candidate test item when the order information does not contain material code and material type.

[0052] The test item selection rules of the embodiment of the present application can be as follows Figure 2 As shown, the embodiment of the present application can first determine whether the test item to be selected can be effective in the corresponding order to be created. If it cannot be effective, it will be skipped. If it can be effective, there is a candidate test item;

[0053] The embodiment of the present application can determine whether the order information includes model information (whether the model is empty) or model information that can be fuzzy matched. If the model can be identified, the corresponding candidate test item is matched according to the model;

[0054] The embodiment of the present application can determine whether the order information includes customer information (whether the customer is empty). If customer information exists, the customer information is used for matching to obtain subsequent test items.

[0055] The embodiment of the present application can determine whether the order information includes the material code and material type (the material code and material type are not empty). If both are included, the corresponding candidate test items are matched in combination with the material code and material type.

[0056] The embodiment of the present application can determine whether the order information includes the material type (the material type is not empty). If included, the corresponding candidate test item is matched according to the material type;

[0057] The embodiment of the present application can determine whether the order information includes a material code (the material code is not empty). If included, the corresponding candidate test item is matched according to the material code;

[0058] The embodiment of the present application can determine whether the order information does not include the material code and material type (the material code and material type are both empty). If not, the corresponding candidate test item is matched.

[0059] In an embodiment of the present application, the test item selection rules are used to achieve more efficient traversal through pre-compiled trigger conditions and priority mapping; through the mapping relationship between the rules and the key fields of the requirements, it is ensured that each test item corresponds to a clear functional point or non-functional indicator.

[0060] In step S103, a test item list file of any to-be-created order is generated using multiple test items, and any to-be-created order for which a test item list file has been created is modified into a test order until no to-be-created order exists in the to-be-delivered order list.

[0061] Furthermore, the embodiment of the present application can use multiple test items to generate a test item list file, wherein the embodiment of the present application can also sort the multiple test items according to the priority set in the rule table.

[0062] After obtaining the test item list file, the embodiment of the present application can modify the order to be built into a test order, and then generate a test item list file for the next order to be built until all orders to be built are modified.

[0063] The embodiment of the present application can actively inspect recent orders based on a scheduled inspection mechanism, trigger the start-up generation module for orders without a test item list file, and when the test item list is generated, accurately screen and deduplicate sorting is performed through a preset test item rule table to adapt to the complex configuration differences of the factory, and finally generate a test item list file according to a standardized template.

[0064] Optionally, in one embodiment of the present application, it also includes: filtering out multiple abnormal orders that exceed a preset test time from multiple test orders; confirming the test status of all machines in any abnormal order; if the test status of all machines is a passed test status, removing any abnormal order from the order list, and transferring the test item list file of any abnormal order to the history directory, otherwise, ignoring any abnormal order until all abnormal orders are confirmed.

[0065] For test orders, the embodiment of the present application can determine whether there is an abnormality based on the order information, such as whether the test time of the test order exceeds a certain period of time (such as 10 days). After exceeding a certain period of time, it can be determined that the test order may have been tested but not archived. At this time, the embodiment of the present application can confirm the test status of each machine involved in the abnormal order based on the order information. If all machines have completed the test, the abnormal order is judged to be completed, and it is archived, and the test item list file is transferred to the history directory. If there is at least one machine that has not completed the test, it can be confirmed that the abnormal order has not yet ended, and the abnormal order can be ignored at this time.

[0066] The embodiment of the present application can judge all abnormal orders until all abnormal orders are confirmed.

[0067] By checking the order machine status of overdue orders and confirming the dynamic archiving of historical files, the embodiment of the present application can avoid high-frequency access pressure on the database.

[0068] Optionally, in one embodiment of the present application, after ignoring any abnormal order, it also includes: determining whether any abnormal order is overdue based on the order information of any abnormal order; if overdue, locating all machines to be tested in any abnormal order that are not in the test pass state; matching the corresponding overdue policy based on the machine to be tested, the overdue duration of any abnormal order and the order list, and arranging a queue-jumping test for the machine to be tested based on the overdue policy.

[0069] The embodiment of the present application can confirm whether the abnormal order is overdue based on the delivery time field in the order information. In the case of overdue, the embodiment of the present application can locate all machines in the abnormal order that are being tested or have not been tested.

[0070] Based on the number of machines being tested, the number of machines not yet tested, and the length of the overdue period, the embodiment of the present application can combine the delivery dates, material usage expectations, test item arrangements, etc. of all orders in the order list that are awaiting testing (test orders) and have not yet started testing (orders to be built), and match the corresponding overdue strategy. For example, orders with lower dynamic priority (large redundancy in delivery date, no urgent material demand, or sufficient materials) can be put in the back row, and limited resources can be supplied to overdue orders.

[0071] The embodiments of the present application can effectively reduce the risk of default and achieve dynamic adaptation of resource priorities.

[0072] Combine Figure 2-Figure 4 As shown, the working principle of the test order management method of the embodiment of the present application is described in detail with an embodiment.

[0073] like Figure 3 As shown, the embodiment of the present application may include the following steps:

[0074] Step S301, scheduled inspection. The embodiment of the present application can be started on a scheduled basis, and the inspection orders are inspected at fixed times of 0:00, 6:00, 12:00, and 18:00 every day.

[0075] Step S302, List table obtains the latest order->A. In the embodiment of the present application, the order table list in the database can be queried, and the orders in the last 5 days can be queried according to the order time starttime in the list table, and the order number listid can be recorded in file A.

[0076] Step S303: traverse the order numbers in file A. Obtain the order numbers listid_n in file A one by one, and use the order numbers listid_n to determine whether a test item list file exists.

[0077] Step S304 determines whether the test item list already exists. The program checks the test item list directory to see if a file named listid_n exists. If so, the test item list file corresponding to this order number has been generated. The program then proceeds to step S307 and continues to obtain the next order number in file A. Otherwise, the program proceeds to step S305 and loops until all order numbers in file A have been processed.

[0078] Step S305: Generate an order test item list file.

[0079] First, the embodiment of the present application can maintain a test item name management table testitem in the database (as shown in Table 1), recording all the test item names at the current stage for easy query; mainly maintaining fields such as serial number, test item name, test item description, update time, etc., among which Table 1 is the testitem structure table.

[0080] Table 1

[0081] Field Name Numeric Types constraint illustrate Id Int Not null, primary key Unique identifier Serial number int Not empty, unique Identify the order of test items in the actual test Test item name VARCHAR Not empty, unique Test item name describe TEXT Nullable Detailed description of the test items Update Time TIMESTAMP Not empty Default current time, record the last updated time

[0082] Maintain the test item selection rule table testitem_select in the database. Record the test items involved based on information such as machine model, material, and customer. Generate a test item list for a specific order based on this table's contents (as shown in Table 2). Maintain fields such as serial number, machine model, customer, material code, material type, test item, test item duration, effectiveness, and update time. Table 2 shows the testitem select structure table.

[0083] Table 2

[0084]

[0085] Furthermore, the test item selection rule table can be as follows Figure 2 As shown:

[0086] The test item in testitem_select cannot be empty;

[0087] Exclude the rules whose validity is set to "No" in testitem_select, and only select the valid rules;

[0088] The model name supports a fuzzy matching mechanism. When a specific character sequence (such as "M6") is entered, all associated models containing this sequence will be automatically matched. This rule applies to derivative models with the same naming characteristics within the same generation of models, and batch coverage can be achieved without having to list the complete model names separately.

[0089] The Model field can be left blank. If it is left blank, it means that the model is not differentiated and it is applicable to all models. The Material Code, Material Type, and Customer fields are the same as the Model field and can be left blank.

[0090] If two or more of the following conditions are true: Machine Model, Material Code, Material Type, or Customer, then the corresponding test item can only be selected if all conditions are true.

[0091] Furthermore, the embodiment of the present application can generate a corresponding test item list file according to the order number.

[0092] First, the embodiment of the present application can obtain the model and customer information of the order in the order table according to the order number, obtain the order BOM in the listMaterial table, all material codes MaterialID and corresponding material type type;

[0093] The embodiment of the present application can traverse the rules of the testitem_select table, ① skip if the rule is not effective; ② check whether the model is empty or whether it is a fuzzy match (such as M6 matches all models containing M6); ③ check whether the customer is empty or whether it exactly matches the customer information corresponding to the order; ④ check whether the material code and material type are both non-empty, then search whether there is a material in the order that meets the conditions for both material type and material code; if only one is non-empty, check whether there is a corresponding material code or material type in the order; otherwise, if both are empty, it is also acceptable; ⑤ if the above ② to ④ conditions are all met, then record the test item name and test item duration in this item into a temporary file;

[0094] After traversing the testitem_select table, remove duplicate test items in the temporary file;

[0095] Reorder the test items in the temporary file according to the sequence numbers in the Testitem table;

[0096] Get the standard template for the test item list, replace the test items and corresponding durations in the temporary file, generate the test item list for this order, name it after the order number: listid_itemlist.ini, and save it in the test item list directory.

[0097] Among them, such as Figure 4 As shown, the embodiment of the present application can also create, edit, and perform other operations on the test item selection rule table on the Web page, and simultaneously add, delete, and modify the test item selection rule table in the database, making it convenient for developers to operate and view the rules.

[0098] Step S306: Check whether the order numbers in file A have been traversed.

[0099] Step S307: query all files in the test item list directory and extract the order number -> B. In this embodiment of the application, all files in the test item list directory can be queried, and the order number listid can be extracted separately according to the fixed file format listid_itemlist.ini and recorded in file B.

[0100] Step S308: Filter out order numbers older than 10 days from order B, and then select C. In this embodiment, the order number listid_n in file B is retrieved one by one. The order time starttime in the list table is retrieved based on the order number listid_n. If the current time minus the order time is greater than 10 days, the order number is recorded in file C. Otherwise, the query is skipped and the next order is checked until all order numbers in file B are exhausted.

[0101] Step S309: traverse the order numbers in C. Obtain the order numbers listid_n in file C one by one, and query the machine test status table for the item with the same listid_n.

[0102] Step S310: The status of all machines corresponding to the order. If the returned value is null, it means that the machine for this order has not yet been put online. If all the statuses are approved, the process proceeds to step S311. If any machine has a failed status, the process proceeds to step S314. After this determination, the present embodiment can continue to obtain the next order number for processing until all orders are processed.

[0103] Step S311: If all the tests are passed, then all the machines for this order have completed the test.

[0104] Step S312: Move the test item list file to the history directory. In this embodiment of the present application, the test item list file corresponding to the order can be moved from the test item list directory to the test item list history folder to back up the completed order.

[0105] Step S313, determine whether the order numbers in file C have been traversed.

[0106] Step S314: Not fully tested or not found, which means that the machine for this order has not yet been fully tested.

[0107] In summary, the embodiment of the present application can proactively inspect recent orders based on a scheduled inspection mechanism, trigger the generation of orders without test item list files, and at the same time check the order machine status for overdue orders to confirm the dynamic archiving of historical files to avoid high-frequency access pressure on the database; when the test item list is generated, it can be accurately screened and de-duplicated through a preset test item rule table to adapt to the complex configuration differences of the factory, and finally generate a test item list file according to a standardized template. The system adopts a modular architecture, taking into account rule extensibility and operation and maintenance flexibility, and balances data security and performance consumption through hierarchical operations (such as short-term orders exempt from machine status inspection), realizing resource optimization and full-process automated management and control of test item list files, avoiding problems and customer complaints caused by missing test items, and no redundant test items causing trouble for log viewing, thereby improving the accuracy of factory server diagnostic test item content and ensuring the factory quality of servers.

[0108] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0109] The embodiment of the present application also provides a test order management device, such as Figure 4 As shown, the test order management device 10 includes: an inspection module 100 , a determination module 200 and a first management module 300 .

[0110] Specifically, the inspection module 100 is configured to inspect the to-be-delivered order list within a preset period at preset intervals to identify at least one to-be-delivered order for which no test item list file has been established and multiple test orders for which test item list files have been established.

[0111] The determination module 200 is configured to determine multiple test items of any order to be established by combining pre-built test item selection rules and order information of any order to be established.

[0112] The first management module 300 is configured to generate a test item list file of any to-be-created order using a plurality of test items, and modify any to-be-created order for which a test item list file has been created into a test order, until no to-be-created order exists in the to-be-delivered order list.

[0113] Optionally, in one embodiment of the present application, the determination module 200 includes: a matching unit and a deleting unit.

[0114] The matching unit is used to traverse a pre-built rule table based on the order information of any order to be established using the test item selection rule to match multiple candidate test items for any order to be established.

[0115] The deleting unit is used to delete duplicate test items from multiple candidate test items to obtain multiple test items.

[0116] Optionally, in one embodiment of the present application, the test item selection rules include: skipping candidate test items that do not meet preset effectiveness conditions; using the model to match the first candidate test item when the order information contains model information or the model meets the preset fuzzy matching conditions; using the customer to match the second candidate test item when the order information contains customer information or the customer's customer information meets the preset exact matching conditions; matching the third candidate test item based on the material code and / or material type when the order information contains material code and / or material type; matching the fourth candidate test item when the order information does not contain material code and material type.

[0117] Optionally, in one embodiment of the present application, the test order management device 10 further includes: an acquisition module, a first confirmation module and a reminder module.

[0118] The acquisition module is used to acquire multiple historical test orders obtained during the last inspection when no test order is identified in the list of orders to be delivered.

[0119] The first confirmation module is configured to confirm corresponding order delivery dates based on order information of a plurality of historical test orders, and use the order delivery dates to confirm whether there is at least one historical test order with a delivery date after the current inspection time.

[0120] The reminder module is used to generate an order recognition error reminder when there is at least one historical test order.

[0121] Optionally, in one embodiment of the present application, the test order management device 10 further includes: a filtering module, a second confirmation module and a second management module.

[0122] Among them, the filtering module is used to filter out multiple abnormal orders that exceed the preset test time from multiple test orders.

[0123] The second confirmation module is used to confirm the test status of all machines in any abnormal order.

[0124] The second management module is used to remove any abnormal order from the order list when the test status of all machines is the test passed status, and transfer the test item list file of any abnormal order to the history directory. Otherwise, any abnormal order is ignored until all abnormal orders are confirmed.

[0125] Optionally, in one embodiment of the present application, the test order management device 10 further includes: a judgment module, a positioning module and a third management module.

[0126] Among them, the judgment module is used to judge whether any abnormal order is overdue based on the order information of any abnormal order.

[0127] The positioning module is used to locate all the machines under test that are not in the test passing state in any abnormal order in the event of overdue.

[0128] The third management module is used to match the corresponding overdue policy based on the machine to be tested, the overdue period of any abnormal order and the order list, so as to arrange a queue-jumping test for the machine to be tested based on the overdue policy.

[0129] Optionally, in one embodiment of the present application, the test order management device 10 further includes: a matching module and a generation module.

[0130] The matching module is used to match the historical test item list file that meets the preset conditions in the historical directory based on the order information of any order to be established.

[0131] A generation module is used to use the historical test item list file as any test item list file for an order to be created.

[0132] For the description of the features in the embodiment corresponding to the test order management device, please refer to the relevant description of the embodiment corresponding to the test order management method, which will not be repeated here.

[0133] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps of any of the above-mentioned test order management method embodiments.

[0134] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above-mentioned test order management method embodiments when running.

[0135] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0136] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of any of the above-mentioned test order management method embodiments are implemented.

[0137] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, implementing the steps of any of the above-mentioned test order management method embodiments.

[0138] Professionals may further appreciate 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 above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0139] The above is a detailed introduction to the test order management method, device, electronic device and storage medium provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A test order management method, characterized in that: The following steps are involved: Inspecting the list of pending orders within a preset time period at preset intervals to identify at least one pending order for which a test item list file has not been established and multiple test orders for which test item list files have been established; Determine multiple test items for any order to be established by combining pre-established test item selection rules and order information of any order to be established; A test item list file of any to-be-created order is generated using the multiple test items, and any to-be-created order for which the test item list file has been created is modified into a test order until no to-be-created order exists in the to-be-delivered order list.

2. The method according to claim 1, characterized in that The determining of the multiple test items of any order to be established by combining the pre-built test item selection rules and the order information of any order to be established includes: Based on the order information of any one of the pending orders, traverse a pre-built rule table using the test item selection rule to match a plurality of candidate test items for the any one of the pending orders; Duplicate test items are deleted from the multiple candidate test items to obtain the multiple test items.

3. The method according to claim 1, characterized in that The test item selection rules include: Skip the test items that do not meet the preset validity conditions; In a case where the order information includes model information or the model meets a preset fuzzy matching condition, using the model to match the first candidate test item; In a case where the order information contains customer information or the customer information of the customer meets a preset exact matching condition, using the customer to match the second candidate test item; In a case where the order information includes a material code and / or a material type, matching a third candidate test item based on the material code and / or the material type; When the order information does not include the material code and the material type, the fourth candidate test item is matched.

4. The method according to claim 1, wherein After checking the list of pending orders within the preset time period at preset intervals, it also includes: If no test order is identified in the list of pending orders, obtaining multiple historical test orders obtained during the last inspection; Confirming corresponding order delivery dates based on the order information of the multiple historical test orders, and using the order delivery dates to confirm whether there is at least one historical test order with a delivery date after the current inspection time; If the at least one historical test order exists, an order recognition error alert is generated.

5. The method according to claim 1, characterized in that Also includes: Filtering out multiple abnormal orders exceeding a preset test time from the multiple test orders; Confirm the test status of all machines in any abnormal order; If the test status of all the machines is the test passed status, any abnormal order will be removed from the order list, and the test item list file of any abnormal order will be transferred to the history directory. Otherwise, any abnormal order will be ignored until all abnormal orders are confirmed.

6. The method according to claim 5, characterized in that After ignoring any of the abnormal orders, it also includes: Determining whether any abnormal order is overdue based on the order information of any abnormal order; If the deadline has expired, all machines to be tested that are not in the test passing state in any abnormal order are located; Based on the machine to be tested, the overdue duration of any abnormal order and the order list, a corresponding overdue policy is matched to arrange a queue-jumping test for the machine to be tested based on the overdue policy.

7. The method according to claim 5, characterized in that After identifying at least one pending order for which a test item list file has not been established, the method further includes: Matching the historical test item list file that meets the preset conditions in the historical directory based on the order information of any pending order; The historical test item list file is used as the test item list file of any order to be created.

8. A test order management device, characterized in that: include: An inspection module is used to inspect the list of pending orders within a preset period of time at preset intervals to identify at least one pending order for which a test item list file has not been established and multiple test orders for which test item list files have been established; a determination module, configured to determine a plurality of test items for any order to be established by combining a pre-established test item selection rule and order information of any order to be established; The management module is configured to generate a test item list file of any to-be-created order using the multiple test items, and modify any to-be-created order for which a test item list file has been created into a test order until no to-be-created order exists in the to-be-delivered order list.

9. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the test order management method according to any one of claims 1 to 7 when executing the computer program.

10. 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, the steps of the test order management method according to any one of claims 1 to 7 are implemented.

Images