CN115860422A

CN115860422A - Test case distribution method and device

Info

Publication number: CN115860422A
Application number: CN202211680806.0A
Authority: CN
Inventors: 李男
Original assignee: Suzhou Inspur Intelligent Technology Co Ltd
Current assignee: Suzhou Inspur Intelligent Technology Co Ltd
Priority date: 2022-12-22
Filing date: 2022-12-22
Publication date: 2023-03-28

Abstract

The application discloses a test case distribution method and device, and belongs to the technical field of server testing. The method comprises the following steps: receiving a distribution waiting request sent by a test terminal; responding to the waiting distribution request, acquiring a first weight of the tester, and adding the identity information of the tester and the first weight into a testing manpower library; receiving a test case sent by a test case end; acquiring a second weight of the test case, and adding the test case and the second weight into a test case library; under the condition that the test case distribution condition is met, reading the test cases and the second weight from a test case library, and reading the tester identity information and the first weight from the tester library; and determining a target tester corresponding to the test case according to the first weight and the second weight, and distributing the test case to a tester corresponding to the identity information of the tester for testing.

Description

Test case distribution method and device

Technical Field

The application belongs to the technical field of server testing, and particularly relates to a method and a device for distributing test cases.

Background

With the continuous development of software and information technology industries, software tends to be large-scale and complex, and users pay more and more attention to the quality of the software. Software testing is an indispensable operation for guaranteeing the quality of software.

At present, software test cases are distributed mainly by means of manual distribution of responsible personnel, however, software complexity is increased, so that software test cases are increased, software test complexity is increased, the test personnel can be reused by multiple projects in a product development process, the level and the investable time of the test personnel are different, and the responsible personnel often need to spend a large amount of time for distributing the test cases.

Disclosure of Invention

The embodiment of the application aims to provide a test case allocation method and device, and the method and device can solve the problem that a responsible person needs to spend a large amount of time for allocating test cases due to the fact that a tester is possibly reused by a plurality of projects and the levels and the investable time of the tester are different in a product development process.

In a first aspect, an embodiment of the present application provides a method for distributing test cases, where the method includes:

receiving a distribution waiting request sent by a test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester;

responding to the waiting distribution request, acquiring a first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database;

receiving a test case sent by a test case end;

acquiring a second weight of the test case according to the test content of the test case, and adding the test case and the second weight into a test case library;

under the condition that the test case distribution condition is met, reading the test cases and the second weight from a test case library, and reading the tester identity information and the first weight from the tester library;

and determining a target tester corresponding to the test case according to the first weight and the second weight, and distributing the test case to a tester corresponding to the identity information of the tester for testing.

In a second aspect, an embodiment of the present application provides a test case assignment device, where the device includes:

the first receiving module is used for receiving a distribution waiting request sent by the test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester;

the first module is used for responding to the waiting distribution request, acquiring first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database;

the second receiving module is used for receiving the test case sent by the test case end; (ii) a

The second module is used for acquiring a second weight of the test case according to the test content of the test case, and adding the test case and the second weight into a test case library;

the reading module is used for reading the test cases and the second weight from the test case library and reading the identity information and the first weight of the tester from the tester library under the condition that the test case distribution condition is reached;

and the distribution module is used for determining a target tester corresponding to the test case according to the first weight and the second weight and distributing the test case to a tester corresponding to the identity information of the tester for testing.

In a third aspect, embodiments of the present application provide an electronic device, which includes a processor and a memory, where the memory stores a program or instructions executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

In a sixth aspect, embodiments of the present application provide a computer program product, stored on a storage medium, for execution by at least one processor to implement the method according to the first aspect.

