CN114610597A - Pressure testing method, device, equipment and storage medium - Google Patents

Abstract

The embodiment of the application discloses a pressure testing method, a pressure testing device, equipment and a storage medium, wherein the method comprises the following steps: the server determines a test script according to script configuration parameters of the web interface; the server determines a container cluster according to container hardware configuration parameters of the web interface; the server configures the operating environment of the container cluster according to the container software configuration parameters of the web interface; the server runs the test script on the operating environment of the container cluster to complete the stress test. Therefore, a web interface is used, distributed automatic tests are integrated into a platform, multiple persons can use the platform simultaneously, and related test work is managed in a unified mode. The container technology is used, the operation of the container is transparent, so that the deployment of the tester is completely automatic, and under the condition that the container resources are enough, the large-scale clustering deployment can be realized, and the manual operation cost is reduced.

Description

Pressure testing method, device, equipment and storage medium

Technical Field

The embodiment of the application relates to the field of software testing, and relates to but is not limited to a pressure testing method, a pressure testing device, pressure testing equipment and a storage medium.

Background

In the existing distributed pressure testing method, when a testing server executes a testing task, a tester needs to upload and start a testing script to each testing machine in a manual mode, and when the number of testing machines is large, a large amount of human resources are wasted, and the labor cost is high.

Disclosure of Invention

In view of this, embodiments of the present application provide a pressure testing method, apparatus, device, and storage medium for solving at least one problem in the prior art, which at least solve the problem that the existing distributed pressure testing method requires manually uploading a test script to each testing machine and starting the script according to a certain testing scheme, which seriously affects the work efficiency of testing personnel, and has a high labor cost.

The technical scheme of the embodiment of the application is realized as follows:

in a first aspect, an embodiment of the present application provides a pressure testing method, including: the server determines a test script according to script configuration parameters of a World Wide Web (Web) interface; the server determines a container cluster according to the container hardware configuration parameters of the web interface; the server configures the operating environment of the container cluster according to the container software configuration parameters of the web interface; the server runs the test script on the operating environment of the container cluster to complete the stress test.

In a second aspect, an embodiment of the present application provides a pressure testing apparatus, including: the test management component is used for determining a test script according to script configuration parameters of the web interface; the test management component is also used for determining the pressure generator and the controller according to the container hardware configuration parameters of the web interface; the container management component is used for configuring the operating environment of the pressure generator and the operating environment of the controller according to the container software configuration parameters of the web interface; the controller controls the pressure generator to run the test script to complete the pressure test.

In a third aspect, an embodiment of the present application provides a computer device, including a memory and a processor, where the memory stores a computer program executable on the processor, and the processor implements the pressure testing method of the above method when executing the program.

In a fourth aspect, embodiments of the present application provide a computer storage medium storing executable instructions for causing a processor to implement a stress testing method of the above method when executed.

The embodiment of the application provides a pressure test method, a pressure test device, pressure test equipment and a pressure test storage medium, wherein all parameters required by pressure test configuration come from a web interface, a test script is determined according to script configuration parameters, a container cluster is determined according to container hardware configuration parameters, the operating environment of the container cluster is configured according to container software configuration parameters, and finally the test script is operated on the operating environment of the container cluster to complete the pressure test. Therefore, a web interface is used, distributed automatic tests are integrated into a platform, multiple persons can use the platform simultaneously, and related test work is managed in a unified mode. The container technology is used, the operation of the container is transparent, the deployment of the testing machine is fully automated, and the large-scale clustering deployment can be realized under the condition that the container resources are enough, so that the pressure test can be automatically carried out even under the condition that the testing machines are more, the human resources are saved, and the labor cost is reduced.

Drawings

Fig. 1 is a schematic flow chart illustrating an implementation of a pressure testing method according to an embodiment of the present disclosure;

FIG. 2A is a schematic view of a pressure testing assembly according to an embodiment of the present disclosure;

fig. 2B is a schematic flow chart illustrating an implementation of a pressure testing method according to an embodiment of the present disclosure;

fig. 3 is a schematic flow chart illustrating an implementation of a pressure testing method according to an embodiment of the present disclosure;

fig. 4 is a schematic flow chart illustrating an implementation of a pressure testing method according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a pressure testing apparatus provided in an embodiment of the present application;

fig. 6 is a hardware entity diagram of a computer device according to an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

It should be understood that some of the embodiments described herein are only for explaining the technical solutions of the present application, and are not intended to limit the technical scope of the present application.

Before the system is applied to online, pressure testing is needed, and an actual scene is simulated to find out performance bottlenecks. The pressure test is used for testing the performance, reliability, stability and the like of the tested system by simulating the software and hardware environment of practical application and the system load of a user in the using process and running the test software for a long time or in an ultra-heavy load manner.

