Task allocation method, device, electronic device and computer readable storage medium

Abstract

The implementation method of this specification discloses a task allocation method, device, electronic device and computer-readable storage medium, which can be used in the field of financial technology, wherein the method includes: receiving a test request sent by a terminal user device, the test request is accompanied by at least one account; determining a first account set according to at least one account; wherein the terminal user device corresponding to the account included in the first account set is not assigned a test task; or, the first account set is used to limit the terminal user devices that can accept the test task; sending a processing request to a storage system; the processing request is accompanied by the first account set, so that the task allocation system obtains the first account set or the associated account set of the first account set from the storage system, and determines the target account when allocating the test task according to the acquired set. Through this method, the task allocation system allocates tasks to certain test accounts for processing, thereby improving the test efficiency.

Description

Technical Field

[0001] The present application relates to the field of test automation technology, and in particular to a task allocation method, device, electronic device and computer-readable storage medium. Background Art

[0002] The task allocation system is responsible for the distribution of tasks and is more common in business centralized processing platforms. Using the business centralized processing platform, business personnel submit all the work they have completed to the business centralized processing platform, which is uniformly managed by the business centralized processing platform and stored in the database. The business centralized processing platform calls its task allocation system to prepare tasks and assigns tasks to business personnel for processing. If the task allocation system assigns tasks to the wrong business personnel for processing, it will lead to information leakage, tasks not being processed or processed in an irregular manner; if the task allocation system cannot assign a task, the business type to which the task belongs cannot be carried out normally. Therefore, it can be seen that it is very important to test the task allocation system of the business centralized processing platform.

[0003] However, in actual scenarios, for each type of task, a business person only needs to handle one step or link in the task pipeline of that type, while in test scenarios, a tester needs to be responsible for all processing links of a business type, that is, he needs to log in to the account of each processing link one by one to test the business type he is responsible for. When testers responsible for testing different business types log in to the account of the same processing link at the same time, the task allocation system may assign the task required by tester 1 to tester 2 for processing. When tester 2 operates "skip" on the task, the task will be assigned to tester 1 for processing, resulting in low test efficiency. Therefore, in the test scenario, it is necessary to intervene in the task allocation system to improve the test efficiency. Summary of the invention

[0004] The purpose of the embodiments of this specification is to provide a task allocation method, device, electronic device and computer-readable storage medium to improve the efficiency of testing the task allocation system of the business centralized processing platform.

[0005] To solve the above technical problems, an embodiment of the present specification provides a testing method for a task allocation system, the method comprising: receiving a test request sent by a terminal user device, the test request being accompanied by at least one account; determining a first account set based on the at least one account; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned test tasks; or, the first account set is used to limit the terminal user devices that can accept test tasks; sending a processing request to a storage system; the processing request being accompanied by the first account set, so that the task allocation system obtains the first account set or an associated account set of the first account set from the storage system, and determines the target account when assigning the test task based on the acquired set.

[0006] An embodiment of the present specification provides a test method for a task allocation system, the method comprising: receiving a processing request sent by a test device; the processing request is accompanied by a first account set; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or, the first account set is used to limit the terminal user devices that can accept the test task; determining a second account set based on the first account set; in the case where the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task, the terminal user devices corresponding to the accounts included in the second account set are also not assigned a test task; or, the second account set is used to limit the terminal user devices that can accept the test task; in the case where the first account set is used to limit the terminal user devices that can accept the test task, the second account set is also used to limit the terminal user devices that can accept the test task, or, the terminal user devices corresponding to the accounts included in the second account set are not assigned a test task; sending a test task to a task allocation system with the second account set attached, so that the task allocation system obtains the second account set, and determines the target account when allocating the test task based on the second account set.

[0007] An embodiment of the present specification provides a task allocation method, the method comprising: receiving a second account set attached to a storage system when sending a test task; wherein the terminal user device corresponding to the account included in the second account set is not allocated the test task, or the second account set is used to limit the terminal user device that can accept the test task; searching for a stored online account set; wherein the account included in the online account set can accept the test task; determining a target account when allocating the test task based on the second account set and the online account set; and sending the test task to the terminal user device corresponding to the target account.

[0008] The task allocation method provided in the embodiment of the specification sets a test device in the test scenario, so that the test account writes the remaining accounts other than the test account into the second account set through the test device, simulating the situation that the remaining accounts other than the test account refuse (or skip) the task in the actual application scenario, so that the task allocation system allocates the task to the test account in a targeted manner; and, in the test scenario, the test account also sends the business number to the storage device through the test device, so that the storage device only modifies the second account set corresponding to the task corresponding to the business number, so that the task allocated to the test account in a targeted manner can be determined as the task required by the tester. Through the above method, the tester can intercept the tasks he needs in a targeted manner, select the tasks he submits from the massive tasks, and transfer them to himself (the different job accounts logged in) for input, review and verification, greatly reducing the number of tasks that each tester needs to process (including skipping operations); on the other hand, in the actual application and test scenario of the task allocation system, the tasks skipped by a business person will be re-allocated, but will not be allocated to the business person who has skipped the task. Therefore, the above method can reduce the number of tasks that need to be allocated on the basis of reducing the tasks skipped by each business person, thereby improving the allocation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the implementation methods of the present application or the technical solutions in the prior art, the drawings required for use in the implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some implementation methods recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0010] Figure 1 A schematic diagram of a task allocation system in an actual application scenario is shown;

[0011] Figure 2 A schematic diagram of the task allocation system in a test scenario is shown;

[0012] Figure 3 A schematic diagram of a business voucher is shown;

[0013] Figure 4 A schematic diagram of an interactive process of a task allocation method according to an embodiment of this specification is shown;

[0014] Figure 5 A flowchart of another task allocation method according to an embodiment of this specification is shown;

[0015] Figure 6 A flowchart of a task allocation method according to an embodiment of this specification is shown;

[0016] Figure 7 A flowchart of a task allocation method according to an embodiment of this specification is shown;

[0017] Figure 8 A schematic diagram of an interaction process of another task allocation method according to an embodiment of this specification is shown;

[0018] Fig. 9 A flowchart of another task allocation method according to an embodiment of this specification is shown;

[0019] Fig.10 A flowchart of another task allocation method according to an embodiment of this specification is shown;

[0020] Fig.11 A principle block diagram of a task allocation device according to an embodiment of this specification is shown;

