Method and system for testing stability of terminal computing power management platform

Abstract

The invention discloses a terminal computing power management platform stability test method and system, and belongs to the technical field of computing power platform tests.The method comprises the steps that for a test object, connection is established, basic configuration is carried out, and association extraction is carried out; service arrangement, self-definition of published message test parameters and message template customization are carried out to quickly create a service pressure test script and accurately simulate access of users of different magnitudes to a service system; scene construction: dividing a test scene according to two basic dimensions of connection and message throughput, constructing a standard test scene, and rapidly simulating a complex service scene in combination with a set point, thinking time and a condition control instruction; result visualization and performance optimization are carried out, and the performance is optimized by combining service index and resource index data in a test report, so that the stable operation of the system is ensured. According to the invention, various scenes and configurations can be quickly constructed, the test difficulty is reduced, the test efficiency is improved, and the test reliability is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of computing power platform testing, and specifically to a method and system for testing the stability of a terminal computing power management platform. Background Art

[0002] With the popularization of edge computing and terminal devices, a unified terminal computing power management platform has emerged to achieve unified management and scheduling of decentralized terminal devices. The stability of the platform is a key factor in ensuring its normal operation and providing reliable services, so a comprehensive stability test is required.

[0003] The system needs to connect and communicate with a large number of devices and generate a massive amount of data. In performance stability testing, it is very important to simulate real scenarios. The key to designing test scenarios is to consider how to simulate the different behaviors of publishers and subscribers, and to analyze the test results more effectively, providing key data and support for performance optimization.

[0004] The current system stability test has the following problems:

[0005] Traditional system stability testing methods are relatively simple, the request changes are not flexible and automatic enough, and the input parameter variable settings may not meet the requirements;

[0006] Traditional system stability testing methods support limited scenarios and cannot automatically verify complex business scenarios;

[0007] Traditional system stability testing methods need to be combined with other monitoring tools to test indicator data, which is inconvenient to use and has high testing costs. Summary of the invention

[0008] The technical task of the present invention is to address the above shortcomings and provide a terminal computing power management platform stability testing method and system, which can quickly build various scenarios and configurations, reduce testing difficulty, improve testing efficiency, and ensure testing reliability.

[0009] The technical solution adopted by the present invention to solve its technical problem is:

[0010] A method for testing the stability of a terminal computing power management platform, comprising:

[0011] 1) For the test object: create a connection, perform basic configuration, and perform association extraction;

[0012] 2) Business orchestration: Customize the test parameters for publishing messages and customize message templates to quickly create business stress testing scripts and accurately simulate users of different sizes accessing the business system;

[0013] 3) Scenario construction: Divide the test scenarios according to the two basic dimensions of connection and message throughput, build standard test scenarios, and combine the collection point, thinking time and conditional control instructions to quickly simulate complex business scenarios;

[0014] 4) Result visualization: After designing the test scenario, formulate and analyze the metrics to test and evaluate whether the test is successful. The metrics include business metrics and resource metrics. During the test process, provide rich and real-time test reports and key performance indicators that testers can view at any time. The test results and performance indicators are displayed through rich statistical charts and log recording functions.

[0015] 5) Performance optimization: Combine the business indicators and resource indicator data in the test report to optimize the performance and ensure the smooth operation of the system.

[0016] The core of the stability test of the terminal computing power management platform is to detect the stability of the platform and the accuracy of the reported data by simulating the connection and data reporting process of a large number of devices. The difficulty lies in initiating and maintaining a large number of connections at the same time, and the design of QoS, payload size, and subject wildcards are also factors that affect the performance of the production environment system. In view of the above situation, this method provides business orchestration capabilities during the stability test, can dynamically set parameters, and provides standard test scenarios such as connection tests and message throughput tests. It can quickly build various scenarios and configurations, but it is not too complicated to use. At the same time, it provides sufficient business indicators and resource indicators to help us understand the performance of platform services as comprehensively as possible, reduce the difficulty of testing, improve test efficiency, and ensure the reliability of testing.

