Work order system testing method, electronic device and computer-readable storage medium

Abstract

The present application belongs to the field of testing technology and discloses a method, electronic device, and computer-readable storage medium for testing a work order system. The method includes: upon receiving a test start instruction, each work order client sends a work order creation request to a work order server; and upon receiving a work order operation task sent by the work order server, executing the work order operation task and returning the operation execution result to the work order server; upon receiving a work order creation request sent by any work order client, the work order server creates a work order and sends a work order assignment task to one of the work order clients; and upon receiving an operation execution result returned by any work order client based on the received work order operation task, sending the next work order operation task to one of the work order clients based on the operation execution result, and performing performance monitoring to obtain performance test data. In this way, costs are reduced and test accuracy is improved.

Description

Technical Field

[0001] The present application relates to the field of testing technology, and in particular to a method, electronic device, and computer-readable storage medium for testing a work order system. Background Art

[0002] A work order system is typically used as an internal business system within a company to handle various work order tasks. It consists of a work order client and a work order server. The work order client typically includes multiple work order service nodes (e.g., work order creation node, work order assignment node, work order processing node, and work order review node). Each work order typically needs to flow through multiple work order service nodes to complete operations such as creation, assignment, processing, review, and closure.

[0003] Under the existing technology, manual methods are usually used to control the flow of work order clients between various work order business nodes to obtain performance test data of the work order system.

[0004] However, when testing a work order system for a large number of work orders, it consumes a lot of time and manpower costs, and the accuracy of the test results is poor. Summary of the Invention

[0005] The purpose of the embodiments of the present application is to provide a method, electronic device and computer-readable storage medium for testing a work order system, so as to reduce the time and manpower costs consumed and improve the accuracy of the test results when testing a work order system for a large number of work orders.

[0006] On the one hand, a method for testing a work order system is provided, comprising: a test platform and a work order system, wherein the work order system comprises a work order server and a plurality of user devices equipped with work order clients, wherein:

[0007] The test platform is used to send test start instructions to multiple work order clients and monitor the performance of the work order server to obtain performance test data;

[0008] Each work order client is configured to send a work order creation request to the work order server upon receiving a test start instruction; and to execute the work order operation task upon receiving a work order operation task sent by the work order server, and return the operation execution result to the work order server;

[0009] The work order server is used to: determine that a work order is created when a work order creation request is received from any work order client, and send a work order assignment task to one of the work order clients; and, when an operation execution result is received based on the work order operation task returned by any work order client, send the next work order operation task to one of the work order clients based on the operation execution result; and, perform performance monitoring to obtain performance test data of the work order server. The work order operation tasks include work order assignment tasks.

[0010] In one embodiment, the work order client includes a work order application and a work order web client;

[0011] Work order operation tasks also include: work order processing tasks and work order review tasks;

[0012] Work order assignment tasks are tasks used to assign work order clients to process work orders; work order processing tasks are tasks used to process work orders; and work order review tasks are tasks used to review work orders.

[0013] The work order client includes the following work order business nodes: a work order creation node for requesting the creation of a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders;

[0014] The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory usage, CPU usage, hard disk read and write rate, and network bandwidth.

[0015] In one embodiment, the work order creation node is configured to: upon determining that a test start instruction is received, send a work order creation request to a work order server, so that the work order server creates a work order based on the work order creation request;

[0016] The work order allocation node is used to: upon receiving a work order allocation task sent by the work order server for any work order, allocate a work order client to the work order from among the work order clients, and send the work order allocation result to the work order server, so that the server sends the work order processing task for the work order to the allocated work order client based on the work order allocation result;

[0017] The work order processing node is used to: determine that when receiving a work order processing task sent by the work order server for any work order, process the work order for any work order, and send the work order processing result of any work order to the work order server, so that the work order server sends a work order review task to one of the work order clients;

[0018] The work order review node is used to: when determining that a work order review task sent by the work order server for any work order is received, review the task processing results in the work order review task; if it is determined that the review is passed, send an audit closing request for any work order to the work order server, so that when the work order server determines that it has received an audit closing request sent for any work order, it closes the work order processing flow of any work order.

[0019] In one embodiment, the work order allocation node is further used to:

[0020] When it is determined that a test start instruction has been received, work order allocation tasks for multiple preset work orders are obtained, a corresponding work order client is allocated to each preset work order, and the work order allocation result is sent to the work order server, so that the server sends the respectively allocated work order processing tasks to each work order client based on the received work order allocation result;

[0021] The work order processing node is further configured to: upon receiving a test start instruction, obtain and process work order processing tasks for a plurality of preset work orders, and send task processing results of each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on the received task processing results;

[0022] The work order review node is used to: when determining that a test start instruction is received, obtain work order review tasks for multiple preset work orders, and send a review closing request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request;

[0023] The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders preset before receiving the test start instruction.

[0024] In one embodiment, the test platform is further used to:

[0025] Analyze the work order server based on the performance test data to obtain the performance analysis results of the work order server;

[0026] According to the performance analysis results, adjust the number of work order clients that send test start instructions, as well as the number of work order operation tasks of the preset work orders of each work order business node, and test the work order system again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0027] In one aspect, a method for testing a work order system is provided, which is applied to a work order system, wherein the work order system includes a work order server and multiple user devices equipped with work order clients, including:

[0028] When each work order client determines that it has received a test start instruction, it sends a work order creation request to the work order server; and when it determines that it has received a work order operation task sent by the work order server, it executes the work order operation task and returns the operation execution result to the work order server;

[0029] The work order server determines to create a work order when it receives a work order creation request sent by any work order client, and sends a work order allocation task to one of the work order clients. Moreover, when it determines to receive an operation execution result returned by any work order client based on the received work order operation task, it sends the next work order operation task to one of the work order clients based on the operation execution result. Furthermore, it performs performance monitoring to obtain performance test data of the work order server. The work order operation tasks include work order allocation tasks.

[0030] In the above implementation process, multiple platforms can be tested automatically, which reduces the manpower and time costs and improves the test accuracy.

[0031] In one embodiment, the work order client includes a work order application and a work order web client;

[0032] Work order operation tasks also include: work order processing tasks and work order review tasks;

[0033] Work order assignment tasks are tasks used to assign work order clients to process work orders; work order processing tasks are tasks used to process work orders; and work order review tasks are tasks used to review work orders.

[0034] The work order client includes the following work order business nodes: a work order creation node for requesting the creation of a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders;

[0035] The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory usage, CPU usage, hard disk read and write rate, and network bandwidth.

[0036] In one embodiment, when determining that a work order operation task is received from a work order server, executing the work order operation task and returning the operation execution result to the work order server includes:

[0037] If it is determined that a work order allocation task for any work order has been received from the work order server, the work order allocation node allocates a work order client to the work order from among the work order clients, and sends the work order allocation result to the work order server, so that the server sends the work order processing task for the work order to the allocated work order client based on the work order allocation result;

[0038] If it is determined that a work order processing task sent by the work order server for any work order is received, the work order processing node processes the work order and sends the work order processing result of the work order to the work order server, so that the work order server sends a work order review task to one of the work order clients;

[0039] If it is determined that a work order review task sent by the work order server for any work order has been received, the work order review node will review the task processing results in the work order review task. If it is determined that the review is passed, an review closing request for any work order will be sent to the work order server, so that when the work order server determines that it has received the review closing request sent for any work order, it will close the work order processing flow of any work order.

[0040] In the above implementation process, multiple work order business nodes can be combined for testing, which improves the possibility of discovering problems and the accuracy of testing.

[0041] In one embodiment, the method further comprises:

[0042] When it is determined that a test start instruction has been received, the work order allocation node obtains work order allocation tasks for multiple preset work orders, allocates a corresponding work order client to each preset work order, and sends the work order allocation result to the work order server, so that the server sends the assigned work order processing task to each work order client based on the received work order allocation result;

[0043] When it is determined that a test start instruction has been received, the work order processing node obtains and processes work order processing tasks for multiple preset work orders, and sends task processing results of each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on the received task processing results;

[0044] When it is determined that a test start instruction has been received, the work order review node obtains work order review tasks for multiple preset work orders, and sends a review closing request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request;

[0045] The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders preset before receiving the test start instruction.

[0046] During the above implementation process, the test can also be performed in combination with preset work order data, which is more in line with the time application scenario and improves the test accuracy.

[0047] In one embodiment, the method further comprises:

[0048] The performance test data is sent to the test platform, so that the test platform adjusts the number of work order clients that send test start instructions and the number of work order operation tasks of preset work orders of each work order business node based on the performance test data, and performs work order system testing again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0049] In the above implementation process, parameter adjustment tests can be continuously performed according to the test results, thereby further improving the test accuracy.

[0050] On the one hand, a device for testing a work order system is provided, comprising a work order server and a plurality of user devices provided with work order clients, wherein:

[0051] Each work order client is configured to send a work order creation request to the work order server upon receiving a test start instruction; and to execute the work order operation task upon receiving a work order operation task sent by the work order server, and return the operation execution result to the work order server;

[0052] The work order server is used to determine whether to create a work order when receiving a work order creation request sent by any work order client, and send a work order allocation task to one of the work order clients. Moreover, when determining whether to receive an operation execution result returned by any work order client based on the received work order operation task, it sends the next work order operation task to one of the work order clients based on the operation execution result. Furthermore, it performs performance monitoring to obtain performance test data of the work order server. The work order operation tasks include work order allocation tasks.

[0053] In one embodiment, the work order client includes a work order application and a work order web client;

[0054] Work order operation tasks also include: work order processing tasks and work order review tasks;

[0055] Work order assignment tasks are tasks used to assign work order clients to process work orders; work order processing tasks are tasks used to process work orders; and work order review tasks are tasks used to review work orders.

[0056] The work order client includes the following work order business nodes: a work order creation node for requesting the creation of a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders;

[0057] The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory usage, CPU usage, hard disk read and write rate, and network bandwidth.

[0058] In one embodiment, each work order client is used to:

[0059] If it is determined that a work order allocation task for any work order has been received from the work order server, a work order client is allocated to the work order from among the work order clients through the work order allocation node, and the work order allocation result is sent to the work order server, so that the server sends a work order processing task for the work order to the allocated work order client based on the work order allocation result;

[0060] If it is determined that a work order processing task sent by the work order server for any work order is received, the work order processing node processes the work order and sends the work order processing result of the work order to the work order server, so that the work order server sends a work order review task to one of the work order clients;

[0061] If it is determined that a work order review task sent by the work order server for any work order is received, the task processing result in the work order review task is reviewed through the work order review node. If it is determined that the review is passed, an audit closing request for any work order is sent to the work order server, so that when the work order server determines that it has received an audit closing request sent for any work order, it closes the work order processing flow of any work order.

[0062] In one embodiment, each work order client is further configured to:

[0063] When it is determined that a test start instruction has been received, the work order allocation task for multiple preset work orders is obtained through the work order allocation node, a corresponding work order client is allocated to each preset work order, and the work order allocation result is sent to the work order server, so that the server sends the assigned work order processing task to each work order client based on the received work order allocation result;

[0064] When it is determined that a test start instruction is received, the work order processing node obtains and processes work order processing tasks for multiple preset work orders, and sends the task processing results of each preset work order to the work order server, so that the work order server sends the corresponding work order review task based on the received task processing results;

[0065] When it is determined that a test start instruction has been received, the work order review task for multiple preset work orders is obtained through the work order review node, and a review closing request for each preset work order is sent to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request;

[0066] The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders preset before receiving the test start instruction.

[0067] In one embodiment, the work order server is further configured to:

[0068] The performance test data is sent to the test platform, so that the test platform adjusts the number of work order clients that send test start instructions and the number of work order operation tasks of preset work orders of each work order business node based on the performance test data, and performs work order system testing again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0069] On the one hand, an electronic device is provided, comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the method provided in any of the various optional implementations of the work order system test described above are executed.

[0070] On the one hand, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method provided in any of the various optional implementations of the work order system test are executed.

[0071] In one aspect, a computer program product is provided. When the computer program product is run on a computer, the computer is caused to execute the steps of the method provided in any of the various optional implementations of the work order system test described above.

[0072] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0074] Figure 1 A schematic diagram of the architecture of a system for testing a work order system provided in an embodiment of the present application;

[0075] Figure 2 A flowchart of a method for testing a work order system according to an embodiment of the present application;

[0076] Figure 3 A schematic diagram of a node flow process of a work order client provided in an embodiment of the present application;

[0077] Figure 4 A structural block diagram of a device for testing a work order system provided in an embodiment of the present application;

[0078] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0079] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work fall within the scope of protection of the present application.

[0080] First, some of the terms involved in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0081] Terminal device: can be a mobile terminal, fixed terminal or portable terminal, such as a mobile phone, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system device, personal navigation device, personal digital assistant, audio / video player, digital camera / camcorder, positioning device, television receiver, radio broadcast receiver, e-book device, gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. It is also foreseeable that the terminal device can support any type of user interface (such as wearable device), etc.

[0082] Server: It can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, and big data and artificial intelligence platforms.

[0083] In order to reduce the time and manpower costs and improve the accuracy of test results when testing a work order system for a large number of work orders, the embodiments of the present application provide a method, electronic device and computer-readable storage medium for testing a work order system.

[0084] See Figure 1The figure shows an architectural diagram of a system for testing a work order system provided in an embodiment of the present application. The system for testing a work order system includes: a test platform and a work order system. The work order system includes a work order server and multiple user devices equipped with work order clients. The user devices are terminal devices, including smart terminals and personal computers. The smart terminal is equipped with a work order application (Application, APP), and the personal computer is equipped with a work order web client. The work order web client can also be called a World Wide Web (Web) client.

[0085] The test platform is used to send test start instructions to multiple work order clients and perform performance monitoring (in real time or periodically) on the work order server to obtain performance test data;

[0086] Each work order client is configured to send a work order creation request to the work order server upon receiving a test start instruction; and to execute the work order operation task upon receiving a work order operation task sent by the work order server, and return the operation execution result to the work order server;

[0087] The work order server is used to: determine that a work order is created when a work order creation request is received from any work order client, and send a work order assignment task to one of the work order clients; and, when an operation execution result is received based on the received work order operation task returned by any work order client, send the next work order operation task to one of the work order clients based on the operation execution result.

[0088] In one embodiment, the performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory usage, central processing unit usage, hard disk read and write rate, and network bandwidth.

[0089] In one embodiment, the work order client includes the following work order service nodes: a work order creation node for requesting to create a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders.

[0090] In actual applications, the work order business node in the work order client can be set according to the actual application scenario. For example, it can also include a work order business node for secondary review, which is not limited here.

[0091] In one embodiment, the work order operation task includes a work order allocation task. Optionally, the work order operation task also includes: a work order processing task and a work order review task; the work order allocation task is a task for assigning a work order client to process the work order; the work order processing task is a task for processing the work order; and the work order review task is a task for reviewing the work order.

[0092] In one embodiment, the work order allocation node is used to: when determining that a work order allocation task is received from a work order server for any work order, allocate a work order client to any work order from each work order client, and send the work order allocation result to the work order server, so that the server sends a work order processing task for any work order to the assigned work order client based on the work order allocation result.

[0093] In one embodiment, the work order processing node is used to: when it determines that a work order processing task sent by a work order server for any work order has been received, perform work order processing on any work order, and send the work order processing result of any work order to the work order server, so that the work order server sends a work order review task to one of the work order clients.

[0094] In one embodiment, the work order review node is used to: when determining that a work order review task sent by a work order server for any work order is received, review the task processing results in the work order review task; if it is determined that the review is passed, send a review closure request for any work order to the work order server, so that when the work order server determines that a review closure request sent for any work order is received, it closes the work order processing flow of any work order.

[0095] It should be noted that since the work order system usually needs to process work order operation tasks for multiple work orders, in actual applications, each work order review node may be processing work order operation tasks for different work orders at the same time. Therefore, in order to simulate the actual application scenario, in the embodiment of the present application, before testing, multiple preset work order operation tasks can be set for each work order business node in advance.

[0096] In one embodiment, the work order allocation node is further configured to: upon receiving a test start instruction, obtain work order allocation tasks for a plurality of preset work orders, respectively allocate a corresponding work order client to each preset work order, and send the work order allocation result to the work order server, so that the server sends the respective allocated work order processing tasks to each work order client based on the received work order allocation result;

[0097] In one embodiment, the work order processing node is further configured to: upon receiving a test start instruction, obtain and process work order processing tasks for a plurality of preset work orders, and send task processing results for each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on each received task processing result;

[0098] In one embodiment, the work order review node is configured to: upon receiving a test start instruction, obtain work order review tasks for a plurality of preset work orders, and send a review closing request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request;

[0099] The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders preset before receiving the test start instruction.

[0100] Furthermore, after obtaining the performance test data, test adjustments can be made based on the performance test data to obtain performance analysis results that meet set conditions.

[0101] In one embodiment, the work order server is analyzed based on the performance test data to obtain the performance analysis results of the work order server; based on the performance analysis results, the number of work order clients that send test start instructions is adjusted, as well as the number of work order operation tasks of the preset work orders of each work order business node is adjusted, and the work order system test is performed again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0102] See Figure 2 FIG. 1 is a flowchart of a method for testing a work order system according to an embodiment of the present application. Figure 2 right Figure 1 The specific implementation process of this method includes:

[0103] Step 200: When each work order client determines that it has received a test start instruction, it sends a work order creation request to the work order server; and when it determines that it has received a work order operation task sent by the work order server, it executes the work order operation task and returns the operation execution result to the work order server. Step 201: When the work order server determines that it has received a work order creation request sent by any work order client, it creates a work order and sends a work order assignment task to one of the work order clients. When it determines that it has received an operation execution result returned by any work order client based on the received work order operation task, it sends the next work order operation task to one of the work order clients based on the operation execution result, and performs performance monitoring to obtain performance test data of the work order server. Work order operation tasks include work order assignment tasks.

[0104] In one implementation, each work order service node in the work order system executes its own work order operation task and returns the operation execution result to the work order server.

[0105] As an example, if it is determined that a work order allocation task is received from the work order server for any work order, the work order allocation node allocates a work order client to any work order from each work order client, and sends the work order allocation result to the work order server, so that the server sends a work order processing task for any work order to the assigned work order client based on the work order allocation result.

[0106] As another example, if it is determined that a work order processing task sent by the work order server for any work order is received, the work order processing node processes any work order and sends the work order processing result of any work order to the work order server, so that the work order server sends a work order review task to one of the work order clients.

[0107] As another example, if it is determined that a work order review task sent by the work order server for any work order is received, the work order review node reviews the task processing results in the work order review task. If it is determined that the review is passed, an audit closing request for any work order is sent to the work order server, so that when the work order server determines that it has received the audit closing request sent for any work order, it closes the work order processing flow of any work order.

[0108] Since the work order system usually needs to process work order operation tasks for multiple work orders, in actual applications, each work order review node may be processing work order operation tasks for different work orders at the same time. Therefore, in order to simulate the actual application scenario, in the embodiment of the present application, before testing, multiple work order operation tasks for preset work orders can be set for each work order business node in advance.

[0109] As an example, when it is determined that a test start instruction has been received, the work order allocation node obtains work order allocation tasks for multiple preset work orders, assigns corresponding work order clients to each preset work order, and sends the work order allocation results to the work order server, so that the server sends the assigned work order processing tasks to each work order client based on the received work order allocation results.

[0110] As another example, when it is determined that a test start instruction has been received, the work order processing node obtains and processes work order processing tasks for multiple preset work orders, and sends the task processing results of each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on the received task processing results.

[0111] As another example, when it is determined that a test start instruction has been received, the work order review node obtains work order review tasks for multiple preset work orders, and sends a review closure request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closure request.

[0112] Furthermore, after obtaining the performance test data, test adjustments can be made based on the performance test data to obtain performance analysis results that meet set conditions.

[0113] In one embodiment, performance test data is sent to a test platform, so that the test platform adjusts the number of work order clients that send test start instructions and the number of work order operation tasks of preset work orders of each work order business node based on the performance test data, and performs work order system testing again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0114] As an example, the following steps are executed repeatedly until a performance analysis result that meets the set conditions is obtained:

[0115] The testing platform analyzes the work order server based on the performance test data to obtain performance analysis results for the work order server. Based on the performance analysis results, the testing platform adjusts the number of work order clients that send test start commands and the number of work order operation tasks for pre-set work orders at each work order service node. Based on the number of tasks at each work order service node, the testing platform sends a work order task pre-set request to each work order client. Each work order client pre-sets multiple work order operation tasks for the pre-set work orders at each work order service node in accordance with the pre-set request. After the work order server determines that the pre-set work order tasks are complete, it executes step 200 based on the number of work order clients to send a test start command to each work order client.

[0116] In the embodiment of the present application, based on the business process of the work order system, by mixing two different platforms, app and web, and a work order pre-setting scheme, a performance monitoring scheme for simultaneous operation of multiple platforms and multiple work order business nodes is implemented by having a large number of work orders in different approval nodes (i.e., work order business nodes). This provides data reference and direction for the optimization and launch of the work order system, and the test process is clear and simple, and can simulate the actual application scenario as much as possible, thereby improving the accuracy of the test.

[0117] In actual application scenarios, each user has a user account for logging into the work order client, and each user account usually includes multiple roles, such as sales personnel, managers, and engineers. Sales personnel create work orders through the work order creation node of the work order client (for example, submitting product issues through work orders). The server transfers the work order to the next node (i.e., the work order allocation node). The manager assigns the work order to the engineer through the work order allocation node of the work order client. The engineer processes the assigned work order through the work order processing node of the work order client (for example, repairing product issues). The server transfers the work order to the next node (i.e., the work order review node). The manager reviews and closes the work order through the work order review node of the work order client. It should be noted that each role can handle one or more work orders (for example, a manager can assign multiple work orders). Each role can contain one or more user accounts, and there is no restriction here.

[0118] As an example, a company can conduct research on actual business operations to determine the number of user accounts for each role and the concurrent volume of each work order during different time periods. Testing can then be conducted based on these findings (e.g., the maximum number of accounts and concurrent volume for each role during peak time periods). This allows for predictions based on historical data to simulate actual application scenarios.

[0119] In one embodiment, user accounts and work order accounts for each role are created in advance, and a database is linked through an algorithm to store each user account and work order account in the database. Database statements, such as Structured Query Language (SQL), can also be used for splicing so that each field in the database can be traversed and searched later, and multiple database table fields of the system can be summarized and integrated and output to a preset file, such as a comma-separated values ​​(CSV) file, for subsequent preset work order calls.

[0120] See Figure 3 The figure shows a schematic diagram of the node flow process of a work order client. Figure 3 right Figure 2 and Figure 1 The node flow process of the work order client is illustrated as an example. It includes an app platform test module, a web platform test module, and a statistics module. The app platform test module includes a first preset module 31 and a first test module 32. The platform test module includes a second preset module 33 and a second test module 34.

[0121] The first preset module 31 includes: a work order creation preset module 311 , a work order allocation preset module 312 , a work order processing preset module 313 and a work order review preset module 314 .

[0122] The first test module 32 includes: a work order creation test module 321 , a work order allocation test module 322 , a work order processing test module 323 and a work order review test module 324 .

[0123] The second preset module 33 includes: a work order creation preset module 331 , a work order allocation preset module 334 , a work order processing preset module 333 , and a work order review preset module 334 .

[0124] The second test module 34 includes: a work order creation test module 341 , a work order allocation test module 342 , a work order processing test module 343 and a work order review test module 344 .

[0125] The work order creation module preset 301 is used to create multiple work orders through the work order creation nodes in multiple work order apps.

[0126] In one implementation, the test platform sends work order creation instructions to multiple work order apps (e.g., 3,000 work order apps) to simulate an operator (e.g., a salesperson) creating a work order. Based on the work order creation instructions, the work order apps send work order creation requests to the work order server. The work order server creates each work order based on the work order creation requests.

[0127] Furthermore, each created work order flows to the next work order business node (ie, the work order allocation node).

[0128] Optionally, the user account of the work order APP to which the next work order business node belongs may be determined based on the work order creation request, or may be selected by the work order server from user accounts of the manager role.

[0129] Work order allocation preset module 312: used to execute work order allocation tasks for some transferred work orders through multiple work order allocation nodes to allocate them to the next work order business node, and set other transferred work orders as preset work orders to execute work order allocation tasks for preset work orders when the execution conditions are met (i.e., delay the execution of work order allocation tasks).

[0130] In one embodiment, the test platform sends allocation instructions to some (e.g., 1,500) work order APPs, so that they allocate some work orders to the next work order business node (i.e., work order processing node) through the work order allocation node, so that the work order processing node performs the work order processing task, and sends preset instructions to other (e.g., 1,500) work order APPs, so that they set some work orders as preset work orders through the work order allocation node, so that when the execution conditions are met, they execute the work order allocation task for each preset work order.

[0131] In actual applications, the execution conditions can be set according to the actual application scenarios. For example, when the work order APP receives the test start instruction, it can also be set according to the actual application scenario, which is not limited here.

[0132] Work order processing preset module 313: used to process part (e.g., 750) of the transferred work orders through multiple work order processing nodes (i.e., execute work order processing tasks), and transfer the processed work orders to the work order processing nodes, and set the other multiple (e.g., 750) transferred work orders as preset work orders, so as to execute work order processing tasks for the preset work orders when the execution conditions are met.

[0133] The work order review presetting module 314 is used to review each incoming work order through each work order review node, and close the work order that has passed the review (ie, execute the work order review task).

[0134] As an example, each incoming work order (eg, 750) is reviewed and closed through each work order review node.

[0135] As an example, through the CSV component, the work order account of the user account of each role in the database is called, and a large amount of work order data is preset in each work order business node.

[0136] In this way, you can preset the work orders before testing, that is, preset the work orders that flow into each work order business node.

[0137] The work order creation test module 321 is used to determine that when a test start instruction is received, multiple (eg, 3,000) work orders are created through the work order creation nodes in multiple work order APPs.

[0138] The work order allocation test module 322 is used to execute the work order allocation task for the transferred work order through multiple work order allocation nodes to allocate it to each work order processing node.

[0139] For example, 1,000 managers assign 3,000 work orders to the work order processing nodes of each engineer.

[0140] The work order processing test module 323 is used to process the incoming work orders through multiple work order processing nodes and transfer the processed work orders to each work order processing node.

[0141] For example, 2,000 engineers handle 3,000 work orders.

[0142] The work order review test module 324 is used to review each incoming work order through each work order review node, and close the work order that passes the review (i.e., execute the work order review task).

[0143] For example, 1,000 managers review and close 3,000 tickets.

[0144] It should be noted that, among the work orders transferred from various modules in the test module 32 , some are created by the work order creation test module 321 , and some are transferred from various modules in the first preset module 31 .

[0145] The following example illustrates the timeline between each work order service node. At times T1-T4, each work order service node in each module within the first pre-configured module 31 executes sequentially. At T5, the test initiates, and the work order creation node in the test module 321 is created. Simultaneously, each work order service node synchronously executes the corresponding work order operation tasks for each pre-configured work order. Then, each work order service node transfers the completed work order flow to the next work order service node, and so on.

[0146] In this way, some preset work orders can be pre-deployed on each work order business node, so that when the work order system is tested, each work order business node can execute its own tasks synchronously, which is more in line with the actual application scenario.

[0147] The second pre-configuration module 33 and the second test module 34 are applied to the work order web client. The specific functions of each module in the second pre-configuration module 33 and the second test module 34 are described in detail in the first pre-configuration module 31 and the first test module 32, and are not described in detail here. It should be noted that although the functions of the two are similar, due to the different system environments (such as programming languages ​​and calling interfaces) of the work order app and the work order web client, both the work order app and the work order web client need to perform work order testing.

[0148] In this way, a large number of work order apps and work order web clients can create a large number of work orders (for example, 6,000 each) in the work order creation node, and transfer large batches (such as 12,000) of work order data to each work order business node in the work order system in sequence. At the same time, the preset work orders in each work order business node are transferred in the work order system in sequence, so that each work order business node in the work order system is in a high-load state.

[0149] Statistics module: used to monitor the operating status of the work order server during the process of processing each work order in the work order system, so as to obtain the performance test data of the server in real time or periodically.

[0150] Furthermore, it can be sent to a test platform.

[0151] In one implementation, the work order server acquires and records performance test data in a real-time or periodic polling manner, and aggregates the performance test data into a report.

[0152] Furthermore, you can also perform any of the following tests on the work order system:

[0153] Method 1: Test only the work order app and work order server.

[0154] Method 2: Test only the ticket web client and ticket server.

[0155] Method 3: For at least one work order service node among each work order service node, one or more performance monitoring indicators of the work order server are tested.

[0156] For example, each work order business node can be independently separated as an extreme performance monitoring solution for a single node, and the concurrency of a single node can be increased through automated scripts, and various performance monitoring indicators can be monitored in real time, thereby completing the performance monitoring of the maximum concurrency and processing upper limit of a single node.

[0157] Method 4: Test the work order system on work order servers with different configurations to determine the hardware configuration of the work order server that meets service requirements.

[0158] The specific implementation process of executing the above methods 1-4 can refer to the above steps. In actual application, it can be set according to the actual application scenario, which will not be described here.

[0159] In the embodiment of the present application, work order data and user accounts can be preset through the database so that they can be called through test scripts and other means during subsequent testing, replacing manual operations and improving the efficiency of presets. In addition, the work order system test can be carried out in combination with the work order APP and the work order web client, that is, the app platform + web platform multi-platform hybrid processing can be used simultaneously, and the performance monitoring of the two platforms, the app side and the web side, which are actually controlled by two independent sets of code, can be completed at the same time. The possibility of influence between different platforms is increased, the possibility of problem discovery is increased, and the scenario becomes more complex and closer to reality. It simulates the real online operation environment to the maximum extent, and runs multiple nodes at the same time during the test to squeeze out large amounts of data, so as to derive the maximum system concurrency and the upper limit of the system server processing performance of running multiple platforms and multiple nodes at the same time of the work order server, providing a basis for product optimization. In addition, the test process is concise and clear, which reduces the complexity of testing. Manual testing is not required, which reduces a lot of manpower and time costs, thereby saving a lot of manpower and time costs for system testing iteration and system launch, promoting the maturity of the system, and shortening the product launch cycle. In addition, the introduction of multiple work order business nodes and work order processes in the work order system at the same time increases the possibility of influence between each process and each work order business node, and also increases the possibility of problem discovery, making the scenario more complex and closer to reality, shortening the product launch cycle, and reducing the risk caused by product delays. It can complete multi-platform and multi-node concurrent performance monitoring, and can test the overall load and stability of the system software, providing data reference for system software optimization and modification. In addition, the work order server is monitored in real time, and the obtained performance test data is summarized and analyzed, which improves the accuracy and efficiency of the test analysis. Furthermore, the number of test startup instructions sent and the number of tasks of the preset work order can be adjusted based on the test analysis results to obtain accurate performance test data and improve the test accuracy. In addition, the embodiment of the present application has a relatively high degree of reusability. It can be tested in various ways, such as targeting at least one work order business node, work order servers with different configurations, APP platforms, and web platforms. It has a wide range of applications and can test the upper limits of various parameters of service hardware, providing data reference for product hardware optimization and selection.

[0160] Based on the same inventive concept, an apparatus for testing a work order system is also provided in an embodiment of the present application. Since the principle of solving the problem by the above-mentioned apparatus and equipment is similar to a method for testing a work order system, the implementation of the above-mentioned apparatus can refer to the implementation of the method, and the repeated parts will not be repeated.

[0161] like Figure 4As shown, it is a structural diagram of a device for testing a work order system provided in an embodiment of the present application, including a work order server 401 and a plurality of user devices 402 provided with work order clients, wherein,

[0162] Each work order client is configured to send a work order creation request to the work order server 401 upon receiving a test start instruction; and to execute the work order operation task upon receiving a work order operation task sent by the work order server 401, and return the operation execution result to the work order server 401;

[0163] The work order server 401 is used to determine whether to create a work order when receiving a work order creation request sent by any work order client, and send a work order allocation task to one of the work order clients. When it is determined that an operation execution result is returned by any work order client based on the received work order operation task, the next work order operation task is sent to one of the work order clients based on the operation execution result. In addition, the work order operation task performs performance monitoring to obtain performance test data of the work order server. The work order operation task includes the work order allocation task.

[0164] In one embodiment, the work order client includes a work order application and a work order web client;

[0165] Work order operation tasks also include: work order processing tasks and work order review tasks;

[0166] Work order assignment tasks are tasks used to assign work order clients to process work orders; work order processing tasks are tasks used to process work orders; and work order review tasks are tasks used to review work orders.

[0167] The work order client includes the following work order business nodes: a work order creation node for requesting the creation of a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders;

[0168] The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory usage, CPU usage, hard disk read and write rate, and network bandwidth.

[0169] In one embodiment, each work order client is used to:

[0170] If it is determined that a work order assignment task sent by the work order server 401 for any work order is received, a work order client is assigned to the work order from each work order client through the work order assignment node, and the work order assignment result is sent to the work order server 401, so that the server sends a work order processing task for the work order to the assigned work order client based on the work order assignment result;

[0171] If it is determined that a work order processing task sent by the work order server 401 for any work order is received, the work order processing node processes the work order and sends the work order processing result of the work order to the work order server 401, so that the work order server 401 sends a work order review task to one of the work order clients;

[0172] If it is determined that a work order review task sent by the work order server 401 for any work order is received, the task processing result in the work order review task is reviewed through the work order review node. If it is determined that the review is passed, an audit closing request for any work order is sent to the work order server 401, so that when the work order server 401 determines that it has received an audit closing request sent for any work order, it closes the work order processing flow of any work order.

[0173] In one embodiment, each work order client is further configured to:

[0174] When it is determined that a test start instruction has been received, work order allocation tasks for multiple preset work orders are obtained through the work order allocation node, a corresponding work order client is allocated to each preset work order, and the work order allocation result is sent to the work order server 401, so that the server sends the allocated work order processing task to each work order client based on the received work order allocation result;

[0175] When it is determined that a test start instruction has been received, the work order processing node obtains and processes work order processing tasks for multiple preset work orders, and sends the task processing results of each preset work order to the work order server 401, so that the work order server 401 sends the corresponding work order review task based on the received task processing results;

[0176] When it is determined that the test start instruction has been received, the work order review task for multiple preset work orders is obtained through the work order review node, and a review closing request for each preset work order is sent to the work order server 401, so that the work order server 401 closes the corresponding work order processing flow based on the received review closing request;

[0177] The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders preset before receiving the test start instruction.

[0178] In one embodiment, the work order server 401 is further configured to:

[0179] The performance test data is sent to the test platform, so that the test platform adjusts the number of work order clients that send test start instructions and the number of work order operation tasks of preset work orders of each work order business node based on the performance test data, and performs work order system testing again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

[0180] In the method, electronic device, and computer-readable storage medium for testing a work order system provided by an embodiment of the present application, when each work order client determines that it has received a test start instruction, it sends a work order creation request to the work order server; and when it determines that it has received a work order operation task sent by the work order server, it executes the work order operation task and returns the operation execution result to the work order server; the work order server determines that it has created a work order when it has received a work order creation request sent by any work order client, and sends a work order assignment task to one of the work order clients; and when it determines that it has received an operation execution result returned by any work order client based on the received work order operation task, it sends the next work order operation task to one of the work order clients based on the operation execution result, and performs performance monitoring to obtain performance test data of the work order server. The work order operation tasks include work order assignment tasks. In this way, multi-platform testing can be automated, reducing labor and time costs and improving test accuracy.

[0181] Figure 5 A schematic diagram of the structure of an electronic device is shown. Figure 5 As shown, the electronic device 5000 includes: a processor 5010 and a memory 5020, and optionally, may also include a power supply 5030, a display unit 5040, and an input unit 5050.

[0182] The processor 5010 is the control center of the electronic device 5000. It uses various interfaces and lines to connect various components, and performs various functions of the electronic device 5000 by running or executing software programs and / or data stored in the memory 5020, thereby monitoring the electronic device 5000 as a whole.

[0183] In the embodiment of the present application, the processor 5010 executes the various steps in the above embodiment when calling the computer program stored in the memory 5020.

[0184] Optionally, the processor 5010 may include one or more processing units. Preferably, the processor 5010 may integrate an application processor and a modem processor, wherein the application processor primarily processes the operating system, user interface, and applications, and the modem processor primarily processes wireless communications. It is understood that the modem processor may not be integrated into the processor 5010. In some embodiments, the processor and memory may be implemented on a single chip. In some embodiments, they may also be implemented on separate chips.

[0185] The memory 5020 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, various applications, etc., and the data storage area may store data created based on the use of the electronic device 5000. In addition, the memory 5020 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 volatile solid-state storage device.

[0186] The electronic device 5000 also includes a power supply 5030 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 5010 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0187] The display unit 5040 can be used to display information input by the user or information provided to the user, as well as various menus of the electronic device 5000. In the embodiment of the present invention, it is mainly used to display the display interface of each application in the electronic device 5000 and objects such as text and pictures displayed on the display interface. The display unit 5040 may include a display panel 5041. The display panel 5041 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.

[0188] The input unit 5050 can be used to receive information such as numbers or characters input by the user. The input unit 5050 may include a touch panel 5051 and other input devices 5052. The touch panel 5051, also known as a touch screen, can receive user touch operations on or near it (for example, operations performed by the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 5051).

[0189] Specifically, the touch panel 5051 can detect user touch operations and the signals generated by the touch operations, convert these signals into touch point coordinates, send them to the processor 5010, and receive and execute commands sent by the processor 5010. In addition, the touch panel 5051 can be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. Other input devices 5052 can include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, a joystick, etc.

[0190] Of course, the touch panel 5051 can cover the display panel 5041. When the touch panel 5051 detects a touch operation on or near it, it transmits the information to the processor 5010 to determine the type of touch event. Then, the processor 5010 provides corresponding visual output on the display panel 5041 according to the type of touch event. Figure 5 In the embodiment, the touch panel 5051 and the display panel 5041 are two independent components to realize the input and output functions of the electronic device 5000, but in some embodiments, the touch panel 5051 and the display panel 5041 can be integrated to realize the input and output functions of the electronic device 5000.

[0191] The electronic device 5000 may also include one or more sensors, such as a pressure sensor, a gravity acceleration sensor, a proximity light sensor, etc. Of course, according to the needs of specific applications, the electronic device 5000 may also include other components such as a camera. Since these components are not the key components used in the embodiments of this application, Figure 5 It is not shown and will not be described in detail.

[0192] Those skilled in the art will understand that Figure 5 The electronic device is merely an example and does not limit the electronic device. The electronic device may include more or fewer components than shown in the figure, or may include a combination of certain components or different components.

[0193] In an embodiment of the present application, a computer-readable storage medium stores a computer program. When the computer program is executed by a processor, a communication device can perform each step in the above embodiment.

[0194] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0195] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0196] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0197] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0198] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0199] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0200] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A system for testing a work order system, characterized in that: It includes a test platform and a work order system, wherein the work order system includes a work order server and multiple user devices equipped with work order clients, wherein: The test platform is used to send test start instructions to the plurality of work order clients, and perform performance monitoring on the work order server to obtain performance test data; Each work order client is configured to send a work order creation request to the work order server upon receiving the test start instruction; and to execute the work order operation task upon receiving the work order operation task sent by the work order server, and return the operation execution result to the work order server; The work order server is configured to: determine to create a work order upon receiving a work order creation request sent by any work order client, and send a work order assignment task to one of the work order clients; and, upon determining to receive an operation execution result returned by any work order client based on the received work order operation task, send a next work order operation task to one of the work order clients based on the operation execution result, wherein the work order operation task includes the work order assignment task; The work order client includes the following work order service nodes: a work order creation node for requesting to create a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders; The work order allocation node is also used to: When it is determined that the test start instruction is received, work order allocation tasks for multiple preset work orders are obtained, a corresponding work order client is allocated to each preset work order, and a work order allocation result is sent to the work order server, so that the server sends the respectively allocated work order processing task to each work order client based on the received work order allocation result; The work order processing node is further configured to: upon receiving the test start instruction, obtain and process work order processing tasks for a plurality of preset work orders, and send task processing results of each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on the received task processing results; The work order review node is configured to: upon receiving the test start instruction, obtain work order review tasks for a plurality of preset work orders, and send a review closing request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request; The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders pre-set before receiving the test start instruction; The method for setting the preset work order includes: conducting a survey on actual business to determine the number of user accounts of each role and the concurrent volume of each work order in each time period, and conducting a test based on the survey results; wherein the survey results include the maximum number of accounts and the maximum concurrent volume of each role during the peak time period; Through the CSV component, call the work order account of the user account of each role in the database and preset the work order data in each work order business node.

2. The system according to claim 1, wherein The work order client includes a work order application and a work order web client; The work order operation tasks also include: work order processing tasks and work order review tasks; The work order allocation task is a task for allocating work order clients to process work orders; the work order processing task is a task for processing work orders; and the work order review task is a task for reviewing work orders. The work order client includes the following work order service nodes: a work order creation node for requesting to create a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders; The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory occupancy, central processing unit occupancy, hard disk read and write rate, and network bandwidth.

3. The system according to claim 2, characterized in that The work order creation node is configured to: upon determining that the test start instruction is received, send a work order creation request to the work order server, so that the work order server creates a work order based on the work order creation request; The work order allocation node is configured to: upon receiving a work order allocation task sent by the work order server for any work order, allocate a work order client from among the work order clients to the work order, and send the work order allocation result to the work order server, so that the server sends the work order processing task for the work order to the allocated work order client based on the work order allocation result; The work order processing node is configured to: upon receiving a work order processing task sent by the work order server for any work order, perform work order processing on the work order, and send a work order processing result of the work order to the work order server, so that the work order server sends a work order review task to one of the work order clients; The work order review node is used to: when determining that a work order review task sent by the work order server for any work order has been received, review the task processing result in the work order review task; if it is determined that the review is passed, send a review closing request for any work order to the work order server, so that when the work order server determines that a review closing request sent for any work order has been received, it closes the work order processing flow of any work order.

4. The system according to claim 3, wherein: The test platform is also used to: Analyze the work order server according to the performance test data to obtain a performance analysis result of the work order server; According to the performance analysis results, the number of work order clients that send test start instructions is adjusted, as well as the number of work order operation tasks of the preset work orders of each work order business node is adjusted, and the work order system test is performed again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

5. A method for testing a work order system, characterized in that: Applied to a work order system, the work order system includes a work order server and multiple user devices equipped with work order clients, including: When each work order client determines that it has received a test start instruction, it sends a work order creation request to the work order server; and when it determines that it has received a work order operation task sent by the work order server, it executes the work order operation task and returns the operation execution result to the work order server; The work order server determines to create a work order upon receiving a work order creation request sent by any work order client, and sends a work order assignment task to one of the work order clients; and, upon determining to receive an operation execution result returned by any work order client based on the received work order operation task, sends the next work order operation task to one of the work order clients based on the operation execution result; and, performs performance monitoring to obtain performance test data of the work order server, wherein the work order operation task includes the work order assignment task; The work order client includes the following work order service nodes: a work order creation node for requesting to create a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders; The method further comprises: When it is determined that the test start instruction has been received, the work order allocation node obtains work order allocation tasks for multiple preset work orders, allocates a corresponding work order client to each preset work order, and sends the work order allocation result to the work order server, so that the server sends the respectively allocated work order processing task to each work order client based on the received work order allocation result; When it is determined that the test start instruction is received, the work order processing node obtains and processes work order processing tasks for multiple preset work orders, and sends task processing results of each preset work order to the work order server, so that the work order server sends corresponding work order review tasks based on the received task processing results; When it is determined that the test start instruction has been received, the work order review node obtains work order review tasks for multiple preset work orders, and sends a review closing request for each preset work order to the work order server, so that the work order server closes the corresponding work order processing flow based on the received review closing request; The work order operation tasks of the preset work orders corresponding to each work order business node are work order operation tasks of multiple work orders pre-set before receiving the test start instruction; The method for setting the preset work order includes: conducting a survey on actual business to determine the number of user accounts of each role and the concurrent volume of each work order in each time period, and conducting a test based on the survey results; wherein the survey results include the maximum number of accounts and the maximum concurrent volume of each role during the peak time period; Through the CSV component, call the work order account of the user account of each role in the database and preset the work order data in each work order business node.

6. The method according to claim 5, wherein The work order client includes a work order application and a work order web client; The work order operation tasks also include: work order processing tasks and work order review tasks; The work order allocation task is a task for allocating work order clients to process work orders; the work order processing task is a task for processing work orders; and the work order review task is a task for reviewing work orders. The work order client includes the following work order service nodes: a work order creation node for requesting to create a work order, a work order allocation node for allocating work orders, a work order processing node for processing work orders, and a work order review node for reviewing work orders; The performance test data includes at least one of the following parameters: system concurrency, user response time, exception rate, memory occupancy, central processing unit occupancy, hard disk read and write rate, and network bandwidth.

7. The method according to claim 6, wherein The method for determining that, upon receiving a work order operation task sent by the work order server, the work order operation task is executed, and the operation execution result is returned to the work order server, includes: If it is determined that a work order allocation task sent by the work order server for any work order has been received, the work order allocation node allocates a work order client from each work order client to the any work order, and sends the work order allocation result to the work order server, so that the server sends the work order processing task for the any work order to the allocated work order client based on the work order allocation result; If it is determined that a work order processing task sent by the work order server for any work order is received, the work order processing node processes the work order and sends a work order processing result of the work order to the work order server, so that the work order server sends a work order review task to one of the work order clients; If it is determined that a work order review task sent by the work order server for any work order has been received, the work order review node will review the task processing result in the work order review task. If it is determined that the review is passed, an audit closing request for any work order will be sent to the work order server, so that when the work order server determines that it has received the audit closing request sent for any work order, it will close the work order processing process of any work order.

8. The method according to claim 7, wherein The method further comprises: The performance test data is sent to the test platform, so that the test platform adjusts the number of work order clients that send test start instructions and the number of work order operation tasks of preset work orders of each work order business node based on the performance test data, and performs work order system testing again based on the number of work order clients and the number of tasks of each work order business node until a performance analysis result that meets the set conditions is obtained.

9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the method according to any one of claims 5 to 7 is executed.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 5 to 7 is executed.

Images