Automatic scheduling and personnel scheduling method, device and system based on test plan

Abstract

The invention relates to an automatic scheduling and personnel scheduling method, device and system based on a test plan. Comprising the steps that test plan data are acquired, and the test plan data comprise required work order numbers, test plans and tester information; calculating total test working hours based on the test plan and the information of the test personnel; obtaining project test submission time corresponding to the required work order number from a project management system; determining test start time and test completion time based on the total test man-hour and the test submission time; monitoring whether a task saturation condition exists in a scheduling window formed by the test start time and the test completion time by the test personnel, and judging whether personnel scheduling is executed or not according to a monitoring result so as to determine a final test personnel; and inputting the final tester, the test start time and the test completion time into the project management system according to the required work order number. By adopting the method, automatic scheduling calculation and personnel transfer can be realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus and system for automatic scheduling and personnel dispatching based on test plans. Background Technology

[0002] As software development processes become increasingly complex, test scheduling, a critical element affecting project progress, is receiving growing attention for its efficiency and rationality. Test scheduling is part of the overall project schedule, typically occurring after the development phase and during the acceptance testing phase, and involves the time planning of testing tasks.

[0003] Currently, test scheduling is usually done manually. However, manually calculating the start time of tests leads to low scheduling efficiency and easily overlooks the status of testers, causing scheduling conflicts. When faced with adjustments to test tasks, the manual approach is slow to respond and cannot quickly and reasonably reallocate resources and update the schedule, which seriously affects the testing process and the overall progress of the project.

[0004] There is currently no effective solution for automatically calculating test schedules and mobilizing personnel in related technologies. Summary of the Invention

[0005] Therefore, it is necessary to provide a method, apparatus, and system for automatic scheduling and personnel dispatch based on test plans, which can automatically calculate test schedules and mobilize personnel, in order to address the above-mentioned technical problems.

[0006] Firstly, this application provides an automatic scheduling and personnel dispatching method based on a test plan, including:

[0007] Obtain test plan data, which includes the requirement work order number, test plan, and tester information;

[0008] Based on the test plan and test personnel information, calculate the total test hours;

[0009] Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0010] Based on the total test time and the test submission time, the test start time and test completion time are determined.

[0011] The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan.

[0012] Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0013] In one embodiment, the test plan includes dependencies that identify test dependencies; the calculation of total test man-hours includes:

[0014] The test complexity of the test plan is analyzed to determine the estimated man-hours for each function point;

[0015] Obtain the ability coefficient of the tester;

[0016] The buffer time is determined based on the dependencies and the estimated working hours of the function points;

[0017] The total test time is determined based on the estimated working hours of the function points, the capacity coefficient, and the buffer time.

[0018] In one embodiment, the analysis of the test complexity of the test plan includes:

[0019] The testers analyze the complexity of the test plan requirements, technical risks, and data preparation difficulties to obtain the estimated working hours for the functional points.

[0020] In one embodiment, the task saturation situation includes task conflicts and / or full workload; the step of determining whether personnel scheduling is needed based on monitoring results includes:

[0021] If the testers have task conflicts and / or their workload is full within the scheduling window, the personnel information is retrieved from the project management system, and available personnel are rescheduled based on the personnel's workload and their matching degree with the test plan.

[0022] If it does not exist, no personnel will be dispatched.

[0023] In one embodiment, the process of acquiring test plan data further includes:

[0024] The test plan data entered according to the test requirements will be stored in the database.

[0025] In one embodiment, it further includes:

[0026] Monitor changes to the test plan and obtain the test plan before and after the change;

[0027] Compare the test plans before and after the changes to determine the content of the changes;

[0028] Obtain the final tester, the test start time, and the test completion time from the project management system;

[0029] Based on the changes, the final test personnel, the test start time, and the test completion time will be adjusted accordingly.

[0030] In one embodiment, prior to monitoring changes to the test plan, the method further includes:

[0031] Listen for test requirement change notifications issued by the project management system;

[0032] Obtain the test requirements before and after the change;