[0017] Furthermore, the test object:

[0018] Establish an MQTT connection: configure basic information, including service address, service port, MQTT version, connection timeout, protocol, signature authentication, user name, and password;

[0019] Association extraction: Extract through four forms: json, regular expression, response header, and response code; customize variable names and extract required parameters.

[0020] Further, the service orchestration,message test parameters include: QoS level, message size, and publishing rate;

[0021] Subscribe to messages, custom parameters include:

[0022] Qos Level, message level, supports 0, 1, 2;

[0023] Topic name(s), subscription topic name, supports + / # wildcard shared subscription;

[0024] Payload includes timestamp, whether the message contains a timestamp;

[0025] Sample on: specified elapsed time (ms), which counts the subscription messages in milliseconds.

[0026] Sample on: number of received messages, count the number of messages received by subscription;

[0027] Publish a message. Custom parameters include:

[0028] QoS Level, message level, supports 0, 1, 2;

[0029] Retained Mesages: whether to retain messages, supports true and false;

[0030] Topic name, topic name;

[0031] Add timestamp in payload, add a timestamp to the message;

[0032] Message type: String, you can fill in a custom string message;

[0033] Message type: Hex string, you can fill in a custom hexadecimal message;

[0034] Message type: Random string with fixed length, fixed-length random characters, where length is the specified length.

[0035] Furthermore, the scene construction includes:

[0036] Concurrent connection test scenario:

[0037] Gradually increase the number of concurrent connections at a fixed lower connection rate to test system response and resource consumption, so as to determine the maximum number of concurrent connections that the system can withstand under given hardware and network resources; at a given number of concurrent connections, test the system response and resource consumption at different connection rates, and distinguish between ordinary TCP connections and TLS / SSL encrypted connections;

[0038] Message throughput test scenario:

[0039] The three scenarios of publish-subscribe 1 to 1, 1 to many, and many to 1 are simulated respectively, among which:

[0040] 1 to 1: The number of publishers and subscribers is equal; for each publisher, there is only one subscriber subscribing to the topic it publishes, that is, the message inflow rate of the MQTT Broker is the same as the outflow rate;

[0041] Many-to-1 (reporting): A typical IoT application scenario where there are a large number of IoT devices as publishers but only a few or a single subscriber, such as a large number of devices reporting their status or data;

[0042] 1 to many: that is, broadcast mode, a small number of clients publish messages, and a large number of devices subscribe to and consume messages, such as under the instructions of the control end.

[0043] Furthermore, the business indicators, i.e. application system indicators, are related to user scenarios and requirements, including: number of MQTT connections, connection rate, connection response time, message throughput, message reception delay, success rate, etc.

[0044] The resource indicators, namely computing resource indicators, are related to hardware resource consumption, including: CPU usage, memory usage, network throughput, etc.

[0045] Furthermore, the performance optimization specifically includes:

[0046] Allocate resources properly: Allocate hardware resources properly to ensure that the server has sufficient memory, CPU, and storage space to support the expected message throughput and number of connections;

[0047] Network optimization: Optimize network connections to reduce latency and improve bandwidth utilization; technologies such as load balancing can be used to ensure that messages can be effectively transmitted between different nodes;

[0048] Message persistence and storage: For message persistence and storage, you can choose a suitable database or persistent storage system to store messages, and set a reasonable storage strategy to balance performance and data consistency requirements;

[0049] Protocol optimization: Optimize the protocol and improve the efficiency and stability of message transmission by reasonably adjusting parameters such as QoS.

[0050] Furthermore, the implementation of this method includes:

[0051] The test case recording unit is used to implement the tasks in the early design and preparation phase of the test, including requirement analysis, case design, and improvement of the interface test pool, preparation and organization of test case data, and monitoring by the client;