The method comprises the steps of receiving a distribution waiting request sent by a test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester; responding to the waiting distribution request, acquiring a first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database; receiving a test case sent by a test case end; according to the test content of the test case, obtaining a second weight of the test case, and adding the test case and the second weight into a test case library; under the condition that the test case distribution condition is met, reading the test case and the second weight from a test case library, and reading the tester identity information and the first weight from the tester library; and determining a target tester corresponding to the test case according to the first weight and the second weight, and distributing the test case to a tester corresponding to the identity information of the tester for testing, so that the problem that a responsible person needs to spend a large amount of time for distributing the test case due to the fact that the tester is possibly reused by a plurality of projects and the level and the investable time of the tester are different in a product development process is solved.

Drawings

FIG. 1 is a flowchart of a test case allocation procedure provided in an embodiment of the present application;

fig. 2 is a block diagram of a test case distribution apparatus according to an embodiment of the present disclosure;

fig. 3 is an electronic device provided in an embodiment of the present application;

fig. 4 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or at least two. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

The message sending method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

The following description will be made of terms related to the embodiments of the present disclosure:

test case: the test case is a description of a test task performed on a specific software product, and embodies a test scheme, a method, a technology and a strategy. The contents of which may include test targets, test environments, input data, test steps, expected results, test scripts, etc., ultimately forming a document. The purpose of the test case is to determine whether a certain characteristic of a specific software product or software development project can work normally and can achieve a preset result. The test case is a guide of test work, is a criterion that software test must comply with, and is a fundamental guarantee of stable software test quality, and each software product or software development project needs to have a set of excellent test scheme and test method.

Referring to fig. 1, fig. 1 shows a flowchart of a test case allocation step provided by an embodiment of the present application, and as shown in fig. 1, the method specifically includes the following steps:

step 101, receiving a distribution waiting request sent by a test terminal; the wait for allocation request comprises: the tester identity information, the tester capability level information, and the tester investable time.

The test terminal may be a terminal used by a tester to test the test case, or any terminal capable of sending a request for waiting distribution to the test case distribution system. After receiving the request for waiting distribution, the test case distribution system acquires the information of the identity information of the tester, the capability level information of the tester, the investable time of the tester and the like included in the request for waiting distribution.

The tester identity information may include information for identifying identities of the tester, such as a name, a job number, and a department to which the tester belongs, and may also include a contact information of the tester, which is not specifically limited in this embodiment. The tester's capability level information reflects the tester's work level, or the amount of testing work the tester can perform a day. In the embodiment of the application, the capability level information of the tester is represented by the capability value. The higher the capability value of the tester is, the more test cases can be processed by the tester in one day or the more difficult the test cases can be tested. The following table is a capability level information table of a tester given in the embodiment of the application, and it can be seen that the tester capability is divided into three levels, i.e., a primary level, a middle level and a high level, and the capability value of the tester at the primary level is greater than or equal to 40 and less than 60; the middle-level tester capability value is more than or equal to 60 and less than 80; the advanced tester capability value is greater than or equal to 80 and less than 100.

TABLE 1 tester's capability level information sheet

Tester capability rating	Capacity value
		Primary stage	40～60
Middle stage	60～80
		Advanced	80～100

The investable time of the tester is the working time of the test that the tester can spend on the project, and can be expressed in various ways such as hours, days, dates and the like.

Step 102, responding to the waiting distribution request, obtaining a first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database.

In this embodiment, the first weight is used to reflect the testing workload that the tester can complete, because the capability level information of the tester can reflect the testing workload that the tester can complete in one day through the capability value, and the investable time of the tester includes the working time that the tester can spend in the testing of the project, the testing workload that the tester can complete can be obtained by multiplying the capability value and the investable time included in the capability level information.

For example, if the capacity of lee is 60 and the investable time is 3 days and half, the test workload that can be handled is 60 × 3.5=210. And so on. The obtained tester identity information and the first weight thereof may be added to the tester database in a format of "tester name — first weight value", for example: lie four-210; zhang III-160; wangwu-180.

And 103, receiving the test case sent by the test case terminal.