[0033] Compare the test requirements before and after the change to determine the changed requirements, so as to guide the modification of the test plan.

[0034] Secondly, this application also provides an automatic scheduling and personnel dispatching device based on a test plan, comprising:

[0035] The scheduling algorithm module is used to acquire test plan data, which includes the requirement work order number, test plan, and tester information; and to calculate the total test hours based on the test plan and tester information.

[0036] The personnel scheduling module is used to obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time. Based on the total test hours and the test submission time, the module determines the test start time and test completion time. The module monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and test completion time. Based on the monitoring results, the module determines whether personnel scheduling is required, thereby determining the final testers to execute the test plan.

[0037] Thirdly, this application also provides an automatic scheduling and personnel dispatching system based on a test plan, including a platform system and a project management system. The platform system interacts with the project management system through a data interaction interface, and the platform system implements the following steps:

[0038] Obtain test plan data, which includes the requirement work order number, test plan, and tester information;

[0039] Based on the test plan and test personnel information, calculate the total test hours;

[0040] Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0041] Based on the total test time and the test submission time, the test start time and test completion time are determined.

[0042] The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan.

[0043] Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0044] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0045] Obtain test plan data, which includes the requirement work order number, test plan, and tester information;

[0046] Based on the test plan and test personnel information, calculate the total test hours;

[0047] Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0048] Based on the total test time and the test submission time, the test start time and test completion time are determined.

[0049] The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan.

[0050] Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0051] The aforementioned automatic scheduling and personnel dispatching method based on test plans involves: acquiring test plan data, including the requirement work order number, test plan, and tester information; calculating the total test hours based on the test plan and tester information; retrieving project-related time information corresponding to the requirement work order number from the project management system, including the test submission time; determining the test start time and test completion time based on the total test hours and the test submission time; monitoring whether the testers in the test plan experience task saturation within the scheduling window formed by the test start time and test completion time, and determining whether personnel dispatching is necessary based on the monitoring results, thereby determining the final testers to execute the test plan. This method achieves automatic calculation of scheduling and personnel deployment, ensuring that the test plan can be effectively executed within the scheduling window. Attached Figure Description

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

[0053] Figure 1 This is an application environment diagram of an automatic scheduling and personnel dispatching method based on a test plan in one embodiment;

[0054] Figure 2 This is a flowchart illustrating an automatic scheduling and personnel dispatching method based on a test plan in one embodiment;

[0055] Figure 3 This is a flowchart illustrating an automatic scheduling and personnel dispatching method based on a test plan in an example embodiment.

[0056] Figure 4 This is a structural block diagram of an automatic scheduling and personnel dispatching device based on a test plan in one embodiment. Detailed Implementation

[0057] 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.

[0058] The automatic scheduling and personnel dispatching method based on test plans provided in this application embodiment can be applied to, for example... Figure 1In the application environment shown, the project management server 102 communicates with the quality platform server 104 via a network. A data storage system can store the data that the quality platform server 104 needs to process. The data storage system can be integrated onto the quality platform server 104 or placed on a cloud or other network server. Based on the obtained test plan data containing the requirement work order number, test plan, and tester information, the quality platform server 104 calculates the total test hours and obtains the project-related time information corresponding to the requirement work order number from the project management server 102. Based on the total test hours and the test submission time, it determines the test start time and test completion time. Simultaneously, it monitors whether there is task saturation for testers within the scheduling window formed by the test start time and test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan. According to the requirement work order number, the final testers, the test start time, and the test completion time are entered into the project management server 102. Among them, the project management server 102 and the quality platform server 104 can be independent physical servers, or they can be server clusters or distributed systems composed of multiple physical servers, or they can be cloud servers that provide cloud computing services.

[0059] In one exemplary embodiment, such as Figure 2 As shown, an automatic scheduling and personnel dispatching method based on test plans is provided, which is then applied to... Figure 1 Taking the quality platform server 104 as an example, the following steps are included:

[0060] S201, Obtain test plan data, which includes the requirement work order number, test plan, and tester information.

