Automatic system performance test method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to an automatic system performance testing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: acquiring a gateway log of a to-be-tested system, and analyzing the gateway log to obtain a plurality of to-be-tested interfaces and corresponding interface information; for any to-be-tested interface, if a test case corresponding to the test interface exists, obtaining the test case, otherwise, based on the interface information of the to-be-tested interface, developing the test case corresponding to the to-be-tested interface; setting test parameters for the test case, and testing the plurality of to-be-tested interfaces based on the test case with the set test parameters to obtain a test result; and generating a summary report and a detailed report based on the test result. By adopting the method, the problems of low business model accuracy, insufficient interface coverage rate and long test configuration and result analysis time consumption in a traditional manual mode can be solved.

Description

Technical Field

[0001] This application relates to the field of system testing technology, and in particular to an automated system performance testing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] The rapid development of internet technology and the widespread adoption of mobile devices and cloud computing have placed higher demands on application responsiveness, stability, and scalability. Performance directly impacts enterprise costs, user experience, and brand value. Poor performance leads to increased investment in hardware or cloud services and can cause slow page loading, system crashes, and ultimately affect user retention and enterprise revenue. In industries such as finance and healthcare, meeting performance standards is a core prerequisite for complying with regulatory requirements. Performance testing, as a crucial aspect of software quality assurance, is highly dependent on the rationality of the business model.

[0003] In existing technologies, the manual method of building business models and test models has significant drawbacks, among which the problem of low accuracy of business models is particularly prominent: manual analysis can only count the transaction volume within a specific time period, and cannot accurately capture the specific query per second (QPS) of each interface within all time periods, resulting in a deviation between the built business model and the real business load in the production environment. Summary of the Invention

[0004] Therefore, it is necessary to provide an automated system performance testing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can automatically and efficiently configure test task parameters and efficiently analyze test results, addressing the aforementioned technical problems.

[0005] Firstly, this application provides an automated system performance testing method, including:

[0006] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0007] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0008] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0009] Based on the test results, a summary report and a detailed report are generated.

[0010] In one embodiment, the interface information includes the query rate per second. Based on the interface information of the interface to be tested, test cases are developed for the interface to be tested, including:

[0011] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0012] In one embodiment, setting test parameters for test cases includes:

[0013] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0014] In one embodiment, the method further includes:

[0015] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0016] In one embodiment, based on the test results, a summary report and a detailed report are generated, including:

[0017] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0018] In one embodiment, the process of determining the first preset value includes:

[0019] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0020] Secondly, this application also provides an automated system performance testing device, comprising:

[0021] The acquisition module is used to acquire the gateway logs of the system under test, parse the gateway logs, and obtain multiple interfaces to be tested and their corresponding interface information.

[0022] The development module is used to obtain test cases for any interface to be tested if test cases exist; otherwise, it develops test cases for the interface to be tested based on the interface information.

[0023] The testing module is used to set test parameters for test cases, and then test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results.

[0024] The generation module is used to generate summary reports and detailed reports based on the test results.

[0025] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0026] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0027] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0028] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0029] Based on the test results, a summary report and a detailed report are generated.

[0030] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0031] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0032] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0033] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0034] Based on the test results, a summary report and a detailed report are generated.

[0035] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0036] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0037] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0038] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0039] Based on the test results, a summary report and a detailed report are generated.

[0040] The aforementioned automated system performance testing method, apparatus, computer equipment, computer-readable storage medium, and computer program product first acquire the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information; then, for any interface to be tested, if a test case exists, the test case is acquired; otherwise, based on the interface information of the interface to be tested, a test case corresponding to the interface to be tested is developed; next, test parameters are set for the test cases, and multiple interfaces to be tested are tested based on the test cases with set test parameters to obtain test results; finally, based on the test results, a summary report and a detailed report are generated. This application achieves end-to-end intelligent performance testing through automated end-to-end processing (from gateway log parsing, test case matching and development, test parameter configuration to test report generation), which can solve the problems of low accuracy of business models, insufficient interface coverage, and long time consumption of test configuration and result analysis in the traditional manual mode, ensuring that the performance testing scenario is highly consistent with the production environment, significantly improving testing efficiency and reliability, and providing effective protection for the stable operation of the system in critical scenarios such as high concurrency. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a flowchart illustrating an automated system performance testing method in one embodiment;

[0043] Figure 2 A detailed flowchart of an automated system performance testing method in one embodiment;

[0044] Figure 3 This is a structural block diagram of the flowchart apparatus in one embodiment;