Currently, there are many methods for performing pressure testing on a system, and there are two methods that are mainly implemented by using a pressure testing tool (such as loadrunner, JMeter, grind, Locust, etc.) and by programming. The resource of a single test server is limited, and the concurrency peak value required by testing some complex systems cannot be met, so that a plurality of test servers need to be considered to be cooperated to form enough concurrency pressure, a distributed pressure test method needs to be adopted, the pressure for simulating real service generated by a test server cluster is used for pressurizing a tested system, the performance of the tested system under different pressure conditions is analyzed, and the potential bottleneck of the tested system is found out.

In the distributed pressure testing method in the prior art, when the testing server executes a testing task, a testing script needs to be manually uploaded to each testing machine and started according to a certain testing scheme, so that the working efficiency of testing personnel is seriously influenced. And moreover, the test machines are difficult to uniformly manage, and resources are easy to idle. And the CI/CD tool is difficult to access, and unattended and continuous inheritance cannot be achieved.

As shown in fig. 1, the pressure testing method provided in the embodiment of the present application includes:

s101, a server determines a test script according to script configuration parameters of a web interface;

the web is also called world wide web, is a distributed graphic information system which is based on HyperText Transfer Protocol (HTTP), global, dynamic interactive and cross-platform, is a network service established on the Internet, provides a graphical and easily-accessed visual interface for a browser to search and browse information on the Internet, and documents and hyperlinks therein organize information nodes on the Internet into a mutually-associated mesh structure. The web interface refers to a software interface which can be seen under a browser, script configuration parameters are input into the web interface, and the server determines a test script according to the script configuration parameters. The script configuration parameters comprise test names and test sets, wherein the test names are determined by testers according to specific test requirements, the test sets are a set of a series of test cases, the test cases required to be included can be set in the test sets, and the execution sequence of the test cases can be adjusted in the test sets. A test case can be understood as a test step, so that a test set is a specific test scenario and is a series of ordered test steps.

Here, the tester can upload the script configuration parameters through a web interface provided by a test starting program on the server, and the server performs the stress test according to the received script configuration parameters.

Step S102, the server determines a container cluster according to container hardware configuration parameters of the web interface;

the container cluster comprises a plurality of containers, the containers are all in a sandbox mechanism, and no interface exists among the containers. The container may also be referred to herein as a container example. The container instance is a completely independent and isolated environment and does not conflict with the environment of the operating system, and a physical machine or a virtual machine (an operating system) can start a plurality of completely identical container instances at the same time and the containers are mutually independent. In this way, the running test is not concerned about how many physical machines need to be prepared, but only how many container instances are started. Each container instance contains all the software and dependencies needed to run the test and can be considered as an independent node.

Containers can be created using the Docker container technology, which can be understood as an ultra-lightweight virtual machine, which is encapsulated on the basis of linux containers. The difference between Docker and traditional virtualization is that the container is virtualized on the os level, and directly multiplexes the os of the local host, whereas traditional virtualization is implemented on the hardware level. Because the container does not need to perform hardware virtualization, run the complete operating system and other additional expenses, the Docker has higher utilization rate of system resources. The method is more efficient than the traditional virtual machine technology in terms of application execution speed, memory loss or file storage speed. Therefore, a host with the same configuration can often run a larger number of applications than virtual machine technology. The traditional virtual machine technology starts application services, which usually need several minutes because a complete operating system needs to be started, and the Docker container application runs in a host kernel without starting the complete operating system, so that the starting can be carried out in a second level or even a millisecond level. The development, test and deployment time is greatly saved. Compared with the traditional virtualization method, the Docker has the advantages of high starting speed, high resource utilization rate and low performance overhead.

The container hardware configuration parameters comprise the number of nodes, the concurrency amount of the pressure test and the node configuration parameters. Here, the number of nodes is the number of network nodes such as workstations, servers, terminal devices, and network devices in the network. A node is a computer or other device connected to a network having an independent address and having the function of transmitting or receiving data. The nodes may be workstations, clients, network users or personal computers, servers, printers and other network-connected devices. Each workstation, the server, the terminal equipment and the network equipment, namely equipment with own unique network address, are all nodes; the concurrency is an important index of performance test, and refers to how many users simultaneously request the server interface of the tested system. The higher the concurrency supported by the system to be tested is, the better the performance of the system to be tested is; the node configuration parameters include Central Processing Unit (CPU) parameters, memory parameters, and the like, that is, starting parameters of the container, for example, 1 CPU is allocated to 1 container, and 4G memory is allocated to 1 container, so that 20 containers are hardware occupation amounts of 20 CPUs and 80G memory in total.

And configuring the container hardware configuration parameters at the web interface, and determining the container cluster according to the container hardware configuration parameters by the server.

Step S103, the server configures the running environment of the container cluster according to the container software configuration parameters of the web interface;

here, the running environment of the container cluster, that is, the running environment of the pressure generator and the running environment of the controller, may be configured according to the container software configuration parameters, by configuring the container software configuration parameters at the web interface, using files such as programs, libraries, resources, configurations, and some configuration parameters (e.g., environment variables, users, etc.) prepared for the running.

And step S104, the server runs the test script on the running environment of the container cluster to complete the pressure test.

