Test task allocation method and device, electronic equipment and storage medium
By integrating the historical data of testers on the work collaboration platform, generating test user portraits and selecting target test modes, and automatically assigning test tasks, the high cost and inefficiency problems caused by manual allocation are solved, and more efficient test task allocation is achieved.
Patent Information
- Application Number
- CN202510409247.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-02
- Publication Date
- 2025-07-18
AI Technical Summary
In the prior art, the allocation of software testing tasks mainly relies on manual allocation, which is easily affected by subjective factors of allocating personnel, resulting in high allocation cost and low allocation efficiency of test tasks.
By obtaining the historical test work data of the work collaboration platform, the test user portrait information of the tester is integrated and sorting out, and the target test mode is selected based on the work status data of the software test group, a requirement test allocation table is generated, and the test tasks are automatically assigned.
It reduces the influence of human subjective factors, improves the objectivity of testing task allocation, reduces costs and improves allocation efficiency.
Smart Images
Figure CN120336175A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, specifically to the field of software testing technology, and particularly to a test task allocation method, device, electronic device, and storage medium. Background Art
[0002] During the software development process, in order to achieve the goals of improving the software quality at the time of software launch, reducing the later maintenance cost, and increasing the satisfaction of software users, software testing has become an essential part of the software development process. And the allocation of test tasks in the software testing process has a great impact on the completion efficiency of test tasks.
[0003] In the prior art, the allocation of software test tasks mainly depends on the test team leader to subjectively judge after reviewing the business requirements, the complexity of test tasks, and the working ability of each tester, and then manually allocate test tasks.
[0004] The inventor found that in the prior art, there are at least the following technical problems: mainly relying on manual allocation of test tasks is easily affected by the subjective factors of the allocator, resulting in high costs and low efficiency of test task allocation. Summary of the Invention
[0005] Embodiments of this application provide a test task allocation method, device, electronic device, and storage medium, so as to achieve the effects of reducing the influence degree of subjective factors on test task allocation, reducing the cost of test task allocation, and improving the efficiency of test task allocation.
[0006] In a first aspect, embodiments of this application provide a test task allocation method, which is applied to a server and includes:
[0007] Obtain historical test work data of the work collaboration platform;
[0008] Perform an integration and sorting operation on the historical test work data to obtain test user profile information of all testers in the software test group;
[0009] Obtain information about the software to be tested and work status data of the software test group;
[0010] Select a target test mode from the preset mode decisions according to the work status data of the software test group;
[0011] Generate a requirements test allocation table according to the test user profile information and the target test mode;
[0012] Send the information about the software to be tested to the operation terminals of each tester in the software test group according to the requirements test allocation table, so that the operation terminals complete the software test and generate test results;
[0013] Receive the test results returned by the operation terminal.
[0014] In a possible implementation manner, the historical test work data includes historical requirement data, historical test task data, historical test case data, and historical test defect data; correspondingly, performing an integration and sorting operation according to the historical test work data to obtain test user portrait information of all testers in the software test group, including: using a pre-stored database query language to count according to the historical requirement data to obtain the associated data between the requirement function module and the tester and the requirement test difficulty data; using a pre-stored database query language to count according to the historical test task data to obtain the tester's test time data; using a pre-stored database query language to count according to the historical test case data to obtain the test case writing efficiency data of the tester; determining the test defect associated data of the tester according to the historical test defect data, historical requirement data, and historical test case data; performing statistical processing according to the associated data between the requirement function module and the tester, the requirement test difficulty data, the tester's test time data, the test case writing efficiency data of the tester, and the test defect associated data of the tester through a preset statistical rule to obtain the test user portrait information of all testers in the software test group.
[0015] In a possible implementation manner, the historical test defect data includes the number of discovered defects and the number of missed defects, the historical requirement data includes the number of test requirements, and the historical test case data includes the number of newly created test cases; correspondingly, determining the test defect associated data of the tester according to the historical test defect data, historical requirement data, and historical test case data includes: determining the defect discovery rate according to the number of discovered defects and the number of test requirements; determining the missed defect rate according to the number of missed defects and the number of test requirements; determining the defect discovery efficiency according to the number of discovered defects and the number of newly created test cases; determining the defect discovery rate, the missed defect rate, and the defect discovery efficiency as the test defect associated data of the tester.
[0016] In a possible implementation manner, the preset mode decision includes a sprint mode and a training mode; correspondingly, selecting a target test mode from the preset mode decision according to the software test group work status data includes: performing a work evaluation process on the testers according to the software test group work status data to obtain the work status description information of the software test group; when it is detected that the work status description information of the software test group is in a sprint state, then select the sprint mode from the preset mode decision as the target test mode; when it is detected that the work status of the software test group is in an idle state, then select the training mode from the preset mode decision as the target test mode.
[0017] In a possible implementation, before selecting a target test mode from the preset mode decision based on the software test group's working status data, it further includes: obtaining a mode selection operation instruction, where the instruction is generated by the terminal of the software test leader of the software test group in response to the mode selection operation of the software test leader; and selecting a sprint mode or a training mode as the target test mode from the preset mode decision according to the mode selection operation instruction.
[0018] In a possible implementation, it further includes: obtaining actual work requirement information; and performing parameter configuration processing on the preset statistical rule according to the actual work requirement information to obtain a new preset statistical rule.
[0019] In a possible implementation, before obtaining the historical test work data of the work collaboration platform, it further includes: receiving access request information from the operation terminal; and performing user information authentication processing by the work collaboration platform according to the access request information to establish a data acquisition channel with the operation terminal.
[0020] In a possible implementation, after receiving the test result returned by the operation terminal, it further includes: receiving access request information from the operation terminal; performing user information authentication processing by the work collaboration platform according to the access request information to establish a data transmission channel with the operation terminal; receiving platform modification data sent by the operation terminal through the data transmission channel, and performing an update operation on the historical test work data of the work collaboration platform according to the platform modification data to obtain new historical test work data.
[0021] In a second aspect, an embodiment of the present application provides a test task allocation device, including:
[0022] An acquisition module, configured to acquire historical test work data of a work collaboration platform;
[0023] A portrait generation module, configured to perform integration and sorting operations according to the historical test work data to obtain test user portrait information of all testers in the software test group;
[0024] The acquisition module is further configured to acquire information about the software to be tested and the working status data of the software test group;
[0025] A mode decision module, configured to select a target test mode from the preset mode decision according to the working status data of the software test group;
[0026] A test allocation module, configured to generate a requirement test allocation form according to the test user portrait information and the target test mode;
[0027] The test assignment module is further configured to send the software information to be tested to the operation terminals of each tester in the software test group according to the demand test assignment table, so that the operation terminals complete the software test and generate test results.
[0028] The obtaining module is further configured to receive the test results returned by the operation terminals.
[0029] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor;
[0030] The memory stores computer execution instructions;
[0031] The processor executes the computer execution instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementation manners of the first aspect.
[0032] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the above first aspect and / or various possible implementation manners of the first aspect.
[0033] An embodiment of the present application provides a test task assignment method, device, electronic device and storage medium. The method first performs an integration and sorting operation on the obtained historical test work data to obtain the test user portrait information of all testers in the software test group, then selects a target test mode according to the software test group work status data, and then generates a demand test assignment table according to the test user portrait information and the target test mode, so as to subsequently send the software information to be tested to the operation terminals of each tester according to the demand test assignment table, so that the operation terminals complete the software test and generate test results. It reduces the influence of human subjective factors in the entire test task assignment process, improves the objectivity of test task assignment, reduces the cost of test task assignment, and improves the efficiency of test task assignment. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.
[0035] Figure 1 It is a schematic diagram of the scenario of the test task assignment method provided by the present application;
[0036] Figure 2 It is a schematic flowchart of the test task assignment method provided by the present application;
[0037] Figure 3 It is a schematic diagram of the implementation process of the test task assignment method provided by an embodiment of the present application;
[0038] Figure 4 Schematic structural diagram of the test task allocation device provided for this application;
[0039] Figure 5 Schematic structural diagram of the electronic device provided for this application.
[0040] Through the above-mentioned drawings, specific embodiments of this application have been shown, and more detailed descriptions will be given in the following text. These drawings and textual descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. Detailed implementation manners
[0041] Exemplary embodiments will be described in detail herein, and examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this application. On the contrary, they are merely examples of devices and methods consistent with some aspects of this application as detailed in the appended claims.
[0042] The inventors found in the practice process that in the prior art, software test task allocation work is based on the data of the work collaboration platform, where the work collaboration platform is the daily office system for personnel in the software development group's requirements, development, testing, and operation and maintenance positions. Daily work data such as business requirements, test cases, test tasks, and test defects are circulated on the work collaboration platform. When performing test task allocation work, the test team leader allocates test tasks by combining factors such as the importance, complexity, online time of business requirements, and the work ability of test personnel. Therefore, the subjective factors have a greater impact and there is a lack of objective data support, resulting in problems of high test task allocation cost and low allocation efficiency.
[0043] In response to the above technical problems, the inventors proposed the following inventive concept: First, collect test work data on the work collaboration platform, analyze the work ability of test personnel based on these test work data, form a test personnel ability profile, and when performing test task allocation, automatically allocate requirement test tasks according to the test personnel ability profile, which improves the objectivity of test task allocation, reduces the test task allocation cost, and improves the test task allocation efficiency.
[0044] The following uses specific embodiments to detail the technical solutions of this application and how the technical solutions of this application solve the above technical problems. These several specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below in conjunction with the drawings.
[0045] Figure 1Schematic diagram of the scenario for the test task allocation method provided by this application, as Figure 1 shown, the specific application scenarios of this application include: an operation terminal 101 and a server 102.
[0046] Among them, the operation terminal 101 can be the operation terminals of task assignees and testers in a software test workgroup. The operation terminal 101 can be a computer, a tablet computer, or other computer-related devices that can respond to the operation instructions of task assignees. The operation terminal 101 can also display the test task allocation results. The server 102 can be a hardware device installed with a work collaboration platform. The server 102 is used to receive the daily work data of post personnel sent by other terminals in the software test group and automatically execute the task allocation task.
[0047] Figure 2 Schematic diagram of the process for the test task allocation method provided by this application, as Figure 2 shown, the execution entity of this test task allocation method can be Figure 1 the server 102 shown, or other computer-related devices that can perform the test task allocation function. This embodiment does not limit this here.
[0048] As Figure 2 shown, this test task allocation method includes:
[0049] S201: Obtain the historical test work data of the work collaboration platform.
[0050] In this embodiment, the historical test work data can be all the test work data related to the software test group that has been carried out and stored based on the work collaboration platform.
[0051] S202: Perform an integration and sorting operation based on the historical test work data to obtain the test user portrait information of all team members in the software test group.
[0052] In this embodiment, the integration and sorting operation can be a process of statistically sorting out the test work data related to each tester from the historical test work data. These statistical results can be used to describe the personnel portrait data such as the test capabilities of each tester and the test requirements met.
[0053] Specifically, in an optional embodiment of this application, the historical test work data includes historical requirement data, historical test task data, historical test case data, and historical test defect data; correspondingly, step S202 includes:
[0054] S202a: Use the pre-stored database query language to statistically analyze the historical requirement data to obtain the associated data between the requirement function modules and testers and the requirement test difficulty data.
[0055] In this embodiment, the historical requirement data may include information related to requirements such as requirement description, functional module, software development person in charge, software testing, software development workload, software testing workload, etc.
[0056] In this embodiment, the pre-stored database query language may be a language for interacting with a database, such as SQL, which can be specifically used to access, query, update, and manage a relational database system. The requirement function module and tester association data may be data indicating the number of times which test function modules are tested by which testers. For example, the requirement function module A is tested 10 times by the first tester and 1 time by the second tester. Then, when allocating software testing tasks subsequently, if the test requirement is to obtain a test report as soon as possible, the test task of the requirement function module A can be assigned to the first test team member.
[0057] In this embodiment, the requirement test difficulty data can be determined according to the software testing workload. For example, the greater the software testing workload, the greater the requirement test difficulty.
[0058] S202b: Use the pre-stored database query language to count based on the historical test task data to obtain the tester test time data.
[0059] In this embodiment, the historical test task data may include data related to the test process such as task description, functional module, software testing person in charge, task start time, task end time, etc. In this embodiment, the pre-stored database query language SQL can also be used to count the tester test time data.
[0060] In this embodiment, the tester test time data may be the test time of each tester in each functional cabinet module. Based on the tester test time data, it can be counted which testers spend more test time in which test modules, providing data for subsequent test task allocation.
[0061] S202c: Use the pre-stored database query language to count based on the historical test case data to obtain the test case writing efficiency data of the testers.
[0062] In this embodiment, the historical test case data may include information such as operation steps, expected results, functional module, software testing person in charge, writing start time, and writing end time. In this embodiment, the pre-stored database query language SQL can also be used to count which testers write more test cases for which functional modules and the efficiency of which testers in writing test cases. Provide data for subsequent software testing task allocation.
[0063] S202d: Determine the test defect association data of the testers according to the historical test defect data, historical requirement data, and historical test case data.
[0064] In an optional embodiment of the present application, the historical test defect data may include function modules, software test team leaders, and defect types. The test defect correlation data may include data related to the defect discovery rate, missed defect rate, test efficiency of testers, and which function modules the defects are concentrated in, etc.
[0065] Specifically, in an optional embodiment of the present application, the historical test defect data includes the number of discovered defects and the number of missed defects, the historical requirement data includes the number of test requirements, the historical test case data includes the number of newly created test cases, and step S202d includes:
[0066] Step d1: Determine the defect discovery rate according to the number of discovered defects and the number of test requirements.
[0067] In this embodiment, step d1 can be expressed as formula 1: Defect discovery rate = (Number of discovered defects ÷ Number of test requirements).
[0068] Step d2: Determine the missed defect rate according to the number of missed defects and the number of test requirements.
[0069] In this embodiment, step d2 can be expressed as formula 2: Missed defect rate = (Number of missed defects ÷ Number of test requirements).
[0070] Step d3: Determine the defect discovery efficiency according to the number of discovered defects and the number of newly created test cases.
[0071] In this embodiment, step d3 can be expressed as formula 3: Defect discovery efficiency = (Number of discovered defects ÷ Number of newly created test cases).
[0072] In an optional embodiment of the present application, the defect discovery efficiency can also be the number of test cases written for the same function module, the number of discovered defects, the number of missed defects, and the time to obtain the number of discovered defects and the number of missed defects.
[0073] Step d4: Determine the defect discovery rate, missed defect rate, and defect discovery efficiency as the test defect correlation data of the tester.
[0074] In this embodiment, the defect discovery rate, missed defect rate, and defect discovery efficiency are used as the test defect correlation data of the tester to provide data for obtaining the test user portrait information later.
[0075] S202e: According to the requirement function module and tester correlation data, requirement test difficulty data, tester test time data, tester test case writing efficiency data, and tester test defect correlation data, perform statistical processing through a preset statistical rule to obtain the test user portrait information of all testers in the software test group.
[0076] In this embodiment, the test user portrait information of all testers in the software test group can be information that can represent the test capabilities of the testers or the fields in which they are good at testing work.
[0077] Exemplarily, the test user portrait information of all testers in the software test group is as follows:
[0078] Before, Function Module A was mainly tested by Tester No. 1 and Tester No. 2. Among them, Tester No. 1 created 100 test cases, spent 8 hours on test tasks, and found 20 defects; Tester No. 2 created 30 test cases, spent 3 hours on test tasks, and found 3 defects.
[0079] Tester No. 3 is mainly responsible for manual testing of page functions, and created 50 manual test cases for page functions and 10 automated test cases.
[0080] Tester No. 4 is mainly responsible for automated testing, and created 200 automated test cases and 20 page function test cases.
[0081] Tester No. 5 is mainly responsible for tasks such as the joint debugging of requirement functions and the setup and maintenance of the test environment.
[0082] In this embodiment, the preset statistical rules can be preset statistical indicators and formulas.
[0083] Based on the above embodiment, the test task allocation method provided in an optional embodiment of the present application further includes:
[0084] Step a: Obtain actual work requirement information.
[0085] Step b: Perform parameter configuration processing on the preset statistical rules according to the actual work requirement information to obtain new preset statistical rules.
[0086] In this embodiment, the actual work requirement information can be information related to test tasks such as test requirements and software development requirements. Parameter configuration processing refers to the process of modifying the parameters of the preset statistical rules according to the actual work requirement information. For example: when the test requirement is to train the newly added testers in the software test group, at this time, the data with low defect discovery efficiency of the testers can be focused on for statistics and used as one of the reference bases for test task allocation.
[0087] S203: Obtain the information of the software to be tested and the working status data of the software test group.
[0088] In this embodiment, the working status data of the software testing group may be data recorded by the server in real time through the work collaboration platform on whether the working status of the operation terminals of each tester in the software testing group is idle or in a testing state.
[0089] S204: Select a target testing mode from the preset mode decisions according to the working status data of the software testing group.
[0090] In this embodiment, the working status data of the software testing group can be used to determine which testing method the entire software testing group can select according to the testing requirements.
[0091] In an alternative embodiment of the present application, the preset mode decisions include a sprint mode and a training mode. Correspondingly, step S204 includes:
[0092] S204a: Perform a work evaluation process on the testers according to the working status data of the software testing group to obtain the working status description information of the software testing group.
[0093] S204b: When it is detected that the working status description information of the software testing group is in a sprint state, select the sprint mode as the target testing mode from the preset mode decisions.
[0094] In this embodiment, after matching the corresponding testing requirements, it is possible to traverse and find the testers among all the testers in the working status description information of the software testing group who are responsible for writing test cases and finding more defects in this module, and designate these testers to be responsible for testing this testing requirement.
[0095] In this embodiment, the sprint mode can perform a forward allocation of new requirement testing based on historical data to ensure that the testing quality reaches the sprint effect, so that each tester can perform the testing task quickly and well after the testing task is assigned.
[0096] S204c: When it is detected that the working status of the software testing group is in an idle state, select the training mode as the target testing mode from the preset mode decisions.
[0097] In this embodiment, after matching the corresponding testing requirements, traverse and find the testers among all the testers in the working status description information of the software testing group who are responsible for writing test cases and finding fewer defects in this module, and designate these testers to be responsible for testing this testing requirement.
[0098] In this embodiment, the training mode can perform a reverse allocation of new requirement testing based on historical data. Although the testing quality is sacrificed to a certain extent, the training effect is achieved. When the testing tasks are not busy, it can effectively exercise the testing ability of newly added testers and provide a basis for improving the testing efficiency in the subsequent sprint mode.
[0099] The above is the way to automatically select the target test mode. In some special cases, such as when a batch of urgent software to be tested is added temporarily and the person in charge of software testing needs to adjust the software testing assignment task, in an alternative embodiment of the present application, before step S204, it further includes: the step of obtaining a mode selection operation instruction, which is generated by the terminal of the person in charge of software testing in the software testing group in response to the mode selection operation of the person in charge of software testing; selecting the sprint mode or the training mode as the target test mode from the preset mode decision according to the mode selection operation instruction.
[0100] In this embodiment, the person in charge of software testing in the software testing group can respond quickly according to the actual situation or temporary requirements, and select the sprint mode or the training mode as the target test mode, so as to quickly complete the test task assignment work.
[0101] S205: Generate a requirements test assignment form according to the test user portrait information and the target test mode.
[0102] In this embodiment, the requirements test assignment form can be a chart indicating that different requirements are assigned to different software testers.
[0103] S206: Send the software information to be tested to the operation terminal of the tester according to the requirements test assignment form, so that the operation terminal completes the software test and generates a test result.
[0104] In this embodiment, sending the software information to be tested to the operation terminal of the tester according to the requirements test assignment form means distributing the to-be-tested function modules in the software information to be tested to the operation terminals of different testers according to the requirements test assignment form, so that the corresponding testers complete the corresponding software test tasks at the operation terminal and obtain the test results.
[0105] S207: Receive the test result returned by the operation terminal.
[0106] In this embodiment, the server can automatically collect the test results generated by the operation terminals of the testers through the work collaboration platform to complete the entire test task assignment work.
[0107] Based on the above embodiments, as a test task assignment method provided in an alternative embodiment of the present application, before step S201, it further includes:
[0108] Step A: Receive the access request information of the operation terminal.
[0109] In this embodiment, the access request information can be the login information and the encrypted data packet to be authenticated sent when the operation terminal of the tester automatically logs in or logs in to the work collaboration platform manually after startup.
[0110] Step B: The work collaboration platform performs user information authentication processing based on the access request information to establish a data acquisition channel with the operation terminal.
[0111] In this embodiment, the built-in encryption authentication mechanism of the work collaboration platform can perform user authentication processing based on the access request information, that is, perform permission authentication. After passing the authentication, the operation terminal can obtain the stored historical test work data from the server through the work collaboration platform. Otherwise, it cannot obtain the stored historical test work data.
[0112] Based on the above embodiment, in an optional embodiment of the present application, the test task allocation method further includes, after step S207:
[0113] Step C: Receive the access request information of the operation terminal.
[0114] Step D: The work collaboration platform performs user information authentication processing based on the access request information to establish a data transmission channel with the operation terminal.
[0115] In this embodiment, the principle of user information authentication in steps C and D is similar to that in steps A and B in the above embodiment, so it will not be elaborated here in this embodiment.
[0116] Step E: Receive the platform modification data sent by the operation terminal through the data transmission channel, and update the historical test work data of the work collaboration platform according to the platform modification data to obtain new historical test work data.
[0117] In this embodiment, only the operation terminal that passes the user information authentication can send platform modification data to the server. The platform modification data can be data related to the tester's test association data and can be used to modify the test user portrait information. These data are merged into the historical test work data to provide real-time updated data for subsequent test task allocation, making the data of the subsequent obtained test user portrait information more accurate. And modifying the platform data through user information authentication can be modified in real time, which is simpler and more efficient than the system database synchronization method.
[0118] Figure 3 It is a schematic diagram of the implementation process of the test task allocation method provided in the embodiment of the present application.
[0119] As Figure 3 shown, after logging in to the work collaboration platform, user information authentication operations can be performed first. When the user information authentication passes, platform data can be obtained. These platform data can include the historical test work data, to-be-tested software information, and software test group work status data in the above embodiment. Specifically, the obtained platform test data is mainly divided into historical requirement data, test task data, test case data, test defect data, and to-be-tested requirement data.
[0120] Then, count the platform data to obtain the data required for the tester portrait and obtain the test user portrait information. The test user portrait information may include descriptive information such as function modules, testers, task duration, defect discovery rate, and missed defect rate.
[0121] Then, perform mode decision to select the sprint mode or the training mode, and generate a requirement test allocation table according to the test user portrait information and the target test mode. The requirement test allocation table may include that for the sprint mode, key requirements are allocated to a type of testers who are proficient in testing work, and other requirements are allocated to a type of new testers; in the training mode, key requirements are allocated to the new type of testers, and other requirements are allocated to the type of testers who are proficient in testing work.
[0122] Finally, after the test is completed and when modifying the platform data, first perform user information authentication and then complete the modification of the platform data.
[0123] In summary, for the test task allocation method provided in the embodiment of the present application, first, perform an integration and sorting operation on the obtained historical test work data to obtain the test user portrait information of all testers in the software test group, then select the target test mode according to the software test group work status data, and then generate a requirement test allocation table according to the test user portrait information and the target test mode, so as to subsequently send the software information to be tested to the operation terminals of each tester according to the requirement test allocation table, so that the operation terminals complete the software test and generate test results. It reduces the influence of human subjective factors in the entire test task allocation process, improves the objectivity of test task allocation, reduces the cost of test task allocation, and improves the efficiency of test task allocation.
[0124] Figure 4 It is a schematic structural diagram of a test task allocation device provided by the present application, which is applied to the Figure 1 server 102 as shown in Figure 4 As shown, the test task allocation device provided in this embodiment includes: an acquisition module 41, a portrait generation module 42, a mode decision module 43, and a test allocation module 44.
[0125] Among them, the acquisition module 41 is used to acquire the historical test work data of the work collaboration platform.
[0126] The portrait generation module 42 is used to perform an integration and sorting operation on the historical test work data to obtain the test user portrait information of all testers in the software test group.
[0127] The acquisition module 41 is further used to acquire the software information to be tested and the software test group work status data.
[0128] The mode decision module 43 is configured to select a target test mode from preset mode decisions according to the working status data of the software test group.
[0129] The test assignment module 44 is configured to generate a requirements test assignment form according to the test user profile information and the target test mode.
[0130] The test assignment module 44 is further configured to send the software information to be tested to the operation terminals of each tester in the software test group according to the requirements test assignment form, so that the operation terminals complete the software test and generate test results.
[0131] The acquisition module 41 is further configured to receive the test results returned by the operation terminals.
[0132] In a possible implementation manner, the historical test work data includes historical requirement data, historical test task data, historical test case data, and historical test defect data; correspondingly, the profile generation module 42 is specifically configured to: use the pre-stored database query language to count according to the historical requirement data to obtain the associated data between the requirement function module and the tester and the requirement test difficulty data; use the pre-stored database query language to count according to the historical test task data to obtain the tester's test time data; use the pre-stored database query language to count according to the historical test case data to obtain the test case writing efficiency data of the tester; determine the test defect associated data of the tester according to the historical test defect data, historical requirement data, and historical test case data; perform statistical processing on the associated data between the requirement function module and the tester, the requirement test difficulty data, the tester's test time data, the test case writing efficiency data of the tester, and the test defect associated data of the tester through preset statistical rules to obtain the test user profile information of all testers in the software test group.
[0133] In a possible implementation manner, the historical test defect data includes the number of discovered defects and the number of missed defects, the historical requirement data includes the number of test requirements, and the historical test case data includes the number of newly created test cases; correspondingly, the profile generation module 42 is specifically configured to: determine the discovered defect rate according to the number of discovered defects and the number of test requirements; determine the missed defect rate according to the number of missed defects and the number of test requirements; determine the discovered defect efficiency according to the number of discovered defects and the number of newly created test cases; determine the discovered defect rate, the missed defect rate, and the discovered defect efficiency as the test defect associated data of the tester.
[0134] In a possible implementation, the preset mode decision includes a sprint mode and a training mode; correspondingly, the mode decision module 43 is specifically configured to: perform a work evaluation process on testers based on the work status data of the software test group to obtain the work status description information of the software test group; when it is detected that the work status description information of the software test group is in a sprint state, select the sprint mode from the preset mode decision as the target test mode; when it is detected that the work status of the software test group is in an idle state, select the training mode from the preset mode decision as the target test mode.
[0135] In an alternative embodiment of the present application, the acquisition module 41 is further configured to: obtain a mode selection operation instruction, which is generated by the terminal of the software test leader of the software test group in response to the mode selection operation of the software test leader; the mode decision module 43 is further configured to: select the sprint mode or the training mode from the preset mode decision as the target test mode according to the mode selection operation instruction.
[0136] In an alternative embodiment of the present application, the acquisition module 41 is further configured to: obtain actual work requirement information; perform parameter configuration processing on the preset statistical rule according to the actual work requirement information to obtain a new preset statistical rule.
[0137] In an alternative embodiment of the present application, the acquisition module 41 is further configured to: receive access request information from the operation end; perform user information authentication processing according to the access request information through the work collaboration platform to establish a data acquisition channel with the operation end.
[0138] In an alternative embodiment of the present application, the acquisition module 41 is further configured to: receive access request information from the operation end; perform user information authentication processing according to the access request information through the work collaboration platform to establish a data transmission channel with the operation end; receive the platform modification data sent by the operation end through the data transmission channel, and update the historical test work data of the work collaboration platform according to the platform modification data to obtain new historical test work data.
[0139] The test task allocation device provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, which will not be elaborated here in this embodiment.
[0140] Figure 5 It is a schematic structural diagram of an electronic device provided for the present application. As Figure 5 shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. Among them, the processor 501, the memory 502, and the communication component 503 are connected through a bus.
[0141] In a specific implementation process, at least one processor 501 executes computer-executable instructions stored in a memory 502, so that at least one processor 501 executes the above method.
[0142] For the specific implementation process of the processor 501, reference may be made to the above method embodiment, and its implementation principle and technical effects are similar, so they will not be elaborated here in this embodiment.
[0143] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above test task allocation method is implemented.
[0144] An embodiment of the present application further provides a computer program product, including a computer program, which implements the above test task allocation method when executed by a processor.
[0145] In the above embodiments, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated as: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated as: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
[0146] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.
[0147] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.
[0148] The present application also provides a computer program product, including a computer program, which implements the above-mentioned method when executed by a processor.
[0149] The present application also provides a computer-readable storage medium storing computer-executable instructions, which implement the above-mentioned method when the processor executes the computer-executable instructions.
[0150] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk or an optical disc. The readable storage medium can be any available medium accessible by a general-purpose or special-purpose computer.
[0151] An exemplary readable storage medium is coupled to the processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in a device.
[0152] The division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the couplings, direct couplings or communication connections shown or discussed among each other can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.
[0153] The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0154] In addition, in each embodiment of the present invention, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.
[0155] If a function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present invention. The foregoing storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs, and other various media that can store program codes.
[0156] Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including the above method embodiments; and the foregoing storage medium includes: ROMs, RAMs, magnetic disks, or optical discs, and other various media that can store program codes.
[0157] Finally, it should be noted that: after considering the specification and practicing the invention disclosed herein, those skilled in the art will easily think of other implementation manners of the present invention. The present invention is intended to cover any variations, uses, or adaptations of the present invention. These variations, uses, or adaptations follow the general principles of the present invention and include common general knowledge or conventional technical means in the technical field not disclosed in the present invention. It is not limited to the precise structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present invention is only limited by the appended claims.
Claims
1. A test task allocation method, applied to a server, characterized in that, Including: Obtaining historical test work data of the work collaboration platform; Performing an integration and sorting operation based on the historical test work data to obtain test user profile information of all testers in the software test group; Obtaining information of the software to be tested and work status data of the software test group; Selecting a target test mode from the preset mode decisions according to the work status data of the software test group; Generating a requirements test allocation form according to the test user profile information and the target test mode; Sending the information of the software to be tested to the operation terminals of each tester in the software test group according to the requirements test allocation form, so that the operation terminals complete software testing and generate test results; Receiving the test results returned by the operation terminals.
2. The method according to claim 1, characterized in that The historical test work data includes historical requirement data, historical test task data, historical test case data, and historical test defect data; Correspondingly, the performing an integration and sorting operation based on the historical test work data to obtain test user profile information of all testers in the software test group includes: Statistically processing the historical requirement data using the pre-stored database query language to obtain associated data between requirement function modules and testers and requirement test difficulty data; Statistically processing the historical test task data using the pre-stored database query language to obtain testers' test time data; Statistically processing the historical test case data using the pre-stored database query language to obtain testers' test case writing efficiency data; Determining testers' test defect associated data according to the historical test defect data, historical requirement data, and historical test case data; Statistically processing the associated data between requirement function modules and testers, requirement test difficulty data, testers' test time data, testers' test case writing efficiency data, and testers' test defect associated data through preset statistical rules to obtain test user profile information of all testers in the software test group.
3. The method according to claim 2, wherein The historical test defect data includes the number of discovered defects and the number of missed defects, the historical requirement data includes the number of test requirements, and the historical test case data includes the number of newly created test cases; Correspondingly, the determining testers' test defect associated data according to the historical test defect data, historical requirement data, and historical test case data includes: Determining the defect discovery rate according to the number of discovered defects and the number of test requirements; Determining the missed defect rate according to the number of missed defects and the number of test requirements; Determining the defect discovery efficiency according to the number of discovered defects and the number of newly created test cases; Determining the defect discovery rate, the missed defect rate, and the defect discovery efficiency as testers' test defect associated data.
4. The method according to claim 1, wherein The preset mode decisions include a sprint mode and a training mode; Correspondingly, the selecting a target test mode from the preset mode decisions according to the work status data of the software test group includes: Performing a work evaluation process on the testers according to the work status data of the software test group to obtain work status description information of the software test group; When it is detected that the working status description information of the software test group is the sprint state, the sprint mode is selected from the preset mode decisions as the target test mode; When it is detected that the working status of the software test group is the idle state, the training mode is selected from the preset mode decisions as the target test mode.
5. The method according to claim 4, wherein Before selecting the target test mode from the preset mode decisions according to the working status data of the software test group, it further includes: Obtaining a mode selection operation instruction, which is generated by the terminal of the software test leader of the software test group in response to the mode selection operation of the software test leader; Selecting the sprint mode or the training mode from the preset mode decisions as the target test mode according to the mode selection operation instruction.
6. The method according to claim 2, wherein It further includes: Obtaining actual work requirement information; Performing parameter configuration processing on the preset statistical rule according to the actual work requirement information to obtain a new preset statistical rule.
7. The method according to any one of claims 1 to 6, characterized in that, Before obtaining the historical test work data of the work collaboration platform, it further includes: Receiving the access request information of the operation terminal; Performing user information authentication processing according to the access request information through the work collaboration platform to establish a data acquisition channel with the operation terminal.
8. The method according to claim 1, wherein After receiving the test result returned by the operation terminal, it further includes: Receiving the access request information of the operation terminal; Performing user information authentication processing according to the access request information through the work collaboration platform to establish a data transmission channel with the operation terminal; Receiving the platform modification data sent by the operation terminal through the data transmission channel, and performing an update operation on the historical test work data of the work collaboration platform according to the platform modification data to obtain new historical test work data.
9. A test task allocation device, characterized in that, It includes: An acquisition module, configured to acquire the historical test work data of the work collaboration platform; A portrait generation module, configured to perform an integration and sorting operation according to the historical test work data to obtain the test user portrait information of all testers in the software test group; The acquisition module is further configured to acquire the to-be-tested software information and the working status data of the software test group; A mode decision module, configured to select a target test mode from the preset mode decisions according to the working status data of the software test group; A test assignment module, configured to generate a requirement test assignment table according to the test user portrait information and the target test mode; The test assignment module is further configured to send the to-be-tested software information to the operation terminals of each tester in the software test group according to the requirement test assignment table, so that the operation terminals complete software testing and generate test results; The acquisition module is further configured to receive the test results returned by the operation terminals.
10. An electronic device, characterized in that, It includes: A memory, a processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the method according to any one of claims 1 to 8.
11. A computer-readable storage medium, characterized in that, Computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by the processor, they are used to implement the method according to any one of claims 1 to 8.