[0021] Fig.12 A principle block diagram of a task allocation device according to an embodiment of this specification is shown;

[0022] Fig.13 A principle block diagram of a task allocation device according to an embodiment of this specification is shown;

[0023] Fig.14 A principle block diagram of a testing device according to an embodiment of this specification is shown;

[0024] Fig.15 A principle block diagram of a storage system according to an embodiment of this specification is shown;

[0025] Fig.16 A principle block diagram of a server according to an embodiment of this specification is shown. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0027] Application scenarios of task allocation system Figure 1 and Figure 2 As shown, Figure 1 This is a schematic diagram of the task allocation system in actual application scenarios. Figure 2 This is a schematic diagram of the task allocation system in a test scenario. Figure 1 and Figure 2 As shown, the application scenarios of the task allocation system include servers, storage systems, and end-user devices.

[0028] The server can be an electronic device with certain computing and processing capabilities, which can have a network communication module, a processor, a memory, etc. The server can be a single electronic device, or a system in which multiple processors, memories, network communication modules, etc. work together; or the server can also be a server cluster formed by several server devices.

[0029] The server runs the business centralized processing platform software. The task allocation system is included in the business centralized processing platform and is responsible for the distribution of tasks in the business centralized processing platform. The server receives tasks submitted to the server by business personnel after processing by running the software, manages these tasks in a unified manner, and stores them in the storage system. The server's own memory can also store task-related data.

[0030] However, when the amount of data to be stored is large, it is usually necessary to set up another storage system to store and manage the massive data. The storage system can run independently of the server, so that any server can access the storage system through a pre-set interface program; in contrast, the storage system is bound to a specific server. If bound, only the specific server can access this storage system, and the data on the storage device cannot be accessed and modified by operating the terminal user device or an independently running test device, unless the server address bound to the storage system is modified or added. The above storage system can be, for example, a distributed memcached cache system, or a Netease Cloud Object Storage Service NOS (NeteaseObject Storage) cloud storage service.

[0031] The terminal user equipment includes equipment that can be used by users of the business centralized processing platform, such as self-service teller machines (including deposit and withdrawal machines set up in self-service banks or self-service machines set up in bank halls), computers, mobile terminals (such as mobile phones, tablet computers, etc.). Users of the business centralized processing platform can be internal employees of the software user unit, such as bank tellers and personnel at various steps of the bank back-end (i.e., positions that perform a type of operation in the business process, such as voucher cutting and submission positions, fragment identification positions, information entry positions, information review positions, etc.), or users served by the software user unit, such as users who go to the bank to open accounts, transfer money, remittance and other services. The operation interface presented to the user by the terminal user device can be a browser page that is linked to the business centralized processing platform; it can also be a client software program that is connected to the business centralized processing platform.

[0032] The following takes the centralized business processing platform used by banks (hereinafter referred to as the platform) as an example to illustrate the differences between the task allocation system in actual application scenarios and test scenarios.

[0033] To conduct banking business, you usually need to fill out a voucher first. Figure 3 This is a schematic diagram of a voucher that the user needs to fill out. The voucher will be photographed or recorded by the counter staff to form an image voucher. There are nearly 200 types of bank image voucher data, covering almost all banking businesses. The processing flow for image vouchers is generally "voucher cutting-fragment identification-information entry-information review-information verification". The image voucher is cut into voucher fragments, and each voucher fragment corresponds to an information filled in by the user. The work of processing voucher fragments in the business process can be called a task, which is assigned to the business personnel by the task allocation system of the business centralized processing platform. The following is a detailed introduction to the processing flow of voucher fragments.

[0034] In actual application scenarios, such as Figure 1 As shown in the figure, after the voucher fragment (i.e., task) is submitted by the submitting post A, it is assigned by the platform to the identification post B for identification, then to the input post C for information entry, then to the review post D for review of the input information, and finally to the verification post E for verification. After A, B, C, D, and E are processed, they are all submitted to the platform. Each allocation step is executed by the platform. In the business process, a step post or each step post that performs a type of operation may have multiple business personnel. Each voucher fragment (i.e., task) is randomly assigned between two or more business personnel in the same step post.

[0035] For example, the platform randomly distributes the voucher fragment (i.e., task) X among the business personnel B1, B2, and B3 at the identification post, among the business personnel C1, C2, and C3 at the data entry post, among the business personnel D1, D2, and D3 at the audit post, and among the business personnel E1, E2, and E3 at the verification post. It can be seen that in actual application scenarios, for each type of task, a business personnel only needs to handle one step or link in the task pipeline of that type. Therefore, the task allocation system only needs to randomly distribute the tasks among the accounts of each business personnel, or assign the tasks to the business personnel with the least current task volume according to the processing speed of the business personnel. For banking business, the centralized processing method of the platform enables the back-end personnel to quickly process the customer's business when the front-end teller accepts the customer's business, and feedback the business results to the front-end teller, who will inform the customer of the results, thereby speeding up the business processing speed.

[0036] In the test scenario, Figure 2As shown in the figure, each business personnel involved in the platform test is responsible for the test of the entire business process of "voucher cutting-fragment identification-information entry-information review-information verification", that is, a tester needs to be responsible for all steps or links in a type of task pipeline, and each tester needs to log in to the account of submission post A, identification post B, entry post C, review post D, and verification post E one by one to perform operations to simulate the actual application scenario. When two or more testers are responsible for the entire business process test of different types of business, and the test is carried out at the same time, there may be two or more testers logging in to different accounts of the same step post. The business centralized processing platform will still randomly distribute the voucher fragments (i.e., tasks) among different accounts of the review post, so that the business fragments submitted by tester F1 through the submission post account for testing type X business may be randomly assigned to the review post account logged in by tester F2, who is responsible for the test of type Y business; and the test process expects that the business fragments are assigned to the review post account logged in by tester F1 for processing.

[0037] In this regard, the task allocation method provided in the embodiments of this specification sets up a testing device to assist testers in testing the task allocation system and improve the testing efficiency.

[0038] Specifically, the tester logs in to the account F1 on the terminal user device, and sends a test request to the test device through the terminal user device. The test request is accompanied by the account F1 and the business number of the business that the tester needs to test. The business number is the business serial number. For example, the tester needs to test the transfer and remittance business, and there are multiple transfer and remittance businesses, such as num1, num2, and num3. The tester tests the num3 business, and the business number attached to the test request is num3.