In the embodiment of the application, all parameters required by the pressure test are from a web interface, a test script is determined according to script configuration parameters, a container cluster is determined according to container hardware configuration parameters, the operating environment of the container cluster is configured according to container software configuration parameters, and finally the test script is operated on the operating environment of the container cluster to complete the pressure test. Therefore, a web interface is used, distributed automatic tests are integrated into a platform, multiple persons can use the platform simultaneously, and related test work is managed in a unified mode. The container technology is used, the operation of the container is transparent, the deployment of the testing machine is fully automated, and the large-scale clustering deployment can be realized under the condition that the container resources are enough, so that the pressure test can be automatically carried out even under the condition that the testing machines are more, the human resources are saved, and the labor cost is reduced.

Fig. 2A is a schematic view of a pressure testing assembly according to an embodiment of the present application, as shown in fig. 2A, the schematic view includes: a web module 201 including an external interface component 2011, a test case management 2012, a test set management component 2013, a test management component 2014, a container management component 2015 and a test result component 2016; a back-end (back-end)202 including a test script generation 2021 and a test engine 2022; a vessel cluster 203 comprising a pressure generator 2031 and a controller 2032; a storage medium 204 comprising a non-relational database 2041 and a relational database 2042, wherein:

external interface component 2011 (external Hook/API): and the user realizes the alarm functions such as mail prompt and the like by self-defining the Hook script. Threshold configuration for multiple indexes is provided, and Hook is triggered once data of a certain index exceeds a threshold value in a stress test process. The Hook function is called a Hook function, before the system does not call the function, the Hook program captures the message, the Hook function obtains control right first, and the Hook function can process (change) the execution behavior of the function and can also forcibly end the transfer of the message.

Meanwhile, the system also provides an external Application Programming Interface (API) access continuous integration, a CI/CD tool drive, a pressure test triggered and started by an HTTP request, and a request body carries a parameter Interface of the test; and sending an HTTP request after the pressure test is executed, wherein the request body carries the summary result of the test.

The test case management component 2012 is configured to receive parameters input by the web interface, including a tested host address, a tested interface Uniform Resource Locator (URL), a request mode, a request header, a request parameter, and a request body, and provide functions of adding, deleting, editing, and querying for a test case.

The test set management component 2013 is used for providing a management function for the test set through parameters input on the web interface, creating and deleting the test set, and compiling test cases contained in the test set. And when the test is operated, the link level pressure test is carried out according to the test case compiling sequence in the test set. Here, the test set is a set of a series of test cases, and the test cases that need to be included may be set in the test set, and the sequence of executing the test cases may be adjusted. If a test case is understood as a test step, the test set is a specific test scenario and is a series of ordered test steps. In performance/stress testing, a common test case is to test an interface. In real-life service use, one service often includes calls of a plurality of interfaces, and due to the barrel effect, the whole performance of the service is affected by the bottleneck of any one interface. The link requests a series of related interfaces one by one according to the interface calling sequence of the actual service, and the test set containing a plurality of ordered test cases can realize the performance/pressure test of the link type.

The test management component 2014 is configured to start the distributed pressure test according to parameters, such as the test name, the project, the concurrency, the number of nodes, the node hardware configuration and the like, input on the web interface, generate a Universal Unique Identifier (UUID) of a Unique Identifier belonging to the test, and drive the test engine component 2022 to perform the test. Meanwhile, the component also provides management functions of tests based on different projects, including screening of test sets, checking of relevant test details and the like.

The container management component 2015, which is a Docker management component, is configured on the Web side. The configuration for receiving web interface input manages the container. Connecting the clusters by configuring cluster addresses of the remote Docker servers; an upload container file (Dockerfile) or a designated container image (Docker image) containing Python, locust and corresponding dependency libraries may be used as a controller or a pressure generator when the container is started. Here, Locust is a python-based performance testing tool, and has the advantages of being simple to learn, completely self-customized in function, flexible to use, and supporting distribution.

After the Docker is started, a container instance is generated, and software and dependent libraries required by the runtime of python and locusts predefined in the Docker file or Docker image are automatically installed in the container. The container instance is a completely independent and isolated environment and does not conflict with the environment of the operating system, and a physical machine or a virtual machine (an operating system) can start a plurality of completely identical container instances at the same time, and the containers are mutually independent. In this way, it is no longer necessary to pay attention to how many physical machines need to be prepared, but only how many container instances are started when running the test. Each container instance contains all the software and dependencies needed to run the test and can be considered as an independent node.

A test results component 2016 for obtaining test results from the relational database 2042 and the non-relational database 2041. Here, the test result includes two parts, wherein the first part is performance data of the current pressure test, and the concrete representation on the web interface is a curve formed by connecting data of a certain index at a series of time points in a certain pressure test; the second part is when the results of the pressure tests are summarized, and the concrete representation on the web interface is the summarized numerical value for a plurality of indexes presented in a certain pressure test, and the results of the transverse comparison of the same test set in a certain number of pressure tests.

