Methods, systems, and computer devices and storage media for test rig management

Abstract

The application relates to a test sample management method, system, computer device and storage medium. The method comprises the following steps: creating a test task; acquiring all uncompleted test tasks and test samples of the uncompleted test tasks, and establishing an ordered mapping relationship between the test samples and the test tasks and test configurations; for each test task, checking whether a corresponding test sample exists in the mapping relationship, and if not, checking whether the test sample corresponding to the test task can be scheduled; if yes, recording the use plan adjustment content and configuration change content of the test sample scheduled when the test task is completed; and if not, recording the test configuration required when the test task is completed. The method automatically identifies the use plan adjustment content and test configuration content of the newly added test task, improves the timeliness of test task processing, and ensures the execution progress of the test task.

Description

Technical Field

[0001] This application relates to the technical field of test prototype management, and in particular to a method, system, computer equipment, and storage medium for test prototype management. Background Technology

[0002] With the development of the internet, the demand for servers of different product types is increasing. Before production on the production line, servers need to undergo extensive testing under different configurations, requiring a large number of prototypes to support the testing.

[0003] In the existing testing process, different product types of servers are tested by different project teams. The Test System Engineer (TSE) develops the test plan, and the Test Manager (VM) arranges the test schedule according to the test plan and assigns test tasks to the Test Engineers (TE). Before starting the test, the test engineers need to build different test prototypes according to the different configurations of the test tasks, and also need to adjust the usage plan of the available prototypes accordingly to implement the corresponding test content. However, identifying the test configuration of newly added test prototypes is very cumbersome and prone to errors, which leads to deviations in the usage plan adjustment and configuration changes, affecting the progress of the test tasks. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, system, computer equipment, and storage medium for test prototype management to address the above-mentioned technical problems. This would solve the current technical problem that when different test prototypes are built according to different test tasks, identifying the test configuration content of newly added test prototypes is cumbersome and prone to errors, leading to deviations in the use of plan adjustments and configuration changes, thus affecting the progress of test tasks.

[0005] On the one hand, a method for managing test prototypes is provided, the method comprising:

[0006] Create a test task, which includes test configuration, test cases, and test prototype information;

[0007] Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0008] Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If so, record the usage plan adjustment and configuration change of the test prototype scheduled when completing this test task. If a test prototype corresponding to the test task cannot be scheduled, record the test configuration required to complete this test task.

[0009] In one embodiment, the traversal of the mapping relationship further includes:

[0010] Determine whether all unexecuted test tasks were completed during the traversal of the mapping relationship. If so, trigger the pending prototype task according to the recorded test task test configuration. Otherwise, return to the step of determining whether the next test task has a corresponding test prototype.

[0011] In one embodiment, after all unfinished test tasks have been determined, a usage plan for the test prototype is automatically generated based on the recorded information.

[0012] In one embodiment, after creating the test task, the method further includes: obtaining the test configuration contained in the test task, analyzing the prototypes required to complete the test task, retrieving data from the test sample library, and determining whether all required prototypes are included in the test sample library; if yes, skipping the test task; if no, creating the required prototypes not included in the test sample library and issuing a warning message for pending prototype tasks.

[0013] In one embodiment, when viewing the warning information of the prototype task to be processed, one can also view the information recorded when traversing the mapping relationship, or one can also view the usage plan of the automatically generated test prototype.

[0014] In one embodiment, when creating a test task, the test task further includes a planned start time, a planned end time, and a preset number of days; when traversing the mapping relationship, a test task is selected from all test tasks. If the planned start time of the test task minus the current time is less than or equal to the preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes not included in the test sample library are created as idle prototypes, and the test configuration of the idle prototypes is issued together with the warning information of the prototype task to be processed.

[0015] In one embodiment, before creating a test task, a test sample library is also constructed, wherein the configuration, location, status, and information of the person who built each test prototype are recorded.

[0016] After the usage plan of the test prototype is completed, the test prototype will be automatically released upon expiration according to the usage plan. After being released, the test prototype can be recycled and dismantled.

[0017] On the other hand, a system for managing test prototypes is provided, the system comprising:

[0018] The test task creation module is used to create test tasks, which include test configuration, test cases, and test prototype information.