In the embodiment of the application, the test case terminal is a terminal which generates or owns a test case to be tested. And the test case terminal sends the generated or owned test case of the item to the test case distribution system, and the test case distribution system continues the subsequent distribution operation to distribute the test case to the tester.

And 104, acquiring a second weight of the test case according to the test content of the test case, and adding the test case and the second weight into a test case library.

In the embodiment of the present application, the second weight is used to reflect the workload of the test case, or the difficulty of the test case, and the time required for performing the test of the test case. The higher the value of the second weight of the test case is, the higher the difficulty of the test case is, and the more time is required for completing the test; the lower the value of the second weight of the test case, the less difficult the test case is, and the shorter the time it takes to complete the test. The obtained test case and the second weight thereof may be added to the test case library according to a format of "test case X — second weight value", for example: test cases 1-3.4; test case 2- -2.0; test cases 3-6.5.

The test content of the test case includes the content of the execution step and the like. Therefore, the test cases and the second weight are added into the test case library, and proper testers can be conveniently selected to distribute the test cases according to the second weight of the test cases.

And 105, reading the test cases and the second weight from the test case library and reading the identity information of the testers and the first weight from the tester library under the condition that the test case distribution condition is reached.

And the situation of the test case distribution condition is achieved, namely, the distribution is planned again under the situation that the test case distribution is needed, so that the system, the equipment or the terminal is prevented from repeatedly calculating. The first weight reflects the test workload which can be completed by a tester, and the second weight reflects the workload of the test case, so that the test case can be distributed according to the second weight of the test case and the first weight of the tester, and corresponding information needs to be acquired from the test case library and the tester human library.

And 106, determining a target tester corresponding to the test case according to the first weight and the second weight, and distributing the test case to a tester corresponding to the identity information of the tester for testing.

In the embodiment of the application, in order to ensure the accuracy of the test result and the smooth progress of the test, the test case with high difficulty can be firstly allocated to the tester with high capability value. Firstly, the testers are ranked from small to large according to the capacity values, then the testers with the highest capacity values are started, and the test cases are distributed to the testers, namely target testers, according to the difficulty and the ease. The higher the second weight value of the test case is, the higher the difficulty of the test case is. That is, the test cases are assigned to the tester in the order from high to low according to the value of the second weight.

And sequentially distributing N +1 test cases to the tester according to the sequence, when the sum of the values of the second weights of the N test cases is less than the first weight of the tester and the sum of the values of the second weights of the N +1 test cases is greater than or equal to the first weight of the tester, indicating that the workload of the tester is saturated, stopping distributing the test cases to the tester, and continuously distributing the test cases to the next tester sequenced according to the same method until all the test cases are distributed or the workload of each tester is saturated.

It should be added that the test cases in the test case library are usually divided according to the function modules, and the test cases may also be allocated according to the modules, for example, the scene type test cases are usually difficult to allocate, the allocation may be performed from the scene type test cases first, the allocation is started from the scene test case with the largest second weight value in the module, and the allocation of the test cases of other modules is continued after the allocation of the scene type test cases is completed.

Or, the test cases are directly distributed according to the sequence of the test cases in the test case library, which is not specifically limited in this application.

Optionally, step 104 includes:

substep 1041, acquiring each execution step of the test case.

Each test case includes at least one execution step, and the following is an example of a test case a provided in the embodiment of the present application:

{ test case a:

1) The command ipmitool fru print is executed.

2) Checking the information of the case: the type of the case, the number of the case part and the serial number of the case.

3) Checking various information of the main board: manufacturing date and time, mainboard manufacturer, mainboard product name, mainboard serial number and mainboard part serial number.

4) Checking product information: product manufacturer, product name, product part number, product version, product serial number, and asset tag. }

As can be seen, this test case A includes 4 execution steps.

Substep 1042, determining the category of the executing step according to the content of each executing step.