[0052] The middleware service unit is used to implement the specific execution phase tasks of the test, including specific request construction, interface response verification, execution logic control, execution process monitoring and optimization, and execution result analysis;

[0053] The continuous integration test unit is used to implement the tasks in the continuous integration stage, including interface assembly, automatic regression, unit test framework execution of test cases, and continuous integration platform scheduled execution of test cases.

[0054] The present invention also claims protection for a terminal computing power management platform stability testing system, including a test case recording unit, a middleware service unit and a continuous integration testing unit. The system implements the stability test of the terminal computing power management platform through the above-mentioned method.

[0055] The present invention also claims protection for a terminal computing power management platform stability testing device, comprising: at least one memory and at least one processor;

[0056] The at least one memory is used to store a machine-readable program;

[0057] The at least one processor is used to call the machine-readable program to implement the above method.

[0058] The present invention also claims protection for a computer-readable medium having computer instructions stored thereon, which can implement the above method when executed by a processor.

[0059] Compared with the prior art, the terminal computing power management platform stability testing method and system of the present invention have the following beneficial effects:

[0060] The traditional system stability testing method is relatively simple, the request changes are not flexible and automatic enough, and the input parameter variable settings do not meet the requirements. By using the business orchestration in this testing method, the QoS level, message size, publishing rate, etc. are dynamically configured to achieve customized performance testing.

[0061] Traditional system stability testing methods support limited scenarios and cannot automatically verify problems in complex business scenarios. This testing method provides flexible business orchestration capabilities, specifies execution order, and dynamically associates data to improve the accuracy of business logic testing.

[0062] As traditional system stability testing methods need to be combined with other monitoring tools to test indicator data, this testing method can automatically output statistical information to facilitate result analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 It is a diagram showing the implementation of the terminal computing power management platform stability testing method provided by an embodiment of the present invention;

[0064] Figure 2 It is a schematic diagram of the architecture of a terminal computing power management platform stability testing method provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0065] The present invention will be further described below in conjunction with specific embodiments.

[0066] The embodiment of the present invention provides a method for testing the stability of a terminal computing power management platform. Figure 1 As shown, including:

[0067] 1. Test object.

[0068] For the test object, create a connection, perform basic configuration, and perform associated extraction. The details are as follows:

[0069] Establish an MQTT connection: configure basic information, including service address, service port, MQTT version, connection timeout, protocol, signature authentication, user name, and password.

[0070] Association extraction: Extract through four forms: json, regular expression, response header, and response code; customize variable names and extract required parameters.

[0071] 2. Business orchestration.

[0072] Custom message bodies can contain dynamic variables to facilitate simulation of more complex message interaction scenarios.

[0073] Customize the message publishing test parameters, such as QoS level, message size, publishing rate, etc., and customize the message template to quickly create business stress testing scripts and accurately simulate different levels of users accessing the business system.

[0074] Specifically include:

[0075] a. Subscription message, customizable parameters:

[0076] Qos Level, message level, supports 0, 1, 2;

[0077] Topic name(s), subscription topic name, supports + / # wildcard shared subscription;

[0078] Payload includes timestamp, whether the message contains a timestamp;

[0079] Sample on: specified elapsed time (ms), which counts the subscription messages in milliseconds.

[0080] Sample on: number of received messages, count the number of messages received by subscription;

[0081] b. Publish messages, customizable parameters:

[0082] QoS Level, message level, supports 0, 1, 2;

[0083] Retained Mesages: whether to retain messages, supports true and false;

[0084] Topic name, topic name;

[0085] Add timestamp in payload, add a timestamp to the message;

[0086] Message type: String, you can fill in a custom string message;

[0087] Message type: Hex string, you can fill in a custom hexadecimal message;

[0088] Message type: Random string with fixed length, fixed-length random characters, where length is the specified length.

[0089] 3. Scene construction.