The test engine component 2022 is used for starting a test driver, calling the Docker management component, starting a container as a controller and a corresponding number of containers as pressure generators, and acquiring ip addresses of the dockers; calling a test script generating component to generate a test script and transmitting the test script to the controller; then, running a pressure test, starting a main coordinating stroke of the controller, and waiting for the pressure generator to be on line at a monitoring port; and then sending the ip address of the controller to the pressure generator and starting the main protocol process of the pressure generator, and then starting a plurality of sub protocol processes according to the concurrency quantity and generating pressure after connecting the controller. Here, Coroutines (Coroutines) are a lighter weight existence than threads, just as a process may have multiple threads, a thread may have multiple Coroutines.

The test script generating component 2021 is configured to automatically generate a test script that can be identified by the test tool after starting the test through a preset template and a selected test set, communicate with the controller through a paramiko library in a Secure Shell (SSH) manner, transmit the test script to the controller of the test tool, and analyze the test script into a test instruction by the controller and issue the test instruction to the plurality of pressure generators through an HTTP protocol. Here, paramiko is a device based on secure shell protocol for connecting to a remote server and performing related operations, and may perform commands or file operations on the remote server. The test cases run when Locust executes the stress test are python files, so the test cases need to be written by using python grammar, the python files have fixed structures and writing rules, and the predefined templates are used for abstracting the structures and the rules. In order to reduce the use difficulty, a test executor is not required to write a python file, and the python file which can be identified by Locust is generated on the spot according to the template and is sent to Locust for testing.

The core function of the pressure generator 2031 is provided by a slave component of locust written by Python, which plays a role of a consumer, is only communicated with the controller, and is responsible for receiving a test instruction, generating a plurality of coroutines according to the instruction (the operation efficiency of multithreading is not ideal because of the limitation of GIL global lock of Python, so the locust uses a get coroutine library, replaces threads by a coroutine technology), initiates a network request, receives a response, analyzes and reports a request result.

The controller 2032, whose core function is provided by the master component of locust written by Python, serves as the producer role in the producer-consumer model, and is responsible for communicating with the pressure generator nodes, issuing test instructions, monitoring node status, collecting and summarizing the request results of each node, and recording the test results. The controller carries out accumulated statistics after acquiring a request result sent by the pressure generator, and writes the request result into Influxdb as performance data at intervals; after the test is finished, the pressure generator is automatically turned off, the controller 2032 integrates the test result, reports the test result to the test engine 2022 and then automatically turns off, and the test engine 2022 writes the summary result into MySQL.

A non-relational database 2041 for storing the tested performance data, for example, the tested performance data is stored in the inflixdb database.

The relational database 2042 is used for data management and test result summarization of components such as a test set, a test case, and a Docker, for example, summarize and store test results in a MySQL database;

after the test is finished, the container cluster 203 is destroyed and a corresponding test report is generated in the web module 201. The Web module 201 reads the non-relational 2041 and draws a performance curve aiming at a certain index at a proper time; the web module 201 reads the relational database 2042 to generate a test report pertaining to the pressure test.

In an embodiment of the present application, the server includes a test management component and a container management component, the container cluster includes a pressure generator and a controller, and as shown in fig. 2B, the method includes:

step S201, the test management component determines a test script according to script configuration parameters of the web interface;

as shown in FIG. 2A, a test management component 2014 determines test scripts based on the test names, items and test sets that are typed in the web interface. Meanwhile, the test management component 2014 also provides management functions of tests based on different projects, including screening of test sets, checking of relevant test details and the like.

Step S202, the test management component determines the pressure generator and the controller according to the container hardware configuration parameters of the web interface;

as shown in fig. 2A, the test management component 2014 is further configured to determine the pressure generator and the controller according to the parameters of the test item, the concurrency amount, the number of nodes, the hardware configuration of the nodes, and the like, input on the web interface.

Step S203, the container management component configures the operating environment of the pressure generator and the operating environment of the controller according to the container software configuration parameters of the web interface;

taking the Docker container technology as an example, as shown in fig. 2A, the container management component, that is, the Docker management component, is configured to receive the container software configuration parameters input by the web interface, and configure the operating environment of the pressure generator and the operating environment of the controller. Connecting the clusters by configuring cluster addresses of the remote Docker servers; the upload Dockerfile or the designated Docker image contains Python, locusts and corresponding dependent libraries, and when the container is started, the container can be used as a controller or a pressure generator.

And step S204, the controller controls the pressure generator to run the test script so as to complete the pressure test.

As shown in fig. 2A, the controller 2032 controls the pressure generator 2031 to run a test script to complete the pressure test.