[0061] Optionally, the test plan data may also include the requirement name and requirement document. The requirement work order number is a unique identifier used to associate and trace the test plan. Tester information may include the tester ID or the tester's name.

[0062] The test plan guides the entire testing process. Optionally, the test plan is a collection of structured data, containing multiple data points that can identify the module to which the test belongs, the specific function of the test, the type of test, the time required to complete the test, and the dependencies of the test plan. The data used to identify the type of test can be an enumeration type, which may include functional testing, stress testing, and regression testing. The data used to identify the time required to complete the test can be in hours.

[0063] By obtaining test plan data, we can lay the foundation for calculating the total test hours later.

[0064] S202, Calculate the total test hours based on the test plan and test personnel information.

[0065] Optionally, a thread pool can be created and a task queue defined to store test plans, enabling the parallel processing of multiple test plans. Specifically, threads in the thread pool continuously monitor the task queue, and once a new test plan is available in the queue, an idle thread retrieves the new test plan from the queue and performs the total test time calculation.

[0066] S203, obtain the project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0067] Optionally, data can be exchanged with the project management system via a RESTful API based on the HTTP protocol to obtain project-related time information corresponding to the required work order number.

[0068] The testing submission deadline is the date by which the development team promises to complete the code development and deliver it to the testing team to begin testing.

[0069] Optionally, project-related time information may also include backend start time, backend end time, integration testing time, and frontend start time. Combining this project-related time information can verify whether the calculated total test time is correct.

[0070] S204. Based on the total test time and the test submission time, determine the test start time and test completion time.

[0071] The test submission time is taken as the test start time, and the test submission time plus the total test man-hours is taken as the test completion time. By determining the test start time and test completion time, a time range benchmark is provided for subsequent assessment of whether there is a task saturation situation.

[0072] S205, monitor whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time, and determine whether personnel scheduling is required based on the monitoring results, thereby determining the final testers to execute the test plan.

[0073] By monitoring for task saturation within the scheduling window, the effective execution of the test plan is ensured. Dynamic optimization of personnel scheduling is achieved by determining whether to implement personnel scheduling based on the monitoring results, thereby identifying the final testers to execute the test plan.

[0074] S206. Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0075] Optionally, the final tester, the test start time, and the test completion time can be entered into the project management system via a RESTful API based on the HTTP protocol.

[0076] By entering the final testers, test start time, and test completion time into the project management system, the test plan and project progress are linked, ensuring transparent and traceable resource allocation and providing data support for personnel scheduling for new test plans.

[0077] The aforementioned automatic scheduling and personnel dispatching method based on test plans involves: acquiring test plan data, including the requirement work order number, test plan, and tester information; calculating the total test hours based on the test plan and tester information; retrieving project-related time information corresponding to the requirement work order number from the project management system, including the test submission time; determining the test start time and test completion time based on the total test hours and the test submission time; monitoring whether the testers in the test plan experience task saturation within the scheduling window formed by the test start time and test completion time, and determining whether personnel dispatching is necessary based on the monitoring results, thereby determining the final testers to execute the test plan. This method achieves automatic calculation of scheduling and personnel deployment, ensuring that the test plan can be effectively executed within the scheduling window.

[0078] In one embodiment, the test plan includes dependencies, which are used to identify the dependencies of the test; the calculation of total test hours includes: analyzing the test complexity of the test plan to determine the estimated test hours for each function point; obtaining the capability coefficient of the testers; determining a buffer time based on the dependencies and the estimated test hours for each function point; and determining the total test hours based on the estimated test hours for each function point, the capability coefficient, and the buffer time.

[0079] A test plan can include several parts: module, function, test type, estimated time, and dependencies. The module identifies the module to which the test belongs, the function identifies the specific function being tested, the test type identifies the type of test, the estimated time indicates the time required to complete the test, and the dependencies identify the dependencies within the test plan.

