CN115129577A - Pressure testing system and method, storage medium and electronic equipment - Google Patents

Pressure testing system and method, storage medium and electronic equipment Download PDF

Info

Publication number
CN115129577A
CN115129577A CN202110321331.5A CN202110321331A CN115129577A CN 115129577 A CN115129577 A CN 115129577A CN 202110321331 A CN202110321331 A CN 202110321331A CN 115129577 A CN115129577 A CN 115129577A
Authority
CN
China
Prior art keywords
test
piling
service
parameter
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110321331.5A
Other languages
Chinese (zh)
Inventor
赵嘉铎
邢淇翔
任莉强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Wodong Tianjun Information Technology Co Ltd
Priority to CN202110321331.5A priority Critical patent/CN115129577A/en
Publication of CN115129577A publication Critical patent/CN115129577A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)

Abstract

The invention discloses a pressure test system, a pressure test method, a storage medium and electronic equipment, wherein the pressure test system comprises: the configuration analyzer is used for receiving the test configuration file and analyzing the test configuration file to obtain test process information; the parameter generator is used for reading a parameter generation strategy in the test process information and generating a test parameter based on the parameter generation strategy; the test behavior configurator is used for initializing the test behavior based on the test behavior information and the test parameters; and the test executor is used for initializing based on the test execution information and the multiplexed test behaviors, executing a test task on the multiplexed test behaviors based on the test execution information, and outputting a test result. And a pressure test code is not required to be written, the difficulty and the workload of the pressure test are reduced, and the pressure test process is simplified.

Description