[0090] Test scenarios can be divided according to the two basic dimensions of connection and message throughput to build standard test scenarios. At the same time, combined with instructions such as collection points, thinking time and conditional control, complex business scenarios can be quickly simulated. Including:

[0091] a. Concurrent connection test scenario:

[0092] Gradually increase the number of concurrent connections at a fixed lower connection rate, test the system response and resource consumption, and determine the maximum number of concurrent connections that the system can withstand with given hardware and network resources. At a given number of concurrent connections, test the system response and resource consumption at different connection rates, and distinguish between ordinary TCP connections and TLS / SSL encrypted connections.

[0093] b. Message throughput test scenario:

[0094] Simulate the publish-subscribe 1 to 1, 1 to many, and many to 1 scenarios respectively.

[0095] 1 to 1: The number of publishers and subscribers is equal. For each publisher, there is only one subscriber subscribing to the topic it publishes, that is, the message inflow rate of the MQTT Broker is the same as the outflow rate.

[0096] Many-to-1 (reporting): A typical IoT application scenario where there are a large number of IoT devices as publishers but only a few or a single subscriber, for example, a large number of devices report their status or data.

[0097] 1 to many: that is, broadcast mode, a small number of clients publish messages, and a large number of devices subscribe to and consume messages, such as under the instructions of the control end.

[0098] 4. Visualize the results.

[0099] After designing the test scenario, formulate and analyze the metrics to test and evaluate whether the test is successful.

[0100] Metrics include business indicators and resource indicators. Business indicators, namely application system indicators, are related to user scenarios and needs, including: number of MQTT connections, connection rate, connection response time, message throughput, message reception delay, success rate, etc. Resource indicators, namely computing resource indicators, are related to hardware resource consumption, including: CPU usage, memory usage, network throughput, etc.

[0101] During the test process, it provides rich and real-time test reports and key performance indicators that testers can view at any time. It displays test results and performance indicators through rich statistical charts and log recording functions.

[0102] 5. Performance optimization.

[0103] Combine the business indicators and resource indicator data in the test report to optimize performance and ensure the smooth operation of the system. Including:

[0104] Allocate resources properly: Allocate hardware resources properly to ensure that the server has sufficient memory, CPU, and storage space to support the expected message throughput and number of connections.

[0105] Network optimization: Optimize network connections to reduce latency and improve bandwidth utilization; technologies such as load balancing can be used to ensure that messages can be effectively transmitted between different nodes.

[0106] Message persistence and storage: For message persistence and storage, you can choose a suitable database or persistent storage system to store messages, and set a reasonable storage strategy to balance performance and data consistency requirements.

[0107] Protocol optimization: Optimize the protocol and improve the efficiency and stability of message transmission by reasonably adjusting parameters such as QoS.

[0108] The technical architecture layering to implement this method includes the test case recording unit, middleware service unit, and continuous integration test unit from top to bottom. Figure 2 shown.

[0109] Test case recording unit, the pre-test design and preparation stage, including requirements analysis, case design, and improvement of the interface test pool, preparation and organization of test case data, and client monitoring;

[0110] Middleware service unit tests the specific execution phase, including specific request construction, interface response verification, execution logic control, execution process monitoring and optimization, and execution result analysis;

[0111] Continuous integration test unit, continuous integration stage, including interface assembly, automatic regression, unit test framework execution of test cases, and continuous integration platform scheduled execution of test cases.

[0112] Faced with a huge number of devices and the data they generate, applications and services are becoming increasingly complex. We must not only ensure that the system's business functions are correct, but also that the system can support continuous and stable communication between a large number of devices. Therefore, it is necessary to analyze the performance stability test data to optimize performance, effectively improve the performance and stability of the terminal computing power management platform in processing the time reporting of a large number of devices, and ensure the reliable operation of the platform. By adopting the terminal computing power management platform stability test method, repetitive work tasks in the test process can be dealt with, which can reduce testing costs, improve testing efficiency, cover more complex test scenarios, and provide higher accuracy and consistency;