In the embodiment of the application, the server comprises a test management component and a container management component, the container cluster comprises a pressure generator and a controller, the test management component determines a test script according to script configuration parameters of a web interface, the test management component determines the pressure generator and the controller according to container hardware configuration parameters of the web interface, the container management component configures the running environment of the pressure generator and the running environment of the controller according to container software configuration parameters of the web interface, and the controller controls the pressure generator to run the test script to complete the pressure test. Therefore, the server is divided into different assemblies according to the functions which cannot be achieved, the containers of the container cluster are divided into the pressure generator and the controller, and the pressure test can be efficiently and automatically completed through cooperation and labor division among the assemblies.

In the pressure testing method provided in the embodiment of the present application, the server further includes a script generation component, the script configuration parameters include a test name and a test set, the server further includes a test engine component, the container hardware configuration parameters include a node number, a concurrency amount of the pressure test and a node configuration parameter, the container configuration parameters include a container file or a container mirror image, as shown in fig. 3, the method includes:

step S301, the test management component determines a test identifier according to the test name;

as shown in FIG. 2A, a test management component 2014 determines test scripts based on the test names, items and test sets that are typed in the web interface. The test name may generate a Universally Unique Identifier (UUID) belonging to the test, that is, a test Identifier.

Step S302, the test management component sends the test identification and the test set to the script generation component so as to enable the script generation component to generate a test script according to the test identification and the test set and a preset template, wherein the preset template is a template for converting the test set into a test script running on the container cluster;

when the test script generating component 2021 is used, as shown in fig. 2A, after a test is started, a test script that can be identified by a test tool can be automatically generated through a preset template and a selected test set, and the test script is communicated with a controller through a paramiko library in a secure shell protocol manner, transmitted to the controller of the test tool, and analyzed into a test instruction by the controller and issued to a plurality of pressure generators through an HTTP protocol. Here, paramiko is a device based on secure shell protocol for connecting to a remote server and performing related operations, and can perform commands or file operations on the remote server. The test cases run when Locust executes the stress test are python files, so the test cases need to be written by using python grammar, the python files have fixed structures and writing rules, and the predefined templates are used for abstracting the structures and the rules. In order to reduce the use difficulty, a test executor is not required to write a python file, and the python file which can be identified by Locust is generated on the spot according to the template and is sent to Locust for testing.

Step S303, the test management component sends the node number and the concurrency amount of the pressure test to the test engine component, so that the test engine component determines the number of the pressure generators according to the node number and determines the concurrency amount of each pressure generator according to the concurrency amount of the pressure test and the number of the pressure generators;

taking the Docker container technology as an example, as shown in fig. 2A, the test engine component 2022 is used to start the post-test driver component, call the Docker management component, start a container as a controller and a corresponding number of containers as pressure generators, and obtain the ip addresses of the dockers. The test engine component 2022 can determine the number of pressure generators based on the number of nodes and determine the amount of concurrency for each of the pressure generators based on the amount of concurrency for the pressure tests and the number of pressure generators. The test script generated by the test script generating component 2021 can be called to transmit to the controller; then, running a pressure test, starting a main coordinating stroke of the controller, and waiting for the pressure generator to be on line at a monitoring port; and then sending the ip address of the controller to the pressure generator and starting the main protocol process of the pressure generator, and then starting a plurality of sub protocol processes according to the concurrency of each pressure generator and generating pressure after connecting the controller.

Step S304, the test management component configures the pressure generator and the controller according to the node configuration parameters;

here, the node configuration parameters include Central Processing Unit (CPU) parameters, memory parameters, and the like, which are start parameters of the containers, for example, 1 CPU is allocated to 1 container, and 4G memory is allocated to 1 container, so that the total of 20 containers is the hardware occupation amount of 20 CPUs and 80G memory. A test management component configures the pressure generator and the controller according to the node configuration parameters.

Step S305, under the condition that the container software configuration parameter is a container file, the container management component creates the container mirror image according to the container file;

the most common way to create an image in a container is to use a container file. The container file is a description of a container image that can be understood as the step A, B, C, D … of rocket launching. The container file contains a piece of instruction inside, each piece of instruction constructs a layer, and therefore the content of each piece of instruction describes how the layer should be constructed. The container mirror can be set in a manner of creating/uploading/editing the container file, pulling/locally pushing from the container repository. In the case where the container configuration parameter is a container file, the container management component may create the container image from the container file.

Step S306, the container management component configures the operating environment of the pressure generator and the operating environment of the controller according to the container mirror image;

the container mirror is a special file system, which provides files of programs, libraries, resources, configuration, etc. required by the container runtime, and also contains some configuration parameters (such as environment variables, users, etc.) prepared for the runtime. The image does not contain any dynamic data, nor does its content be changed after construction. The container mirror image provides a complete running environment, and ensures the consistency of the application running environment. Uploading a container file or specifying a container image containing Python, locust and the corresponding dependency library, and when the container is started, the container can be used as a controller or pressure generator. After the container is started, an instance of the container is generated, and software and dependent libraries required by the predefined python and log runtime in the container file or container image, namely the runtime environment of the pressure generator and the runtime environment of the controller, are automatically installed in the container.

Step S307, under the condition that the container software configuration parameters are container mirror images, the container manager configures the operating environment of the pressure generator and the operating environment of the controller according to the container mirror images;