[0045] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0048] In one embodiment, such as Figure 1 As shown, an automated system performance testing method is provided. This embodiment illustrates the method applied to a terminal, but it is understood that the method can also be applied to a server, and to a system including both a terminal and a server, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0049] Step 102: Obtain the gateway log of the system under test, parse the gateway log to obtain multiple interfaces to be tested and their corresponding interface information.

[0050] The system under test is a software application with a distributed microservice architecture as its core, providing multiple interface services and carrying actual business traffic. Gateway logs are the complete interface interaction data recorded by the gateway component of the system under test, including unique identifiers for each interface (such as interface name and URL path), request timestamps, request parameters (including data type and value range), response status (success / failure indicators and response codes), response time, and call source. Parsing the gateway logs includes structured processing (converting unstructured logs into analyzable field formats) and invalid data filtering (removing duplicate requests, incorrectly formatted requests, and requests from the test environment). Ultimately, a list of all interfaces actually called by the system under test in the production environment is extracted, forming basic attributes for each interface (such as function description, input / output specifications, and call frequency characteristics) and historical interaction data (such as request volume distribution over different time periods and maximum query rate per second).

[0051] Step 104: For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the interface to be tested based on the interface information of the interface to be tested.

[0052] Test cases are scripted programs used to verify the performance of the interface under test. They include interface call logic (such as request methods and parameter assembly rules), performance monitoring metrics (such as response time thresholds and error rate tolerance ranges), and execution configurations (such as request sending frequency control). The basis for determining "the existence of a corresponding test case" is the "interface-test case binding relationship" stored in the test case management module. That is, the test script that has been developed and debugged is matched by the unique identifier of the interface (such as the interface ID). If no corresponding test case exists, test cases are developed based on the interface information of the interface under test. Specifically, this includes: extracting the request parameter format, response data structure, and call dependencies of the interface from the parsing results (such as whether a token returned by the preceding interface is required), generating a request template that conforms to the interface interaction specification; setting the baseline pressure parameters of the script (such as the initial concurrency and request duration) by combining the historical QPS data of the interface (obtained from the gateway log parsing); verifying the effectiveness of the script by simulating normal requests and abnormal requests (such as missing parameters and timeout scenarios), and finally forming an automated script that can be directly used for performance testing. After binding it with the interface under test, the script is stored in the test case library.

[0053] Step 106: Set test parameters for the test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results.

[0054] The test parameters include global and local parameters: global parameters apply to all test cases, including the QPS amplification factor (controlling the test load intensity, default value is 1, i.e., applying pressure as a multiple of the actual business peak), concurrent users (calculated by default as 30% of the corresponding interface's baseline QPS), test runtime (default 10 minutes), QPS assertion threshold (default set to 95% of the interface's baseline QPS), and success rate assertion threshold (default 99.9%). Local parameters are set individually for each test case (e.g., the success rate threshold for core interfaces can be increased to 99.99%), and have higher priority than global parameters. The testing process for multiple interfaces to be tested is as follows: the test task management module reads the configuration parameters, sorts the execution order according to the interface call dependency relationship (e.g., executes the login interface test case first), calls the test engine to initiate pressure requests to each interface that conform to the parameter configuration, and collects performance data such as actual QPS, response time distribution, request success rate, and error details in real time to form test results. When generating the report, the summary report automatically filters out test cases that fail assertions (such as actual QPS below the threshold or success rate not meeting the standard), and presents the failed interfaces and reasons in a list format; the detailed report includes performance indicator trend charts for each test case (such as QPS change curve over time), response time quantile statistics, and specific logs of failed requests (including timestamps, parameters, and error codes), providing a complete basis for problem localization.

[0055] Step 108: Based on the test results, generate a summary report and a detailed report.

[0056] Optionally, the summary report shows the results of failures, while the detailed report contains all results.

[0057] The aforementioned automated system performance testing method first obtains the gateway logs of the system under test, parses them to obtain multiple interfaces to be tested and their corresponding interface information; then, for any interface to be tested, if a test case exists, the test case is obtained; otherwise, based on the interface information, a test case is developed for the interface to be tested; next, test parameters are set for the test cases, and the multiple interfaces to be tested are tested based on the test cases with set test parameters to obtain test results; finally, a summary report and a detailed report are generated based on the test results. This application achieves end-to-end intelligent performance testing through automated end-to-end processing (from gateway log parsing, test case matching and development, test parameter configuration to test report generation), which can solve the problems of low accuracy of business models, insufficient interface coverage, and long time consumption of test configuration and result analysis in the traditional manual mode, ensuring that the performance testing scenario is highly consistent with the production environment, significantly improving testing efficiency and reliability, and providing effective protection for the stable operation of the system in critical scenarios such as high concurrency.