[0019] A mapping relationship establishment module is used to obtain all unfinished test tasks and test prototypes of unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0020] The plan difference content recording module is used to traverse the mapping relationship and determine one by one whether there is a corresponding test prototype for each of the unfinished test tasks. If so, it determines whether there is a corresponding test prototype for the next test task. Otherwise, it checks whether a test prototype corresponding to the test task can be scheduled. If so, it records the usage plan adjustment content and configuration change content of the test prototype scheduled when completing this test task. If not, it records the test configuration required to complete this test task.

[0021] In one embodiment, the system further includes:

[0022] The early warning information management module is used to obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if so, skip it; if not, create the required prototypes not included in the test sample library and issue an early warning information for the prototype task to be processed.

[0023] In one embodiment, the system includes:

[0024] The plan generation module is used to determine whether all unfinished test tasks have been completed during the traversal of the mapping relationship. If so, the pending prototype task is triggered according to the recorded test task test configuration. Otherwise, the process returns to the step of determining whether the next test task has a corresponding test prototype. After all unfinished test tasks have been determined, the usage plan of the test prototype is automatically generated according to the recorded information.

[0025] In one embodiment, the system includes:

[0026] The test prototype management module is used to build a test prototype library and to automatically release the test prototypes upon expiration of the usage plan, according to the usage plan. The released test prototypes can be recycled and dismantled.

[0027] In another aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0028] Create a test task, which includes test configuration, test cases, and test prototype information;

[0029] Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0030] Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If so, record the usage plan adjustment and configuration change of the scheduled test prototype when completing this test task. If not, record the test configuration required to complete this test task.

[0031] In another aspect, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0032] Create a test task, which includes test configuration, test cases, and test prototype information;

[0033] Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0034] Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If so, record the usage plan adjustment and configuration change of the scheduled test prototype when completing this test task. If not, record the test configuration required to complete this test task.

[0035] The aforementioned method, system, computer equipment, and storage medium for test prototype management establish an ordered mapping relationship between test prototypes and test tasks and test configurations. For each test task, the mapping relationship is traversed to find the usage plan adjustment content and configuration change content of existing test prototypes that can be scheduled, as well as the test configuration information of test tasks for which there are no existing test prototypes. This enables automatic identification of the usage plan adjustment content and test configuration content of newly added test tasks, improves the timeliness of test task processing, and ensures the execution progress of test tasks. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a block diagram of a system for managing test prototypes in one embodiment;

[0038] Figure 2 This is a flowchart illustrating a method for managing test prototypes in one embodiment;

[0039] Figure 3 A flowchart of a method for test prototype management in another embodiment;

[0040] Figure 4 This is a block diagram of the system for managing test prototypes in another embodiment;

[0041] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0043] As described in the background section, in the existing server testing process, the Test System Engineer (TSE) formulates the test plan, and the Test Manager (VM) arranges the test schedule according to the test plan and assigns test tasks to the Test Engineers (TE). Before starting the test, the test engineers need to borrow materials and build test prototypes with different configurations according to the different configurations of the test tasks. This requires a lot of manpower, and there are often situations where materials are not complete, resulting in poor timeliness of prototype building, affecting the progress of the test tasks, causing the test plan to be not completed on time, and affecting product delivery.

[0044] Therefore, it is extremely important to design a method and system for intelligent management of server test prototypes. This will not only ensure the timeliness of test prototype provision and reduce the number of prototypes to be built, saving resources and manpower, but also allow for advance scheduling of prototypes, improving their utilization rate. The overall project plan and the progress of testing tasks can also be adjusted and optimized in advance, ensuring that the testing work is completed on time and with high quality.

[0045] Example 1

[0046] To address the aforementioned issues, Embodiment 1 of this invention creatively proposes a test prototype management system. Based on the Spring, SpringBoot, and M5batis frameworks, and developed using the Java language, it establishes a microservice platform, provides early warnings of missing prototypes, and intelligently schedules idle prototypes according to a preset number of days, thereby achieving accurate and efficient intelligent scheduling and early warning of server test prototypes.

[0047] like Figure 1 As shown, the test prototype management system 10 mainly comprises three major modules: test task management module 1, test prototype management module 2, and intelligent scheduling management module 3.