in the case that the container configuration parameter is a container file, the operating environment of the pressure generator and the operating environment of the controller can be directly configured according to the container image.

And S308, controlling the pressure generator to run the test script by the controller so as to complete the pressure test.

In the embodiment of the application, the test management component sends the test identifier and the test set to the script generation component, so that the script generation component generates the test script according to the test identifier and the test set and a preset template. Therefore, the using difficulty can be reduced, a test executor is not required to write a python file, and the python file which can be identified by Locust is generated on the spot according to the template and is sent to Locust for testing. And configuring the operating environment of the pressure generator and the operating environment of the controller according to the container file or the container mirror image. Thus, the container operation environment is provided more efficiently, and the consistency of the container application operation environment is ensured.

In an embodiment of the present application, a pressure testing method is provided, where a server includes a test management component, a container management component, a test case management component, a test set management component, a non-relational database component, a test result component, and an external interface component, where a container cluster includes a pressure generator and a controller, as shown in fig. 4, and the method includes:

step S401, the test management component manages the test cases according to case management parameters of the web interface so as to realize addition, deletion, editing and query of the test cases;

as shown in fig. 2A, the test case management component 2012 is configured to receive parameters input by the web interface, including a tested host address, a tested interface uniform resource locator, a request manner, a request header, request parameters, and a request body, and provide functions of adding, deleting, editing, and querying for a test case.

Step S402, the test set management component manages the test set according to the test set management parameters of the web interface so as to create and delete the test set, wherein the test set consists of one or more test cases;

as shown in fig. 2A, the testset management component 2013 is configured to provide a management function for a testset through parameters input in a web interface, create and delete the testset, and compile one or more test cases included in the testset. And when the test is operated, the link level pressure test is carried out according to the test case compiling sequence in the test set. Here, the test set is a set of a series of test cases, and the test cases that need to be included may be set in the test set, and the sequence of executing the test cases may be adjusted. If a test case is understood as a test step, the test set is a specific test scenario and is a series of ordered test steps. In the prior art, in a performance or pressure test, one test case is to test one interface. In real-life service use, one service often includes calls of a plurality of interfaces, and due to the barrel effect, the whole performance of the service is affected by the bottleneck of any one interface. The link requests a series of related interfaces one by one according to the interface calling sequence of the actual service, and then the test set containing a plurality of ordered test cases can realize the performance/pressure test of the link type.

Step S403, the test management component determines a test script according to the script configuration parameters of the web interface;

step S404, the test management component determines the pressure generator and the controller according to the container hardware configuration parameters of the web interface;

step S405, the container management component configures the operating environment of the pressure generator and the operating environment of the controller according to the container software configuration parameters of the web interface;

step S406, the controller controls the pressure generator to run the test script so as to complete the pressure test;

step S407, recording the performance data of the pressure test in real time by the non-relational database component;

as shown in fig. 2A, the non-relational database 2041 is used to store the performance data of the test, for example, the performance data of the test is stored in the inflixdb database. The non-relational database can inquire and store time sequence data with high performance, wherein each record is attached with a time stamp which can be accurate to nanosecond. The main application scenario is that the sequence data is generated (performance test data), and the historical trend, the periodic rule and the abnormality of the sequence data need to be displayed, and the summary, induction and prediction analysis are carried out on the basis of the sequence data. Here, because performance testing produces a large amount of time-series related test data and the time intervals are very short (milliseconds or even microseconds), the non-relational database 2041 needs to be used to record the performance data.

Step S408, the relational database component records the summary result of each pressure test;

as shown in fig. 2A, the relational database 2042 is used for data management of components such as a test set, a test case, and a Docker, and summarize the test results, for example, the summarize test results are stored in a MySQL database.

Step S409, the test result component reads the performance data and draws a curve on the web interface in real time;

as shown in fig. 2A, a test results component 2016 reads performance data and plots the data in real time on a web interface. For example, reading the performance data of the current pressure test, and connecting the data of a series of time points according to a certain index to form a performance curve. The horizontal axis of the performance curve is a time sequence, the vertical axis of the performance curve is the number of the performance indexes, and the change trend of the performance indexes in a certain time period and whether a certain time point is abnormal (through a preset threshold value) can be conveniently checked through the performance curve. Therefore, the performance inflection point and the bottleneck of the tested system are analyzed.

S410, the test result component reads the summary result and displays the summary result on the web interface according to the test identification;

as shown in fig. 2A, the test result component 2016 is configured to read the summary result and display the summary result on the web interface according to the test identifier. For example, on a web interface are summary values for several metrics presented in a certain stress test, and results of lateral comparisons of the same test set in certain stress tests.

Step S411, the external interface component outputs the performance data and the summary result to the outside so as to output an alarm identifier under the condition that the performance data is abnormal and/or the summary result is abnormal; alternatively, the first and second electrodes may be,