Pressure testing system and method, storage medium and electronic equipment
Technical Field
The embodiment of the invention relates to the technical field of pressure testing, in particular to a pressure testing system, a pressure testing method, a storage medium and electronic equipment.
Background
With the continuous development of computer technology, more services are included in each application program, and more interface protocols are adopted in each application program. Currently, there are many well-established stress testing tools.
However, in the process of implementing the present invention, the inventors found that at least the following technical problems exist in the prior art: the current pressure testing tool needs to write related testing codes by an operating user, is difficult for operators who are not familiar with the codes, and increases the workload for performing additional coding for testing.
Disclosure of Invention
The embodiment of the invention provides a pressure test system, a pressure test method, a storage medium and electronic equipment, which are used for realizing pressure test without coding.
In a first aspect, an embodiment of the present invention provides a pressure testing system, including:
the configuration analyzer is used for receiving the test configuration file and analyzing the test configuration file to obtain test process information;
the parameter generator is used for reading a parameter generation strategy in the test process information and generating a test parameter based on the parameter generation strategy;
the test behavior configurator is connected with the parameter generator and used for reading the test behavior information in the test process information, multiplexing the test parameters generated by the parameter generator and initializing the test behavior based on the test behavior information and the test parameters;
and the test executor is connected with the test behavior configurator and used for reading test execution information in the test process information, multiplexing the test behaviors of the test behavior configurator, initializing based on the test execution information and the multiplexed test behaviors, executing a test task on the multiplexed test behaviors based on the test execution information and outputting a test result.
In a second aspect, an embodiment of the present invention further provides a pressure testing method, including:
receiving a test configuration file based on a configuration analyzer, and analyzing the test configuration file to obtain test process information;
reading a parameter generation strategy in the test process information based on a parameter generator, and generating a test parameter based on the parameter generation strategy;
reading test behavior information in the test process information based on a test behavior configurator, multiplexing test parameters generated by the parameter generator, and initializing test behaviors based on the test behavior information and the test parameters;
reading test execution information in the test process information based on a test executor, multiplexing the test behavior of the test behavior configurator, initializing based on the test execution information and the multiplexed test behavior, executing a test task to the multiplexed test behavior based on the test execution information, and outputting a test result.
In a third aspect, an embodiment of the present invention further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the pressure testing method according to any embodiment of the present invention.
In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the pressure testing method according to any embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, the configuration file is set and comprises the test process information required in the pressure test process of the target object, the configuration analyzer analyzes the configuration file to obtain the test process information, the parameter generator, the test behavior configurator and the test actuator are initialized based on the analyzed test process information to obtain the pressure test system for performing the pressure test on the target object, the target object is subjected to the pressure test to obtain the test result, the pressure test code does not need to be compiled, the difficulty and the workload of the pressure test are reduced, and the pressure test process is simplified.
Drawings
Fig. 1 is a schematic structural diagram of a pressure testing system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a pressure testing system according to a second embodiment of the present invention;
FIG. 3 is a schematic structural diagram of another pressure testing system provided in the second embodiment of the present invention;
fig. 4 is a schematic flow chart of a pressure testing method according to a third embodiment of the present invention;
FIG. 5 is a schematic flow chart of another pressure testing method provided in the third embodiment of the present invention;
fig. 6 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic structural diagram of a pressure testing system according to an embodiment of the present invention, where the apparatus includes:
a configuration analyzer 110, configured to receive the test configuration file and analyze the test configuration file to obtain test process information;
the parameter generator 120 is configured to read a parameter generation policy in the test process information, and generate a test parameter based on the parameter generation policy;
a test behavior configurator 130, connected to the parameter generator, for reading the test behavior information in the test process information, multiplexing the test parameters generated by the parameter generator, and initializing the test behavior based on the test behavior information and the test parameters;
and the test executor 140 is connected with the test behavior configurator, and is configured to read test execution information in the test process information, multiplex the test behavior of the test behavior configurator, initialize based on the test execution information and the multiplexed test behavior, execute a test task on the multiplexed test behavior based on the test execution information, and output a test result.
In this embodiment, the configuration parser 110 receives a configuration file input from the outside, where the configuration file may be directly imported, may be formed by writing in a code format, or may be generated by a configuration information acquisition page, where the configuration information acquisition page may be an information input control including an information identifier to be input and information corresponding to each identifier, acquires test process information input by a user to test a target test object through the information input control, converts the acquired test process information into a configuration file in a preset format, and the configuration file is used for performing a pressure test on the target object. The target object may be one or more services in the application program, and for example, the target object may include, but is not limited to, a payment service, a contract service, and the like in the application level.
The configuration file can be named based on the target object, so that the query and management of the configuration file based on the target object are facilitated. The configuration file can be edited for the second time, and is convenient to update according to the pressure test requirement of the target object. By maintaining the configuration files of the target objects, the configuration files can be called during pressure testing, the target objects are subjected to pressure testing, pressure testing codes do not need to be written, the difficulty and the workload of the pressure testing are reduced, and the pressure testing process is simplified.
The configuration parser 110 parses the received configuration file to obtain each test procedure information in the configuration file, where the test procedure information may include information required for performing a stress test on the target object at different stages.
The parameter generator 120, the test behavior configurator 130, and the test executor 140 may monitor the test process information analyzed by the configuration analyzer 110 after the configuration analyzer 110 is started, and perform information configuration based on the monitored test process information, that is, perform initialization, and have a function of performing a stress test on a target object through initialization.
The test procedure information is set according to the test requirement of the target object, and may include, but is not limited to, a stress test mode, a parameter generation policy, a test behavior, an execution mode of the test behavior, and the like of the target object.
According to the technical scheme, the configuration file is set and comprises the test process information required in the target object pressure test process, the configuration analyzer analyzes the configuration file to obtain the test process information, the parameter generator, the test behavior configurator and the test actuator are initialized based on the analyzed test process information to obtain the pressure test system for performing pressure test on the target object, the target object is subjected to pressure test to obtain the test result, a pressure test code does not need to be written, the difficulty and the workload of the pressure test are reduced, and the pressure test process is simplified.
The parameter generator 120 is connected to the configuration parser 110, and configured to read a parameter generation policy in the test procedure information, and generate a test parameter based on the parameter generation policy, in this embodiment, the test parameter generated by the parameter generator 120 may be a parameter value in a pressure test request, where the parameter value in the pressure test request may be determined according to a requirement of a pressure test, for example, in a pressure test based on a communication method of a thrift interface, the parameter value of the pressure test request may be a parameter value of the thrift interface, in a pressure test based on JMS (Java Message Service) and a kafka communication method, the parameter value of the pressure test request may be a Message body of a Message partition, and in a pressure test based on a redis communication method, the parameter value of the pressure test request may be a key value pair in redis.
The parameter value in the pressure test request may be composed of at least one basic parameter value, and correspondingly, a parameter generation policy is configured in the test process information according to the requirements of the different parameter values, where the parameter generation policy includes a preset type of parameter value and a parameter object. Wherein the parameter values of the preset type are basic parameter values, such as but not limited to fixed or random character strings, positive numbers, floating point numbers, boolean and date types. The parameter object is composed of at least one level of basic parameter values, and illustratively, the parameter object may include a plurality of child node parameters, and any child node parameter may include a next level of child node parameters. The parameter object in the parameter generation policy may be a parameter type (e.g., a base parameter value or a parameter object) including nodes of each level, and a parameter attribute (a data type of the base parameter value).
The parameter generator 120 includes a simple parameter generator and a complex parameter generator, wherein the simple parameter generator is configured to generate a parameter value of a corresponding type based on the type of the parameter value; the complex parameter generator is for multiplexing at least one simple parameter generator and/or at least one complex parameter generator for generating a parameter object. By setting the parameter generator, the corresponding parameters can be automatically generated by setting the parameter generation strategy without manual configuration of a user, the parameter setting efficiency is improved, meanwhile, the relation among different parameters is not required to be set in the encoding process, the difficulty of parameter setting is reduced, and the probability of failure of pressure test caused by parameter setting errors is reduced.
And the test behavior configurator 130 is respectively connected with the configuration parser 110 and the parameter generator 120, and is configured to read the test behavior information in the test process information and multiplex the test parameters generated by the parameter generator, and initialize the test behavior based on the test behavior information and the test parameters.
The test behavior information may include, but is not limited to, an interface type used in the stress test, a set interface attribute, and the like, and different test behaviors correspond to different test behavior information. The test behavior configurator 130 is initialized by the read test behavior information and the test parameters generated by the multiplexing parameter generator, so as to configure the test behaviors.
In this embodiment, the test behavior configurator includes a test behavior configuration unit of a plurality of protocols. Each test behavior configuration unit may be configured for different test behaviors, wherein the test behavior configuration unit may be, but is not limited to, a thrift configuration unit, a JMS configuration unit, a kafka configuration unit, and a redis configuration unit. Correspondingly, for the test behavior of the thrift interface, the test behavior information may include an IP address of the tested thrift service, a port number of the tested thrift service, a fully-defined Java class name of an RPC client call interface generated by the thrift, and a method name in the RPC interface to be tested; for a JMS test behavior or a kafka test behavior, the test behavior information may be a generation policy including a provider vendor providing the message and a message body; for the redis test behavior, the test behavior information may include a address of a redis server to which the test data is to be written, a port number of the redis server to which the test data is to be written, and write the redis test data, etc.
In some embodiments, the configuration file may include test behavior information including one or more test behaviors for testing the plurality of test behaviors. Optionally, the test behavior configurator further includes an extension interface, and a new test behavior configuration unit may be added through the extension interface, so as to improve compatibility and applicability of the pressure test.
And the test executor 140 is connected to the configuration parser 110 and the test behavior configurator 130, respectively, and is configured to read test execution information in the test process information and multiplex the test behavior of the test behavior configurator, initialize based on the test execution information and the multiplexed test behavior, execute a test task on the multiplexed test behavior based on the test execution information, and output a test result.
The test execution information includes at least one of the number of threads of the test behavior, the number of tests per thread, and the test time. The test executor 140 is initialized by the test execution information, and the test behavior is set on the test executor 140 by the multiplexed test execution information, so that the test executor 140 has a function of performing a pressure test on the target object, and after the initialization and the configuration of the test behavior are completed by the test executor 140, a pressure test task is executed to obtain a test result, thereby completing the pressure test on the target object. The test result may include, but is not limited to, request delay, number of execution times error, and the like.
On the basis of the above embodiment, the pressure testing system further includes a result statistics device 150, where the result statistics device 150 is connected to the test executor 140, receives the test result output by the test executor, and generates a test report based on the test index in the test result. The result statistics device 150 may be further connected to the configuration parser 110, and the test process information parsed by the configuration parser 110 may include a test result statistics policy, where the test result statistics policy may include an index type to be counted, where the index type may be a TPS (transactionally psersecond, throughput) index, a QPS (query rate per second) index, an error rate index, and a delay index, and the indexes respectively correspond to a maximum value, a minimum value, and a mean value.
The result statistics device 150 processes the received test result through the test result statistics policy, and outputs a test report.
According to the technical scheme provided by the embodiment, the test executor, the test behavior configurator and the parameter generator are arranged, the test execution information, the test behavior information and the parameter generation strategy in the test process information are respectively read and initialized, the test behavior is configured through the test parameters generated by the parameter generator, and the test behavior is written into the test executor to form the test executor with the pressure test function so as to execute the pressure test task. The test executor, the test behavior configurator and the parameter generator are subjected to information configuration through the test process information analyzed and processed by the configuration file, test codes do not need to be written, the pressure test process is simplified, and the pressure test difficulty is reduced.
Example two
Fig. 2 is a schematic structural diagram of a pressure testing system provided in a second embodiment of the present invention, which is optimized based on the second embodiment, and optionally, the pressure testing system further includes a piling service simulator; the parameter generator is also used for generating a piling service parameter according to the read parameter generation strategy; and the piling service simulator is connected with the parameter generator and used for reading piling service information in the test process information, multiplexing the piling service parameters generated by the parameter generator, initializing based on the piling service information and the piling service parameters, executing a piling service simulation task and outputting a piling service simulation result.
Accordingly, the pressure testing system comprises:
and the configuration analyzer 110 is configured to receive the test configuration file and analyze the test configuration file to obtain test process information.
And the parameter generator 120 is configured to read a parameter generation policy in the test procedure information, and generate a test parameter based on the parameter generation policy.
And the test behavior configurator 130 is connected with the parameter generator 120 and is used for reading the test behavior information in the test process information, multiplexing the test parameters generated by the parameter generator 120, initializing the test behavior based on the test behavior information and the test parameters, and generating the piling service parameters according to the read parameter generation strategy.
And the test executor 140 is connected with the test behavior configurator 130, and is configured to read the test execution information in the test process information, multiplex the test behavior of the test behavior configurator 130, initialize based on the test execution information and the multiplexed test behavior, execute a test task on the multiplexed test behavior based on the test execution information, and output a test result.
And the piling service simulator 160 is respectively connected to the configuration parser 110 and the parameter generator 120, and is configured to read piling service information in the test process information and multiplex the piling service parameters generated by the parameter generator 120, initialize based on the piling service information and the piling service parameters, execute a piling service simulation task, and output a piling service simulation result.
In each system or application program, the mutual dependence between each service in the micro-service architecture realizes the overall function of the system together, and for the service with the dependence relationship, the front-end service can return correctly after acquiring the resource provided by the back-end service, so the performance of the front-end service is influenced by the performance of the back-end service, and the difficulty of pressure test on the single micro-service is increased. In this embodiment, the piling service simulator 160 is configured to simulate a service on which a target object depends, so as to avoid interference of the dependent service with a front-end service, and implement a pressure test on a single micro service without interference of other dependent services.
Optionally, the test process information includes a test mode attribute, the test mode attribute includes a piling service mode identifier and a common mode identifier, where the piling service mode identifier is used to trigger the test executor to execute a test task, the common mode identifier is used to trigger the piling service simulator to execute a piling service simulation, the test executor 140 and the piling service simulator 160 respectively read the test process information and identify the test mode attribute, the test executor 140 starts a pressure test when the identified test mode attribute is the common mode identifier, and the piling service simulator 160 starts a piling service when the identified test mode attribute is the piling service mode identifier.
The parameter generator 120 generates a piling service parameter, which may be a return value of the piling service, according to the read parameter generation policy. The return value of the pile driving service may be a base data value or a parameter object, and may be generated according to a parameter generation policy. The piling service simulator 160 may multiplex the piling service parameters generated in the parameter generator 120, initialize the piling service simulator 160, generate a piling service simulator having a piling service function, and execute a piling service task to obtain a piling service result.
The piling services simulator 160 includes at least one interface piling services simulation unit, wherein the piling services simulation unit may include, but is not limited to, a HTTP interface piling services simulation unit and a thrift interface piling services simulation unit for simulating a HTTP interface piling function and a thrift interface piling function, respectively. Optionally, the piling service simulator 160 may further include an expansion interface for adding a new piling service simulation unit, so as to improve the applicability and compatibility of the piling service.
Each piling service simulation unit is used for executing the piling service simulation task of the corresponding interface according to the piling service information and the piling service parameters generated by the multiplexing parameter generator, so as to realize piling services of different interface types.
The result statistics generator 150 is connected to the test executor 140 and the piling service simulator 160, respectively, receives the test result and the piling service simulation result, and generates a test report based on the test indexes in the test result and the piling service simulation result. The pressure test performed by the test executor 140 is performed based on the real service-dependent return values, the test result includes each service-dependent real return value and the corresponding time stamp, and the simulation result of the piling service generated by the piling service simulator 160 includes the theoretical return value and the corresponding time stamp. The result counter 150 compares the simulation result of the piling service with the test result, and determines whether the dependent service has a negative effect on the current object to be subjected to the pressure test, so as to eliminate the interference of the dependent service and realize a single test on the target object.
According to the technical scheme provided by the embodiment, the piling service simulator is arranged to simulate at least one dependent service of the target object to be tested, so that the interference of the dependent service on the front-end service is avoided, and the pressure test on the single micro service is realized under the condition that no other dependent service is interfered.
On the basis of the above embodiments, a preferred example of a pressure testing system is further provided, for example, referring to fig. 3, fig. 3 is a schematic structural diagram of another pressure testing system provided in the second embodiment of the present invention. The pressure testing system comprises a configuration analyzer ConfigParser, a test executor TestExecutor, a test behavior configurator TestBehave, a parameter generator ParamGenerator, a piling service simulator ServerMocker and a result counter StatisticModule.
The configuration parser ConfigParser is used for parsing the configuration file, configuring the working state of the system through the XML file, and defining that the XML Schema file restricts each XML element and the attribute thereof. The parameter generation strategy, the test behavior, how to execute the test behavior, whether to carry out piling service, how to carry out test result statistics and other functions of the test task can be configured through the configuration file.
The < tester > element is arranged between the configuration resolvers, the < tester > element is a root element in the whole configuration file and is used for defining a test case, and other XML elements contained in the configuration file are child elements of the element. The < TESTER > element is provided with an optional enumerated type attribute mode specifying whether the system is operating in normal mode (value TESTER) or in pile driving service mode (value MOCK _ SERVER).
A parameter generator ParamGenerator for generating parameter values in the pressure test request or return values for the pile driving service, the parameter generator being configurable in a configuration file by two elements, a simple parameter value generator < simpleValue > and a complex parameter value generator < objectValue > to generate different types of parameter values and return values. Wherein, the < simpleValue > element generates the parameter values of fixed or random character string, integer, floating point number, Boolean and date type, these simple parameter values can be used to further form the following values of thrift interface parameter, message body of message service, and key name or key value in redis, etc., and the < simpleValue > element is provided with the following attributes: the optional attribute id is used to uniquely identify a parameter value generator and to refer to the parameter generator among other elements; the optional values are string, int, long, float, double, borolean and date, wherein the date type specifies that the parameter value is a time string; and the mandatory attribute mode is an enumeration type and is used for defining a mode for generating parameter values, and selectable values are const, length and range, and are respectively used for specifying the mode for generating the parameter values to be a fixed value, a random value with a specified length and a random value with a specified range. When the type attribute is string, the mode attribute can only be set to fix and length; an optional attribute format, which is effective when the type attribute is date, specifies the format of the generated time string, is defined by adopting a Java standard time string format, and the default format is 'yyyy-MM-ddHH: MM: ss'; an optional attribute value, valid when the mode attribute is equal to const, for specifying a fixed value for generating a parameter, optionally "0" by default; an optional attribute length, which is valid when the mode attribute is equal to length, and is used for specifying the length of generating the random parameter; an optional attribute min, valid when mode equals range, for specifying a minimum value for generating random parameters; an optional attribute max, valid when mode equals range, for specifying the maximum value for generating the random parameter; an optional attribute ref is used to reference a defined global < simpleValue > element. The configuration file may be a parameter range configured with a < simpleValue > element or used for generating random parameters, or the like.
The < objectValue > element is a parameter generator at the top layer, and can directly generate parameter values such as a complex parameter object of a triple interface, a MapMessage in a message service, or a Json character string, and the < objectValue > element is provided with the following attributes: the optional attribute id is used to uniquely identify a parameter value generator and to refer to the parameter generator among other elements; the optional attribute class is used for specifying the fully qualified java class name of the parameter object; an optional attribute ref for referencing other global < objectValue > elements.
Optionally, the < objectValue > element may be a sub-element defining a plurality of < property > elements for configuring a generation policy of a certain field value in the parameter object, where the < property > sub-element may be provided with the following properties: a mandatory attribute name for specifying a field name to be set; an optional attribute value for specifying a constant value for a corresponding field value; an optional attribute valuefef for referencing a global < simpleValue > element or an < objectvalue > element as a value of a generation parameter for a specified field.
The < property > sub-element supports defining a property value generator for a field value of a collection type using < list >, < set > and < map > sub-elements. Where < list > and < set > the following sub-elements can be defined: the < simpleValue > child element directly defines a simple parameter value generator, the < objectValue > child element: a thrift parameter object generator is defined directly. The < map > element for which a set element needs to be added through the < entry > sub-element, under which key-value pairs need to be added through the < key > and < value > sub-elements, which are the same as the < list > and < set > elements. The < list > element, the < set > element, and the < map > element may also be directly child elements of the < objectValue > for directly generating an object value of the java collection type.
The test behavior configurator testbehavior is used for defining the operation of one test execution, including specifying the interface type adopted by the test, setting the interface attribute and the test parameter, and the like, and the module takes effect only when the attribute of the mode of the < TESTER > element is set to be TESTER, namely the test case works in a common mode. The module is configured by the < testBehave > element, and a plurality of < testBehave > elements can be defined in one configuration file.
The < testBehave > element is provided with an attribute id for uniquely identifying one < testBehave > element and referring to the element definition among other elements. The < testwhile > element is under and has only one sub-element, which can be configured as one of several sub-elements: the < thick > element, the < messages > element, and the < redis > element.
Where the < thrift > element is used to define the test behavior based on the thrift interface. The < thick > element may be configured with the following mandatory properties: a host attribute used for specifying the IP address of the measured thrift service, and a port attribute used for specifying the port number of the measured thrift service; the class attribute is used for specifying the fully-restricted Java class name of the RPC client call interface generated by the thick; a method attribute for specifying the name of the method in the RPC interface to be tested.
Optionally, a plurality of < param > sub-elements may be defined under the < thick > element, and are used to configure the parameters of how to generate the RPC interface method under test, and the order of the < param > sub-elements is the same as the order defined by the parameters in the RPC interface method under test. Each < param > child element has an optional attribute ref for referencing a globally defined < simpleValue > element or < objectValue > element, thereby configuring the parameter value generation policy. In addition to this, a dedicated < simpleValue > sub-element or < objectValue > sub-element may be directly defined under the < param > sub-element.
The < messages > element is used to configure message service based test behavior and may be configured with the following attributes: the provider attribute is used for specifying vendors providing the message provider, and in this embodiment, the vendors may be supported as ACTIVEMQ and KAFKA; the type attribute is only valid when the provider attribute is ACTIVEMQ, is used for specifying the message type, and has the following optional values: TEXT, MAP, BYTE, used to configure the test behavior to produce TextMessage, MapMessage and ByteMessage, respectively; a brokers attribute for connecting to the URL of the message server, and if the provider attribute value is KAFKA, the attribute value is host: a string in port format, separated by commas if there are multiple addresses; destination attribute, JMS queue or topic name for the service under test to use, or Kafka topic name; the isPersistent attribute is used for being effective only when the provider attribute is ACTIVEMQ, is of a Boolean type and is used for appointing whether a persistent mode is adopted to send the message; the isQueue attribute, which is used to be valid only if the provider attribute is ACTIVEMQ, is a Boolean type, and is used to specify whether the destination type of the message is Queue or Topic.
Optionally, one or more < message > sub-elements may be further defined under the < messages > element, so as to define a generation policy of the message body. If a plurality of < message > sub-elements are defined under a < messages > element, each time the test action is executed, messages are sequentially sent according to the defined sequence of the < message > sub-elements. The attribute of the < message > element is the same as < messages >, and if < messages > and < message > elements define the same attribute, the value of the attribute in < message > overrides the value of the homonymous attribute in its parent element.
The following sub-elements may also be defined under the < message > element: a < header > sub-element and a < body > sub-element. Wherein, the < header > sub-element is only valid when the provider attribute is ACTIVEMQ, and is used for configuring a message header of a sending message, and the < header > sub-element is configured with the following attributes: a mandatory attribute name, which is used to specify the message header to be set, for example, the name attribute value is set to "correlitinationid", and the system will call setjmscorrelationid (long correlitinationid) method setting of JMS; an optional attribute ref for setting the value of the header with reference to a globally defined < simpleValue > element, the optional attribute value specifying the value of a header as a constant. Optionally, a proprietary < simpleValue > element may be defined directly under the < header > element. The attribute and sub-element of the < Property > element are the same as the < header > element, which is used to configure the attribute value of the transmission message when the provider attribute is ACTIVEMQ, and the system calls the set [ type ] Property (Stringname, [ type ] value) method of JMS to set the attribute value of the message according to the type attribute of the < simpleValue > element referenced by the ref attribute. When the provider attribute is KAFKA, the attribute of the < header > element is used to configure the KAFKA producer.
A < body > sub-element for configuring the content of the message body, which is configured with a ref attribute for referring to a globally defined < simpleValue > element or < map > element, or a proprietary < simpleValue > sub-element or < map > sub-element may be defined directly under the < body > element. When the type attribute of the < message > element is MAP, the < body sub > element can only refer to or define the < MAP > element, and when the type attribute is TEXT or BYTE, or the provider attribute is KAFKA, the object defined by the < MAP > element will be converted into a Json string.
The < Redis > element is used to configure Redis-based test behavior, and the < Redis > element may be configured with the following attributes: a host attribute used for specifying a redis server address to which the test data is written; and the port attribute is used for specifying a redis server port number to which the test data is written.
Optionally, a number of < data > sub-elements may be defined under the < redis > element, the < data > sub-elements specifying that redis test data is to be written. The < data > sub-element has several attributes: a host attribute used for specifying the address of the redis server to which the test data is written, if the address is set, covering the corresponding attribute value in the parent element, otherwise inheriting the value in the parent element; port attribute, which is used to designate the number of the redis server port in which the test data is to be written, if set, the corresponding attribute value in the parent element is covered, otherwise, the value in the parent element is inherited; the type attribute is an enumeration type, and is used for specifying a data structure type of the test data stored in redis, and the selectable values are: STRING, LIST, SET and HASH, when the type value is STRING, the testing behavior will write the corresponding value into the redis designated key, when the type value is LIST and SET, the testing behavior will add the designated value into the LIST or SET structure designated by redis, when the type value is HASH, the testing behavior will add the designated field and field value into the HASH structure designated by redis; the key attribute is used for appointing the name of a redis key for storing the test data as a constant; a keyRef attribute for referencing a global < simpleValue > element to generate a name for the redis key of the saved data; a value attribute for specifying a value of data as a constant, the attribute being invalid when the type attribute value is HASH; the valuefef attribute, specifying that the test data value is generated by a global < simpleValue >, is invalid when the type attribute value is HASH.
Optionally, the following three optional sub-elements may also be defined under the < data > sub-element: sub-element < key >, sub-element < field >, and sub-element < value >. Where the child element < key > is used to specify the name of the redis key that holds the test data, there are two optional attributes: value and ref, which are used to specify the key name as a constant and reference a global < simpleValue >, respectively, and may also define a proprietary < simpleValue > element directly under this element; sub-element < field >: valid only when the type attribute is HASH, for specifying the name of a certain field in the key of the HASH type, the attribute and sub-element of this element being the same as the < key > element; child element < value >: a value for specifying how to generate test data, the attribute and sub-element of this element being the same as the < key > element.
The test executor testExecutor is used for configuring an execution plan of the pressure test, comprises one or more items of the thread number of the execution test behavior, the test execution times of each thread and the test time, is responsible for executing the test and reporting the test result to the statistical module, and the test executor takes effect only when the attribute of the < TESTER > element mode is set as TESTER, namely the test case works in a common mode. The test executor is configured by a < testExecutor > element, and one configuration file can define a plurality of < testExecutor > elements.
The < testExecutor > element is used for configuring an execution plan of the test executor module for executing the pressure test, and is configured with the following attributes: the thread number attribute is used for specifying the number of threads started by the test executor, and the concurrency number can be controlled through the thread number attribute; the execluteNomber attribute is used for specifying the times of executing the test behaviors of each test thread; a behavefef attribute for referencing a global < testBehave > element, which is used to configure the test actions to be performed by the executor. Optionally, the < testExecutor > element may also directly define a proprietary < testbeat > element under the < testExecutor > element, for configuring a test behavior to be executed by the executor.
The test result counter is used for summarizing the test results reported by each thread in the test executor, wherein the test results comprise information such as request delay, execution times, error times and the like, and then calculating the maximum, minimum and average TPS, QPS, error rate and delay index of the test. The test result counter is configured with a < statisticModule > element. The < staticimod > element is used to configure the test report generation policy of the test result statistics, and is configured with the following attributes: the Boolean type attribute doTPS is used for configuring whether to count TPS indexes or not; the Boolean type attribute doQPS is used for configuring whether to count a QPS index or not; a Boolean type attribute doErrorRate, which is used for configuring whether to count error rate indexes; the boolean type attribute doDelay is used to configure whether to count the delay indicators.
The pile driving service simulator ServerMocker is used for simulating the rear-end service behavior adopting the HTTP or the Thrift interface, responding to the request of the tested module for the rear-end service and quickly returning a specified result value. The piling service simulator is only effective when the < tester > element mode attribute is set to SERVER _ pointer, i.e. the test case is operating in the piling service mode. The piling services simulator is configured with a < serverMocker > element. The < serverMocker > element defines a sub-element < httpMocker > for configuring a pile driving function of the HTTP interface, and the < thriftMocker > sub-element for configuring a pile driving function of the thrift interface.
The < httpMocker > sub-element is used for configuring a service piling module to provide a back-end service simulation function adopting an HTTP interface, a test case can be configured to return a specified value according to an HTTP request URL received from a tested service through the < httpMocker > sub-element, and the < httpMocker > sub-element has the following attributes: and (3) a mandatory attribute urlPrefix for defining a URL prefix of the test case for providing the HttpMock service, and if the value of the urlPrefix attribute is configured to be "mypacker", the test case only provides the Mock service for the http request of which the URL is "http://///mypacker/". And the optional attribute port is used for defining the port number of the current Mocker for externally providing the http service.
Optionally, a plurality of < urlMapping > sub-elements may be defined under the < httpmarker > sub-element for configuring the specific URL return result, and the following two mandatory sub-elements need to be defined under the < urlMapping > sub-element: a < pattern > sub-element for specifying a regular expression to configure a specific URL suffix, a < result > sub-element for specifying that a specific value is returned for a URL that successfully matches the < pattern > specified pattern, the < result > sub-element having a ref selectable attribute for referencing a global < simpleValue > sub-element or an < objectValue > sub-element, or a proprietary < simpleValue > sub-element or an < objectValue > sub-element may be defined directly under the element. The return value generated by the < objectValue > child element will be translated into a Json string.
The pile driving service simulator can provide an implementation class of a server-side interface generated by a triple framework through a JAVA dynamic proxy technology, so as to realize a function of returning a specified value to a specific triple interface request, wherein the function provides a < triple Mocker > child element configuration, and the < triple Mocker > child element configuration has the following attributes: the port of the optional attribute is used for appointing the port number of the current packer for providing the thrift service to the outside; the mandatory attribute class is used for specifying the authority of a server-side interface generated by the thrift frame to determine the name of the Java interface; the optional attribute server mode is used for specifying the working mode of the thrift piling service server, and the optional values are as follows: read _ POOL and select; the optional attribute maxThreadNum is valid when the server mode is the read _ POOL and is used for specifying the maximum THREAD number started by the thrif service server end; the optional attribute minThreadNum, which is valid when the server mode is the read _ POOL, is used to specify the minimum number of THREADs started by the thrif service server side.
Optionally, a plurality of < method > sub-elements may be defined under the < threshold mocker > sub-element, for configuring the return value of each interface method of each threshold service, where the < method > sub-element has the following attributes: the mandatory attribute name is used for specifying a specific interface method name in the thrift interface; and an optional attribute resultRef for referring to a globally defined < simpleValue > or < objectValue > element, and configuring the interface method specified by the name attribute to return a corresponding value.
Optionally, a specific < simplevalue > sub-element or < objectValue > sub-element is directly defined under the < method > sub-element, and is configured to return a corresponding value for the specified interface method.
EXAMPLE III
Fig. 4 is a schematic flow chart of a pressure testing method provided in an embodiment of the present invention, where the embodiment is applicable to a pressure test on a microservice without encoding, and the method can be executed by the pressure testing system provided in the embodiment of the present invention, and specifically includes the following steps:
s210, receiving a test configuration file based on a configuration analyzer, and analyzing the test configuration file to obtain test process information.
S220, reading a parameter generation strategy in the test process information based on a parameter generator, and generating a test parameter based on the parameter generation strategy.
And S230, reading the test behavior information in the test process information based on a test behavior configurator, multiplexing the test parameters generated by the parameter generator, and initializing the test behavior based on the test behavior information and the test parameters.
S240, reading test execution information in the test process information based on a test executor, multiplexing the test behaviors of the test behavior configurator, initializing based on the test execution information and the multiplexed test behaviors, executing a test task to the multiplexed test behaviors based on the test execution information, and outputting a test result.
Optionally, the parameter generator includes a simple parameter generator and a complex parameter generator, and the parameter generation policy includes a preset type of parameter value and a parameter object.
Optionally, the simple parameter generator is configured to generate a parameter value of a corresponding type based on the type of the parameter value; the complex parameter generator is used for multiplexing at least one simple parameter generator and/or at least one complex parameter generator for generating the parameter object.
Optionally, the test behavior configurator includes a test behavior configuration unit of a plurality of protocols.
Optionally, the test execution information includes at least one of a thread number of the test behavior, a test number and a test time.
Optionally, the method further includes:
generating a piling service parameter according to the read parameter generation strategy based on the parameter generator;
and reading piling service information in the test process information based on a piling service simulator, multiplexing the piling service parameters generated by the parameter generator, initializing based on the piling service information and the piling service parameters, executing a piling service simulation task, and outputting a piling service simulation result.
Optionally, the pile driving service simulator includes a pile driving service simulation unit of at least one interface;
the simulation method comprises the following steps that a piling service simulator based on piling service reads piling service information in the test process information, multiplexes piling service parameters generated by the parameter generator, initializes based on the piling service information and the piling service parameters, and executes a piling service simulation task, and comprises the following steps:
and executing a piling service simulation task of a corresponding interface based on each piling service simulation unit according to the piling service information and the piling service parameters generated by multiplexing the parameter generator.
Optionally, the test process information includes a test mode attribute, where the test mode attribute includes a piling service mode identifier and a common mode identifier, where the piling service mode identifier is used to trigger the test executor to execute a test task, and the common mode identifier is used to trigger the piling service simulator to execute a piling service simulation.
Optionally, the method further includes:
receiving a test result output by the test executor based on a result counter, and generating a test report based on a test index in the test result;
or receiving the test result and the piling service simulation result based on a result statistics device, and generating a test report based on the test result and the test indexes in the piling service simulation result.
According to the technical scheme, the configuration file is set and comprises the test process information required in the pressure test process of the target object, the configuration analyzer analyzes the configuration file to obtain the test process information, the parameter generator, the test behavior configurator and the test actuator are initialized based on the analyzed test process information to obtain the pressure test system for performing the pressure test on the target object, the target object is subjected to the pressure test to obtain the test result, the pressure test code does not need to be written, the difficulty and the workload of the pressure test are reduced, and the pressure test process is simplified.
The preferred embodiment of the pressure testing method is also provided on the basis of the above embodiment. Referring to fig. 5, fig. 5 is a schematic flow chart of another pressure testing method provided in the third embodiment of the present invention. The method comprises the following steps: and acquiring a configuration file, and analyzing the configuration file to obtain test process information. And generating a strategy initialization parameter generator based on the parameters in the test process information to generate test parameters. Judging whether the driving mode identification ServerMocker is the driving mode identification or not based on the test mode attribute in the test process information, if so, initializing a driving service simulator based on the driving service parameters in the test process information, configuring a parameter generator for the driving service simulator through a multiplexing parameter generator, executing a driving service task, and obtaining a driving service result. If the test mode attribute is not the piling mode identification, namely the common test mode, initializing the test behavior based on the test behavior information in the test process information, configuring a parameter generator for the test behavior, further initializing a test actuator based on the test execution information in the test process information, configuring the test behavior on the actuator, executing a pressure test task, obtaining a test result, and counting an operation result based on the test result and the piling service result by a result counting module to obtain a test report.
Example four
Fig. 6 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 6 illustrates a block diagram of an electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 6 is only an example and should not bring any limitation to the function and the scope of use of the embodiment of the present invention. The device 12 is typically an electronic device that assumes image classification functionality.
As shown in FIG. 6, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors 16, a memory device 28, and a bus 18 that couples various system components including the memory device 28 and the processors 16.
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
Storage 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard drive"). Although not shown in FIG. 6, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), a Digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Storage 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program 36 having a set (at least one) of program modules 26 may be stored, for example, in storage 28, such program modules 26 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination of which may comprise an implementation of the gateway environment. Program modules 26 generally carry out the functions and/or methodologies of the described embodiments of the invention.
Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, camera, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, electronic device 12 may communicate with one or more gateways (e.g., Local Area Network (LAN), Wide Area Network (WAN), etc.) and/or a public gateway, such as the internet, via gateway adapter 20. As shown, the gateway adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.
The processor 16 executes various functional applications and data processing by executing programs stored in the storage device 28, for example, implementing the pressure test method provided by the above-described embodiment of the present invention.
EXAMPLE five
Fifth embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the pressure testing method provided by the fifth embodiment of the present invention.
Of course, the computer program stored on the computer-readable storage medium provided by the embodiments of the present invention is not limited to the method operations described above, and may also perform the pressure testing method provided by any embodiment of the present invention.
Computer storage media for embodiments of the present invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable source code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Source code embodied on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer source code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The source code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of gateway, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will appreciate that the present invention is not limited to the particular embodiments described herein, and that various obvious changes, rearrangements and substitutions will now be apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (11)