[0048] The test task management module 1 mainly manages test tasks, estimates the number of prototypes required for test tasks, and provides early warnings of missing prototypes.

[0049] The test task management module 1 mainly implements the following functions:

[0050] 1) Adding and maintaining test tasks, recording information such as test configuration, test cases, planned start / end time, and test engineer (TE) included in the task;

[0051] 2) The task creator can set the preset number of days, which is used to schedule the test prototypes required for the test task within the preset number of days before the scheduled start time of the test task (hereinafter referred to as the preset number of days);

[0052] 3) After task allocation, the system automatically triggers the estimation and early warning of the prototypes required for the test task. First, it obtains the test configurations included in the task and analyzes them to estimate the minimum number of prototypes needed without affecting the test quality. At the same time, it analyzes the current test prototype library and the test plan time allocated to the prototypes, and provides early warning of which test configurations are currently missing. It automatically triggers pending prototype tasks or sends message notifications to the prototype building team.

[0053] The test prototype management module 2 mainly manages all test prototypes. A dedicated prototype building team is responsible for building the prototypes, creating a test prototype library, and recording information such as the configuration, location, status, and builder of each test prototype.

[0054] The test prototype management module 2 mainly performs the following functions:

[0055] 1) Adding, setting up, and maintaining test prototypes;

[0056] 2) Test prototype recycling and dismantling: Before recycling, check whether there are any test tasks configured for this prototype that have not been tested. If so, it cannot be recycled or dismantled.

[0057] The intelligent scheduling and management module 3 mainly realizes the intelligent scheduling of test prototypes and the monitoring of test tasks, and automatically records the usage plan of the prototypes.

[0058] Based on the above-mentioned test prototype management system 10, such as Figure 2 As shown, a method for managing test prototypes is provided, including the following steps:

[0059] 1) Obtain all unfinished test tasks and their respective test engineers (TEs). Based on the test tasks, obtain all test configurations to establish an ordered mapping relationship between test engineers (TEs), test tasks, and test configurations, sorted from fewest to most.

[0060] 2) Traverse the mapping relationship to obtain and traverse all test tasks and test configurations of the test engineer (TE);

[0061] 3) Select a test task from all test tasks. If the planned start time of the test task - the current time ≤ the preset number of days, proceed to the next step. It can be understood that if the planned start time of the test task - the current time > the preset number of days, it is considered that this type of task has been executed before or is currently being executed.

[0062] 4) Determine if a prototype has been found for this test task and test configuration. If a prototype has been found, skip this step.

[0063] 5) If no prototype is found, the test task will be scheduled with an idle prototype configured for that test.

[0064] 6) If a test prototype can be scheduled, assign the test prototype to the test engineer (TE) of the task during the start / end time of the task plan, record that the test configuration of the test task has found a prototype, record the prototype usage plan, and change the prototype status.

[0065] 7) If no test prototype is scheduled, record the test configuration for the test task that did not obtain a prototype;

[0066] 8) Continue with steps 3-7 until all test tasks are completed. Based on the recorded test configurations for test tasks that have not yet obtained prototypes, automatically trigger pending prototype tasks or send message notifications to the prototype setup team.

[0067] 9) After traversing all test tasks and all test configurations, automatically generate a usage plan for the prototype;

[0068] 10) After the prototype is no longer in use, the test engineer (TE) can proactively release the machine. If the machine is not proactively released, it will be automatically released upon expiration according to the prototype's usage plan. This maximizes the utilization rate of the test prototype while ensuring test progress and quality.

[0069] Therefore, the test prototype management method described above in this application can automatically trigger the estimation and early warning of the prototypes required for the task after the test task is assigned:

[0070] 1. First, obtain the test configurations included in the task, and analyze them to estimate the minimum number of prototypes required without affecting the test quality;

[0071] 2. Simultaneously analyze the current test prototype library and the test usage plan allocated to the prototypes, provide early warnings of which idle prototypes are currently lacking test configurations, and automatically trigger pending prototype tasks or send message notifications to the prototype setup team.

[0072] Understandably, a test usage plan, also known as a usage plan, is a test plan for completing test tasks for which no prototype has been obtained. Idle prototypes are the missing prototypes that need to be tested, making it easier to distinguish between existing prototypes and those that are missing when building a test prototype library.