[0058] In one exemplary embodiment, the interface information includes the query rate per second. Based on the interface information of the interface to be tested, test cases corresponding to the interface to be tested are developed, including:

[0059] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0060] For example, suppose that after parsing the gateway logs of a financial payment system, the query per second (QPS) of three interfaces to be tested are: "Transfer Interface" 1500 times / second, "Balance Inquiry Interface" 900 times / second, and "Bill Push Interface" 300 times / second. The system automatically sorts them based on the QPS values ​​as follows: Transfer Interface (1500) > Balance Inquiry Interface (900) > Bill Push Interface (300). Testers develop test cases based on this sorting result: First, for the "Transfer Interface", combined with its interface information (such as request parameters needing to include transfer amount and account information, and the response needing to return transaction status), test cases that can simulate a load of 1500 QPS are developed, focusing on covering transaction consistency verification under high concurrency; after completion, test cases for the "Balance Inquiry Interface" are developed to adapt to query requests of 900 QPS, focusing on whether the response time is stable within 50ms; finally, test cases for the "Bill Push Interface" are developed to verify the message push success rate under 300 QPS.

[0061] In this embodiment, by sorting interfaces by queries per second (QPS) and prioritizing the development of test cases for high-QPS interfaces, a precise match between test resources and business priorities is achieved.

[0062] In one exemplary embodiment, setting test parameters for test cases includes:

[0063] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0064] For example, suppose an e-commerce system, after parsing the gateway logs, obtains the historical maximum QPS of 2000 times / second for the "product search interface," 1200 times / second for the "add to cart interface," and 800 times / second for the "submit order interface." Based on this interface information, the system automatically generates global and local configuration information: In the global configuration information, the query rate coefficient per second is set to 1 by default (applying 1 times the historical peak pressure), the number of concurrent users is calculated as 30% of the maximum QPS of each interface (600 users for the product search interface, 360 users for the add to cart interface, and 240 users for the submit order interface), the default runtime is 10 minutes, the query rate threshold per second is set to 95% of the maximum QPS of each interface (1900 for the product search interface, 1140 for the add to cart interface, and 760 for the submit order interface), and the number of requests is automatically calculated as "QPS × runtime (600 seconds)" (1.2 million for the product search interface, 720,000 for the add to cart interface, and 480,000 for the submit order interface). The local configuration information is adjusted separately for the "Submit Order Interface" (core transaction interface): the success rate threshold in its local parameters is increased from the global default of 99.9% to 99.99%, and an independent response time threshold (≤100ms) is set. The remaining parameters inherit the global configuration.

[0065] In this embodiment, global and local configuration information is automatically generated based on the actual load information of the interface (historical maximum QPS), which realizes the accurate and differentiated configuration of test parameters and solves the problems of parameters being out of touch with actual business and insufficient coverage of special requirements of core interfaces in traditional manual configuration.

[0066] In one exemplary embodiment, the method further includes:

[0067] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0068] For example, an online education platform plans to conduct performance testing before the start of the new semester, simulating a high-load scenario of concentrated student logins and course queries. Testers operate through the platform's configuration interface: in the global settings, based on historical back-to-school traffic characteristics, they set the query rate per second coefficient to 2 (i.e., applying twice the daily peak load), uniformly adjusted the number of concurrent users to 50% of the maximum QPS for each interface (higher than the default 30%, to simulate concentrated access pressure), set the runtime to 60 minutes (covering the morning peak login period), and set the query rate per second threshold to 90% of the maximum QPS (appropriately relaxing the standard to observe the ultimate capacity). These settings generate global configuration information and are applied to all test cases (such as the "user login interface," "course list query interface," and "video playback interface"). For local configuration operations, testers focused on the core interface "User Login Interface" (which directly affects students' enrollment experience), and increased its success rate threshold from the global default of 99.9% to 99.99% in the local configuration, and added a local rule "trigger an alarm if three consecutive requests time out"; while the "Course Comment Interface" (a non-core function) kept its local parameters consistent with the global configuration.

[0069] In this embodiment, the operation mode of global unified control and local precise optimization can ensure that the test scenario of the whole system fits the overall traffic characteristics of the school season, and can strengthen the performance requirements of the core interface through local configuration. This avoids the problem of insufficient core function test accuracy caused by one-size-fits-all configuration, and makes the test parameters more in line with the actual business risk management needs.