[0113] An embodiment of the present invention also provides a terminal computing power management platform stability testing system, which implements the stability testing of the terminal computing power management platform through the terminal computing power management platform stability testing method described in the above embodiment.

[0114] The system includes a test case recording unit, a middleware service unit, and a continuous integration test unit.

[0115] The test case recording unit is used to implement the tasks in the early design and preparation phase of the test, including requirement analysis, case design, and improvement of the interface test pool, preparation and organization of test case data, and monitoring by the client;

[0116] The middleware service unit is used to implement the specific execution phase tasks of the test, including specific request construction, interface response verification, execution logic control, execution process monitoring and optimization, and execution result analysis;

[0117] The continuous integration test unit is used to implement the tasks in the continuous integration stage, including interface assembly, automatic regression, unit test framework execution of test cases, and continuous integration platform scheduled execution of test cases.

[0118] The system implements the stability test of the terminal computing power management platform through the following processes:

[0119] 1. Test object establishment.

[0120] For the test object, create a connection, perform basic configuration, and perform associated extraction. The details are as follows:

[0121] Establish an MQTT connection: configure basic information, including service address, service port, MQTT version, connection timeout, protocol, signature authentication, user name, and password.

[0122] Association extraction: Extract through four forms: json, regular expression, response header, and response code; customize variable names and extract required parameters.

[0123] 2. Business orchestration.

[0124] Custom message bodies can contain dynamic variables to facilitate simulation of more complex message interaction scenarios.

[0125] Customize the message publishing test parameters, such as QoS level, message size, publishing rate, etc., and customize the message template to quickly create business stress testing scripts and accurately simulate different levels of users accessing the business system.

[0126] Specifically include:

[0127] a. Subscription message, customizable parameters:

[0128] Qos Level, message level, supports 0, 1, 2;

[0129] Topic name(s), subscription topic name, supports + / # wildcard shared subscription;

[0130] Payload includes timestamp, whether the message contains a timestamp;

[0131] Sample on: specified elapsed time (ms), which counts the subscription messages in milliseconds.

[0132] Sample on: number of received messages, count the number of messages received by subscription;

[0133] b. Publish messages, customizable parameters:

[0134] QoS Level, message level, supports 0, 1, 2;

[0135] Retained Mesages: whether to retain messages, supports true and false;

[0136] Topic name, topic name;

[0137] Add timestamp in payload, add a timestamp to the message;

[0138] Message type: String, you can fill in a custom string message;

[0139] Message type: Hex string, you can fill in a custom hexadecimal message;

[0140] Message type: Random string with fixed length, fixed-length random characters, where length is the specified length.

[0141] 3. Scene construction.

[0142] Test scenarios can be divided according to the two basic dimensions of connection and message throughput to build standard test scenarios. At the same time, combined with instructions such as collection points, thinking time and conditional control, complex business scenarios can be quickly simulated. Including:

[0143] a. Concurrent connection test scenario:

[0144] Gradually increase the number of concurrent connections at a fixed lower connection rate, test the system response and resource consumption, and determine the maximum number of concurrent connections that the system can withstand with given hardware and network resources. At a given number of concurrent connections, test the system response and resource consumption at different connection rates, and distinguish between ordinary TCP connections and TLS / SSL encrypted connections.

[0145] b. Message throughput test scenario:

[0146] Simulate the publish-subscribe 1 to 1, 1 to many, and many to 1 scenarios respectively.

[0147] 1 to 1: The number of publishers and subscribers is equal. For each publisher, there is only one subscriber subscribing to the topic it publishes, that is, the message inflow rate of the MQTT Broker is the same as the outflow rate.

[0148] Many-to-1 (reporting): A typical IoT application scenario where there are a large number of IoT devices as publishers but only a few or a single subscriber, for example, a large number of devices report their status or data.