[0073] In one optimized embodiment, the test prototype management system can be integrated with server automated testing, automatically acquiring prototypes when completing automated tasks, eliminating the need for manual addition of machines.

[0074] This invention relates to a method and system for managing server test prototypes based on microservices. It can provide accurate early warnings of server test prototype needs, ensuring the timeliness of prototype setup, reducing manpower investment in prototype setup, saving resources, and intelligently scheduling and allocating prototypes to testers. It can also schedule prototypes according to test tasks, improving prototype utilization. The overall project plan and test task progress can also be adjusted and optimized in advance, ensuring that the test work is completed on time and with high quality, thereby improving test efficiency and test quality.

[0075] Example 2

[0076] Based on the same inventive concept as in Embodiment 1, such as Figure 3 As shown in Example 2, a method for managing test prototypes is provided, including the following steps:

[0077] Step S1: Create a test task, which includes test configuration, test cases, and test prototype information.

[0078] Step S2: Obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if yes, skip; if no, create the required prototypes not included in the test sample library and issue a warning message for the pending prototype task.

[0079] Step S3: Obtain all unfinished test tasks and test prototypes of the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks.

[0080] Step S4: Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If a test prototype corresponding to the test task can be scheduled, record the usage plan adjustment and configuration change content of the scheduled test prototype when completing this test task. If a test prototype corresponding to the test task cannot be scheduled, record the test configuration required to complete this test task.

[0081] Step S5: Determine whether all unfinished test tasks were determined during the traversal of the mapping relationship. If so, trigger the pending prototype task according to the recorded test task test configuration. Otherwise, return to the step of determining whether the next test task has a corresponding test prototype. After all unfinished test tasks have been determined, automatically generate a test prototype usage plan based on the recorded information.

[0082] Understandably, steps S1, S3, and S4 can be executed independently. By establishing an ordered mapping relationship between the test prototype, test tasks, and test configurations, and for each test task, traversing the mapping relationship to find the usage plan adjustment content and configuration change content of the existing test prototypes that can be scheduled, as well as the test configuration information of test tasks for which there are no existing test prototypes, the system automatically identifies the usage plan adjustment content and test configuration content of newly added test tasks, improves the timeliness of test task processing, and ensures the execution progress of test tasks.

[0083] Steps S1 and S2 can be executed independently. The newly created test task content is checked to see if it is in the test sample library. If it is not, a test prototype needs to be built. At this time, an early warning message for the pending prototype task is issued in a timely manner. This does not require a lot of manpower to investigate, improves the timeliness of prototype building, ensures that the test task can be completed on time according to the test plan, and guarantees product delivery.

[0084] In this embodiment, when viewing the early warning information of the prototype task to be processed, one can also view the information recorded when traversing the mapping relationship, or one can also view the usage plan of the automatically generated test prototype.

[0085] In this embodiment, when creating a test task, the test task also includes a planned start time, a planned end time, and a preset number of days. When traversing the mapping relationship, a test task is selected from all test tasks. If the planned start time of the test task minus the current time is less than or equal to the preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes not included in the test sample library are created as idle prototypes, and the test configuration of the idle prototypes is issued together with the warning information of the pending prototype tasks. This allows for intelligent scheduling of idle prototypes based on the preset number of days, ensuring the timeliness of test prototype setup and reducing manpower input.

[0086] In this embodiment, before creating a test task, a test sample library is established. This library records the configuration, location, status, and information of the person who built each test prototype. After the usage plan for each test prototype is completed, the prototype is automatically released upon expiration according to the plan. Once released, the prototype can be recycled and dismantled. Before recycling, it is checked whether there are any untested test tasks associated with the prototype's configuration; if so, it cannot be recycled or dismantled.