[0080] The competence coefficient is a coefficient that reflects the competence of the test personnel. Optionally, the competence coefficient can be a coefficient set according to the personnel's experience and skill level, with a competence coefficient of 1.2 for junior engineers, 1.0 for intermediate engineers, and 0.8 for senior engineers.

[0081] The dependencies can be an enumeration type, including no dependencies, internal dependencies, and external dependencies. Optionally, the estimated test time is calculated based on the dependencies and function points. For test plans with no dependencies, the buffer time is automatically calculated as 5% of the estimated function point test time; for test plans with internal dependencies, the buffer time is automatically calculated as 10% of the estimated function point test time; and for test plans with external dependencies, the buffer time is automatically calculated as 20% of the estimated function point test time. By calculating the buffer time, the calculated total test time becomes more reasonable.

[0082] Optionally, total test man-hours = estimated function point man-hours × capacity coefficient + buffer time. The calculated total test man-hours are used to further determine the test schedule.

[0083] In practical applications, test complexity refers to the combined difficulty of understanding and executing a test plan in terms of intellectual and resource investment. Therefore, the test complexity of a test plan can be analyzed from multiple perspectives. In one embodiment, the analysis of the test complexity of the test plan includes: the testers analyzing the requirement complexity, technical risks, and data preparation difficulty of the test plan to obtain the estimated man-hours for the functional points.

[0084] This includes analyzing requirement complexity, which may involve breaking down test requirements into the smallest testable units and assessing the complexity of each unit; analyzing technical risks, which may include analyzing the impact of new technology applications, integration complexity, and external dependencies on the total test man-hours; and analyzing data preparation difficulty, which may include analyzing the complexity of test data construction, especially in scenarios with large data volumes. Through the analysis by testers, accurate estimates of the expected man-hours for each feature can be achieved.

[0085] In one embodiment, the task saturation situation includes task conflicts and / or full workload; the step of determining whether personnel scheduling is required based on monitoring results includes: if the testers have task conflicts and / or full workload within the scheduling window, then obtain personnel information from the project management system, and reschedule available personnel according to the personnel's workload and matching degree with the test plan; if not, then no personnel scheduling is performed.

[0086] Optionally, if there are no task conflicts or full workloads for the testers in the test plan within the monitoring schedule window, then that tester will be designated as the final tester for that test plan. If there are task conflicts and / or full workloads for the testers in the test plan within the monitoring schedule window, then another available person will be designated as the final tester for that test plan. After designating another available person, the schedule will be adjusted accordingly.

[0087] Optionally, personnel information can be obtained from the project management system, and available personnel can be rescheduled based on workload and matching with the test plan, or available personnel can be rescheduled based on historical performance.

[0088] In an example implementation, suppose the test plan is for a new payment function test, and the initially designated tester is Zhang San. The calculated schedule window is from November 10th to November 14th, 2025, requiring five consecutive days of testing. It is necessary to monitor whether Zhang San has a workload saturation within this schedule window to determine the final tester. If the project management system shows that Zhang San needs to perform refund function testing throughout the schedule window, this indicates a task conflict and workload saturation, requiring a re-selection of available personnel from the project management system. Conversely, if the project management system shows that Zhang San is not available for all five consecutive days during the schedule window, this indicates that the workload is full, also indicating workload saturation, requiring a re-selection of available personnel from the project management system.

[0089] In another example embodiment, suppose the test plan is a Bluetooth function test, and the initial designated tester is Xiao Wang. The calculated scheduling window is from December 3rd to December 5th, 2025, requiring three consecutive days of testing. However, Xiao Wang is at full capacity within the scheduling window. Therefore, from the project management system, after re-screening based on workload, skill matching, and historical performance, Li Si is designated as the final tester for this test plan. The scheduling is then readjusted based on Li Si's ability coefficient. If Li Si's ability coefficient is higher than Xiao Wang's, the testing time will be shortened.

[0090] In one embodiment, prior to obtaining the test plan data, the method further includes storing the test plan data, which is entered according to test requirements, in a database.

[0091] Optionally, a relational database can be used to store test plan data, and the MyBatis framework can be used for the data access layer to ensure efficient data storage and retrieval. By storing test plans in a database, test plans can be easily managed, queried, and modified.

[0092] In one embodiment, the automatic scheduling and personnel dispatching method based on the test plan further includes: monitoring changes to the test plan and obtaining the test plan before and after the change; comparing the test plan before and after the change to determine the content of the change; obtaining the final test personnel, the test start time, and the test completion time from the project management system; and adjusting the final test personnel, the test start time, and the test completion time accordingly based on the content of the change.

[0093] Optionally, changes to the test plan can be monitored in real time, including monitoring test types, estimated man-hours, and dependencies in the test plan.

[0094] Optionally, a difference comparison algorithm can be used to compare the test plans before and after the change. Specifically, this can be achieved through two steps: difference identification and path backtracking. Difference identification can employ the Myers algorithm, which determines the difference by calculating the minimum edit distance between two sequences. Here, the edit distance refers to the minimum number of operations required to transform one sequence into another, including insertion, deletion, or replacement. Path backtracking involves starting from the last element of the two-dimensional array and tracing back a path from the top left corner to the bottom right corner; this path represents the difference between the two sequences.

[0095] By identifying the changes and adjusting the final test personnel, test start time, and test completion time accordingly, the efficiency and accuracy of automatic scheduling and personnel allocation can be ensured.

[0096] In one embodiment, before monitoring changes to the test plan, the method further includes: listening for test requirement change notifications issued by the project management system; obtaining the test requirements before and after the change; comparing the test requirements before and after the change to determine the changed requirement content, so as to guide changes to the test plan.

[0097] Optionally, the test plan can be re-entered according to the changed requirements. After the test plan is changed, the test plan before and after the change is compared according to the difference comparison algorithm to determine the changed content, and the final test personnel, the test start time and the test completion time are adjusted accordingly.

[0098] In an exemplary embodiment, when the testing requirements of a new consumer business unit change, the project management system sends a notification of the changed testing requirements. Upon receiving this notification, the quality platform uses a difference comparison algorithm to compare the testing requirements before and after the change to determine the content of the changed requirements. Relevant personnel then modify the test plan according to these changed requirements. Once the quality platform detects the change in the test plan, it uses the difference comparison algorithm again to compare the test plans before and after the change to determine the content of the change. Based on the changed content, it adjusts the final testers, the test start time, and the test completion time accordingly. The adjusted final testers, test start time, and test completion time are then entered into the project management system, and a change notification is sent to relevant personnel. The adjusted final testers, test start time, and test completion time can be checked by the test team leader for their reasonableness.

[0099] In one example embodiment, an automatic scheduling and personnel dispatching method based on a test plan is provided. Figure 3 The flowchart of this method includes the following steps:

[0100] S301, Testers participate in requirements review to obtain requirements.

[0101] S302, Testers write test plan data into the quality platform according to requirements. Test plan data includes requirement work order number, test plan and tester information.

[0102] S303, the quality platform acquires test plan data and calculates the total test hours based on the test plan data.

[0103] S304, the quality platform obtains the test submission time from the project management system and determines the test start time and test completion time in combination with the total test man-hours.

[0104] S305, the quality platform uses a scheduling window consisting of the test start time and the test completion time to determine the final testers.

[0105] S306, the quality platform will enter the final tester, test start time, and test completion time into the project management system.

[0106] S307, the quality platform monitors whether the project management system has issued a change notification for test requirements. If yes, proceed to step S308; otherwise, continue monitoring.

[0107] S308, the quality platform obtains the test requirements before and after the change, and uses a difference comparison algorithm to compare and determine the changed requirements.

[0108] S309, the quality platform monitors whether the testers have changed the test plan. If yes, proceed to step S310; otherwise, continue monitoring.

[0109] S310, the quality platform obtains the test plans before and after the change, and uses a difference comparison algorithm to compare them to determine the content of the change.

[0110] S311, the quality platform obtains the final tester, the test start time, and the test completion time from the project management system.

[0111] S312, the quality platform adjusts the final tester, the test start time, and the test completion time accordingly based on the changed content.

[0112] S313, the quality platform enters the adjusted final testers, the test start time, and the test completion time into the project management system and sends a change notification to relevant personnel.

[0113] Optionally, after step S305, you can jump to step S309 and directly use the quality platform to monitor whether the testers have changed the test plan. If so, proceed to steps S310 to S313.

[0114] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0115] Based on the same inventive concept, this application also provides an automatic scheduling and personnel scheduling device based on a test plan for implementing the aforementioned automatic scheduling and personnel scheduling method based on a test plan. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more embodiments of the automatic scheduling and personnel scheduling device based on a test plan provided below can be found in the limitations of the automatic scheduling and personnel scheduling method based on a test plan described above, and will not be repeated here.

[0116] In one embodiment, such as Figure 4 As shown, an automatic scheduling and personnel dispatching device based on a test plan is provided, including:

[0117] The scheduling algorithm module 41 is used to obtain test plan data, which includes a requirement work order number, a test plan, and tester information; calculate the total test hours based on the test plan and tester information; and obtain project-related time information corresponding to the requirement work order number from the project management system, which includes the test submission time.

[0118] The personnel scheduling module 42 is used to determine the test start time and test completion time based on the total test hours and the test submission time; monitor whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time; and determine whether personnel scheduling needs to be performed based on the monitoring results, thereby determining the final testers to execute the test plan.

[0119] The aforementioned automatic scheduling and personnel dispatching device based on test plans employs the following steps: First, it acquires test plan data, including the requirement work order number, the test plan itself, and tester information. Based on this data, it calculates the total test hours. Then, it retrieves project-related time information corresponding to the requirement work order number from the project management system, including the test submission time. Based on the total test hours and the test submission time, it determines the test start and end times. Finally, it monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start and end times, and determines whether personnel dispatching is necessary based on the monitoring results, thereby identifying the final testers to execute the test plan. This achieves automatic scheduling and personnel deployment, ensuring that the test plan can be effectively executed within the scheduling window.

[0120] Furthermore, the test plan includes dependencies, which are used to identify the dependencies between tests. The scheduling algorithm module 41 is also used to analyze the test complexity of the test plan, determine the estimated working hours for each function point; obtain the capability coefficient of the testers; determine the buffer time based on the dependencies and the estimated working hours for each function point; and determine the total test working hours based on the estimated working hours for each function point, the capability coefficient, and the buffer time.

[0121] Furthermore, the scheduling algorithm module 41 is also used by the testers to analyze the complexity of the test plan requirements, technical risks, and data preparation difficulties to obtain the estimated working hours for the function points.

[0122] Furthermore, the task saturation situation includes task conflicts and / or full workload; the step of determining whether personnel scheduling is necessary based on monitoring results. The personnel scheduling module 42 is also used to obtain personnel information from the project management system if the test personnel have task conflicts and / or full workload within the scheduling window, and to reschedule available personnel according to the personnel's workload and matching degree with the test plan; if not, no personnel scheduling is performed.

[0123] Furthermore, the aforementioned automatic scheduling and personnel dispatching device based on a test plan also includes:

[0124] The intelligent adjustment module is used to monitor changes to the test plan, obtain the test plan before and after the change; compare the test plan before and after the change to determine the content of the change; obtain the final testers, the test start time, and the test completion time from the project management system; and adjust the final testers, the test start time, and the test completion time accordingly based on the content of the change.

[0125] Furthermore, the intelligent adjustment module is also used to monitor test requirement change notifications issued by the project management system; obtain the test requirements before and after the change; compare the test requirements before and after the change, determine the changed requirement content, and guide the modification of the test plan.

[0126] The modules in the aforementioned automated scheduling and personnel dispatching device based on test plans can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, 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.

[0127] In one embodiment, an automated scheduling and personnel dispatching system based on a test plan is provided. The system includes a platform system and a project management system. The platform system interacts with the project management system through a data interaction interface. The platform system implements the following steps:

[0128] Obtain test plan data, which includes the requirement work order number, test plan, and tester information;

[0129] Based on the test plan and test personnel information, calculate the total test hours;

[0130] Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0131] Based on the total test time and the test submission time, the test start time and test completion time are determined.

[0132] The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan.

[0133] Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0134] 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:

[0135] Obtain test plan data, which includes the requirement work order number, test plan, and tester information;

[0136] Based on the test plan and test personnel information, calculate the total test hours;

[0137] Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time.

[0138] Based on the total test time and the test submission time, the test start time and test completion time are determined.

[0139] The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan.

[0140] Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

[0141] 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, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0142] 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 application.

[0143] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. 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 application should be determined by the appended claims.

Claims

1. An automatic scheduling and personnel dispatching method based on test plans, characterized in that, include: Obtain test plan data, which includes the requirement work order number, test plan, and tester information; Based on the test plan and test personnel information, calculate the total test hours; Obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time. Based on the total test time and the test submission time, the test start time and test completion time are determined. The system monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and the test completion time. Based on the monitoring results, it determines whether personnel scheduling is necessary, thereby determining the final testers to execute the test plan. Based on the required work order number, the final tester, the test start time, and the test completion time are entered into the project management system.

2. The method according to claim 1, characterized in that, The test plan includes dependencies, which are used to identify the dependencies between tests; The calculation of total test hours includes: The test complexity of the test plan is analyzed to determine the estimated man-hours for each function point; Obtain the ability coefficient of the tester; The buffer time is determined based on the dependencies and the estimated working hours of the function points; The total test time is determined based on the estimated working hours of the function points, the capacity coefficient, and the buffer time.

3. The method according to claim 2, characterized in that, The analysis of the test complexity of the test plan includes: The testers analyze the complexity of the test plan requirements, technical risks, and data preparation difficulties to obtain the estimated working hours for the functional points.

4. The method according to claim 1, characterized in that, The task saturation situation includes task conflicts and / or full workload; the step of determining whether personnel scheduling is needed based on monitoring results includes: If the testers have task conflicts and / or their workload is full within the scheduling window, the personnel information is retrieved from the project management system, and available personnel are rescheduled based on the personnel's workload and their matching degree with the test plan. If it does not exist, no personnel will be dispatched.

5. The method according to claim 1, characterized in that, Before obtaining the test plan data, the following steps are also included: The test plan data entered according to the test requirements will be stored in the database.

6. The method according to claim 1, characterized in that, Also includes: Monitor changes to the test plan and obtain the test plan before and after the change; Compare the test plans before and after the changes to determine the content of the changes; Obtain the final tester, the test start time, and the test completion time from the project management system; Based on the changes, the final test personnel, the test start time, and the test completion time will be adjusted accordingly.

7. The method according to claim 6, characterized in that, Before monitoring changes to the test plan, the process also includes: Listen for test requirement change notifications issued by the project management system; Obtain the test requirements before and after the change; Compare the test requirements before and after the change to determine the changed requirements, so as to guide the modification of the test plan.

8. An automatic scheduling and personnel dispatching device based on a test plan, characterized in that, include: The scheduling algorithm module is used to obtain test plan data, which includes the requirement work order number, test plan, and tester information. Based on the test plan and test personnel information, calculate the total test hours; The personnel scheduling module is used to obtain project-related time information corresponding to the required work order number from the project management system. The project-related time information includes the test submission time. Based on the total test hours and the test submission time, the module determines the test start time and test completion time. The module monitors whether the testers in the test plan are experiencing task saturation within the scheduling window formed by the test start time and test completion time. Based on the monitoring results, the module determines whether personnel scheduling is required, thereby determining the final testers to execute the test plan.

9. An automatic scheduling and personnel dispatching system based on test plans, characterized in that, The system includes a platform system and a project management system. The platform system interacts with the project management system through a data interaction interface. The platform system implements the steps of the method according to any one of claims 1 to 7.

10. 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 7.

Images