WO2018072095A1 - Procédé et système de gestion de test de charge - Google Patents

Procédé et système de gestion de test de charge Download PDF

Info

Publication number
WO2018072095A1
WO2018072095A1 PCT/CN2016/102436 CN2016102436W WO2018072095A1 WO 2018072095 A1 WO2018072095 A1 WO 2018072095A1 CN 2016102436 W CN2016102436 W CN 2016102436W WO 2018072095 A1 WO2018072095 A1 WO 2018072095A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
parameter
pressure test
script
parameters
Prior art date
Application number
PCT/CN2016/102436
Other languages
English (en)
Chinese (zh)
Inventor
文青山
Original Assignee
深圳市福斯康姆智能科技有限公司
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 深圳市福斯康姆智能科技有限公司 filed Critical 深圳市福斯康姆智能科技有限公司
Priority to PCT/CN2016/102436 priority Critical patent/WO2018072095A1/fr
Publication of WO2018072095A1 publication Critical patent/WO2018072095A1/fr

Links

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

Definitions

  • the present invention belongs to the field of stress testing, and in particular, to a stress test management method and system.
  • Locust is a Python-based distributed stress testing tool that tests the system's concurrent processing capabilities and can be used to test web services or other services.
  • the main idea of Locust is to simulate a group of users who will visit your website. During the test, a large number of users (Locust s ⁇ group) are generated to attack the system. The behavior of each user (Locust Locust) is controlled by the Python language code definition, and the entire test process has a website interface that can be implemented. Observe the test data.
  • the embodiment of the present invention provides a stress test management method and system, so as to solve the parameters required for each test in the prior art, all need to be manually input, the stress test script needs to be in each stress test node. The separate operations have led to the problem of inefficient Locust.
  • a stress test management method including:
  • the pressure test script parameters in the database include:
  • the stress test parameters include: a pressure test script parameter, a monitoring parameter, and a scene parameter; the pressure test script parameter includes: a configuration address of the stress test node and a stress test script.
  • the pressure test script parameters uploaded by the receiving client include:
  • the stress test script parameter is data of a multiple morphological data format.
  • the pressure test scripts for configuring the pressure test nodes in batch according to the stress test script parameters include:
  • the pressure test script is batch uploaded to the corresponding pressure test nodes by using the safe transmission method of the paramiko module.
  • the sending, by the entity, the monitoring information and the test result information to the client includes:
  • a stress test management system including:
  • the first receiving unit is configured to receive the pressure test parameter uploaded by the client, and store the data in the database
  • a reading unit configured to read a pressure test parameter in the database
  • a transmission unit configured to batch transfer the pressure test parameter to all pressure test nodes, and configure a pressure test script of all the pressure test nodes in batch according to the pressure test parameter;
  • an instruction sending unit configured to batch send a test start command to all the pressure test nodes, and send the monitoring command in batches to the system under test;
  • the second receiving unit is configured to receive the test condition parameter, store the test condition parameter in a database, and send the test condition data to the client.
  • the pressure test script parameters in the database include:
  • the stress test parameters include: a stress test script parameter, a monitoring parameter, and a scene parameter; the pressure test script parameter includes: a configuration address of the stress test node and a stress test script.
  • the pressure test script parameters uploaded by the receiving client include:
  • the stress test script parameter is data of a multiple morphological data format.
  • the transmission unit includes:
  • the pressure test script is batch uploaded to the corresponding pressure test nodes by using the secure transmission method of the paramiko module.
  • the second receiving unit includes:
  • the pressure test scripts of all the pressure test nodes are configured in batches, so that Locust does not need to be manually performed one by one.
  • the pressure test parameter input eliminates the need for script configuration for each pressure test node one by one, and uses the batch send monitoring command, so that the monitoring operation does not need to be manually operated one by one. Compared with the existing Locust, it is more automated, which greatly improves the Locust efficiency.
  • FIG. 1 is a flowchart of an implementation of a stress test management method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a method for generating a Locust stress test script by a proxy server according to an embodiment of the present invention
  • 3 is a flowchart of a specific implementation of a pressure test script parameter formation and upload database according to an embodiment of the present invention
  • 4 is a schematic flowchart of a query result of a Locust stress test history result according to an embodiment of the present invention
  • FIG. 5 is a flow chart of a specific embodiment of applying the present invention to a Locust stress test
  • FIG. 6 is a structural block diagram of a stress test management system according to an embodiment of the present invention.
  • the embodiment of the present invention is based on the Locust implementation, receiving the stress test parameters uploaded by the client, and storing the data in the database; reading the pressure test parameters in the database; and transmitting the pressure test parameters to all the pressure test nodes in batches, according to the Pressure test parameters, batch configuration of pressure test scripts of all the pressure test nodes; batch sending test start commands to all of the pressure test nodes, and batch sending monitoring instructions to the system under test; receiving test condition parameters, the test conditions The parameters are stored in the database, and the test case data is sent to the client.
  • Embodiment 1 shows an implementation flow of a stress test management method according to Embodiment 1 of the present invention, which is described in detail as follows: [0047]
  • S101 a pressure test parameter uploaded by a client is received and stored in a database.
  • the client refers to an application or website of the terminal, such as a mobile app application and a computer website.
  • the pressure test parameters include: a pressure test script parameter, a monitoring parameter, and a scene parameter;
  • the stress test script parameters include: a configuration address of the stress test node and a stress test script.
  • the configuration address of the stress test node refers to the address of the stress test node corresponding to the stress test script to be uploaded. After uploading the stress test node, the stress test script needs to specify the pressure test node corresponding to each stress test script. Therefore, it is necessary to determine the address of the stress test node to be uploaded for each stress test script, that is, the stress test.
  • the configuration address of the node is necessary to determine the address of the stress test node to be uploaded for each stress test script, that is, the stress test.
  • the monitoring parameters include: a monitoring address and a monitoring status.
  • the monitoring address refers to the address of the system under test
  • the monitoring status refers to the system under test to be monitored.
  • Test the parameters of various parameter indicators, such as response time, transaction capacity, concurrent capacity, resource usage and other parameters.
  • the system under test may be a web server or other business, taking the system under test as a web server as an example, suppose that it is desirable to stress test the response speed of a web server in a large number of users, we need to determine the IP of the website.
  • the address, the IP address of the website is the monitoring address of the stress test, and the status of the website response speed is the monitoring status without using the number of users.
  • the user obtains the state of the specific test parameter to be monitored in the stress test by setting the monitoring state to meet the actual demand.
  • the scene parameters include: a number of virtual users and a test time.
  • the number of virtual users refers to a compression capability for simulating an actual user login system and operating to test the system.
  • the test time refers to the length of time required for the stress test. If the pressure test is set to continue for 30 minutes, and the pressure test is stopped after 30 minutes, the 30 minutes is The test was conducted.
  • the peer-to-peer server that performs the stress test also performs the test daytime monitoring task, and ends the stress test after the set test is reached.
  • the client Before receiving the stress test parameter uploaded by the client and storing the data in the database, the client further obtains the stress test script by using a proxy server to generate a Locust stress test script, and then the user sets the pressure test script.
  • the configuration address of the stress test node forms the final stress test script parameters.
  • the Locust stress test script ie, the Locust stress test code
  • the embodiment of the present invention adopts a method of generating a Locust stress test script by a proxy server to realize automation. Generate Locust stress test scripts to improve the efficiency of Locust stress tests as detailed below:
  • the proxy server used in the embodiments of the present invention needs to meet the following requirements:
  • mitmproxy (man-in-the-middle agent) is an http proxy, which can be used to debug http communication, initiating Interpersonal attacks, etc. Mitmproxy provides a console interface for dynamically intercepting and editing http packets
  • Mitmdump is the command line version of mitmproxy, which has the same functionality.
  • mitmdump supports inline (inline) script can intercept the contents of the read request and response, use this feature, read the relevant code in Python code, you can automatically generate Locust stress test script, the specific steps are shown in Figure 2. Show, as detailed below:
  • a local proxy is set to connect to the proxy server.
  • the setting of the local proxy to connect to the proxy server may be set by the mobile terminal application or through the website as a client.
  • the proxy server reads the specified domain name and obtains the http request type.
  • the http request type includes a get request and a post request, wherein the get request is to acquire data from the server, and the post request is to transfer data to the server.
  • FIG. 3 The specific implementation process of the pressure test script parameter formation and uploading database is as shown in FIG. 3, which is detailed as follows:
  • the user selects a stress test script and configures a corresponding upload address to form a stress test script parameter.
  • the uploading address refers to a specific address of the stress test node to be uploaded by each stress test script.
  • the pressure test script parameter is uploaded to the server.
  • the client uploads the stress test script parameters to the server by setting a multiple morphological data format.
  • the server uploads the stress test script parameters to the database.
  • the pressure test parameters in the database are read.
  • the pressure test parameters are bulk transferred to all pressure test nodes, and pressure test scripts of all the pressure test nodes are configured in batch according to the pressure test parameters.
  • the stress test script is batch uploaded to the corresponding pressure test nodes by using the secure transmission method of the paramiko module.
  • the system server After obtaining the configuration address of the stress test node, the system server renames and uploads the file to each stress test according to the configuration address of the stress test node through the secure transmission (sftp.put) method of the pammiko module. node.
  • the paramiko module is a module written in the Python language that supports connection to a remote server in an encrypted and authenticated manner.
  • the file is heavy by using the secure transmission method of the pammiko module. Named and uploaded to each stress test node, the centralized configuration and management of the stress test script in the client, simplified the operation of logging in and uploading to multiple stress test nodes, and also established the stress test script baseline, the stress test script standard. .
  • the batch transmission of the pressure test parameters to all pressure test nodes is also carried out in batch transmission using the secure transmission method of the paramiko module.
  • the stress test script parameter is data of a multiple morphological data format.
  • the multipart/form-data format has a feature of not encoding characters in data, and does not encode characters in data during data transmission, but directly transmits data. Because the stress test script parameter contains both the stress test script file and the configuration address of the stress test node belongs to the existing text data, and the binary data of the file, using the multiple shape data format for transmission, the pressure test script parameter data can be obtained. Full upload.
  • test start command is sent in batches to all of the pressure test nodes, and the monitoring command is sent in batches to the system under test.
  • the server sends batches of initialization, execution stress tests, stop stress tests, and the like to the pressure test nodes to control the stress test through the ssh.exec command method of the paramiko module.
  • the node works, and the system under test performs the dstat monitoring command in batches.
  • the ssh.exec_command method of the paramiko module can perform a plurality of remote terminal batch execution commands without manually inputting commands by a pair of pressure test nodes.
  • the dstat is a versatile system information statistical tool for monitoring the status of various parameter indicators of the system under test, having a color interface, and manually observing performance status, the data is more conspicuous and easy to observe, and dstat support That is, refresh, for example, input dstat 3 is collected every three seconds, but the latest data will be refreshed every second. Dstat can collect specified performance resources, such as dstat -c to display CPU usage.
  • test condition parameter is received, the test condition parameter is stored in a database, and the test condition data is sent to the client.
  • the test condition parameter includes monitoring status information and test result information.
  • the monitoring status information refers to monitoring results of various parameter states monitored in the monitoring state, and the parameters such as response time, transaction capacity, concurrent capacity, resource usage rate, etc. mentioned above are in stress test.
  • the system under test may have different response speeds, resulting in multiple different response periods, ie, response time.
  • the system under test After the dstat monitoring command is executed, the system under test saves the monitoring status information as a CSV (Comma Separated Value File Format) file, and transmits the monitoring status information to the server.
  • CSV Common Separated Value File Format
  • the pressure test node transmits the test result information of the stress test to the server.
  • the server After receiving the monitoring status information and the test result information, the server stores the monitoring status information and the test result information, and simultaneously returns the monitored actual information to the client through the socket communication, thereby implementing simple configuration and batch monitoring. the goal of.
  • the socket (socket) communication can directly transmit data after the communication parties establish a connection, and the active push of the information can be realized after the connection, and the server does not need to be sent by the client every time. Send the request.
  • a socket connection By establishing a socket connection, a channel can be provided for data transmission between the two parties.
  • the main features of socket are low data loss rate, easy to use and easy to port.
  • the method further includes:
  • the client generates a historical test query command according to the Locust stress test item name or the date information of the Locust stress test input by the user, and sends the history test query command to the server;
  • the server determines the data range to be queried according to the Locus pressure test item name included in the historical test query instruction or the date information of the Locust stress test, and reads Take the corresponding stress test parameters and corresponding test condition parameters in the database and send them to the client.
  • the system displays the Locust stress test result information of the query and the corresponding scene parameter, and provides an option for downloading the query result.
  • the client After receiving the corresponding stress test parameter and the corresponding test condition parameter, the client displays the historical test data on the client for display, and simultaneously displays the download option of the data. [0115] In S403, the user is free to select the query result to be downloaded.
  • the client is a terminal application or website, such as an app application and a website of the mobile phone.
  • the proxy server used is the mitmdump proxy server.
  • a stress test script is produced by a proxy server.
  • the proxy server reads the specified domain name and obtains the http request type of the get request or the post request, reads the flow.r equest.host and flow.request.path codes, and according to the specific geti request or posti request, press
  • the format of the Locus t stress test script generates the corresponding Locust stress test script for the http request and sends it to the client.
  • the script address is configured, and the configured script parameters are uploaded to the database.
  • the user loads the corresponding stress test node upload address of the stress test script to form a final stress test script parameter, and then the client tests the pressure test script parameter by setting the format to multipart/form-data (multiple form data). Upload to the server.
  • the monitoring parameters and the scene parameters are configured, and the configured monitoring parameters and scene parameters are uploaded to the database.
  • the user configures the monitoring address, the monitoring status, the number of virtual users, and the test time on the client, forms monitoring parameters and scene parameters, and uploads the configured monitoring parameters and scene parameters to the database.
  • the server reads the pressure test parameters, initializes each pressure test node, configures the pressure test parameters of all the pressure test nodes, and starts the Locust stress test, the dstat monitoring, and the peer monitoring test.
  • the server After the server reads the stress test parameters, that is, the pressure test script parameters, the monitoring parameters, and the scene parameters, the ssh.exec_command method of the paramiko module is used to batchly send the command to start the Locust stress test, and then call the swarm (group) of locust. Interface, start test execution.
  • the stress test parameters that is, the pressure test script parameters, the monitoring parameters, and the scene parameters
  • the ssh.exec_command method of the paramiko module is used to batchly send the command to start the Locust stress test, and then call the swarm (group) of locust. Interface, start test execution.
  • each pressure test node is initialized, and the server uses the sftp.put method of the paramiko module to configure the pressure test script parameters, the monitoring parameters and the scene parameters of all the pressure test nodes, and simultaneously starts the ds tat monitoring and monitoring test. between.
  • the swarm allows programs to be distributed among multiple computers, to some extent make the program completely transparent to the programmer, and the test of the stress test node can be started in batches through the swarm interface.
  • test condition parameter is saved and the feedback is sent to the client for display.
  • the system under test will save the monitoring status information as a CSV (Comma Separated Value File Format) file, and transmit the monitoring status information to the server.
  • CSV Common Separated Value File Format
  • the pressure test node transmits the test result information of the stress test to the server.
  • the server After receiving the monitoring status information and the test result information, the server stores the monitoring status information and the test result information, and simultaneously returns the monitored actual information to the client through the socket communication, thereby implementing simple configuration and batch monitoring. the goal of.
  • the client After receiving the test condition parameter, the client performs a real display.
  • the server saves the test condition parameter and uploads it to the database for querying and comparing the historical test result information.
  • the user queries the test condition parameter and the stress test parameter through the client.
  • the user needs to query the historical Locust stress test data, and only needs to input the Locus t stress test item name of the query or the date of the Locust stress test on the client.
  • the client displays the Locust stress test condition parameters and stress test parameters of the query, and provides the option to download the query results. Users choose their own needs If you want to download the data, you can download only some of the data, such as downloading only the historical test result information, or download all the historical test related data. Users can compare historical tests with existing tests to establish baseline standards, or perform performance analysis of tests.
  • the Locust stress test script is automatically generated by using a proxy server in advance, the stress test node address production stress test script parameter corresponding to the stress test script is set, and the stress test script parameter, the monitoring parameter, and the scenario are set.
  • the parameters are stored in the database, which makes the acquisition of the test parameters fully automatic during the Locust stress test process. It does not need to manually input the test parameters one by one manually every time, and use the pammiko module to upload the script parameters in batches.
  • the test starts the same batch execution monitoring command, which enables the multi-terminal script configuration and monitoring to be automated without having to operate each pressure test node one by one. By automating the test parameter input, the pressure test script operation batch, monitoring start and test Synchronization is initiated, which greatly improves the efficiency of Locust stress testing.
  • FIG. 6 is a block diagram showing the structure of the stress test management system provided by the embodiment of the present invention.
  • the system includes:
  • the first receiving unit 61 is configured to receive the pressure test parameter uploaded by the client, and store the data in the database; [0147] the reading unit 62 is configured to read the pressure test parameter in the database;
  • a transmission unit 63 configured to batch transfer the pressure test parameter to all pressure test nodes, and batch configure a pressure test script of all the pressure test nodes according to the stress test parameter;
  • the instruction sending unit 64 is configured to batch send a test start command to all the pressure test nodes, and batch send the monitoring command to the system under test;
  • the second receiving unit 65 is configured to receive a test condition parameter, store the test condition parameter in a database, and send the test condition data to the client.
  • the pressure test script parameters in the database include:
  • the stress test parameters include: a stress test script parameter, a monitoring parameter, and a scene parameter; the pressure test script parameter includes: a configuration address of the stress test node and a stress test script.
  • the pressure test script parameters uploaded by the receiving client include:
  • the stress test script parameter is data of a multiple morphological data format.
  • the transmission unit 63 includes:
  • the pressure test script is batch uploaded to the corresponding pressure test nodes by using the secure transmission method of the paramiko module.
  • the second receiving unit 65 includes:
  • the disclosed systems, systems, and methods may be implemented in other manners.
  • the system embodiment described above is merely illustrative.
  • the division of the unit is only a logical function division, and the actual implementation may have another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, system or unit, and may be in electrical, mechanical or other form.
  • the unit described as a separate component may or may not be physically distributed, and the component displayed as a unit may or may not be a physical unit, that is, may be located in one place, or may be distributed to multiple On the network unit. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or Therefore, each unit physically exists alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read only memory (ROM, Read-Only)
  • RAM random access memory
  • disk disk or optical disk, and other media that can store program code.

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)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un système de gestion de test de charge. Le procédé consiste à : recevoir un paramètre de test de charge téléchargé vers l'amont par un client et stocker celui-ci dans une base de données ; lire le paramètre de test de charge dans la base de données ; transmettre par lots le paramètre de test de charge à tous les nœuds de test de charge, configurer par lots un script de test de charge pour tous les nœuds de test de charge en fonction du paramètre de test de charge ; envoyer par lots une instruction d'activation de test à tous les nœuds de test de charge, envoyer par lots une instruction de surveillance à un système en cours de test ; et recevoir un paramètre de situation de test et stocker celui-ci dans la base de données, et envoyer des données de situation de test en temps réel au client. En lisant directement le paramètre de test de charge dans la base de données et en effectuant une configuration uniforme sur les nœuds de test de charge en fonction d'un paramètre de script prédéfini, il n'est pas nécessaire d'entrer manuellement les paramètres de test à chaque fois dans Locust, ou d'effectuer une configuration de script sur chacun des nœuds de test de charge, ce qui rend le procédé plus automatisé que les systèmes Locust existants, et augmente significativement l'efficacité de Locust.
PCT/CN2016/102436 2016-10-18 2016-10-18 Procédé et système de gestion de test de charge WO2018072095A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/102436 WO2018072095A1 (fr) 2016-10-18 2016-10-18 Procédé et système de gestion de test de charge

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/102436 WO2018072095A1 (fr) 2016-10-18 2016-10-18 Procédé et système de gestion de test de charge