[0087] In the aforementioned method for managing test prototypes, the system checks whether newly created test task content exists in the test sample library. If not, a test prototype needs to be built, and an early warning message for pending prototype tasks is issued promptly. This eliminates the need for extensive manpower for investigation, improving the timeliness of prototype building and ensuring that test tasks are completed on schedule according to the test plan, thus guaranteeing product delivery. By establishing an ordered mapping relationship between test prototypes, test tasks, and test configurations, the system iterates through this mapping relationship for each test task to find the usage plan adjustments and configuration changes of existing test prototypes that can be scheduled, as well as the test configuration information for test tasks without corresponding existing test prototypes. This achieves automatic identification of the usage plan adjustments and test configurations of newly added test tasks, improving the timeliness of test task processing and ensuring the execution progress of test tasks. Furthermore, the system automatically generates a usage plan for the test prototype based on the recorded information. When viewing the warning information of the pending prototype task, users can also view the information recorded when traversing the mapping relationship, or they can also view the automatically generated usage plan for the test prototype. This further improves the efficiency of processing based on the warning information of the pending prototype task and the generated usage plan, enhances the timeliness of test task processing, and ensures the execution progress of the test task.

[0088] It should be understood that, although Figure 3 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 3 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0089] In one embodiment, such as Figure 4 As shown, a test prototype management system 10 is provided, which mainly includes three major components: test task management module 1, test prototype management module 2, and intelligent scheduling management module 3.

[0090] The test task management module 1 includes: a test task creation module 11 and an early warning information management module 12; the intelligent scheduling management module 3 includes: a mapping relationship establishment module 31, a usage plan difference content recording module 32, a usage plan generation module 33, and a test prototype management module 34.

[0091] The test task creation module 11 is used to create test tasks, which include test configuration, test cases, and test prototype information.

[0092] The early warning information management module 12 is used to obtain the test configuration included in the test task, analyze the prototype required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if yes, skip it; if no, create the required prototypes not included in the test sample library and issue an early warning information for the prototype task to be processed.

[0093] The mapping relationship establishment module 31 is used to obtain all unfinished test tasks and test prototypes of unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks.

[0094] The usage plan difference recording module 32 is used to traverse the mapping relationship and determine whether each test task in all unfinished test tasks has a corresponding test prototype. If so, it determines whether the next test task has a corresponding test prototype. Otherwise, it checks whether a test prototype corresponding to the test task can be scheduled. If a test prototype corresponding to the test task can be scheduled, it records the usage plan adjustment content and configuration change content of the test prototype scheduled when completing this test task. If a test prototype corresponding to the test task cannot be scheduled, it records the test configuration required to complete this test task.

[0095] The usage plan generation module 33 is used to determine whether all unfinished test tasks have been determined during the traversal of the mapping relationship. If so, the pending prototype task is triggered according to the recorded test task test configuration. Otherwise, the process returns to the step of determining whether the next test task has a corresponding test prototype. After all unfinished test tasks have been determined, the usage plan of the test prototype is automatically generated according to the recorded information.

[0096] The test prototype management module 34 is used to build a test sample library and to automatically release the test prototypes upon expiration of the test prototype usage plan after the test prototype usage plan has been completed. The test prototypes can be recycled and dismantled after being released.

[0097] In this embodiment, when viewing the early warning information of the prototype task to be processed, one can also view the information recorded when traversing the mapping relationship, or one can also view the usage plan of the automatically generated test prototype.

[0098] In this embodiment, when creating a test task, the test task also includes a planned start time, a planned end time, and a preset number of days. When traversing the mapping relationship, a test task is selected from all test tasks. If the planned start time of the test task minus the current time is less than or equal to the preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes not included in the test sample library are created as idle prototypes, and the test configuration of the idle prototypes is issued together with the warning information of the prototype task to be processed.

[0099] In this embodiment, the test prototype management module 2 is used to build a test sample library, which records the configuration, location, status, and information of the person who built each test prototype.

[0100] The test prototype management module 2 is used to automatically release the test prototype upon expiration of the test prototype's usage plan after the plan has been completed. The released test prototype can be recycled and dismantled.

[0101] In the aforementioned test prototype management system, newly created test task content is checked against the test sample library. If not, a test prototype needs to be built. At this point, a timely warning message for pending prototype tasks is issued, eliminating the need for extensive manpower for investigation. This improves the timeliness of prototype building, ensuring that test tasks are completed on schedule according to the test plan and guaranteeing product delivery. By establishing an ordered mapping relationship between test prototypes, test tasks, and test configurations, the system iterates through this mapping relationship for each test task to find the usage plan adjustments and configuration changes for existing test prototypes that can be scheduled, as well as the test configuration information for test tasks without corresponding existing test prototypes. This achieves automatic identification of the usage plan adjustments and test configurations for newly added test tasks, improving the timeliness of test task processing and ensuring the execution progress of test tasks. Furthermore, the system automatically generates a usage plan for the test prototype based on the recorded information. When viewing the warning information of the pending prototype task, users can also view the information recorded when traversing the mapping relationship, or they can also view the automatically generated usage plan for the test prototype. This further improves the efficiency of processing based on the warning information of the pending prototype task and the generated usage plan, enhances the timeliness of test task processing, and ensures the execution progress of the test task.