[0039] After receiving the test request, the test device obtains a set of all accounts (including online and offline accounts) on the positions to be assigned, such as (F1, F2, F3, F4, F5), and determines the first account set as (F2, F3, F4, F5) based on the account F1 included in the test request. Then, the test device sends a processing request to the storage system, which includes the first account set and the business number num3 received by the test device.

[0040] After receiving the processing request, the storage system determines the second account set as (F2, F3, F4, F5) according to the first account set (F2, F3, F4, F5). The set of credential fragments (X1, X2, X3) corresponding to the business number num3 is found from the stored credential fragment list, and each credential fragment in these sets is stored in correspondence with the second account set. The correspondence between the business number, credential fragment and the second account set is shown in each row of Table 1 below.

[0041] Table 1

[0042] Business Number Credential fragments Second account collection Num3 X1 F2, F3, F4, F5 Num3 X2 F2, F3, F4, F5 Num3 X3 F2, F3, F4, F5

[0043] When the task allocation system needs to allocate data in the credential fragment set, the storage system sends the credential fragment X1 in the credential fragment set to the task allocation system together with the second account set (F2, F3, F4, F5).

[0044] After receiving the credential fragment X1 and the second account set (F2, F3, F4, F5), the task allocation system searches for the set of all online accounts (F1, F2, F3, F4), determines the target account set (F1) based on the second account set and the online account set, and then allocates the credential fragment X1 to the account in the target account set, i.e., F1, so that the tester can intercept the credential fragments required for his test in a targeted manner.

[0045] In the above method, the actual application scenario stipulates that: the storage system stipulates that credential fragments and a second account set are stored, and the two are stored correspondingly, wherein the terminal user devices corresponding to the accounts included in the second account set are not allocated the credential fragments corresponding to the second account set, and when the task allocation system allocates the credential fragments in the storage system, it does not allocate them to the accounts included in the corresponding second account set, but randomly allocates them among the remaining online accounts other than these accounts. In the actual application scenario, when a credential fragment is allocated to an account and the account rejects (or skips) the credential fragment, the storage system will put the account in the second account set corresponding to the rejected (or skipped) credential fragment. In addition, the actual application scenario also stipulates that: the storage system stores the business number and the credential fragment, and the two are stored correspondingly.

[0046] Based on these regulations, a test device is set up in a test scenario, so that the test account writes the remaining accounts other than the test account into the second account set through the test device, simulating the situation in which the remaining accounts other than the test account in the actual application scenario reject (or skip) the credential fragments, so that the task allocation system allocates the credential fragments to the test account in a targeted manner; and, in the test scenario, the test account also sends the business number to the storage device through the test device, so that the storage device only modifies the second account set corresponding to the credential fragments corresponding to the business number, so as to determine that the credential fragments allocated to the test account are the credential fragments required by the tester.

[0047] Through the above method, testers can intercept the credential fragments they need in a targeted manner, select the fragments they submit from the massive fragments, and transfer them to themselves (different job accounts logged in) for entry, review and verification, which greatly reduces the number of credential fragments that each tester needs to process (including skipping operations); on the other hand, in the actual application and testing scenarios of the credential fragment allocation system, the credential fragments skipped by a business person will be re-allocated, but will not be allocated to the business person who has skipped the credential fragment. Therefore, the above method can reduce the number of credential fragments that need to be allocated on the basis of reducing the credential fragments skipped by each business person, thereby improving the allocation efficiency.

[0048] The processing of the above-mentioned credential fragment can be considered as a task.

[0049] The above specific implementation method embodies a task allocation method. Figure 4 As shown,

[0050] S1. The terminal user device sends a test request to the test device, and the test request is accompanied by at least one account number. For example, in the above specific embodiment, the account number F1 is attached.

[0051] S2. The testing device receives a testing request sent by the terminal user device.

[0052] S3. The testing device determines a first account set based on the at least one account, wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task. For example, in the above specific embodiment, the first account set is determined to be (F2, F3, F4, F5).

[0053] S4. The test device sends a processing request to the storage system; the processing request is accompanied by the first account set, so that the task allocation system can obtain the associated account set of the first account set from the storage system, and determine the target account when allocating the test task according to the associated account set. In the above specific embodiment, the associated account refers to the second account set.

[0054] S5. The storage system receives a processing request sent by the testing device.

[0055] S6. The storage system determines a second account set based on the first account set, wherein the terminal user devices corresponding to the accounts included in the second account set are not assigned test tasks. For example, in the above specific embodiment, the second account set is determined to be (F2, F3, F4, F5) based on the first account set (F2, F3, F4, F5).

[0056] S7. The storage system sends the test task and the second account set to the task allocation system, so that the task allocation system obtains the second account set and determines the target account when allocating the test task according to the second account set.

[0057] S8. The task allocation system receives the second account set that is included when the storage system sends the test task.

[0058] S9. The task allocation system searches for a stored online account set, where the accounts included in the online account set can accept the test task. For example, the online account set (F1, F2, F3, F4) in the above specific embodiment.

[0059] S10, the task allocation system determines the target account when allocating the test task according to the second account set and the online account set. For example, the target account set (F1) in the above specific embodiment.

[0060] S11, the task allocation system allocates the test task to the terminal user device corresponding to the target account. For example, in the above specific embodiment, the task is allocated to the terminal user device corresponding to the F1 account.

[0061] In the above specific embodiment, the testing device determines the first account set as (F2, F3, F4, F5) by sending the account F1 attached to the test request, the storage system determines the second account set as (F2, F3, F4, F5) based on the first account set, and the task allocation system determines the target account set as (F1) based on the second account set and the online account set.

[0062] In the above specific embodiment, when all account sets are (F1, F2, F3, F4, F5) and online account sets are (F1, F2, F3, F4), the account attached when the terminal user device corresponding to account F1 sends a test request can be either F1 or F2, F3, F4, F5. The first account set determined according to the attached account can be either (F1) or (F2, F3, F4, F5). The second account set can be either (F1) or (F2, F3, F4, F5). The target account set is (F1). The above two situations of attached accounts, two situations of the first account set, and two situations of the second account can be freely combined, that is, there are eight situations.