as shown in fig. 2A, the external interface assembly 2011 includes an external Hook. And the user realizes the alarm functions such as mail prompt and the like by self-defining the Hook script. Threshold configuration for multiple indexes is provided, and Hook is triggered once data of a certain index exceeds a threshold value in a stress test process. The Hook function is called a Hook function, before the system does not call the function, the Hook program captures the message, the Hook function obtains control right first, and the Hook function can process (change) the execution behavior of the function and can also forcibly end the transfer of the message.

Step S412, the external interface component accesses the performance data and the summary result to continuous integration or continuous delivery;

as shown in fig. 2A, the external interface component 2011 also provides external API access to CI/CD tool drivers, including HTTP request triggering to start pressure test, and the requesting entity carries a parameter interface of the test; and sending an HTTP request after the pressure test is executed, wherein the request body carries the summary result of the test.

In the embodiment of the application, the test case component is used for managing the test cases, the test set component is used for managing the test sets, the relational database and the non-relational database are used for storing the test results, the stored test results are displayed on a web interface by using the test result component, and the external interface component can realize the alarm functions of mail prompting and the like and access the test results to continuous integration or continuous delivery. Therefore, the test case management component and the test set management component are used in the pressure test, so that the test efficiency can be effectively improved, the non-relational database is used for storing real-time data and drawing a performance curve on a web interface, and the change trend of the performance index in a certain time period and whether a certain time point is abnormal (passes through a preset threshold value) can be conveniently checked. Therefore, the performance inflection point and the bottleneck of the tested system are analyzed. And the API is provided for continuous integration of external systems such as Jenkins and the like, and is driven by a CI/CD tool to access a continuous integration process. Unified configuration management of the web website is achieved, the whole process is automatic, and agile testing is achieved.

Based on the foregoing embodiments, the present application provides a pressure testing apparatus, which includes components and devices, and can be implemented by a processor in a computer device; of course, the implementation can also be realized through a specific logic circuit; in implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.

Fig. 5 is a schematic structural diagram of a pressure testing apparatus provided in an embodiment of the present application, and as shown in fig. 5, the apparatus 500 includes a test management component 2014, a container management component 2015, a pressure generator 2031, and a controller 2032, where:

the test management component 2014 is used for determining a test script according to script configuration parameters of the web interface; the controller is also used for determining the pressure generator and the controller according to the container hardware configuration parameters of the web interface;

a container management component 2015 to configure an operating environment of the pressure generator and an operating environment of the controller according to container software configuration parameters of the web interface;

the controller 2032 controls the pressure generator 2031 to run the test script to complete the pressure test.

In some embodiments, the apparatus further includes a test engine component, the container hardware configuration parameters include a number of nodes, a concurrency amount of the stress test, and a node configuration parameter, and the test management component 2014 is further configured to send the number of nodes and the concurrency amount of the stress test to the test engine component, so as to enable the test engine component to determine the number of the stress generators according to the number of nodes and determine the concurrency amount of each stress generator according to the number of the stress test and the number of the stress generators; the test management component 2014 is further configured to configure the pressure generator and the controller according to the node configuration parameters

In some embodiments, the container configuration parameter includes a container file or a container image, and in the case that the container configuration parameter is a container file, the container management component 2015 is configured to create the container image according to the container file, and further configured to configure an operating environment of the pressure generator and an operating environment of the controller according to the container image; in a case that the container configuration parameter is a container mirror image, the container manager 2015 is configured to configure an operating environment of the pressure generator and an operating environment of the controller according to the container mirror image.

In some embodiments, the apparatus further includes a test case management component and a test set management component, where the test management component is configured to manage the test cases according to the case management parameters of the web interface, so as to add, delete, edit, and query the test cases; and the test set management component is used for managing the test set according to the test set management parameters of the web interface so as to realize the creation and deletion of the test set, wherein the test set consists of the test cases.

In some embodiments, the apparatus further comprises a non-relational database component, a relational database component, and a test result component, wherein the non-relational database component is configured to record performance data of the stress test in real time; the relational database component is used for recording the summary result of each pressure test; the test result component is used for reading the performance data and drawing a curve on the web interface in real time; and the test result component is used for reading the summary result and displaying the summary result on the web interface according to the test identifier.

In some embodiments, the apparatus further includes an external interface component, configured to output the performance data and the summary result externally, so as to output an alarm identifier when the performance data and/or the summary result is abnormal; or for accessing the performance data and the aggregated results into a continuous integration or a continuous delivery.

The above description of the apparatus embodiments, similar to the above description of the method embodiments, has similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.

It should be noted that, in the embodiment of the present application, if the pressure testing method is implemented in the form of a software functional module and sold or used as a standalone product, the pressure testing method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing an electronic device (which may be a server, a desktop computer, or the like) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.

Correspondingly, the present application provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in the pressure testing method provided in the above embodiments.