[0102] Specific limitations regarding the system for test prototype management can be found in the limitations of the test prototype management method described above, and will not be repeated here. Each module in the aforementioned test prototype management system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0103] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data for test prototype management. The database can also store data for a test sample library. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a test prototype management method.

[0104] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0105] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0106] Create a test task, which includes test configuration, test cases, and test prototype information;

[0107] Obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if yes, skip it; if no, create the required prototypes not included in the test sample library and issue a warning message for the pending prototype task.

[0108] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0109] After issuing the warning information for the pending prototype task, the following is also included:

[0110] Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0111] Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If a test prototype corresponding to the test task can be scheduled, record the usage plan adjustment and configuration change content of the scheduled test prototype when completing this test task. If a test prototype corresponding to the test task cannot be scheduled, record the test configuration required to complete this test task.

[0112] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0113] The process of traversing the mapping relationship also includes:

[0114] Determine whether all unexecuted test tasks were completed during the traversal of the mapping relationship. If so, trigger the pending prototype task according to the recorded test task test configuration. Otherwise, return to the step of determining whether the next test task has a corresponding test prototype.

[0115] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0116] Once all unfinished test tasks have been assessed, a usage plan for the test prototype is automatically generated based on the recorded information.

[0117] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0118] When viewing the warning information of the prototype task to be processed, you can also view the information recorded when traversing the mapping relationship, or you can also view the usage plan of the automatically generated test prototype.

[0119] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0120] When creating a test task, the test task also includes a planned start time, a planned end time, and a preset number of days;

[0121] When traversing the mapping relationship, a test task is selected from all test tasks. When the planned start time of the test task minus the current time is less than or equal to the preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes not included in the test sample library are created as idle prototypes, and the test configuration of the idle prototypes is sent together with the warning information of the prototype task to be processed.

[0122] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0123] Before creating a test task, a test sample library is also built, which records the configuration, location, status, and information of the person who built each test prototype.

[0124] After the usage plan of the test prototype is completed, the test prototype will be automatically released upon expiration according to the usage plan. After being released, the test prototype can be recycled and dismantled.

[0125] For specific limitations on the steps a processor takes when executing a computer program, please refer to the limitations on the methods for managing test prototypes mentioned above, which will not be repeated here.

[0126] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0127] Create a test task, which includes test configuration, test cases, and test prototype information;

[0128] Obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if yes, skip it; if no, create the required prototypes not included in the test sample library and issue a warning message for the pending prototype task.

[0129] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0130] After issuing the warning information for the pending prototype task, the following is also included:

[0131] Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks;

[0132] Traverse the mapping relationship and determine whether each of the unfinished test tasks has a corresponding test prototype. If so, determine whether the next test task has a corresponding test prototype. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If a test prototype corresponding to the test task can be scheduled, record the usage plan adjustment and configuration change content of the scheduled test prototype when completing this test task. If a test prototype corresponding to the test task cannot be scheduled, record the test configuration required to complete this test task.

[0133] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0134] The process of traversing the mapping relationship also includes:

[0135] Determine whether all unexecuted test tasks were completed during the traversal of the mapping relationship. If so, trigger the pending prototype task according to the recorded test task test configuration. Otherwise, return to the step of determining whether the next test task has a corresponding test prototype.

[0136] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0137] Once all unfinished test tasks have been assessed, a usage plan for the test prototype is automatically generated based on the recorded information.

[0138] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0139] When viewing the warning information of the prototype task to be processed, you can also view the information recorded when traversing the mapping relationship, or you can also view the usage plan of the automatically generated test prototype.

[0140] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0141] When creating a test task, the test task also includes a planned start time, a planned end time, and a preset number of days;