1. A pressure testing system, comprising:
the configuration analyzer is used for receiving the test configuration file and analyzing the test configuration file to obtain test process information;
the parameter generator is used for reading a parameter generation strategy in the test process information and generating a test parameter based on the parameter generation strategy;
the test behavior configurator is connected with the parameter generator and used for reading the test behavior information in the test process information, multiplexing the test parameters generated by the parameter generator and initializing the test behavior based on the test behavior information and the test parameters;
and the test executor is connected with the test behavior configurator and used for reading test execution information in the test process information, multiplexing the test behaviors of the test behavior configurator, initializing based on the test execution information and the multiplexed test behaviors, executing a test task on the multiplexed test behaviors based on the test execution information and outputting a test result.
2. The pressure testing system of claim 1, wherein the parameter generator comprises a simple parameter generator and a complex parameter generator, the parameter generation strategy comprising parameter values of a preset type and parameter objects;
wherein the simple parameter generator is used for generating parameter values of corresponding types based on the types of the parameter values;
the complex parameter generator is used for multiplexing at least one simple parameter generator and/or at least one complex parameter generator for generating the parameter object.
3. A stress testing system according to claim 1, wherein the test behaviour configurator comprises a test behaviour configuration unit of a plurality of protocols.
4. The pressure test system of claim 1, wherein the test execution information includes at least one of a number of threads of a test action, a number of tests, and a test time.
5. A pressure testing system as claimed in claim 1, further comprising a pile driving service simulator;
the parameter generator is also used for generating a strategy according to the read parameters to generate piling service parameters;
and the piling service simulator is connected with the parameter generator and used for reading piling service information in the test process information, multiplexing the piling service parameters generated by the parameter generator, initializing based on the piling service information and the piling service parameters, executing a piling service simulation task and outputting a piling service simulation result.
6. A pressure testing system according to claim 5, characterized in that the piling services simulator comprises at least one interfaced piling services simulation unit;
and each piling service simulation unit is used for executing a piling service simulation task of a corresponding interface according to the piling service information and the piling service parameters generated by multiplexing the parameter generator.
7. A pressure testing system according to claim 5, characterized in that the test procedure information comprises test mode attributes including a piling service mode identification and a common mode identification, wherein the piling service mode identification is used to trigger the test executor to perform a test task, and the common mode identification is used to trigger the piling service simulator to perform a piling service simulation.
8. The pressure testing system of claim 1 or 5, further comprising a result statistics generator;
the result statistics device is connected with the test actuator, receives the test result output by the test actuator, and generates a test report based on the test index in the test result;
alternatively, the first and second electrodes may be,
and the result counter is respectively connected with the test executor and the piling service simulator, receives the test result and the piling service simulation result, and generates a test report based on test indexes in the test result and the piling service simulation result.
9. A pressure testing method, comprising:
receiving a test configuration file based on a configuration analyzer, and analyzing the test configuration file to obtain test process information;
reading a parameter generation strategy in the test process information based on a parameter generator, and generating a test parameter based on the parameter generation strategy;
reading test behavior information in the test process information based on a test behavior configurator, multiplexing test parameters generated by the parameter generator, and initializing test behaviors based on the test behavior information and the test parameters;
reading test execution information in the test process information based on a test executor, multiplexing the test behavior of the test behavior configurator, initializing based on the test execution information and the multiplexed test behavior, executing a test task to the multiplexed test behavior based on the test execution information, and outputting a test result.
10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the stress testing method of claim 9 when executing the program.
11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the stress-testing method of claim 9.
CN202110321331.5A 2021-03-25 2021-03-25 Pressure testing system and method, storage medium and electronic equipment Pending CN115129577A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110321331.5A CN115129577A (en) 2021-03-25 2021-03-25 Pressure testing system and method, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110321331.5A CN115129577A (en) 2021-03-25 2021-03-25 Pressure testing system and method, storage medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN115129577A true CN115129577A (en) 2022-09-30