Publications (1)

Publication Number Publication Date
WO2018072095A1 true WO2018072095A1 (fr) 2018-04-26

Family

ID=62018253

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/102436 WO2018072095A1 (fr) 2016-10-18 2016-10-18 Procédé et système de gestion de test de charge

Country Status (1)

Country Link
WO (1) WO2018072095A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108923997A (zh) * 2018-05-24 2018-11-30 广东睿江云计算股份有限公司 一种基于python的云服务节点自动测试方法及装置
CN110245083A (zh) * 2019-06-11 2019-09-17 四川长虹电器股份有限公司 一种基于python的接口自动化测试方法
CN110704312A (zh) * 2019-09-25 2020-01-17 浙江大搜车软件技术有限公司 压力测试的方法、装置、计算机设备和存储介质
CN114077449A (zh) * 2020-08-20 2022-02-22 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217419A (zh) * 2007-12-28 2008-07-09 西安西电捷通无线网络通信有限公司 一种分布式ip网络性能测试方法
US20110055633A1 (en) * 2009-08-31 2011-03-03 Martin Vecera Declarative Test Execution
CN103916283A (zh) * 2012-12-31 2014-07-09 北京新媒传信科技有限公司 服务器压力测试系统和方法
CN105471675A (zh) * 2015-11-20 2016-04-06 浪潮电子信息产业股份有限公司 一种多节点批量测试的方法及系统
CN105740142A (zh) * 2016-01-22 2016-07-06 浪潮电子信息产业股份有限公司 Ssr集中管理平台压力测试管理系统
CN105740152A (zh) * 2016-02-04 2016-07-06 浪潮电子信息产业股份有限公司 一种多节点批量部署系统压力测试的方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217419A (zh) * 2007-12-28 2008-07-09 西安西电捷通无线网络通信有限公司 一种分布式ip网络性能测试方法
US20110055633A1 (en) * 2009-08-31 2011-03-03 Martin Vecera Declarative Test Execution
CN103916283A (zh) * 2012-12-31 2014-07-09 北京新媒传信科技有限公司 服务器压力测试系统和方法
CN105471675A (zh) * 2015-11-20 2016-04-06 浪潮电子信息产业股份有限公司 一种多节点批量测试的方法及系统
CN105740142A (zh) * 2016-01-22 2016-07-06 浪潮电子信息产业股份有限公司 Ssr集中管理平台压力测试管理系统
CN105740152A (zh) * 2016-02-04 2016-07-06 浪潮电子信息产业股份有限公司 一种多节点批量部署系统压力测试的方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108923997A (zh) * 2018-05-24 2018-11-30 广东睿江云计算股份有限公司 一种基于python的云服务节点自动测试方法及装置
CN108923997B (zh) * 2018-05-24 2021-07-20 广东睿江云计算股份有限公司 一种基于python的云服务节点自动测试方法及装置
CN110245083A (zh) * 2019-06-11 2019-09-17 四川长虹电器股份有限公司 一种基于python的接口自动化测试方法
CN110704312A (zh) * 2019-09-25 2020-01-17 浙江大搜车软件技术有限公司 压力测试的方法、装置、计算机设备和存储介质
CN110704312B (zh) * 2019-09-25 2023-09-12 浙江大搜车软件技术有限公司 压力测试的方法、装置、计算机设备和存储介质
CN114077449A (zh) * 2020-08-20 2022-02-22 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质
CN114077449B (zh) * 2020-08-20 2023-08-01 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质