In the embodiment of the present application, the execution steps of the test case can be divided into three major types of execution steps, namely get (execution), post (login), and check (detection). The get class executing step includes an executing step of executing a specific command; the post class execution step includes an execution step of executing various login operations; the check-like executing step includes an executing step of checking the corresponding information or result.

For example, the step 1 of executing the test case a belongs to the get class; (ii) a The steps 2, 3 and 4 are executed and belong to check class. It should be noted that different classifications may be set according to specific test case situations.

In sub-step 1043, the third weight corresponding to the category of the executing step is obtained according to the preset corresponding relationship between the category and the third weight.

The third weight is a score determined by a manager according to the operation difficulty of the execution step of the test case or the time required for executing the operation, and is used for reflecting the difficulty or the workload of the execution step. In the embodiment of the present application, the third weight of the get class execution step may be defined as 1, the third weight of the post class execution step is 1.2, and the third weight of the check class execution step is 0.8.

It should be noted that, when one test case involves the same execution step multiple times, the third weight of the execution step is defined as 0.5.

For example, the following is an example of a test case B provided in the embodiment of the present application:

{ test case B:

1) And logging in with correct user name and password.

2) It is checked whether the login is successful.

3) Correct user name, wrong password login.

4) Checking whether the prompt is reasonable.

5) And logging in by a wrong user name and a correct password.

6) Checking whether the prompt is reasonable.

7) Wrong user name and wrong password login.

8) Checking whether the prompt is reasonable. }

It can be seen that the execution steps 1, 3, 5, and 7 of the test case B belong to post type execution steps; the steps 2, 4, 6 and 8 are executed and belong to the check class. Wherein, the execution of steps 4, 6, and 8 is the same execution step, so the third weight for executing steps 4, 6, and 8 is defined as 0.5.

And a substep 1044 of accumulating the third weights of the respective execution steps to obtain the second weight.

The test case is composed of at least one execution step, and the difficulty or the workload of the test case is the sum of the difficulty or the workload of each execution step of the test case, so that the third weights reflecting the workloads of the execution steps are accumulated, and the second weight reflecting the workload of the test case can be obtained.

For example, the execution steps 1, 3, 5, and 7 of the test case B belong to a post class execution step, so the third weight for executing the steps 1, 3, 5, and 7 is 1.2 according to the corresponding relationship between the preset class and the third weight; the execution steps 2, 4, 6, and 8 belong to check-type execution steps, wherein the execution steps 4, 6, and 8 are the same execution step, so the third weight for executing the steps 4, 6, and 8 is defined as 0.5, and the third weight for executing the step 2 is defined as 0.8. The second weight of test case B is equal to the sum of the third weights of the executed steps, equal to 1.2 + 4+0.5 + 3+0.8=6.5.

Optionally, substep 1041, comprising:

substep 10411, identifying each execution step of the test case according to a preset step identification rule.

In the embodiment of the present application, the preset step identification rule may be that each execution step is identified according to a label, for example, after the label 1), the content before the label 2) is identified as the execution step 1; reference numeral 2) later, reference numeral 3) earlier is identified as performing step 2. Or after the number 1, the text content before the number 2 is recognized as performing step 1.

Specifically, the preset step identification rule may be set according to the specific content of the test case, which is not specifically limited in the present application.

Substep 1042, comprising:

a substep 10421 of obtaining the content of the execution step, performing semantic analysis on the content, and determining the category of the execution step.

In the embodiment of the present application, performing semantic analysis on the content may be that when the content of the execution step includes an "execute" word, determining that the execution step is a get-class execution step; when the content of the execution step contains a word of 'check', judging that the execution step is a check-type execution step; when the content of the execution step includes the word "login", the execution step is determined to be a post-class execution step.

Optionally, the reaching of the test case allocation condition in step 105 includes:

and (s 1) a new test case appears in the test case library.

And s2, or the test case library has residual unallocated test cases and the tester identity information appears in the tester identity library.