[0142] When traversing the mapping relationship, a test task is selected from all test tasks. When the planned start time of the test task minus the current time is less than or equal to the preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes not included in the test sample library are created as idle prototypes, and the test configuration of the idle prototypes is sent together with the warning information of the prototype task to be processed.

[0143] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0144] Before creating a test task, a test sample library is also built, which records the configuration, location, status, and information of the person who built each test prototype.

[0145] After the usage plan of the test prototype is completed, the test prototype will be automatically released upon expiration according to the usage plan. After being released, the test prototype can be recycled and dismantled.

[0146] For specific limitations on the steps implemented when a computer program is executed by a processor, please refer to the limitations on the methods for managing test prototypes mentioned above, which will not be repeated here.

[0147] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAM bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0148] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0149] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for managing test prototypes, characterized in that, Including the following steps: Create a test task, which includes test configuration, test cases, and test prototype information; Obtain all unfinished test tasks and test prototypes for the unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks; Traverse the mapping relationship and determine whether there is a corresponding test prototype for each of the unfinished test tasks. If so, determine whether there is a corresponding test prototype for the next test task. Otherwise, check whether a test prototype corresponding to the test task can be scheduled. If so, record the usage plan adjustment and configuration change content of the test prototype scheduled when this test task is completed. If not, record the test configuration required to complete this test task; Following the creation of the test task, the following is also included: Obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if yes, skip it; if no, create the required prototypes not included in the test sample library and issue a warning message for the pending prototype task.

2. The method for managing test prototypes according to claim 1, characterized in that, The process of traversing the mapping relationship also includes: Determine whether all unexecuted test tasks have completed the test prototype judgment by traversing the mapping relationship. If so, trigger the pending prototype task according to the test configuration of the recorded test task. Otherwise, return to the step of determining whether the next test task has a corresponding test prototype.

3. The method for managing test prototypes according to claim 2, characterized in that, Once all unfinished test tasks have been assessed, a usage plan for the test prototype is automatically generated based on the recorded information.

4. The method for managing test prototypes according to claim 1, characterized in that, When viewing the warning information of the prototype task to be processed, you can also view the information recorded when traversing the mapping relationship, or you can also view the usage plan of the automatically generated test prototype.

5. The method for managing test prototypes according to claim 1, characterized in that, When creating a test task, the test task also includes a planned start time, a planned end time, and a preset number of days; When traversing the mapping relationship, a test task is selected from all test tasks. When the planned start time of the test task minus the current time is less than or equal to a preset number of days, it is determined whether all required prototypes are included in the test sample library. If not, the required prototypes that are not included are created as idle prototypes in the test sample library, and the test configuration of the idle prototype is issued together with the warning information of the prototype task to be processed. The idle prototype is the prototype corresponding to the test configuration that is currently missing in the test sample library.

6. The method for managing test prototypes according to claim 1, characterized in that, Before creating a test task, a test sample library is also built, which records the configuration, location, status, and information of the person who built each test prototype. After the usage plan of the test prototype is completed, the test prototype will be automatically released upon expiration according to the usage plan. After being released, the test prototype can be recycled and dismantled.

7. A system for managing test prototypes, characterized in that, The system includes: The test task creation module is used to create test tasks, which include test configuration, test cases, and test prototype information. A mapping relationship establishment module is used to obtain all unfinished test tasks and test prototypes of unfinished test tasks, and establish an ordered mapping relationship between the test prototypes and the test tasks and the test configurations contained in the test tasks; The plan difference content recording module is used to traverse the mapping relationship and determine one by one whether there is a corresponding test prototype for each of the unfinished test tasks. If so, it determines whether there is a corresponding test prototype for the next test task. Otherwise, it checks whether a test prototype corresponding to the test task can be scheduled. If so, it records the usage plan adjustment content and configuration change content of the test prototype scheduled when completing this test task. If not, it records the test configuration required to complete this test task. The early warning information management module is used to obtain the test configuration included in the test task, analyze the prototypes required to complete the test task, retrieve data from the test sample library, and determine whether all required prototypes are included in the test sample library; if so, skip it; if not, create the required prototypes not included in the test sample library and issue an early warning information for the prototype task to be processed.

8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

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

Images