[0063] Which scenario is adopted in the specific embodiment can be preliminarily determined in the actual application scenario (i.e., non-test scenario) according to the content of the account set in the storage system and whether the storage system has the ability of set conversion (i.e., whether the storage system can convert the first account set into a different set). For example, in the actual application scenario, the terminal user devices corresponding to the accounts included in the account set in the storage system are not assigned test tasks, and the storage system does not have the function of set conversion. Then, the contents of the first account set and the second account set are determined, and there are only two scenarios left. These two scenarios are: the terminal user device corresponding to the account attached when the terminal user device sends a test request is not assigned a test task, and the attached account is used to limit the terminal user devices that can accept the test task. These two scenarios can be determined according to actual needs.

[0064] Based on the above content, this specification embodiment provides a task allocation method, which can be used for Figure 2 The test device shown. The test device can be a software program running on a terminal user device, which is communicatively connected to the storage system, and each terminal user device can independently run a software program as a test device. Alternatively, in some embodiments, each terminal user device is communicatively connected to an electronic device, which is communicatively connected to the storage system, and a software program is run on the electronic device as a test device. In some embodiments, the electronic device can also be one of the terminal user devices. In some embodiments, the test device can also be a hardware module. For example, an FPGA module, or a gateway. Figure 5 As shown, the task allocation method may include the following steps.

[0065] S11: Receive a test request sent by a terminal user device, where the test request is accompanied by at least one account.

[0066] The account number attached to the test request can be the account number that sends the test request, or any other account number. Of course, it can also include both the account number that sends the test request and any other account number. The attached account number can be an account number that is not assigned a test task, or an account number that is limited to accepting a test task. The number of accounts attached to the test request can be one or more.

[0067] For example, when the set of all accounts is (F1, F2, F3, F4, F5) and the account sending the test request is F1, the account attached to the test request can be F1, and the final task allocation system will allocate the test task to the F1 account; it can also be F2, F3, F4, F5, and the final task allocation system will not allocate the test task to F2, F3, F4, F5; it can also be F1 and F2, and the final task allocation system will allocate the test task to F1 and F2; it can also be F3 and F4, and the final task allocation system will not allocate the test task to F3 and F4.

[0068] After the test device receives a test request sent through a test account, it can immediately trigger the test device, storage system, and task allocation system to execute corresponding steps to allocate test tasks according to the instructions of a test account.

[0069] Alternatively, in some embodiments, a test request sent by one or two or more accounts may be received within a predetermined time period, and a processing request may be sent to the storage system after the predetermined time is reached, thereby triggering the test device, the storage system, and the task allocation system to perform corresponding steps, so that the test task may be allocated according to the instructions of two or more accounts. In this case, the first account set may be a set of all accounts that sent test requests within the predetermined time period, or a set of accounts other than "all accounts that sent test requests" within the predetermined time period.

[0070] S12: Determine a first account set based on at least one account, wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or, the first account set is used to limit the terminal user devices that can accept the test task.

[0071] The set consisting of the at least one account may be used as the first account set. For example, in the above specific embodiment, the first account set is determined to be (F1). Alternatively, in some embodiments, the set consisting of "the remaining accounts except the at least one account" may also be determined to be the first account set, in which case the set of all accounts is to be obtained. For example, when the set of all accounts is (F1, F2, F3, F4, F5) and the account sending the test request is F1, the first account set may be determined to be (F2, F3, F4, F5).

[0072] S13: Sending a processing request to the storage system; the processing request is accompanied by a first account set, so that the task allocation system can obtain the first account set or an account set associated with the first account set from the storage system, and determine the target account when allocating the test task according to the obtained account set.

[0073] The method of sending the processing request can be a method of direct interaction between the test device and the storage system, or an indirect interaction between the test device and the storage system. The direct interaction method can be: the test system establishes a Redis connection to interact directly with the NOS storage system, transmits data messages through this connection, and thus calls the corresponding API interface to operate the account set in the NOS storage system. Specifically, the message queue submodule of the test device establishes a Redis connection according to the configuration information such as the NOS IP, port, and check code used; the queue communication submodule of the test device reads the message to be sent, splices the data to be sent according to a certain format, and calls the corresponding API interface of the redis message queue for communication according to the task type; the queue processing submodule of the test device uses the corresponding API interface of the Redis message queue to operate the account set in the NOS storage system in real time, and parses the returned operation results. In addition to the Redis connection, the direct interaction method can also use a tunnel connection. The indirect interaction method is: splicing the relevant content including the account set into an Http message, transmitting the Http message through the gateway according to the user environment information to call the distributed service of the business centralized processing platform (the task allocation system is responsible for the task allocation work of the business centralized processing platform), and judging the processing result according to the return information of the Http call. The process of calling the API interface or distributed service is the process of sending a processing request. The process of the specific implementation of the code encapsulated in the API interface or distributed service program is the process of receiving the processing request on the storage system and determining the second account set based on the first account set. It should be pointed out that the indirect interaction method can only be adopted when the business centralized processing platform provides relevant distributed services, that is, provides an API interface.

[0074] Figure 5 For other aspects of the corresponding task allocation method steps, please refer to Figure 4 The corresponding embodiments are not described in detail.

[0075] The embodiments of this specification also provide a task allocation method, which can be used in the above storage system. The storage system can be a hardware storage system built into the server where the task allocation system is located, or a hardware storage system on another server or server cluster; or a storage system owned by a service provider that provides cloud storage services. Figure 6 As shown, the task allocation method may include the following steps.

[0076] S21: receiving a processing request sent by a test device; the processing request is accompanied by a first account set; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or, the first account set is used to limit the terminal user devices that can accept the test task.

[0077] See also Figure 5 Corresponding embodiment.

[0078] S22: Determine the second account set based on the first account set, and when the terminal user devices corresponding to the accounts included in the first account set are not assigned test tasks, the terminal user devices corresponding to the accounts included in the second account set are also not assigned test tasks; or, the second account set is used to limit the terminal user devices that can accept the test tasks; when the first account set is used to limit the terminal user devices that can accept the test tasks, the second account set is also used to limit the terminal user devices that can accept the test tasks, or, the terminal user devices corresponding to the accounts included in the second account set are not assigned test tasks.

[0079] In this step, the content in the first account set may be directly used as the content in the second account set, or the complement (or difference) of the first account set in all account sets may be used as the second account set.

[0080] S23: Sending the test task and the second account set to the task allocation system, so that the task allocation system can obtain the second account set and determine the target account when allocating the test task according to the second account set.

[0081] This step may include the second account set each time a task is sent. Alternatively, in some embodiments, the second account set may be included only when a specific task is sent. For example, the task corresponding to number num3 in the above specific embodiment.