And s3, or the first weight of the tester identity information allocated to the tester human database changes when the test cases which are not allocated exist in the test case library.

Condition s4, or that the test case assigned by the tester is not complete and a request to move the tester out of the test manpower library is received.

The situation of the test case allocation condition is achieved, that is, the situation of the test case allocation is needed. The operation of always distributing the test cases can cause the system, the equipment or the terminal to repeatedly calculate, so that the condition that the test cases need to be distributed needs to be determined, and then the distribution is automatically carried out, so that the time of managers is saved. When a new test case appears in the test case library, the new test case needs to be distributed to testers with residual workload; when new tester identity information appears in the test manpower library, new testers can be added, redundant workload is provided, and unallocated test cases exist at the moment, so that allocation is needed; the first weight of the identity information of the tester distributed by the testing human database changes, and can be that the capability level information of the tester changes or the investable time of the tester changes, the workload changes and needs to be redistributed; and (4) the tester moves out of the testing human database, the rest test cases of the tester need to be returned to the test case database, and the returned test cases are redistributed again.

Optionally, after step 106, the method further includes:

step 107, obtaining the target completion time and the current first time of the distributed test case, and determining the test progress of the test case according to the target completion time and the current first time.

To better reflect the progress of the test, the progress of the test may be flagged at the receiving terminal. For example, the receiving terminal may mark the testers in normal progress as green according to the test progress, mark the testers with the delayed workload less than 50% of the total workload as orange, and mark the testers with the delayed workload more than 50% as serious delay as red.

Optionally, step 107, further includes:

a substep 1071 of receiving a test progress request sent by a terminal; the test progress request comprises the execution steps of the completed test case.

The terminal can be a computer used by a tester, and the terminal of the manager receives the test progress request to obtain the execution steps of the test case completed by the tester.

And a substep 1072 of marking the completion state of the execution step of the test case in response to the test case progress request.

And marking the execution steps of the test cases included in the test progress request as a completed state, and marking the rest execution steps as an uncompleted state.

Optionally, the test case library further includes an item identifier and an item priority weight; step 105, including before, further comprising:

substep 108, receiving a test allocation request for the test item sent by the test management terminal, wherein the test allocation request includes: item identification, item priority weight; wherein different test items differ in priority.

In the embodiment of the application, the test management terminal may be a terminal that generates a test case or a terminal that sends the test case to the test case library. The test case library may include test cases of different test items of a plurality of companies, software or programs, or test cases of different items of the same company and software, and the item identifier is used to identify test item information to which the test case belongs. Such as: test case 1: (company A, project B). The item priority weight is used for reflecting the urgency degree and the importance degree of the test item, and the higher the item priority weight is, the higher the item priority degree is, the urgency degree is, and the time is more urgent.

Step 105, comprising:

sub-step 1051, obtain the item identification and item priority weight from each test distribution request.

Substep 1052, starting from the test item with the highest item priority weight in the test allocation request, reading the test case and the second weight from the test case library corresponding to the corresponding item identifier, and reading the tester identity information and the first weight from the tester library.

Because the priorities of the test items are different, in order to ensure that the test item with the high priority is completed as early as possible, the test management terminal can add an item identifier and an item priority weight to the test allocation request, so that the importance degree or the urgency of the item is reflected, and the test case allocation by a manager or a system is facilitated.

In the embodiment of the present application, the test case of the test item with the highest priority weight may be allocated.

In summary, the method for distributing test cases provided by the embodiment of the present application includes receiving a request for waiting distribution sent by a test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester; responding to the waiting distribution request, acquiring a first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database; receiving a test case sent by a test case end; acquiring a second weight of the test case according to the test content of the test case, and adding the test case and the second weight into a test case library; under the condition that the test case distribution condition is met, reading the test cases and the second weight from a test case library, and reading the tester identity information and the first weight from the tester library; and determining a target tester corresponding to the test case according to the first weight and the second weight, and distributing the test case to a tester corresponding to the identity information of the tester for testing. The method can solve the problem that a plurality of projects can be reused by a tester in a product development process, and the level and the investable time of the tester are different, so that a large amount of time is required for test case distribution by a responsible person.