Correspondingly, an embodiment of the present application provides a computer device, fig. 6 is a schematic diagram of a hardware entity of the computer device in the embodiment of the present application, and as shown in fig. 6, the hardware entity of the device 600 includes: comprising a memory 601 and a processor 602, said memory 601 storing a computer program operable on the processor 602, said processor 602 implementing the steps in the pressure testing method provided in the above embodiments when executing said program.

The Memory 601 is configured to store instructions and applications executable by the processor 602, and may also cache data to be processed or already processed by the processor 602 and modules in the computer device 600 (e.g., image data, audio data, voice communication data, and video communication data), and may be implemented by a FLASH Memory (FLASH) or a Random Access Memory (RAM).

Here, it should be noted that: the above description of the storage medium and device embodiments is similar to the description of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as a removable Memory device, a Read Only Memory (ROM), a magnetic disk, or an optical disk.

Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or a part contributing to the related art may be embodied in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a server, a desktop computer, etc.) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.

The methods disclosed in the several method embodiments provided in the present application may be combined arbitrarily without conflict to obtain new method embodiments.

Features disclosed in several of the product embodiments provided in the present application may be combined in any combination to yield new product embodiments without conflict.

The features disclosed in the several method or apparatus embodiments provided in the present application may be combined arbitrarily, without conflict, to arrive at new method embodiments or apparatus embodiments.

The above description is only for the embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method of pressure testing, the method comprising:

the server determines a test script according to script configuration parameters of the web interface;

the server determines a container cluster according to container hardware configuration parameters of the web interface;

the server configures the operating environment of the container cluster according to the container software configuration parameters of the web interface;

the server runs the test script on the operating environment of the container cluster to complete the stress test.

2. The method of claim 1, wherein the server comprises a test management component and a script generation component; and the script configuration parameters comprise a test name and a test set; then the user can use the device to make a visual display,

the server determines a test script according to script configuration parameters of the web interface, and the method comprises the following steps:

the test management component determines a test identifier according to the test name;

and the test management component sends the test identification and the test set to the script generation component so as to enable the script generation component to generate a test script according to the test identification and the test set and a preset template, wherein the preset template is a template for converting the test set into the test script running on the container cluster.

3. The method of claim 2, wherein the server further comprises a test engine component; the container cluster comprises a pressure generator and a controller, and the container hardware configuration parameters comprise the number of nodes, the concurrency amount of the pressure test and the node configuration parameters; then the user can use the device to make a visual display,

the server determines a container cluster according to the container hardware configuration parameters of the web interface, and the method comprises the following steps:

the test management component sends the node number and the concurrency amount of the pressure test to the test engine component so as to enable the test engine component to determine the number of the pressure generators according to the node number and determine the concurrency amount of each pressure generator according to the concurrency amount of the pressure test and the number of the pressure generators;

the test management component configures the pressure generator and the controller according to the node configuration parameters.

4. The method of claim 3, wherein the server further comprises a container management component; then the process of the first step is carried out,

the server configures the operating environment of the container cluster according to the container software configuration parameters of the web interface, and the method comprises the following steps:

under the condition that the container software configuration parameters are container files, a container management component in the server creates container images according to the container files, and configures the operating environment of the pressure generator and the operating environment of the controller according to the created container images;

and under the condition that the container software configuration parameters are container images, the container management component configures the operating environment of the pressure generator and the operating environment of the controller according to the container images.

5. The method of any of claims 1 to 4, wherein the server further comprises a testcase management component and a testset management component, the method further comprising:

the test management component manages the test cases according to the case management parameters of the web interface so as to realize addition, deletion, editing and/or query of the test cases; and (c) a second step of,

and the test set management component manages the test set according to the test set management parameters of the web interface so as to realize the creation and/or deletion of the test set, wherein the test set consists of one or more test cases.

6. The method of any of claims 1 to 4, wherein the server further comprises a non-relational database component, a relational database component, and a test results component, the method further comprising:

the non-relational database component records the performance data of the pressure test in real time;

the relational database component records the summary result of each pressure test;

the test result component reads the performance data and draws a curve on the web interface in real time;

and the test result component reads the summary result and displays the summary result on the web interface according to the test identifier.

7. The method of claim 6, wherein the server further comprises an external interface component, the method further comprising:

the external interface component outputs the performance data and the summary result to the outside so as to output an alarm identifier under the condition that the performance data is abnormal and/or the summary result is abnormal; alternatively, the first and second electrodes may be,

and the external interface component accesses the performance data and the summary result into continuous integration or continuous delivery.

8. A pressure testing device, comprising:

the test management component is used for determining a test script according to script configuration parameters of the web interface;

the test management component is also used for determining the pressure generator and the controller according to the container hardware configuration parameters of the web interface;

the container management component is used for configuring the operating environment of the pressure generator and the operating environment of the controller according to the container software configuration parameters of the web interface;

the controller controls the pressure generator to run the test script to complete the pressure test.

9. A computer device comprising a memory and a processor, the memory storing a computer program operable on the processor, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the program.

10. A storage medium having stored thereon executable instructions for causing a processor to perform the steps of the method of any one of claims 1 to 7 when executed.

Images