Family

ID=83374502

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110321331.5A Pending CN115129577A (en) 2021-03-25 2021-03-25 Pressure testing system and method, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN115129577A (en)

Similar Documents

Publication Publication Date Title
CN111083225B (en) Data processing method and device in Internet of things platform and Internet of things platform
CN111428462B (en) Communication protocol template construction method and terminal equipment
US9218269B2 (en) Testing multiple target platforms
CN106919511B (en) Application simulation method, simulation application, operation method thereof and simulation system
CN111309343A (en) Development deployment method and device
US7222313B2 (en) Creating description files used to configure components in a distributed system
CN112597018A (en) Interface test case generation method, device, equipment and storage medium
CN111917603A (en) Client test method and device, computer equipment and storage medium
CN113778897A (en) Automatic test method, device, equipment and storage medium of interface
CN113836014A (en) Interface testing method and device, electronic equipment and storage medium
US7958422B2 (en) Method and apparatus for generating self-verifying device scenario code
CN113238739A (en) Plug-in development and data acquisition method, device, electronic equipment and medium
CN111930621A (en) DNS automation performance testing method, device, equipment and readable storage medium
CN115129577A (en) Pressure testing system and method, storage medium and electronic equipment
CN115309657A (en) Method, device, medium and program product for providing test case
CN111399843B (en) Method, system and electronic equipment for mapping SQL running information to SQL file
CN111736924B (en) Method, device, equipment and medium for accessing data acquisition instrument based on Lua script
CN111459984B (en) Log data processing system and method based on streaming processing
CN114791885A (en) Interface test method, device, equipment and medium
CN114219643A (en) Transaction calling method, device, equipment and storage medium
CN113220586A (en) Automatic interface pressure test execution method, device and system
CN111444161A (en) Data processing method and device, electronic equipment and storage medium
CN110795338A (en) Automatic testing method and device based on front-end and back-end interaction and electronic equipment
CN116680171B (en) Test method, device, storage medium and electronic equipment
CN117130933A (en) Baffle service method, system, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination