Multi-cabinet test method and device, electronic equipment and medium

Abstract

The invention provides a multi-cabinet test method and device, electronic equipment and a medium, and the method comprises the steps: obtaining a test data set; and for each test case, issuing the test case to a corresponding client, so that the client controls the corresponding cabinet to execute the test case for testing, receiving test data of the corresponding cabinet reported by the client, and updating the test data to the cache middleware corresponding to the test data set, the cache middleware is used for storing the execution state and the test data reported by each client; and for each client, packaging the test data corresponding to the client in the cache middleware to generate a test report and upload the test report in the process that the client controls the corresponding cabinet to test and when the execution state of the client is monitored to be test completion. According to the method, the cache middleware is introduced, so that the database pressure is relieved, and the hardware and operation and maintenance cost is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cabinet testing, in particular to a multi-cabinet testing method and device, electronic equipment and medium. BACKGROUND

[0002] Currently, the mainstream solution of remote cabinet testing mainly serves single-cabinet testing scenarios. When the testing scenario is expanded to multi-cabinet, the server will batch downlink the instructions of the same test set to multiple host client terminals to start parallel testing tasks. The server needs to receive the feedback data of each client in real time and update the progress and state records in the database in real time to ensure that the tester can master the overall situation.

[0003] However, this traditional method of directly recording interactive data based on the database faces severe challenges in multi-cabinet parallel testing. Due to the differences in the environment of each cabinet and the complexity of the task, high-concurrency data update requests will be generated. The massive concurrent requests also significantly increase the load on the database, putting pressure on hardware performance and operation and maintenance costs. SUMMARY

[0004] Therefore, the present application aims to provide a multi-cabinet testing method and device, electronic equipment and medium to overcome at least one of the above-mentioned defects.

[0005] In a first aspect, the present application provides a multi-cabinet testing method, which comprises: obtaining a test data set, the test data set comprising a plurality of test cases, each test case corresponding to a client, and each client being used to control a cabinet for testing; for each test case, downlinking the test case to the corresponding client to make the client control the corresponding cabinet to execute the test case for testing, receiving the test data of the corresponding cabinet reported by the client, and updating the test data in the cache middleware corresponding to the test data set, the cache middleware being used to store the execution status and test data reported by each client; for each client, monitoring the testing progress according to the execution status of the client in the cache middleware during the process of testing the corresponding cabinet controlled by the client, and when the execution status of the client is monitored to be complete testing, packaging the test data corresponding to the client in the cache middleware to generate a test report upload, and deleting all data of the client in the cache middleware after the test report upload is successful.

[0006] In a possible implementation, the client controls the corresponding rack to perform the test case for testing in the following manner: for each client, receiving the receipt information reported by the client and indicating successful reception of the test case, and updating the execution state of the client in the cache middleware to complete reception; for each client, when determining that the execution state of the client in the cache middleware is more complete reception, sending a start test instruction to the client to make the client start controlling the corresponding rack to perform testing, and updating the execution state of the client in the cache middleware to execution.

[0007] In a possible implementation, the method further includes: monitoring, at a preset monitoring time, whether the test data of the client associated with the test data set exists in the cache middleware; and determining that the test is completed when the test data of all clients in the cache middleware is deleted.

[0008] In a possible implementation, the method further includes: when receiving an interrupt command for the test data set, issuing an interrupt instruction to the client in the cache middleware whose test state is execution; for each client, receiving interrupt feedback of the client, updating the execution state of the client in the cache middleware to interrupt test, and removing all test data of the client in the cache middleware; and determining that the interrupt process is completed when the test data of all clients associated with the test data set in the cache middleware is removed.

[0009] In a possible implementation, the method further includes: if no receipt information reported by any client is received within a preset time, sending prompt information of issuance failure, cleaning all data in the cache middleware, and terminating the test process.

[0010] In a second aspect, the present application provides a multi-cabinet testing device, the device comprising: an acquisition module configured to acquire a test data set, the test data set comprising a plurality of test cases, each test case corresponding to a client, and each client being configured to control a cabinet to perform a test; an execution module configured to, for each test case, distribute the test case to the corresponding client, so that the client controls the corresponding cabinet to perform the test case to perform a test, receives test data of the corresponding cabinet reported by the client, and updates the test data in a cache middleware corresponding to the test data set, the cache middleware being configured to store the execution status and test data reported by each client; and an uploading module configured to, for each client, monitor a test progress according to the execution status of the client in the cache middleware during the process in which the client controls the corresponding cabinet to perform a test, and when it is monitored that the execution status of the client is complete testing, pack the test data corresponding to the client in the cache middleware to generate a test report upload, and delete all data of the client in the cache middleware after the test report upload is successful.

[0011] In a possible implementation, the execution device is further configured to: for each client, receive receipt information reported by the client and indicating that the test case is successfully received, and update the execution status of the client in the cache middleware to complete receiving; for each client, when it is determined that the execution status of the client in the cache middleware is more complete receiving, send a start testing instruction to the client, so that the client starts to control the corresponding cabinet to perform a test, and update the execution status of the client in the cache middleware to be in execution.

[0012] In a possible implementation, the device further comprises a monitoring module configured to, every preset monitoring time, monitor whether there is test data of a client associated with the test data set in the cache middleware; and when the test data of all clients have been deleted in the cache middleware, determine that a test is completed.

[0013] In a third aspect, the present application further provides an electronic device, comprising a processor, a memory and a bus, the memory storing machine readable instructions executable by the processor, the processor and the memory communicating through the bus when the electronic device is running, and the machine readable instructions being executed by the processor to perform the steps of the above method.

[0014] In a fourth aspect, the present application further provides a computer readable storage medium, the computer readable storage medium storing a computer program, the computer program being executed by the processor to perform the steps of the above method.

[0015] The application provides a multi-cabinet test method, device, electronic equipment and medium, wherein the method comprises: obtaining a test data set; for each test case, the test case is distributed to a corresponding client, so that the client controls the corresponding cabinet to execute the test case for testing, receives the test data of the corresponding cabinet reported by the client, and updates the test data to the cache middleware corresponding to the test data set, and the cache middleware is used to store the execution state and test data reported by each client; for each client, in the process of testing the corresponding cabinet controlled by the client, and when it is monitored that the execution state of the client is complete testing, the test data corresponding to the client in the cache middleware is packaged to generate a test report uploaded. The application reduces the database pressure, and reduces the hardware and operation and maintenance cost by introducing the cache middleware.

[0016] In order to make the above objectives, characteristics and advantages of the present application more apparent, the following will describe a preferred embodiment in detail, and the accompanying drawings will be described as follows. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments, and it should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as a limitation to the scope, and for those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0018] Figure 1 A flowchart of a multi-cabinet test method provided by the embodiments of the present application; Figure 2 A flowchart of controlling a cabinet to test provided by the embodiments of the present application; Figure 3 A flowchart of determining test end provided by the embodiments of the present application; Figure 4 A flowchart of interrupting test flow provided by the embodiments of the present application; Figure 5 A structural schematic diagram of a multi-cabinet test device provided by the embodiments of the present application; Figure 6 A structural schematic diagram of an electronic equipment provided by the embodiments of the present application. DETAILED DESCRIPTION

[0019] To make the purposes, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application and are not all the embodiments. The components of the embodiments of the present application described and shown in the drawings herein 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 claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, every other embodiment obtained by a person skilled in the art without creative work belongs to the scope of protection of the present application.

[0020] Firstly, the application scenarios applicable to the present application are introduced. The present application can be applied to the technical field of cabinet testing.

[0021] It is found through research that the current mainstream remote cabinet testing scheme focuses on single-cabinet testing scenarios. The core architecture is based on a server, a client communication mode, and the server as a central management unit of test instructions. The server accurately issues preset test instructions to the host computer connected to the client through a communication protocol. After receiving the instructions, the host computer calls the test tool to establish a connection with the test cabinet, executes the test, and achieves the test purpose. In this process, test data, status feedback, and other information need to be frequently exchanged between the client and the server. The data generated by each interaction needs to be updated to the server database in real time to realize the whole-process monitoring and data storage of the testing process.

[0022] When the testing scenario expands to multiple cabinets, the server issues test instructions of the same test set to multiple host computer clients in batches, each client synchronously starts a test task, and feeds back the test results to the server. After receiving the data, the server needs to immediately analyze and update the corresponding records in the database, including test progress, execution status, and other information, to ensure that the tester can master the test status of each cabinet in real time.

[0023] In the multi-cabinet collaborative testing process, due to the differences in the hardware environment and software configuration of each cabinet, combined with the complexity and diversity of the test tasks, the test results will be different. Whether it is the normal test start execution, test completion phase, or sudden interruption test scenario, the interactive data of each cabinet needs to be accurately collected and the overall test task result and test report needs to be updated with each execution information as the data. However, if the interactive data is simply stored by relying on the traditional database recording method, the accuracy of the data recording will be difficult to guarantee. Since the parallel test faces the concurrent information update scenario, the sequence of updating the data in the database may cause the loss of the execution result information. In the case of a large number of parallel tests, the load of the database will also be increased.

[0024] Based on this, the embodiment of the application provides a multi-cabinet test method, device, electronic equipment and medium, by introducing a cache middleware, the problem of inaccurate data caused by concurrent reading and writing of the database in the traditional scheme is avoided, and the database pressure is reduced, and the hardware and operation and maintenance cost are reduced. Please refer to Figure 1 , Figure 1 The flowchart of the multi-cabinet test method provided by the embodiment of the application is shown in FIG. 1. Figure 1 The multi-cabinet test method provided by the embodiment of the application includes the following steps. S101, obtaining a test data set.

[0025] The test data set includes a plurality of test cases, each test case corresponds to a client, and each client is used to control a cabinet to perform a test.

[0026] Specifically, a test interface can be displayed on the server side, when a test personnel uploads a test data set on the server side interface and triggers a "run test data set" operation, the test data set can be obtained, the test data set contains a plurality of test cases, after receiving the test data set, the test cases in the test data set are first finely disassembled and distributed, the test cases are grouped into a plurality of task units according to the number and configuration of the target cabinet, each task unit corresponds to a target client, and each client is responsible for controlling a cabinet to perform a test.

[0027] S102, for each test case, the test case is distributed to the corresponding client, so that the client controls the corresponding cabinet to execute the test case to perform a test, receives the test data of the corresponding cabinet reported by the client, and updates the test data to the cache middleware corresponding to the test data set.

[0028] The test case carrying the test instruction is distributed to each corresponding client through a network communication module, at the same time, based on the information of the test set, a cache middleware is created, the cache middleware is a dedicated storage area, which is used to store all dynamic information related to the test task, for example: each client ID, execution state (initially "to be distributed"), number of test cases to be executed and data in the test process, etc., which provides unified data support for subsequent whole process monitoring.

[0029] In a preferred example of the application, the client controls the corresponding cabinet to execute the test case to perform a test in the following way, Figure 2 The flowchart of the method for controlling the cabinet to perform a test provided by the embodiment of the application includes the following steps. S201, for each client, receiving the receipt information reported by the client and indicating the successful reception of the test case, and updating the execution state of the client in the cache middleware to complete the reception.

[0030] S202, for each client, when determining that the execution state of the client in the cache middleware is more complete reception, sending a start test instruction to the client to make the client start controlling the corresponding cabinet to test, and updating the execution state of the client in the cache middleware to executing.

[0031] In a preferred example of the present application, if no receipt information reported by any client is received within a preset time, a prompt information of failure of sending is sent, all data in the cache middleware is cleaned, and the test process is terminated.

[0032] Specifically, by receiving the feedback information of the client, it is judged whether the instruction is successfully arrived, if all the clients under the corresponding test set recorded in the cache record feedback instruction sending failure, immediately return the prompt information to the server, and inform the test set sending failure, and when at least one client successfully receives and starts executing the instruction, after receiving the feedback, the test data set state recorded by itself is updated to "executing", and the initial execution information of each client in the cache is written into the database at the same time, indicating that the test execution is officially started.

[0033] Return Figure 1 S103, for each client, in the process of controlling the corresponding cabinet to test, the test progress is monitored according to the execution state of the client in the cache middleware, and when the execution state of the client is monitored to complete the test, the test data corresponding to the client in the cache middleware is packaged to generate a test report, and after the test report is uploaded successfully, all data of the client in the cache middleware is deleted.

[0034] Specifically, in the test execution process, the client will continuously poll the test task execution in the cabinet, and the execution data queried is returned to the server after being arranged and packaged, and the server updates the result information of the corresponding execution case in the cache middleware according to the data content, and when the client monitors that the test task in the cabinet has been executed, the test report generated by the test tool is obtained and sent to the server. After the server receives the test report, the execution result information of the corresponding client is updated first, then the test report file is temporarily stored in the cache, and finally the dynamic information corresponding to the client is removed from the cache.

[0035] In a preferred example of the present application, Figure 3 The flowchart for determining the test end provided by the embodiment of the present application comprises: S301, every preset monitoring time, monitoring whether there is test data of a client associated with a test data set in the cache middleware.

[0036] S302, when all test data of all clients has been deleted in the cache middleware, it is determined that the test is completed.

[0037] Specifically, as the test process advances, when all clients complete the test task, all client information related to the test set in the cache is completely cleared. At this time, the server confirms that there is no client information corresponding to the test set by querying the cache, that is, it is determined that the test execution has been completed. The server then obtains all stored test reports from the cache, packages these reports into a compressed file, and uploads them to a designated storage location. Finally, the server queries all client execution results recorded in the database, and updates the final execution result of the test set according to the preset rules.

[0038] In a preferred example of the present application, Figure 4 The flowchart of the interrupt test process provided by the embodiments of the present application includes: S401, when receiving an interrupt command for a test data set, issuing an interrupt instruction to a client in the cache middleware whose test state is executing; S402, for each client, receiving the interrupt feedback of the client, updating the execution state of the client in the cache middleware to interrupt test, and removing all test data of the client in the cache middleware; S403, when all test data corresponding to the test data set associated with the cache middleware is removed, it is determined that the interrupt process is completed.

[0039] Specifically, in the entire process, if the server starts the interrupt execution command, the processor queries the client information in the cache, sends the interrupt command to the client still existing in the cache, and collects the interrupt execution result. Similar to the normal execution process, the processor updates the interrupt result of the client and removes the cache data. When the relevant data in the cache is empty, it is considered that the interrupt is completed.

[0040] Based on the same inventive concept, the embodiments of the present application also provide a multi-cabinet test device corresponding to the multi-cabinet test method. Since the principle of solving problems in the device of the embodiments of the present application is similar to the above-mentioned multi-cabinet test method of the embodiments of the present application, the implementation of the device can be referred to the implementation of the method, and the repeated parts will not be described again.

[0041] Please refer to Figure 5 , Figure 5 The structure diagram of the multi-cabinet test device provided by the embodiments of the present application, the multi-cabinet test device 500 includes: The acquisition module 501 is configured to acquire a test data set, the test data set comprising a plurality of test cases, each test case corresponding to a client, and each client being configured to control a cabinet to perform a test.

[0042] The execution module 502 is configured to, for each test case, distribute the test case to the corresponding client, so that the client controls the corresponding cabinet to perform the test case to perform a test, receives test data of the corresponding cabinet reported by the client, and updates the test data in the cache middleware corresponding to the test data set, the cache middleware being configured to store the execution status and test data reported by each client.

[0043] The uploading module 503 is configured to, for each client, monitor a test progress according to the execution status of the client in the cache middleware during the process in which the client controls the corresponding cabinet to perform a test, and when it is monitored that the execution status of the client is complete testing, package the test data corresponding to the client in the cache middleware to generate a test report upload, and delete all data of the client in the cache middleware after the test report upload is successful.

[0044] In a preferred example of the present application, the execution module is further configured to, for each client, receive receipt information reported by the client and indicating that the test case is successfully received, and update the execution status of the client in the cache middleware to complete receiving; for each client, when it is determined that the execution status of the client in the cache middleware is more complete receiving, send a start test instruction to the client, so that the client starts to control the corresponding cabinet to perform a test, and update the execution status of the client in the cache middleware to executing.

[0045] In a preferred example of the present application, the device further comprises a monitoring module configured to, every preset monitoring time, monitor whether there is test data of the client associated with the test data set in the cache middleware; and when the test data of all clients have been deleted in the cache middleware, determine that the test is completed.

[0046] Please refer to Figure 6 , Figure 6 A structural schematic diagram of an electronic device provided by an embodiment of the present application is shown in FIG. 6. Figure 6 As shown in FIG. 6, the electronic device 600 comprises a processor 610, a memory 620 and a bus 630.

[0047] The memory 620 stores machine readable instructions executable by the processor 610, when the electronic device 600 is running, the processor 610 and the memory 620 communicate through the bus 630, the machine readable instructions are executed by the processor 610, can execute the steps of the multi-cabinet test method in the above method embodiment, for details, see the method embodiment, and will not be repeated here.

[0048] The computer readable storage medium provided in the embodiments of the present application stores a computer program, and the computer program can execute the steps of the multi-cabinet test method in the above method embodiment when the processor runs, for details, see the method embodiment, and will not be repeated here.

[0049] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, and will not be repeated here.

[0050] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other ways. The device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some communication interface, device or unit, which can be electrical, mechanical or other forms.

[0051] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0052] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0053] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a nonvolatile computer readable storage medium executable by a processor. Based on this understanding, the technical solutions of the present application essentially or the parts of the prior art that make contributions or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0054] Finally, it should be noted that: the above-described embodiments are merely specific embodiments of the present application, used to illustrate the technical solutions of the present application, and not to limit them. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can make modifications or easily think of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed by the present application, or make equivalent replacements to some of the technical features. The modifications, changes or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A multi-rack testing method, characterized in that, The method includes: Obtain a test dataset, which includes multiple test cases. Each test case corresponds to a client, and each client is used to control a cabinet for testing. For each test case, the test case is sent to the corresponding client so that the client controls the corresponding rack to execute the test case for testing. The test data of the corresponding rack reported by the client is received and the test data is updated in the cache middleware corresponding to the test dataset. The cache middleware is used to store the execution status and test data reported by each client. For each client, during the testing process of the corresponding rack controlled by the client, the test progress is monitored according to the execution status of the client in the cache middleware. When the execution status of the client is detected as completed, the test data corresponding to the client in the cache middleware is packaged to generate a test report and uploaded. After the test report is successfully uploaded, all data of the client in the cache middleware is deleted.

2. The method according to claim 1, characterized in that, The client controls the corresponding cabinet to execute the test case for testing in the following manner: For each client, receive the receipt information reported by the client indicating successful reception of the test case, and update the client's execution status in the cache middleware to complete reception; For each client, when the execution status of the client in the caching middleware is determined to be more than completed, a start test command is sent to the client so that the client can start controlling the corresponding rack to perform the test, and the execution status of the client in the caching middleware is updated to be executing.

3. The method according to claim 1, characterized in that, Also includes: Every preset monitoring time, the cache middleware is monitored to see if there is test data of the client associated with the test dataset; The test data on all clients has been deleted from the caching middleware, and the test is now complete.

4. The method according to claim 1, characterized in that, Also includes: When an interrupt command is received for the test dataset, an interrupt command is sent to the client in the cache middleware whose test status is "in execution". For each client, receive the client's interruption feedback, update the client's execution status in the cache middleware to interrupted test, and remove all test data for that client in the cache middleware; Once all test data corresponding to all clients associated with the test dataset in the caching middleware has been removed, the interruption process is considered complete.

5. The method according to claim 2, characterized in that, Also includes: If no response information is received from any client within the preset time, a failure message is sent, all data in the cache middleware is cleared, and the test process is terminated.

6. A multi-rack testing device, characterized in that, The device includes: The acquisition module is used to acquire a test dataset, which includes multiple test cases. Each test case corresponds to a client, and each client is used to control a rack for testing. The execution module is used to send each test case to the corresponding client so that the client controls the corresponding rack to execute the test case for testing. It receives the test data of the corresponding rack reported by the client and updates the test data to the cache middleware corresponding to the test dataset. The cache middleware is used to store the execution status and test data reported by each client. The upload module is used to monitor the test progress of each client during the testing process of the corresponding rack controlled by the client, based on the execution status of the client in the cache middleware. When the execution status of the client is detected as completed, the module packages the test data corresponding to the client in the cache middleware to generate a test report and uploads it. After the test report is successfully uploaded, the module deletes all data of the client in the cache middleware.

7. The apparatus according to claim 6, characterized in that, The execution module is also used for: For each client, receive the receipt information reported by the client indicating successful reception of the test case, and update the client's execution status in the cache middleware to complete reception; For each client, when the execution status of the client in the caching middleware is determined to be more than completed, a start test command is sent to the client so that the client can start controlling the corresponding rack to perform the test, and the execution status of the client in the caching middleware is updated to be executing.

8. The apparatus according to claim 6, characterized in that, The device further includes: The monitoring module is used to monitor at preset monitoring intervals whether there is test data of clients associated with the test dataset in the cache middleware; the test ends when all test data of all clients has been deleted from the cache middleware.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is in operation, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the steps of the method as described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method as described in any one of claims 1 to 5.

Images