[0082] Figure 5 For other aspects of the corresponding task allocation method steps, please refer to Figure 4 The corresponding embodiments are not described in detail.

[0083] The embodiment of this specification also provides a task allocation method, which can be used in the above-mentioned task allocation system. The task allocation system is included in the business centralized processing platform and is responsible for the distribution of tasks, that is, the task allocation system runs on the server. Figure 7 As shown, the task allocation method may include the following steps.

[0084] S31: receiving a second account set attached when the storage system sends a test task; wherein the terminal user devices corresponding to the accounts included in the second account set are not assigned the test task, or the second account set is used to limit the terminal user devices that can accept the test task.

[0085] See also Figure 6 Corresponding embodiment.

[0086] S32: searching for a stored online account set, wherein the accounts included in the online account set are able to accept the test task.

[0087] The business centralized processing platform stores a collection of current online accounts. The method for the business centralized processing platform to obtain the current online accounts can be: when the account logs in to or logs out of the business centralized processing platform system, it sends a login message to the platform to identify that it has been online or offline. After receiving the message, the platform can know whether it is online; or it can also be: when the account is online, it maintains a communication connection with the platform and confirms whether the account is still online through a heartbeat mechanism.

[0088] S33: Determine a target account for assigning a test task according to the second account set and the online account set.

[0089] In this step, an account in the intersection of the second account set and the online account set may be used as the target account. Alternatively, in some embodiments, an account in the relative complement (or difference) of the second account in the online account set may be used as the target account, that is, the target account is in the online account set but not in the second account set.

[0090] S34: Send the test task to the terminal user device corresponding to the target account.

[0091] This step may send all test tasks to the target account. Alternatively, in some embodiments, only specific tasks may be sent to the target account, and the remaining test tasks may be allocated according to other rules. Other rules may be to randomly allocate tasks among all online accounts, or to allocate tasks to the account with the least tasks to be processed, or to allocate tasks in order of the size of the accounts.

[0092] Figure 7 For other aspects of the corresponding task allocation method steps, please refer to Figure 4 The corresponding embodiments are not described in detail.

[0093] In one embodiment, if a specific task needs to be assigned according to the requirements of a specified account, Figures 5 to 7 In the illustrated embodiment, the test request and the processing request may be accompanied by a predetermined identifier, so that the task allocation system can allocate the test task corresponding to the predetermined identifier to the target account.

[0094] A method for enabling a task allocation system to allocate a test task corresponding to a predetermined identifier to a target account through a predetermined identifier may be to store a correspondence between the predetermined identifier and the test task in a storage system, and after receiving a processing request, the storage system further searches out a set of test tasks corresponding to the predetermined identifier based on the predetermined identifier, and only attaches a second account set when the storage system sends a task in the test task set to the task allocation system; after the task allocation system determines the target account based on the second account set, when sending the test task to the target account, the test task corresponding to the second account set is sent to the target account, that is, the test task corresponding to the predetermined identifier is sent to the target account.

[0095] Alternatively, in some embodiments, the correspondence between the predetermined identifier and the task can also be set on the business centralized processing platform. Then, after the storage system receives the processing request, the storage system can directly send the predetermined identifier to the task allocation system, that is, when any test task is sent to the task allocation system, the predetermined identifier is attached. The task allocation system determines whether the test task and the attached predetermined identifier have a correspondence based on the stored correspondence. When there is a correspondence, the test task is assigned to the terminal user device corresponding to the target account; when there is no correspondence, it can be assigned according to other rules, such as: randomly assigning tasks among all online accounts, or assigning tasks to the account with the least tasks to be processed, or assigning them in order of account size, etc.

[0096] The above-mentioned identification can be the business number or business serial number of the banking system, or it can be the case number of the public security, procuratorial and judicial systems.

[0097] In the above-mentioned banking task allocation system, for each step post (i.e., a post that performs a type of operation in the business process), the task allocation system will determine the order of the voucher fragments (i.e., tasks) to be allocated, and allocate the voucher fragments (i.e., tasks) one by one according to the order, that is, allocate the voucher fragments (i.e., tasks) one by one in a queue manner. For each step post, a queue will be determined; the queues corresponding to different step posts are different. The business centralized processing platform can adopt a multi-threaded time-sharing processing mechanism to ensure that the queues corresponding to different step posts are allocated in parallel.

[0098] In actual application scenarios, when allocating voucher fragments, the business centralized management platform determines the allocation order queue of the voucher fragments according to the score values ​​of the voucher fragments. For example, the score values ​​of multiple voucher fragments are shown in Table 2 below, and the allocation order queue of the following voucher fragments is: X4, X1, X2, X3, that is, voucher fragment X4 is allocated first, and voucher fragment X3 is allocated later.

[0099] Table 2

[0100] Credential fragment name X1 X2 X3 X4 X 5 Points 15 18 4 26 20

[0101] In actual application scenarios, the integral value can be generated according to the business type or business weight, which is used to characterize the priority of voucher fragment allocation and determine the order in which task fragments are processed. The method of determining the priority of voucher fragment allocation by integral value enables voucher fragments with higher urgency to be allocated and processed first in actual application scenarios, so as to ensure the processing speed of urgent tasks and related businesses in actual application scenarios.

[0102] However, in the test scenario, the credential fragments may be discarded (i.e., junk credential fragments) because the tester may handle the task fragments arbitrarily or irregularly, but they are still in the set of credential fragments to be allocated. Among them, there may be some junk credential fragments with higher priority, which will seriously affect the allocation efficiency of other credential fragments, and thus affect the test efficiency. On the other hand, the test scenario may have an urgent test requirement for a certain business type, and the test time is not sufficient, so the test efficiency of this business type needs to be greatly improved.

[0103] In this regard, the embodiments of this specification provide a test device for assisting testers in testing the task allocation system and improving test efficiency.

[0104] Specifically, for example, the tester is testing the function of the transfer and remittance service, and the system generates a transfer and remittance type service with the service number num3. Figure 8 As shown, the terminal user device sends a modification request to the test device, and the application is accompanied by a business number such as num3. After receiving the modification request, the test device sends an adjustment request to the storage system, and the adjustment request is also accompanied by the business number num3. After receiving the adjustment request, the storage system finds out the credential fragments X1, X3, and X4 corresponding to the business number num3, and adjusts the integral values ​​of these three credential fragments, and then determines the allocation sequence of the credential fragments according to the adjusted integral values, and then sends the credential fragments in the sequence to the task allocation system in sequence. The task allocation system sends the credential fragments to the terminal user device according to a predetermined rule, for example, it can be randomly allocated to an account, or allocated to an account with the least credential fragments to be processed, etc.