[0149] 1 to many: that is, broadcast mode, a small number of clients publish messages, and a large number of devices subscribe to and consume messages, such as under the instructions of the control end.

[0150] 4. Visualize the results.

[0151] After designing the test scenario, formulate and analyze the metrics to test and evaluate whether the test is successful.

[0152] Metrics include business indicators and resource indicators. Business indicators, namely application system indicators, are related to user scenarios and needs, including: number of MQTT connections, connection rate, connection response time, message throughput, message reception delay, success rate, etc. Resource indicators, namely computing resource indicators, are related to hardware resource consumption, including: CPU usage, memory usage, network throughput, etc.

[0153] During the test process, it provides rich and real-time test reports and key performance indicators that testers can view at any time. It displays test results and performance indicators through rich statistical charts and log recording functions.

[0154] 5. Performance optimization.

[0155] Combine the business indicators and resource indicator data in the test report to optimize performance and ensure the smooth operation of the system. Including:

[0156] Allocate resources properly: Allocate hardware resources properly to ensure that the server has sufficient memory, CPU, and storage space to support the expected message throughput and number of connections.

[0157] Network optimization: Optimize network connections to reduce latency and improve bandwidth utilization; technologies such as load balancing can be used to ensure that messages can be effectively transmitted between different nodes.

[0158] Message persistence and storage: For message persistence and storage, you can choose a suitable database or persistent storage system to store messages, and set a reasonable storage strategy to balance performance and data consistency requirements.

[0159] Protocol optimization: Optimize the protocol and improve the efficiency and stability of message transmission by reasonably adjusting parameters such as QoS.

[0160] The embodiment of the present invention also provides a terminal computing power management platform stability testing device, including: at least one memory and at least one processor;

[0161] The at least one memory is used to store a machine-readable program;

[0162] The at least one processor is used to call the machine-readable program to implement the terminal computing power management platform stability testing method described in the above embodiment.

[0163] The embodiment of the present invention also provides a computer-readable medium, on which computer instructions are stored, and when the computer instructions are executed by the processor, the terminal computing power management platform stability test method described in the above embodiment is implemented. Specifically, a system or device equipped with a storage medium can be provided, on which the software program code that implements the functions of any of the above embodiments is stored, and the computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0164] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.

[0165] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.

[0166] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.

[0167] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or the expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.

[0168] The present invention is shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the code review methods in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the protection scope of the present invention.

Claims

1. A method for testing the stability of a terminal computing power management platform, characterized in that: include: 1) For the test object: create a connection, perform basic configuration, and perform association extraction; 2) Business orchestration: Customize the test parameters for publishing messages and customize message templates to quickly create business stress testing scripts and accurately simulate users of different sizes accessing the business system; 3) Scenario construction: Divide the test scenarios according to the two basic dimensions of connection and message throughput, build standard test scenarios, and combine the collection point, thinking time and conditional control instructions to quickly simulate complex business scenarios; 4) Result visualization: After designing the test scenario, formulate and analyze the metrics to test and evaluate whether the test is successful. The metrics include business metrics and resource metrics. During the test process, it provides real-time test reports and key performance indicators, and displays test results and performance indicators through statistical charts and log recording functions; 5) Performance optimization: Combine the business indicators and resource indicator data in the test report to optimize the performance and ensure the smooth operation of the system.

2. A method for testing the stability of a terminal computing power management platform according to claim 1, characterized in that: The test object: Establish an MQTT connection: configure basic information, including service address, service port, MQTT version, connection timeout, protocol, signature authentication, user name, and password; Association extraction: Extract through four forms: json, regular expression, response header, and response code; customize variable names and extract required parameters.