Similar Documents

Publication Publication Date Title
US10805380B2 (en) Data transmission method and device
CN108370379B (zh) 带有隧道的设备管理方法和系统
US10673978B2 (en) Method and system for implementing network experience shifting using shared objects
CN105430108B (zh) 一种测试环境访问方法及代理服务器
WO2018072095A1 (fr) Procédé et système de gestion de test de charge
WO2019041930A1 (fr) Procédé, dispositif et système d'inspection, appareil informatique et support de stockage
US20140297823A1 (en) Cloud based virtual mobile device
CN108924219B (zh) 远程操作终端的方法、装置及系统
US9893968B1 (en) Troubleshooting network paths in a distributed computing environment
CN109547490B (zh) 监护方法、装置和存储介质
CN111585786A (zh) 一种大数据集群免密搭建方法的实现
CN104010001A (zh) 移动终端中同类联网请求进行连接通信的方法和系统
CN105681122B (zh) 用于电信设备监视的方法和系统
JP6393475B2 (ja) 通信アダプタ装置、通信システム、トンネル通信方法、及びプログラム
US20160292245A1 (en) Method and Device for Implementing Matching Between Acquisition System and Analysis System
WO2018032953A1 (fr) Procédé de partage de fenêtre windows, serveur de passerelle, système, support de stockage
CN111786932B (zh) 账号登录方法、装置、电子设备及计算机存储介质
WO2017124728A1 (fr) Procédé et appareil d'acquisition de configuration de routeur
CN114285668B (zh) 一种网闸测试方法、装置、存储介质和电子设备
US10713278B2 (en) Flexible configuration of offline synchronization scope
Kortebi et al. Home network assistant: Towards better diagnostics and increased customer satisfaction
CN105281944A (zh) 网络协议地址的设定方法及服务管理系统
US20150229701A1 (en) Sending files with multiple job sessions
JP5461646B2 (ja) 遠隔接続過程モニタリング方法及び遠隔接続モニタリングシステム
CN114915565A (zh) 网络调试的方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16919052

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16919052

Country of ref document: EP

Kind code of ref document: A1