[0105] The above method, after receiving a modification request with a business number sent by an account, sends an adjustment request to the storage system to trigger the storage system to adjust the score value of the task corresponding to the business number, so that these tasks with adjusted score values ​​can skip junk tasks and be allocated first, reducing the time testers wait for the tasks they need and improving testing efficiency.

[0106] The processing of the above-mentioned voucher fragment can be regarded as a task, and the business number is the reservation identifier.

[0107] Based on the above content, this specification embodiment provides a task allocation method, which can be used for Figure 2 The test device shown. The test device can be a software program running on a terminal user device, which is communicatively connected to the storage system, and each terminal user device can independently run a software program as a test device. Alternatively, in some embodiments, each terminal user device is communicatively connected to an electronic device, which is communicatively connected to the storage system, and a software program is run on the electronic device as a test device. In some embodiments, the electronic device can also be one of the terminal user devices. In some embodiments, the test device can also be a hardware module. For example, an FPGA module, or a gateway. Fig. 9 As shown, the task allocation method may include the following steps.

[0108] S14: receiving a modification request sent by the terminal user device; the modification request is accompanied by a predetermined identifier.

[0109] The predetermined identifier can be the above-mentioned business number, that is, the business serial number; it can also be the case number in the public security, procuratorial and judicial systems.

[0110] S15: Send an adjustment request to the storage system; the adjustment request is accompanied by a predetermined identifier, so that the storage system can adjust the integral value of at least one test task corresponding to the predetermined identifier; the integral value is used to determine the order of test task allocation.

[0111] Since the corresponding relationship between the task and its integral value is set in the storage system, after receiving the change application, the test device needs to send an adjustment instruction to the storage system so that the storage system adjusts the integral value stored therein.

[0112] The adjustment request may also be accompanied by the direction of the integral value adjustment, i.e., increase (for example, when a task needs to skip the preceding junk task and be assigned priority, increase the integral value of the task) or decrease (for example, when a junk task needs to be ignored, reduce the integral value of the junk task), and may also be accompanied by the amplitude of the adjustment, i.e., the value of each increase or decrease.

[0113] Alternatively, in some embodiments, the adjustment request may include a target value of the adjusted integral value, for example, modifying the integral value to 1000 (in this case, no direction adjustment is required).

[0114] The test device may send an adjustment request to the storage system by directly interacting with the storage system or indirectly interacting with the storage system. The direct interaction method may be: the test device establishes a Redis connection to interact directly with the NOS storage system, transmits data packets through this connection, and calls the corresponding API interface to operate the data stored in the storage system in real time. Specifically, the message queue submodule of the test device establishes a Redis connection according to the configuration information such as the NOS IP, port, and checksum used; the queue communication submodule of the test device reads the message to be sent, assembles the data to be sent in a certain format, and calls the corresponding API interface of the redis message queue for communication according to the task type; the queue processing submodule of the test device uses the corresponding API interface of the Redis message queue to operate the account set in the NOS storage system in real time, and parses the returned operation results. In addition to the Redis connection, the direct interaction method may also use a tunnel connection. The indirect method is: splicing the relevant content including the predetermined identifier into an Http message, transmitting the Http message through the gateway according to the user environment information to call the distributed service of the business centralized processing platform (the task allocation system is responsible for the task allocation work of the business centralized processing platform), and judging the processing result according to the return information of the Http call. The above-mentioned process of calling the API interface or distributed service is the process of sending an adjustment request. The specific implementation process of the code encapsulated in the API interface or distributed service program is the process of receiving the adjustment request on the storage system and adjusting the integral value. It should be pointed out that the indirect interaction method can only be adopted when the business centralized processing platform provides relevant distributed services, that is, provides an API interface.

[0115] The above-mentioned task allocation method, after receiving a change request with a predetermined identifier sent by an account, sends an adjustment request to the storage system to trigger the storage system to adjust the score value of the task corresponding to the predetermined identifier, so that these test tasks with adjusted score values ​​can skip junk tasks and be allocated first, reducing the time testers wait for the tasks they need and improving testing efficiency.

[0116] Fig. 9 For other aspects of the corresponding task allocation method steps, please refer to Figure 8 The corresponding embodiments are not described in detail.

[0117] The present specification also provides a task allocation method that can be used in the above storage system. The storage system can be a hardware storage system built into the server where the task allocation system is located, or a hardware storage system on another server or server cluster; or a storage system owned by a service provider that provides cloud storage services. Fig.10 As shown, the task allocation method may include the following steps.

[0118] S24: receiving an adjustment request sent by the test device, wherein the adjustment request is accompanied by a predetermined identifier.

[0119] S25: Searching for a corresponding test task according to a predetermined identifier.

[0120] S26: adjusting the integral value corresponding to the found test task, where the integral value is used to determine the order of test task allocation.

[0121] S27: Determine a test task allocation sequence according to the adjusted integral value, and send the test tasks in the sequence to the task allocation system in sequence.

[0122] After receiving the adjustment request, the storage system may first find out the task corresponding to the predetermined identifier according to the predetermined identifier, and then adjust the value of the integral.

[0123] The direction of adjustment may be to increase the integral value or to decrease the integral value, and the direction of adjustment may be pre-agreed, or may be included in the adjustment request sent by the test device.

[0124] The adjustment range may also be pre-agreed, in which case the integral values ​​of different tasks corresponding to a business number may be different or the same. For example, it is pre-agreed that the integral value increases by 100 each time the adjustment is made, and the integral value of each corresponding task may be increased by 100. Alternatively, the adjustment range may also be included in the adjustment request sent by the test device.

[0125] Alternatively, in some embodiments, the adjustment request may include a target value of the adjusted integral value, and in this case, there is no need to carry the adjustment direction or pre-determine the adjustment direction. For example, the integral value is adjusted to 1000 (in this case, no adjustment direction is required). In this case, the integral values ​​of different tasks corresponding to a business number after adjustment are the same.

[0126] In some implementations, the adjustment method may also be to query the maximum integral value of all test tasks to be assigned, and adjust the integral value of the task corresponding to the predetermined identifier to any value greater than the maximum value. In this case, the integral values ​​of different tasks corresponding to the predetermined identifier may be the same or different.