3. A terminal computing power management platform stability testing method according to claim 1, characterized in that: The service arrangement and message test parameters include: QoS level, message size, and publishing rate; Subscribe to messages, custom parameters include: Qos Level, message level, supports 0, 1, 2; Topic name(s), subscription topic name, supports + / # wildcard shared subscription; Payload includes timestamp, whether the message contains a timestamp; Sample on: specified elapsed time (ms), which counts the subscription messages in milliseconds. Sample on: number of received messages, count the number of messages received by subscription; Publish a message. Custom parameters include: QoS Level, message level, supports 0, 1, 2; Retained Mesages: whether to retain messages, supports true and false; Topic name, topic name; Add timestamp in payload, add a timestamp to the message; Message type: String, you can fill in a custom string message; Message type: Hex string, you can fill in a custom hexadecimal message; Message type: Random string with fixed length, fixed-length random characters, where length is the specified length.

4. A method for testing the stability of a terminal computing power management platform according to claim 1, characterized in that: The scene construction includes: Concurrent connection test scenario: Gradually increase the number of concurrent connections at a fixed lower connection rate to test system response and resource consumption, so as to determine the maximum number of concurrent connections that the system can withstand under given hardware and network resources; at a given number of concurrent connections, test the system response and resource consumption at different connection rates, and distinguish between ordinary TCP connections and TLS / SSL encrypted connections; Message throughput test scenario: The three scenarios of publish-subscribe 1 to 1, 1 to many, and many to 1 are simulated respectively, among which: 1 to 1: The number of publishers and subscribers is equal; for each publisher, there is only one subscriber subscribing to the topic it publishes, that is, the message inflow rate of the MQTT Broker is the same as the outflow rate; Many-to-1: There are a large number of IoT devices as publishers, but only a few or a single subscriber; 1 to many: that is, broadcast mode, a small number of clients publish messages, and a large number of devices subscribe to and consume messages.

5. A terminal computing power management platform stability testing method according to claim 1, characterized in that: The business indicators, i.e. application system indicators, are related to user scenarios and requirements; including: number of MQTT connections, connection rate, connection response time, message throughput, message reception delay, and success rate; The resource indicators, namely computing resource indicators, are related to hardware resource consumption and include: CPU usage, memory usage, and network throughput.

6. A method for testing the stability of a terminal computing power management platform according to claim 1, characterized in that: The performance optimization specifically includes: Allocate resources properly: Allocate hardware resources properly to ensure that the server has sufficient memory, CPU, and storage space to support the expected message throughput and number of connections; Network optimization: Optimize network connections to reduce latency and improve bandwidth utilization; ensure that messages can be transmitted effectively between different nodes; Message persistence and storage: Choose a suitable database or persistent storage system to store messages, and set a reasonable storage strategy to balance performance and data consistency requirements; Protocol optimization: Optimize the protocol and improve the efficiency and stability of message transmission by reasonably adjusting parameters.

7. A method for testing the stability of a terminal computing power management platform according to claim 1, characterized in that: The implementation of this method includes: The test case recording unit is used to implement the tasks in the early design and preparation phase of the test, including requirement analysis, case design, and improvement of the interface test pool, preparation and organization of test case data, and monitoring by the client; The middleware service unit is used to implement the specific execution phase tasks of the test, including specific request construction, interface response verification, execution logic control, execution process monitoring and optimization, and execution result analysis; The continuous integration test unit is used to implement the tasks in the continuous integration stage, including interface assembly, automatic regression, unit test framework execution of test cases, and continuous integration platform scheduled execution of test cases.

8. A terminal computing power management platform stability testing system, characterized in that: The system comprises a test case recording unit, a middleware service unit and a continuous integration test unit. The system implements the stability test of the terminal computing power management platform through any method described in claims 1 to 7.

9. A terminal computing power management platform stability testing device, characterized in that: include: at least one memory and at least one processor; The at least one memory is used to store a machine-readable program; The at least one processor is used to call the machine-readable program to implement the method described in any one of claims 1 to 7.

10. A computer-readable medium, characterized in that The computer readable medium stores computer instructions, which, when executed by a processor, can implement the method according to any one of claims 1 to 7.

Images