According to the test case distribution method provided by the embodiment of the application, the execution main body can be a test case distribution device. The method for executing test case allocation by the test case allocation device is taken as an example in the embodiment of the present application to explain the test case allocation device provided in the embodiment of the present application.

Referring to fig. 2, fig. 2 is a block diagram of a test case distribution device according to an embodiment of the present application, and as shown in fig. 2, the test case distribution device includes:

a first receiving module 201, configured to receive a request for waiting allocation sent by a test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester;

a first module 202, configured to, in response to the waiting allocation request, obtain a first weight of the tester according to the capability level information of the tester and the investable time of the tester, and add the identity information of the tester and the first weight to a tester database;

the second receiving module 203 is configured to receive a test case sent by the test case end;

a second module 204, configured to obtain a second weight of the test case according to the test content of the test case, and add the test case and the second weight to a test case library;

a reading module 205, configured to read the test case and the second weight from a test case library and read the tester identity information and the first weight from the tester library when a test case allocation condition is met;

and the allocating module 206 is configured to determine a target tester corresponding to the test case according to the first weight and the second weight, and allocate the test case to a tester corresponding to the tester identity information for testing.

To sum up, the test case allocation apparatus provided in the embodiment of the present application includes a first receiving module, configured to receive a request for waiting allocation sent by a test terminal; the wait for allocation request comprises: the identity information of the tester, the capability level information of the tester and the investable time of the tester; the first module is used for responding to the waiting distribution request, acquiring first weight of the tester according to the capability level information of the tester and the investable time of the tester, and adding the identity information of the tester and the first weight into a testing human database; the second receiving module is used for receiving the test case sent by the test case end; the second module is used for acquiring a second weight of the test case according to the test content of the test case, and adding the test case and the second weight into a test case library; (ii) a The reading module is used for reading the test cases and the second weight from the test case library and reading the identity information and the first weight of the tester from the tester library under the condition that the test case distribution condition is reached; and the distribution module is used for determining a target tester corresponding to the test case according to the first weight and the second weight and distributing the test case to a tester corresponding to the identity information of the tester for testing. The device can solve the problem that a plurality of items can be reused by a tester in a product development process, and the level and the investable time of the tester are different, so that a large amount of time is required for test case distribution by a responsible person.

The test case distribution apparatus in the embodiment of the present application may be an electronic device, or may be a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be a device other than a terminal. The electronic Device may be, for example, a Mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic Device, a Mobile Internet Device (MID), an Augmented Reality (AR)/Virtual Reality (VR) Device, a robot, a wearable Device, an ultra-Mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and may also be a server, a Network Attached Storage (Network Attached Storage, NAS), a personal computer (NAS), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not limited in particular.

The test case distribution device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The test case distribution device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 1, and is not described here again to avoid repetition.

Optionally, as shown in fig. 3, an electronic device 300 is further provided in the embodiment of the present application, and includes a processor 301 and a memory 302, where the memory 302 stores a program or an instruction that can be executed on the processor 301, and when the program or the instruction is executed by the processor 301, the steps of the embodiment of the test case distribution method are implemented, and the same technical effects can be achieved, and are not described again here to avoid repetition.

It should be noted that the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.

Fig. 4 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.

The electronic device 100 includes, but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

Those skilled in the art will appreciate that the electronic device 100 may further comprise a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 110 via a power management system, so as to implement functions of managing charging, discharging, and power consumption via the power management system. The electronic device structure shown in fig. 4 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.