[0127] Fig.10 For other aspects of the corresponding task allocation method steps, please refer to Figure 8 The corresponding embodiments are not described in detail.

[0128] The present invention provides a task allocation device which can be used to implement Figure 5 The task allocation method shown is as follows: Fig.11As shown, the device includes a first receiving module 11, a first determining module 12 and a first sending module 13.

[0129] The first receiving module 11 is used to receive a test request sent by a terminal user device, and the test request is accompanied by at least one account. The first determining module 12 is used to determine a first account set based on at least one account; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned test tasks; or, the first account set is used to limit the terminal user devices that can accept test tasks. The first sending module 13 is used to send a processing request to the storage system; the processing request is accompanied by the first account set, so that the task allocation system can obtain the first account set or the associated account set of the first account set from the storage system, and determine the target account when allocating the test task based on the acquired set.

[0130] Fig.11 The steps and technical effects achieved by the modules in Figure 5 The corresponding embodiments are explained and will not be described in detail.

[0131] The present invention provides a task allocation device which can be used to implement Figure 6 The task allocation method shown is as follows: Fig.12 As shown, the device includes a second receiving module 21, a second determining module 22 and a second sending module 23.

[0132] The second receiving module 21 is used to receive a processing request sent by the test device; the processing request is accompanied by a first account set; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or the first account set is used to limit the terminal user devices that can accept the test task. The second determining module 22 is used to determine the second account set according to the first account set; if the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task, the terminal user devices corresponding to the accounts included in the second account set are also not assigned a test task; or the second account set is used to limit the terminal user devices that can accept the test task; if the first account set is used to limit the terminal user devices that can accept the test task, the second account set is also used to limit the terminal user devices that can accept the test task, or the terminal user devices corresponding to the accounts included in the second account set are not assigned a test task. The second sending module 23 is used to send the test task to the task allocation system and the second account set, so that the task allocation system can obtain the second account set, and determine the target account when allocating the test task according to the second account set.

[0133] Fig.12 The steps and technical effects achieved by the modules in Figure 6The corresponding embodiments are explained and will not be described in detail.

[0134] The present invention provides a task allocation device which can be used to implement Figure 7 The task allocation method shown is as follows: Fig.13 As shown, the device includes a third receiving module 31 , a searching module 32 , a third determining module 33 and a third sending module 34 .

[0135] The third receiving module 31 is used to receive the second account set attached when the storage system sends the test task; the terminal user device corresponding to the account included in the second account set is not assigned the test task, or the second account set is used to limit the terminal user device that can accept the test task. The search module 32 is used to search the stored online account set; the account included in the online account set can accept the test task. The third determination module 33 is used to determine the target account when assigning the test task based on the second account set and the online account set. The third sending module 34 is used to send the test task to the terminal user device corresponding to the target account.

[0136] Fig.13 The steps and technical effects achieved by the modules in Figure 7 The corresponding embodiments are explained and will not be described in detail.

[0137] The present specification also provides an electronic device, which can be Figure 2 The test setup shown in . Fig.14 As shown, the electronic device may include a processor 1401, a memory 1402 and a communication module 1403, wherein the processor 1401 and the memory 1402 may be connected via a bus or other means. Fig.14 The example of connecting through bus is taken in the following.

[0138] The processor 1401 may be a central processing unit (CPU). The processor 1401 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0139] The memory 1402 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the task allocation method in the embodiment of the present invention (for example, Fig.11 The processor 1401 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 1402, that is, the task allocation method in the above method embodiment is implemented.

[0140] The memory 1402 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created by the processor 1401, etc. In addition, the memory 1402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 1402 may optionally include a memory remotely arranged relative to the processor 1401, and these remote memories may be connected to the processor 1401 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0141] The one or more modules are stored in the memory 1402, and when executed by the processor 1401, the following is performed: Figure 5 The task allocation method in the illustrated embodiment.

[0142] For details of the above test device, please refer to Figure 5 The corresponding related descriptions and effects in the illustrated embodiments can be understood and will not be repeated here.

[0143] The present specification also provides an electronic device, which can be Figure 2 The storage system shown in . Fig.15 As shown, the storage system may include a processor 1501, a memory 1502, and a communication module 1503, wherein the processor 1501 and the memory 1502 may be connected via a bus or other means. Fig.15 The example of connecting through bus is taken in the following.

[0144] The processor 1501 may be a central processing unit (CPU). The processor 1501 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0145] The memory 1502 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the task allocation method in the embodiment of the present invention (for example, Fig.12 The processor 1501 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 1502, that is, implements the task allocation method in the above method embodiment.

[0146] The memory 1502 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created by the processor 1501, etc. In addition, the memory 1502 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 1502 may optionally include a memory remotely arranged relative to the processor 1501, and these remote memories may be connected to the processor 1501 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0147] The one or more modules are stored in the memory 1502, and when executed by the processor 1501, the following is performed: Figure 6 The task allocation method in the illustrated embodiment.

[0148] For details of the above storage system, please refer to Figure 6 The corresponding related descriptions and effects in the illustrated embodiments can be understood and will not be repeated here.

[0149] The embodiment of this specification also provides a server that can Figure 2 The server shown in . Fig.16 As shown, the server may include a processor 1601, a memory 1602, and a communication module 1603, wherein the processor 1601 and the memory 1602 may be connected via a bus or other means. Fig.16 The example of connecting through bus is taken in the following.

[0150] The processor 1601 may be a central processing unit (CPU). The processor 1601 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0151] The memory 1602 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the task allocation method in the embodiment of the present invention (for example, Fig.13 The processor 1601 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 1602, that is, the task allocation method in the above method embodiment is implemented.

[0152] The memory 1602 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created by the processor 1601, etc. In addition, the memory 1602 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 1602 may optionally include a memory remotely arranged relative to the processor 1601, and these remote memories may be connected to the processor 1601 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0153] The one or more modules are stored in the memory 1602, and when executed by the processor 1601, the following is performed: Figure 7 The task allocation method in the illustrated embodiment.

[0154] For details of the above servers, please refer to Figure 7 The corresponding related descriptions and effects in the illustrated embodiments can be understood and will not be repeated here.