[0070] In one exemplary embodiment, based on the test results, a summary report and a detailed report are generated, including:

[0071] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0072] For example, after a food delivery platform completes peak-hour performance testing, the system automatically generates a report. First, it defines a first preset value (QPS threshold) and a second preset value (success rate threshold): the global QPS threshold is uniformly set at 95% of the historical maximum QPS for each interface, and the global success rate threshold is 99.9%. The system iterates through the test results of all test cases and finds that the actual QPS of the "Order Submission Interface" is 1800 times / second (lower than the first preset value of 1900), and the actual success rate of the "Payment Callback Interface" is 99.7% (lower than the second preset value of 99.9%). These two test cases are judged to have failed the test. The remaining test cases, such as the "Product Browsing Interface" and "User Address Modification Interface," all meet both preset values ​​and are considered passed.

[0073] In this embodiment, by clearly defining dual core judgment criteria (QPS threshold + success rate threshold) to filter out test cases that fail, and generating summary reports and detailed reports respectively, it is possible to achieve a hierarchical presentation of test results. The summary report focuses on core issues, allowing testers to quickly locate non-compliant interfaces and reduce the cost of filtering invalid information.

[0074] In an exemplary embodiment, the process of determining the first preset value includes:

[0075] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0076] Optionally, the first preset value is different for each interface.

[0077] For example, an e-commerce platform needs to determine the first preset value (QPS threshold) for the product details interface: First, obtain the maximum QPS of the interface in the past 30 days (preset time period) as 2000 times / second; assuming that the query rate coefficient set during the test is 1.2 (i.e., applying pressure at 1.2 times the production peak), then the test query rate = 2000 × 1.2 = 2400 times / second; if the first percentage coefficient is 90% (meaning that the actual QPS during the test is allowed to be no less than 90% of the test target), then the first preset value = 2400 × 90% = 2160 times / second.

[0078] In this embodiment, a first preset value is set to determine whether the test passes. This takes into account the pressure of business growth (coefficient 1.2) and sets a reasonable tolerance range (90%), making the threshold more in line with actual testing needs.

[0079] In one embodiment, such as Figure 2As shown, an automated system performance testing method is provided, including: acquiring gateway logs of the system under test, parsing the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information. The interface information includes the query rate per second. For any interface to be tested, if a test case exists, the test case is acquired; otherwise, the interfaces to be tested are sorted based on their query rate per second. Test cases are developed sequentially for each sorted interface. Test cases are developed based on the interface information of the interfaces to be tested. Global and local configuration information are automatically generated based on the interface information of multiple interfaces to be tested. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are set in the test cases; these parameters are all global parameters. Local parameters of the target test cases are set based on the local configuration information. Multiple interfaces to be tested are then tested using the test cases with the set test parameters to obtain the test results. Test cases whose actual query rate per second is lower than a first preset value, or whose request success rate is lower than a second preset value, are designated as failed test cases. A summary report is generated based on the test results of the failed test cases. A detailed report is generated based on the test results of all test cases. The process of determining the first preset value includes: obtaining the maximum query rate per second for all interfaces under test within a preset time period; multiplying the maximum query rate per second by a query rate per second coefficient to determine the test query rate per second for the interface under test; and multiplying the test query rate per second by a first percentage coefficient to obtain the first preset value.

[0080] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0081] In one exemplary embodiment, such as Figure 3As shown, an automated system performance testing device is provided, comprising: an acquisition module 301, a development module 302, a testing module 303, and a generation module 304, wherein:

[0082] The acquisition module is used to acquire the gateway logs of the system under test, parse the gateway logs, and obtain multiple interfaces to be tested and their corresponding interface information.

[0083] The development module is used to obtain test cases for any interface to be tested if test cases exist; otherwise, it develops test cases for the interface to be tested based on the interface information.

[0084] The testing module is used to set test parameters for test cases, and then test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results.

[0085] The generation module is used to generate summary reports and detailed reports based on the test results.

[0086] In one embodiment, the interface information includes queries per second, development modules, and is also used for:

[0087] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0088] In one embodiment, the testing module is further configured to:

[0089] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0090] In one embodiment, the testing module is further configured to:

[0091] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0092] In one embodiment, the generation module is further configured to:

[0093] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0094] In one embodiment, the generation module is further configured to:

[0095] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0096] Each module in the aforementioned automated system performance testing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0097] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 4 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an automated system performance testing method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0098] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0099] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0100] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0101] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0102] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0103] Based on the test results, a summary report and a detailed report are generated.

[0104] In one embodiment, the interface information includes a query rate per second, and the processor, when executing the computer program, also performs the following steps:

[0105] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0106] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0107] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0108] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0109] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0110] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0111] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0112] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0113] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0114] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0115] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0116] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0117] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0118] Based on the test results, a summary report and a detailed report are generated.

[0119] In one embodiment, the interface information includes a query rate per second, and the computer program, when executed by a processor, also performs the following steps:

[0120] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0121] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0122] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0123] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0124] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0125] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0126] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0127] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0128] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0129] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0130] Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information;

[0131] For any interface to be tested, if there are test cases corresponding to the test interface, then obtain the test cases; otherwise, develop test cases corresponding to the test interface based on the interface information of the interface to be tested.

[0132] Set test parameters for test cases, and test multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results;

[0133] Based on the test results, a summary report and a detailed report are generated.

[0134] In one embodiment, the interface information includes a query rate per second, and the computer program, when executed by a processor, also performs the following steps:

[0135] Based on the query rate per second of each interface to be tested, the interfaces to be tested are sorted; test cases are developed for each interface in the order of the sorted interfaces.

[0136] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0137] Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated in the test cases are set. The query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0138] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0139] In response to the global and local configuration operations performed by staff, global and local configuration information is generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold in the test cases are set. The query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, the local parameters of the target test cases are set.

[0140] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0141] Test cases whose actual query rate per second is lower than the first preset value or whose request success rate is lower than the second preset value are designated as failed test cases; a summary report is generated based on the test results of the failed test cases; and a detailed report is generated based on the test results of all test cases.

[0142] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0143] Obtain the maximum query rate per second for all interfaces to be tested within a preset time period. Multiply the maximum query rate per second by the query rate per second coefficient to determine the test query rate per second for the interface to be tested. Multiply the test query rate per second by the first percentage coefficient to obtain the first preset value.

[0144] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0145] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0146] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An automated system performance testing method, characterized in that, The method includes: Obtain the gateway logs of the system under test, parse the gateway logs to obtain multiple interfaces to be tested and their corresponding interface information; For any interface to be tested, if a test case exists for the interface, then the test case is obtained; otherwise, based on the interface information of the interface to be tested, a test case corresponding to the interface to be tested is developed. Set test parameters for the test cases, and test the multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results; Based on the test results, a summary report and a detailed report are generated.

2. The method according to claim 1, characterized in that, The interface information includes the query rate per second. The development of test cases corresponding to the interface to be tested, based on the interface information, includes: The interfaces to be tested are sorted based on their query rate per second. Develop test cases for each interface in the sorted order of the interfaces to be tested.

3. The method according to claim 1, characterized in that, Setting test parameters for the test cases includes: Based on the interface information corresponding to multiple interfaces to be tested, global configuration information and local configuration information are automatically generated. Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are set in the test case; the query rate per second coefficient, concurrent users, runtime, query rate per second threshold, and number of requests initiated are all global parameters; Based on the local configuration information, set the local parameters of the target test case.

4. The method according to claim 3, characterized in that, The method further includes: Responding to global settings and local configuration operations by staff, generate global configuration information and local configuration information; Based on the global configuration information, the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are set in the test case; the query rate per second coefficient, concurrent users, runtime, and query rate per second threshold are all global parameters. Based on the local configuration information, set the local parameters of the target test case.

5. The method according to claim 1, characterized in that, Based on the test results, a summary report and a detailed report are generated, including: Test cases whose test results show that the actual query rate per second is lower than the first preset value, or the request success rate is lower than the second preset value, are considered as failed test cases. A summary report is generated based on the test results of the failed test cases; A detailed report is generated based on the test results of all test cases.

6. The method according to claim 5, characterized in that, The process of determining the first preset value includes: Obtain the maximum query rate per second for all interfaces to be tested within a preset time period, multiply the maximum query rate per second by a query rate per second coefficient to determine the test query rate per second for the interface to be tested, and multiply the test query rate per second by a first percentage coefficient to obtain a first preset value.

7. An automated system performance testing device, characterized in that, The device includes: The acquisition module is used to acquire the gateway logs of the system under test, parse the gateway logs, and obtain multiple interfaces to be tested and their corresponding interface information. The development module is used to, for any interface to be tested, if a test case exists for the interface to be tested, obtain the test case; otherwise, based on the interface information of the interface to be tested, develop the test case corresponding to the interface to be tested. The testing module is used to set test parameters for the test cases, and to test the multiple interfaces to be tested based on the test cases with the set test parameters to obtain test results; The generation module is used to generate summary reports and detailed reports based on the test results.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images