It should be understood that, in the embodiment of the present application, the input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics Processing Unit 1041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a first storage area storing a program or an instruction and a second storage area storing data, wherein the first storage area may store an operating system, an application program or an instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 109 may include volatile memory or nonvolatile memory, or the memory x09 may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM), a Static Random Access Memory (Static RAM, SRAM), a Dynamic Random Access Memory (Dynamic RAM, DRAM), a Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), a Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, ddr SDRAM), an Enhanced Synchronous SDRAM (ESDRAM), a Synchronous Link DRAM (SLDRAM), and a Direct bus RAM (DRRAM). Memory 109 in the embodiments of the subject application includes, but is not limited to, these and any other suitable types of memory.

Processor 110 may include one or at least two processing units; optionally, the processor 110 integrates an application processor, which mainly handles operations related to the operating system, user interface, application programs, etc., and a modem processor, which mainly handles wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing test case allocation method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read only memory ROM, a random access memory RAM, a magnetic or optical disk, and the like.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the foregoing test case allocation method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, or a system-on-chip.

The embodiments of the present application provide a computer program product, where the program product is stored in a storage medium, and the program product is executed by at least one processor to implement the processes of the foregoing test case allocation method embodiments, and can achieve the same technical effects, and in order to avoid repetition, details are not repeated here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for distributing test cases, the method comprising:

receiving a test case sent by a test case end;

under the condition that the test case distribution condition is met, reading the test case and the second weight from a test case library, and reading the tester identity information and the first weight from the tester library;

2. The method according to claim 1, wherein the obtaining the second weight of the test case according to the test content of the test case comprises:

acquiring each execution step of the test case;

determining the category of each execution step according to the content of each execution step;

acquiring a third weight corresponding to the category of the execution step according to the corresponding relation between the preset category and the third weight;

and accumulating the third weights of the execution steps to obtain the second weight.

3. The method according to claim 2, wherein the steps of obtaining the test cases comprise:

identifying each execution step of the test case according to a preset step identification rule;

the determining the category of the execution steps according to the content of each execution step comprises the following steps:

and acquiring the content of the execution step, performing semantic analysis on the content, and determining the category of the execution step.

4. The method according to claim 1, wherein the reaching of the test case allocation condition comprises:

a new test case appears in the test case library;

or, the test case library has residual unallocated test cases and the test human library has new tester identity information;

or, the test case library has residual unallocated test cases, and the first weight of the tester identity information allocated by the test human database changes;

alternatively, the test case assigned at the tester is not completed and a request to move the tester out of the testing personnel library is received.

5. The method according to claim 1, wherein after the test case is assigned to the tester corresponding to the tester identity information for testing, the method further comprises:

and acquiring the target completion time and the current first time of the distributed test case, and determining the test progress of the test case according to the target completion time and the current first time.

6. The method of claim 5, further comprising:

receiving a test progress request sent by a terminal; the test progress request comprises the execution steps of the completed test cases;

and responding to the test case progress request, and marking the completion state of the execution steps of the test case.

7. The method of claim 1, wherein the test case base further comprises an item identification, an item priority weight; before the reading of the test cases and the second weight from the test case library and the reading of the tester identity information and the first weight from the test human library, the method further includes:

receiving a test allocation request for a test item sent by a test management terminal, wherein the test allocation request comprises: item identification, item priority weight; wherein, the priority of different test items is different;

the reading the test case and the second weight from the test case library and the reading the tester identity information and the first weight from the tester database under the condition that the test case distribution condition is met comprises the following steps:

acquiring the item identification and the item priority weight from each test distribution request;

and reading the test cases and the second weight from the test case library corresponding to the corresponding item identification from the test item with the highest item priority weight in the test distribution request, and reading the tester identity information and the first weight from the test human library.

8. A test case assignment apparatus, the apparatus comprising:

9. An electronic device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions when executed by the processor implementing the test case distribution method of any of claims 1 to 7.

10. A readable storage medium, storing thereon a program or instructions which, when executed by a processor, implement the test case distribution method of any of claims 1 to 7.