[0155] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0156] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A task allocation method, characterized in that: The method comprises: Receiving a test request sent by a terminal user device, wherein the test request is accompanied by at least one account number; Determine a first account set according to the at least one account; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned test tasks; or, the first account set is used to limit the terminal user devices that can accept the test tasks; Sending a processing request to the storage system; the processing request is accompanied by the first account set, so that the task allocation system obtains the first account set or an account set associated with the first account set from the storage system, and determines the target account when allocating the test task according to the obtained set; The test request is also accompanied by a predetermined identifier; the method further includes: searching for a set of test tasks corresponding to the predetermined identifier according to the predetermined identifier; accordingly, sending a processing request to the storage system, wherein the processing request is accompanied by the first account set, including: when sending a test task in the test task set to the storage system, an associated account set of the first account set is attached; In which, the test request is also accompanied by a predetermined identifier; when a test task is sent to the storage system, the predetermined identifier is also accompanied, so that the storage system can obtain the predetermined identifier, and when the test task corresponds to the predetermined identifier, the test task is assigned to a target account determined according to the associated account set of the first account set.

2. The method according to claim 1, characterized in that Also includes: Receiving a modification request sent by a terminal user device; the modification request is accompanied by a predetermined identifier; Sending an adjustment request to the storage system; The adjustment request is accompanied by the predetermined identifier, so as to be used for the storage system to adjust the integral value of at least one test task corresponding to the predetermined identifier; the integral value is used to determine the allocation order of the test tasks.

3. A task allocation method, characterized in that: The method comprises: Receiving a processing request sent by a test device; the processing request is accompanied by a first account set; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or, the first account set is used to limit the terminal user devices that can accept the test task; Determine a second account set according to the first account set; in a case where the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task, the terminal user devices corresponding to the accounts included in the second account set are also not assigned a test task; or, the second account set is used to limit the terminal user devices that can accept the test task; in a case where the first account set is used to limit the terminal user devices that can accept the test task, the second account set is also used to limit the terminal user devices that can accept the test task, or, the terminal user devices corresponding to the accounts included in the second account set are not assigned a test task; Sending the test task and the second account set to the task assignment system, so that the task assignment system can obtain the second account set and determine the target account when assigning the test task according to the second account set; The processing request is also accompanied by a predetermined identifier; the method further comprises: searching for a set of test tasks corresponding to the predetermined identifier according to the predetermined identifier; accordingly, the step of sending the test task to the task allocation system and accompanying the second account set comprises: when sending the test task in the test task set to the task allocation system, the second account set is attached; In which, the processing request is also accompanied by a predetermined identifier; when a test task is sent to a task allocation system, the predetermined identifier is also accompanied, so that the task allocation system can obtain the predetermined identifier, and when the test task corresponds to the predetermined identifier, the test task is assigned to a target account determined according to the second account set.

4. The task allocation method according to claim 3, characterized in that: receiving an adjustment request sent by a test device, wherein the adjustment request carries a predetermined identifier; Searching for a corresponding test task according to the predetermined identifier; Adjust the integral value corresponding to the found test task, the integral value is used to determine the order of test task allocation; The test task allocation sequence is determined according to the adjusted integral value, and the test tasks in the sequence are sent to the task allocation system in sequence.

5. The task allocation method according to claim 4, characterized in that: The adjustment request is accompanied by an adjusted target value; the step of adjusting the integral value corresponding to the found test task comprises: The integral value corresponding to the found test task is replaced with the target value.

6. A task allocation device, characterized in that: The device comprises: A first receiving module, configured to receive a test request sent by a terminal user device, wherein the test request is accompanied by at least one account number; A first determination module is used to determine a first account set according to the at least one account; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or the first account set is used to limit the terminal user devices that can accept the test task; A first sending module, configured to send a processing request to a storage system; the processing request is accompanied by the first account set, so that the task allocation system can obtain the first account set or an account set associated with the first account set from the storage system, and determine a target account when allocating a test task according to the obtained set; The test request is also accompanied by a predetermined identifier; the task allocation device is also used to find a set of test tasks corresponding to the predetermined identifier according to the predetermined identifier; accordingly, the step of sending a processing request to the storage system, wherein the processing request is accompanied by the first account set, includes: when sending a test task in the test task set to the storage system, an associated account set of the first account set is attached; In which, the test request is also accompanied by a predetermined identifier; when a test task is sent to the storage system, the predetermined identifier is also accompanied, so that the storage system can obtain the predetermined identifier, and when the test task corresponds to the predetermined identifier, the test task is assigned to a target account determined according to the associated account set of the first account set.

7. The device according to claim 6, characterized in that The device is also used for: Receive a modification request sent by a terminal user device; the modification request is accompanied by a predetermined identifier; send an adjustment request to a storage system; the adjustment request is accompanied by the predetermined identifier, so that the storage system adjusts the integral value of at least one test task corresponding to the predetermined identifier; the integral value is used to determine the allocation order of the test tasks.

8. A task allocation device, characterized in that: The device comprises: A second receiving module is used to receive a processing request sent by the test device; the processing request is accompanied by a first account set; wherein the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task; or the first account set is used to limit the terminal user devices that can accept the test task; A second determination module is used to determine a second account set according to the first account set; in a case where the terminal user devices corresponding to the accounts included in the first account set are not assigned a test task, the terminal user devices corresponding to the accounts included in the second account set are also not assigned a test task; or, the second account set is used to limit the terminal user devices that can accept the test task; in a case where the first account set is used to limit the terminal user devices that can accept the test task, the second account set is also used to limit the terminal user devices that can accept the test task, or, the terminal user devices corresponding to the accounts included in the second account set are not assigned a test task; A second sending module, configured to send the test task and the second account set to the task assignment system, so that the task assignment system can obtain the second account set and determine the target account when assigning the test task according to the second account set; The processing request is also accompanied by a predetermined identifier; the task allocation device is further used to: find out a set of test tasks corresponding to the predetermined identifier according to the predetermined identifier; accordingly, sending the test task to the task allocation system and accompanying the second account set includes: when sending the test task in the test task set to the task allocation system, the second account set is attached; In which, the processing request is also accompanied by a predetermined identifier; when a test task is sent to a task allocation system, the predetermined identifier is also accompanied, so that the task allocation system can obtain the predetermined identifier, and when the test task corresponds to the predetermined identifier, the test task is assigned to a target account determined according to the second account set.

9. An electronic device, characterized in that: include: A communication module, a memory and a processor, wherein the communication module, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the steps of the method according to any one of claims 1 to 5 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed, the steps of the method according to any one of claims 1 to 5 are implemented.

Images