WO2020238066A1 - Procédé et appareil de test de pression de logiciel, support d'informations et serveur. - Google Patents

Procédé et appareil de test de pression de logiciel, support d'informations et serveur. Download PDF

Info

Publication number
WO2020238066A1
WO2020238066A1 PCT/CN2019/118558 CN2019118558W WO2020238066A1 WO 2020238066 A1 WO2020238066 A1 WO 2020238066A1 CN 2019118558 W CN2019118558 W CN 2019118558W WO 2020238066 A1 WO2020238066 A1 WO 2020238066A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
stress
stress test
file
pressure
Prior art date
Application number
PCT/CN2019/118558
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 平安国际智慧城市科技股份有限公司
Publication of WO2020238066A1 publication Critical patent/WO2020238066A1/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
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • 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/3692—Test management for test results analysis

Definitions

  • This application relates to the field of computer technology, and in particular to a software stress testing method , device, storage medium and server.
  • Software stress testing is a basic quality assurance behavior and part of the software testing work.
  • the basic idea of software stress testing is to continuously exert pressure on the system, and obtain the maximum service level test that the system can provide by determining the bottleneck or unacceptable performance points of a system. For example, when testing a Web site under a large load, how The response of the system will degrade or fail.
  • this type of stress test tool can only test for a single stress test scenario at a time, which is quite limited.
  • the embodiments of the present application provide a software stress testing method , device, storage medium, and server, which can simultaneously complete stress testing of multiple stress testing scenarios.
  • the first aspect of the embodiments of the present application provides a software stress testing method, including:
  • the pressure test attribute parameter table records multiple sets of different pressure test attribute parameters, and each set of pressure test attribute parameters corresponds to a pressure test Scenes;
  • saltstack tool uses the saltstack tool to send the nmon file to the stress test server group of the software to be tested, so that the stress test server group executes the nmon background command to collect system performance data;
  • the jmeter tool Call the jmeter tool, set the pressure measurement attribute parameters of the jmeter tool in turn to each set of pressure measurement attribute parameters in the pressure measurement attribute parameter table, and run the pressure measurement script once for each set of pressure measurement attribute parameters to obtain A jtl test file for each stress test scenario, where the jtl test file is a file that records stress test result data obtained after performing a stress test using a jmeter tool;
  • the second aspect of the embodiments of the present application provides a software stress testing device, including:
  • the pressure test information acquisition module is used to obtain the pressure test script and the pressure test attribute parameter table of the software to be tested when the pressure test instruction is received.
  • the pressure test attribute parameter table records multiple sets of different pressure test attribute parameters, each set The pressure test attribute parameter corresponds to a pressure test scene;
  • the nmon file sending module is configured to use the saltstack tool to send nmon files to the stress testing server group of the software to be tested, so that the stress testing server group executes the nmon background command to collect system performance data;
  • the pressure test module is used to call the jmeter tool, and sequentially set the pressure test attribute parameters of the jmeter tool to each set of pressure test attribute parameters in the pressure test attribute parameter table, and run the pressure test attribute parameter once for each set of pressure test attribute parameters.
  • the stress test script obtains the jtl test file of each stress test scenario, and the jtl test file is a file that records stress test result data obtained after the jmeter tool is used to execute the stress test;
  • the performance monitoring file receiving module is configured to use the saltstack tool to receive the performance monitoring file in nmon format returned by the stress testing server group, and the performance monitoring file records the performance data of the stress testing server group;
  • the file integration module is used to integrate the performance monitoring file and the jtl test file of each stress test scenario to obtain the stress test report of the software to be tested.
  • the third aspect of the embodiments of the present application provides a computer-readable storage medium, the computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the implementation is as in the embodiments of the present application.
  • the first aspect proposes the steps of the software stress testing method.
  • a fourth aspect of the embodiments of the present application provides a server, including a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, and the processor executes the computer
  • the readable instructions implement the steps of the software stress testing method as proposed in the first aspect of the embodiments of the present application.
  • This application pre-builds the pressure test attribute parameters of multiple pressure test scenarios.
  • the pressure test attribute parameters of the jmeter tool will be automatically replaced with The pressure test attribute parameters of the next pressure test scenario, and then the pressure test of the next pressure test scenario is executed, until the pressure test of all the pressure test scenarios is executed in the same way.
  • the stress test results of all stress test scenarios are integrated to achieve the purpose of completing the stress test of multiple stress test scenarios at the same time.
  • Fig. 1 is a flowchart of a first embodiment of a software stress testing method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a second embodiment of a software stress testing method provided by an embodiment of the present application
  • FIG. 3 is a structural diagram of an embodiment of a software stress testing device provided by an embodiment of the present application.
  • Fig. 4 is a schematic diagram of a server provided by an embodiment of the present application.
  • a first embodiment of a software stress testing method in the embodiment of the present application includes:
  • This application can design a stress test tool.
  • the user sends a stress test instruction by clicking the start button on the stress test tool, and then can select the pressure test script and the pressure test attribute parameter table of the software to be tested.
  • Both the stress test script and the stress test attribute parameter table are pre-built.
  • the stress test attribute parameter table records multiple sets of different stress test attribute parameters, and each set of stress test attribute parameters corresponds to a stress test scenario.
  • the stress test attribute parameters can include information such as concurrency parameters, execution time, running times, and stress test server group.
  • Concurrency parameters are equivalent to setting the number of threads in the thread group (the number of concurrent users).
  • the execution time is the duration of the thread group work.
  • the number is the number of cycles the thread group runs
  • the stress test server group is the server group deployed by the software under test.
  • stress testing scenarios can be divided into 3 types: (1) Run according to time, that is, set the number of threads of the thread group and the duration of the thread group; (2) Run according to the number of runs, that is, set the number of threads of the thread group and The number of running cycles; (3) Run according to the original setting, that is, run the pressure test script directly, using the pressure test attribute parameters recorded in the pressure test script.
  • saltstack tool uses the saltstack tool to send the nmon file to the stress test server group of the software to be tested, so that the stress test server group executes the nmon background command to collect system performance data;
  • Nmon is a commonly used system performance monitoring tool, which was developed by IBM engineer Nigel Griffiths development, suitable for AIX and Linux operating systems. This tool can directly display the resource utilization of the current operating system on the screen to help you find system bottlenecks and assist in system tuning. It can easily monitor the system CPU, memory, network, disk, file system, NFS, Top process and other information . After the nmon file is sent to the stress testing server group, the performance data of the stress testing server group can be monitored and collected.
  • Saltstack is a set of C/S architecture configuration management tools developed based on Python.
  • the bottom layer uses ZeroMQ message queue pub/sub to communicate, and uses SSL certificate issuance for authentication management. It is easy to deploy, can run in a few minutes, has good scalability, and it is easy to manage tens of thousands of servers. The speed is fast enough and the communication between servers is within seconds.
  • call the jmeter tool sequentially set the pressure measurement attribute parameters of the jmeter tool to each set of pressure measurement attribute parameters in the pressure measurement attribute parameter table, and run the pressure measurement script once for each set of pressure measurement attribute parameters.
  • Get the jtl test file of each stress test scenario That is, the pressure test of each pressure test scene is executed in sequence, and the jmeter tool is called to run the pressure test script under the pressure test attribute parameters of each pressure test scene, and the jtl test file is obtained.
  • the jtl test file is executed by the jmeter tool The file that records the result data of the stress test obtained after the stress test. For example, there are a total of 5 stress test scenarios in AE.
  • Second call the jmeter tool set the stress test attribute parameter to the stress test attribute parameter of the A scene, perform the stress test, and obtain the jtl file of the A scene; then set the stress test attribute parameter to B The stress test attribute parameters of the scene, the stress test is performed, and the jtl file of the B scene is obtained, and so on, the jtl file of the E scene is finally obtained. After the jtl file is opened, the performance test results are line by line.
  • the process of invoking the jmeter tool to execute the stress test of each stress test scene in turn, if the stress test of any one of the stress test scenarios fails, exit the stress test process, and after exiting the stress test process, build and output Error information, where the error information includes the stress test attribute parameter corresponding to the stress test scenario where the stress test fails.
  • the user can know which stress test scenario has a problem in the stress test, which is convenient for locating and analyzing the cause of the problem.
  • the saltstack tool After performing the stress test of all stress test scenarios, call the saltstack tool to receive the performance monitoring file in nmon format returned by the stress test server group, and send the file to a designated storage directory.
  • the nmon tool is used to execute the nmon background collection system resource command, the performance parameters of the stress test server group can be monitored, and a performance monitoring file in nmon format can be generated.
  • the performance monitoring file records the performance data of the stress test server group.
  • the pressure test attribute parameters of multiple pressure test scenarios are constructed in advance.
  • the pressure test attribute parameters of the jmeter tool will be automatically changed after the pressure test of a pressure test scenario is executed. Replace with the pressure test attribute parameters of the next pressure test scenario, and then execute the pressure test of the next pressure test scenario until the pressure test of all the pressure test scenarios is executed in the same way.
  • the stress test results of all stress test scenarios are integrated to achieve the purpose of completing the stress test of multiple stress test scenarios at the same time.
  • a second embodiment of a software stress testing method in an embodiment of the present application includes:
  • Steps 201-204 are the same as steps 101-104. For details, please refer to the relevant descriptions of steps 101-104.
  • the file data is parsed to obtain the stress test result data in each stress test scenario and the performance data of the stress test server group.
  • the stress test result data and the performance data of the stress test server group are added to a pre-built excel template file in a preset manner, and a stress test report of the software to be tested is integrated.
  • adding the stress test result data to the pre-built excel template file in a preset manner may include:
  • the excel template file is divided into 5 areas, and each area corresponds to a number, that is, there are A area and B area. , C area, D area and E area. Then, add the pressure test result of the pressure test scene corresponding to the pressure test attribute parameter of the A number to the A area, and add the pressure test result of the pressure test scene corresponding to the pressure test attribute parameter of the B number to the B area. analogy.
  • a clear stress test report can be obtained, and users can intuitively view the stress test result data and corresponding stress test attribute parameters of each stress test scenario.
  • ELK is the abbreviation of three open source software, respectively: Elasticsearch, Logstash, Kibana.
  • Elasticsearch is an open source distributed search engine that provides three functions of collecting, analyzing, and storing data. Its features are: distributed, zero configuration, automatic discovery, automatic index sharding, index copy mechanism, restful style interface, multiple data sources, automatic search load, etc.
  • Logstash is mainly used to collect, analyze, and filter logs. It supports a large number of data acquisition methods.
  • the general working method is the c/s architecture.
  • the client side is installed on the host that needs to collect logs, and the server side is responsible for filtering and modifying the received node logs and sending them to elasticsearch at the same time.
  • Kibana is also an open source and free tool. Kibana can provide Logstash and ElasticSearch with a friendly web interface for log analysis, which can help summarize, analyze, and search for important data logs.
  • the ELK tool can be used to collect the log information of the asynchronous interface of the stress test server group, analyze the log information to obtain the response time of the asynchronous interface contained therein, and finally add the response time to the stress test report.
  • the performance indicators of the asynchronous interface of the stress test server group can be obtained at the same time, and the comprehensiveness and integrity of the stress test can be further improved.
  • the pressure test attribute parameters of multiple pressure test scenarios are constructed in advance.
  • the pressure test attribute parameters of the jmeter tool will be automatically changed after the pressure test of a pressure test scenario is executed. Replace with the pressure test attribute parameters of the next pressure test scenario, and then execute the pressure test of the next pressure test scenario until the pressure test of all the pressure test scenarios is executed in the same way.
  • the stress test results of all stress test scenarios are integrated to achieve the purpose of completing the stress test of multiple stress test scenarios at the same time.
  • the ELK tool is also used to collect the log information of the asynchronous interface of the stress test server group, parse the log information to obtain the response time of the asynchronous interface contained therein, and finally add the response time to the In the stress test report, the performance indicators of the asynchronous interface of the stress test server group can be obtained at the same time, which further improves the comprehensiveness and integrity of the stress test.
  • an embodiment of a software stress testing device in an embodiment of the present application includes:
  • the pressure test information acquisition module 301 is used to obtain the pressure test script and the pressure test attribute parameter table of the software to be tested when the pressure test instruction is received.
  • the pressure test attribute parameter table records multiple sets of different pressure test attribute parameters.
  • a set of pressure test attribute parameters corresponds to a pressure test scenario;
  • the nmon file sending module 302 is configured to use the saltstack tool to send nmon files to the stress test server group of the software to be tested, so that the stress test server group executes the nmon background command to collect system performance data;
  • the pressure test module 303 is used to call the jmeter tool, and sequentially set the pressure test attribute parameters of the jmeter tool to each set of pressure test attribute parameters in the pressure test attribute parameter table. Each set of pressure test attribute parameters is run once.
  • the stress test script is used to obtain the jtl test file of each stress test scenario, and the jtl test file is a file that records the pressure test result data obtained after the jmeter tool is used to execute the stress test;
  • the performance monitoring file receiving module 304 is configured to use the saltstack tool to receive the performance monitoring file in nmon format returned by the stress testing server group, and the performance monitoring file records the performance data of the stress testing server group;
  • the file integration module 305 is configured to integrate the performance monitoring file and the jtl test file of each stress test scenario to obtain the stress test report of the software to be tested.
  • the pressure testing device may also include:
  • the test exit module is used to exit the process of stress testing if the stress test of any one of the stress testing scenarios fails during the process of invoking the jmeter tool to execute the stress testing of each stress testing scenario in turn;
  • the error information building module is used to construct and output error information after exiting the process of the stress test.
  • the error information includes the stress test attribute parameters corresponding to the stress test scenario where the stress test fails.
  • file integration module may include:
  • the data adding unit is configured to add the stress test result data and the performance data of the stress test server group to a pre-built excel template file in a preset manner to obtain a stress test report of the software to be tested.
  • the data adding unit may include:
  • the parameter quantity statistics subunit is used to count the number of sets of stress test attribute parameters contained in the stress test attribute parameter table, and construct a corresponding parameter number for each set of stress test attribute parameters;
  • the area division subunit is used to divide the excel template file into a plurality of areas of the number of sets, and each of the areas is respectively associated with one of the parameter numbers;
  • the data adding subunit is used to add the pressure test result data of each pressure test scene into the respective areas according to the associated parameter numbers.
  • the pressure testing device may also include:
  • the log information collection module is configured to use the ELK tool to collect log information of the asynchronous interface of the stress testing server group;
  • the log information analysis module is used to analyze the log information to obtain the response time of the asynchronous interface
  • the response time adding module is used to add the response time to the stress test report.
  • An embodiment of the present application also provides a server, including a memory, a processor, and computer-readable instructions stored in the memory and capable of running on the processor.
  • the processor executes the computer-readable instructions to implement Figure 1 or Figure 2 shows the steps of any software stress testing method.
  • Fig. 4 is a schematic diagram of a server provided by an embodiment of the present application.
  • the server 4 of this embodiment includes a processor 40, a memory 41, and computer-readable instructions 42 stored in the memory 41 and running on the processor 40.
  • the processor 40 executes the computer-readable instructions 42, the steps in the above-mentioned stress testing method embodiments of the various software are implemented, such as steps 101 to 105 shown in FIG. 1.
  • the processor 40 executes the computer-readable instructions 42
  • the functions of the modules/units in the foregoing device embodiments such as the functions of the modules 301 to 305 shown in FIG. 3, are realized.
  • the computer-readable instructions 42 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 41 and executed by the processor 40, To complete this application.
  • the one or more modules/units may be a series of computer-readable instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer-readable instructions 42 in the server 4.
  • the processor 40 may be a central processing unit (Central Processing Unit, CPU), it can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory 41 may be an internal storage unit of the server 4, such as a hard disk or a memory of the server 4.
  • the memory 41 may also be an external storage device of the server 4, for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), or a Secure Digital (SD) card equipped on the server 4. Flash memory card Card) etc.
  • the storage 41 may also include both an internal storage unit of the server 4 and an external storage device.
  • the memory 41 is used to store the computer-readable instructions and other instructions and data required by the server 4.
  • the memory 41 can also be used to temporarily store data that has been output or will be output.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer non-volatile readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several computer-readable instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks, and other media that can store computer-readable instructions.
  • Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

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)
  • Measuring Fluid Pressure (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention se rapporte au domaine technique des ordinateurs et concerne un procédé et un appareil de test de pression de logiciel, ainsi qu'un support d'informations et un serveur. Le procédé consiste à : construire des paramètres d'attribut de test de pression d'une pluralité de scènes de test de pression à l'avance ; dans le processus d'appel d'un outil de JMeter pour exécuter un test de pression, chaque fois que le test de pression d'une scène de test de pression est exécuté, remplacer automatiquement des paramètres d'attribut de test de pression de l'outil de JMeter avec des paramètres d'attribut de test de pression de la scène de test de pression suivante, puis exécuter le test de pression de la scène de test de pression suivante jusqu'à ce que les tests de pression de toutes les scènes de test de pression soient exécutés de la même manière ; et enfin, intégrer les résultats de test de pression de toutes les scènes de test de pression pour atteindre l'objectif qui consiste à compléter simultanément le test de pression de la pluralité de scènes de test de pression.
PCT/CN2019/118558 2019-05-24 2019-11-14 Procédé et appareil de test de pression de logiciel, support d'informations et serveur. WO2020238066A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910441474.2 2019-05-24
CN201910441474.2A CN110245078B (zh) 2019-05-24 2019-05-24 一种软件的压力测试方法、装置、存储介质和服务器

Publications (1)

Publication Number Publication Date
WO2020238066A1 true WO2020238066A1 (fr) 2020-12-03

Family

ID=67884992

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118558 WO2020238066A1 (fr) 2019-05-24 2019-11-14 Procédé et appareil de test de pression de logiciel, support d'informations et serveur.

Country Status (2)

Country Link
CN (1) CN110245078B (fr)
WO (1) WO2020238066A1 (fr)

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112559360A (zh) * 2020-12-22 2021-03-26 盛银消费金融有限公司 一种基于代码方法级的压力测试方法
CN112988535A (zh) * 2021-03-03 2021-06-18 北京百度网讯科技有限公司 数据推送服务的测试方法、设备、存储介质及程序产品
CN113064777A (zh) * 2021-04-02 2021-07-02 中国建设银行股份有限公司 数据采集服务的测试方法和装置
CN113094272A (zh) * 2021-04-14 2021-07-09 北京京东振世信息技术有限公司 应用测试方法、装置、电子设备和计算机可读介质
CN113259201A (zh) * 2021-06-17 2021-08-13 中国农业银行股份有限公司 链路性能测试方法、装置、服务器及存储介质
CN113391994A (zh) * 2021-03-09 2021-09-14 深圳市星锐游戏有限公司 一种基于Unity平台的手机软件自动化测试方法
CN113760777A (zh) * 2021-10-12 2021-12-07 平安国际智慧城市科技股份有限公司 应用程序压力测试方法、装置、设备及存储介质
CN113807909A (zh) * 2021-01-13 2021-12-17 北京沃东天骏信息技术有限公司 一种订单压测方法、装置、电子设备以及存储介质
CN113965502A (zh) * 2021-10-20 2022-01-21 上海汇付数据服务有限公司 一种全链路性能测试方法和系统
CN114040191A (zh) * 2021-11-04 2022-02-11 广州博冠信息科技有限公司 直播场景的压力测试方法、装置、介质及电子设备
CN114143238A (zh) * 2021-08-23 2022-03-04 郑州时空隧道信息技术有限公司 一种基于跑腿业务进行的全链路压测系统
CN114186699A (zh) * 2021-11-02 2022-03-15 深圳追一科技有限公司 质检节点的优化方法、装置、计算机设备及存储介质
CN114567578A (zh) * 2022-03-14 2022-05-31 重庆紫光华山智安科技有限公司 一种压力测试方法、装置、测试平台及存储介质
CN114579473A (zh) * 2022-05-09 2022-06-03 太平金融科技服务(上海)有限公司深圳分公司 应用测试方法、装置、设备及存储介质
CN114615171A (zh) * 2022-03-16 2022-06-10 网易（杭州）网络有限公司 云游戏服务器的压测处理方法、设备、介质及程序产品
CN115114127A (zh) * 2021-03-22 2022-09-27 小沃科技有限公司 压力测试系统
CN116680165A (zh) * 2023-04-25 2023-09-01 厦门国际银行股份有限公司 一种接口性能测试方法、装置以及设备
CN117389813A (zh) * 2023-11-07 2024-01-12 中科驭数（北京）科技有限公司 Rdma测试方法、装置、电子设备及计算机存储介质
CN117579531A (zh) * 2024-01-15 2024-02-20 云筑信息科技(成都)有限公司 一种需要动态加验签接口的压测方法

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110245078B (zh) * 2019-05-24 2020-11-13 平安国际智慧城市科技股份有限公司 一种软件的压力测试方法、装置、存储介质和服务器
CN111159009B (zh) * 2019-11-29 2024-03-12 深圳智链物联科技有限公司 一种日志服务系统的压力测试方法及装置
CN111078478B (zh) * 2019-12-17 2022-10-25 腾讯科技（深圳）有限公司 服务器压力测试方法、装置和计算机可读存储介质
CN111444068B (zh) * 2020-03-03 2023-09-19 Oppo广东移动通信有限公司 系统性能测试方法、装置、计算机设备及存储介质
CN111294257B (zh) * 2020-03-09 2022-05-27 北京九州云动科技有限公司 应用服务器自动压力测试的方法、装置和系统
CN111651351B (zh) * 2020-05-29 2022-11-18 成都新潮传媒集团有限公司 一种基于Jenkins的软件性能测试方法及计算机主设备
CN113300900A (zh) * 2020-06-28 2021-08-24 阿里巴巴集团控股有限公司 云上服务测试方法、装置和系统以及容器测试方法和装置
CN114003482B (zh) * 2020-07-28 2024-02-13 沈苏科技(苏州)股份有限公司 一种无编码型软件系统压力测试方法及系统
CN112148600A (zh) * 2020-09-16 2020-12-29 上海中通吉网络技术有限公司 一种软件性能的测试方法、装置、设备及存储介质
CN112148599A (zh) * 2020-09-16 2020-12-29 上海中通吉网络技术有限公司 性能压测方法、装置及设备
CN112463605B (zh) * 2020-11-26 2024-03-15 杭州网易云音乐科技有限公司 自动化测试方法及装置、存储介质、电子设备
CN113037589B (zh) * 2021-03-01 2022-04-22 广东睿住智能科技有限公司 网关设备的压力测试方法、装置、测试平台及存储介质
CN113127356A (zh) * 2021-04-22 2021-07-16 挂号网（杭州）科技有限公司 压测方法、装置、电子设备及存储介质
CN115883431B (zh) * 2022-11-29 2024-06-04 重庆长安汽车股份有限公司 一种终端通讯协议性能测试系统、方法、车辆及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104239218A (zh) * 2014-10-17 2014-12-24 苏州大学 一种实时软件压力测试用例生成方法及装置
CN105117262A (zh) * 2015-09-11 2015-12-02 北京京东尚科信息技术有限公司 一种任务自动化执行方法
CN107544897A (zh) * 2017-08-25 2018-01-05 重庆扬讯软件技术股份有限公司 基于一体化实时监控的性能测试方法与系统
US20180276112A1 (en) * 2017-03-27 2018-09-27 International Business Machines Corporation Balancing memory pressure across systems
CN109426593A (zh) * 2017-08-24 2019-03-05 北京京东尚科信息技术有限公司 自动评估系统性能的方法和装置
CN110245078A (zh) * 2019-05-24 2019-09-17 平安国际智慧城市科技股份有限公司 一种软件的压力测试方法、装置、存储介质和服务器

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063305B (zh) * 2013-03-18 2018-06-22 腾讯科技（深圳）有限公司 智能终端软件的压力测试方法、装置和系统
CN106708818A (zh) * 2015-07-17 2017-05-24 阿里巴巴集团控股有限公司 一种压力测试方法和系统
CN107544783B (zh) * 2016-06-27 2020-11-24 腾讯科技（深圳）有限公司 一种数据更新方法、装置及系统
CN108376061B (zh) * 2016-10-13 2019-12-10 北京百度网讯科技有限公司 用于开发无人驾驶车辆应用的方法和装置
CN107783899B (zh) * 2017-08-25 2020-11-24 深圳壹账通智能科技有限公司 应用程序中h5页面的测试方法、装置和计算机设备
CN107609202B (zh) * 2017-10-25 2020-08-04 武汉斗鱼网络科技有限公司 一种部署数据库实例的方法、装置及计算机设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104239218A (zh) * 2014-10-17 2014-12-24 苏州大学 一种实时软件压力测试用例生成方法及装置
CN105117262A (zh) * 2015-09-11 2015-12-02 北京京东尚科信息技术有限公司 一种任务自动化执行方法
US20180276112A1 (en) * 2017-03-27 2018-09-27 International Business Machines Corporation Balancing memory pressure across systems
CN109426593A (zh) * 2017-08-24 2019-03-05 北京京东尚科信息技术有限公司 自动评估系统性能的方法和装置
CN107544897A (zh) * 2017-08-25 2018-01-05 重庆扬讯软件技术股份有限公司 基于一体化实时监控的性能测试方法与系统
CN110245078A (zh) * 2019-05-24 2019-09-17 平安国际智慧城市科技股份有限公司 一种软件的压力测试方法、装置、存储介质和服务器

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112559360A (zh) * 2020-12-22 2021-03-26 盛银消费金融有限公司 一种基于代码方法级的压力测试方法
CN113807909A (zh) * 2021-01-13 2021-12-17 北京沃东天骏信息技术有限公司 一种订单压测方法、装置、电子设备以及存储介质
CN112988535A (zh) * 2021-03-03 2021-06-18 北京百度网讯科技有限公司 数据推送服务的测试方法、设备、存储介质及程序产品
CN112988535B (zh) * 2021-03-03 2023-12-22 北京百度网讯科技有限公司 数据推送服务的测试方法、设备、存储介质及程序产品
CN113391994A (zh) * 2021-03-09 2021-09-14 深圳市星锐游戏有限公司 一种基于Unity平台的手机软件自动化测试方法
CN115114127A (zh) * 2021-03-22 2022-09-27 小沃科技有限公司 压力测试系统
CN115114127B (zh) * 2021-03-22 2024-04-30 小沃科技有限公司 压力测试系统
CN113064777A (zh) * 2021-04-02 2021-07-02 中国建设银行股份有限公司 数据采集服务的测试方法和装置
CN113094272B (zh) * 2021-04-14 2023-11-03 北京京东振世信息技术有限公司 应用测试方法、装置、电子设备和计算机可读介质
CN113094272A (zh) * 2021-04-14 2021-07-09 北京京东振世信息技术有限公司 应用测试方法、装置、电子设备和计算机可读介质
CN113259201A (zh) * 2021-06-17 2021-08-13 中国农业银行股份有限公司 链路性能测试方法、装置、服务器及存储介质
CN113259201B (zh) * 2021-06-17 2023-10-10 中国农业银行股份有限公司 链路性能测试方法、装置、服务器及存储介质
CN114143238A (zh) * 2021-08-23 2022-03-04 郑州时空隧道信息技术有限公司 一种基于跑腿业务进行的全链路压测系统
CN113760777A (zh) * 2021-10-12 2021-12-07 平安国际智慧城市科技股份有限公司 应用程序压力测试方法、装置、设备及存储介质
CN113760777B (zh) * 2021-10-12 2024-01-23 平安国际智慧城市科技股份有限公司 应用程序压力测试方法、装置、设备及存储介质
CN113965502A (zh) * 2021-10-20 2022-01-21 上海汇付数据服务有限公司 一种全链路性能测试方法和系统
CN113965502B (zh) * 2021-10-20 2023-04-28 上海汇付支付有限公司 一种全链路性能测试方法和系统
CN114186699A (zh) * 2021-11-02 2022-03-15 深圳追一科技有限公司 质检节点的优化方法、装置、计算机设备及存储介质
CN114040191A (zh) * 2021-11-04 2022-02-11 广州博冠信息科技有限公司 直播场景的压力测试方法、装置、介质及电子设备
CN114567578A (zh) * 2022-03-14 2022-05-31 重庆紫光华山智安科技有限公司 一种压力测试方法、装置、测试平台及存储介质
CN114567578B (zh) * 2022-03-14 2023-09-26 重庆紫光华山智安科技有限公司 一种压力测试方法、装置、测试平台及存储介质
CN114615171A (zh) * 2022-03-16 2022-06-10 网易（杭州）网络有限公司 云游戏服务器的压测处理方法、设备、介质及程序产品
CN114615171B (zh) * 2022-03-16 2024-01-30 网易(上海)网络有限公司 云游戏服务器的压测处理方法、设备、介质及程序产品
CN114579473B (zh) * 2022-05-09 2022-09-02 太平金融科技服务(上海)有限公司深圳分公司 应用测试方法、装置、设备及存储介质
CN114579473A (zh) * 2022-05-09 2022-06-03 太平金融科技服务(上海)有限公司深圳分公司 应用测试方法、装置、设备及存储介质
CN116680165A (zh) * 2023-04-25 2023-09-01 厦门国际银行股份有限公司 一种接口性能测试方法、装置以及设备
CN116680165B (zh) * 2023-04-25 2024-01-23 厦门国际银行股份有限公司 一种接口性能测试方法、装置以及设备
CN117389813A (zh) * 2023-11-07 2024-01-12 中科驭数（北京）科技有限公司 Rdma测试方法、装置、电子设备及计算机存储介质
CN117579531A (zh) * 2024-01-15 2024-02-20 云筑信息科技(成都)有限公司 一种需要动态加验签接口的压测方法
CN117579531B (zh) * 2024-01-15 2024-05-28 云筑信息科技(成都)有限公司 一种需要动态加验签接口的压测方法

Also Published As

Publication number Publication date
CN110245078B (zh) 2020-11-13
CN110245078A (zh) 2019-09-17

Similar Documents

Publication Publication Date Title
WO2020238066A1 (fr) Procédé et appareil de test de pression de logiciel, support d'informations et serveur.
CN112910945B (zh) 请求链路跟踪方法和业务请求处理方法
US10810074B2 (en) Unified error monitoring, alerting, and debugging of distributed systems
US20200067791A1 (en) Client account versioning metadata manager for cloud computing environments
US9565260B2 (en) Account state simulation service for cloud computing environments
US20210311858A1 (en) System and method for providing a test manager for use with a mainframe rehosting platform
US10083027B2 (en) Systems and methods for managing software development environments
US9210178B1 (en) Mixed-mode authorization metadata manager for cloud computing environments
US12007866B2 (en) System and method for database replication benchmark testing using a pipeline-based microservices model
US8578017B2 (en) Automatic correlation of service level agreement and operating level agreement
US9356966B2 (en) System and method to provide management of test data at various lifecycle stages
US11036608B2 (en) Identifying differences in resource usage across different versions of a software application
CN110928851B (zh) 处理日志信息的方法、装置、设备及存储介质
WO2021169275A1 (fr) Procédé et appareil d'accès à un dispositif de réseau sdn, dispositif informatique et support de stockage
US11689536B1 (en) Server-based restricted access storage
US11526413B2 (en) Distributed tracing of huge spans for application and dependent application performance monitoring
US20130152102A1 (en) Runtime-agnostic management of applications
US10394793B1 (en) Method and system for governed replay for compliance applications
CN112559525B (zh) 数据检查系统、方法、装置和服务器
CN113836237A (zh) 对数据库的数据操作进行审计的方法及装置
CN111435327B (zh) 一种日志记录的处理方法、装置及系统
CN109669829A (zh) 一种基于bmc的诊断调试方法、装置及服务器
US20200117567A1 (en) Dump analysis generation
CN111382022B (zh) 监控实时流计算平台的方法、装置、电子设备和存储介质
RU2815595C1 (ru) Система и способ прогнозирования признаков инцидентов информационной безопасности в автоматизированных системах управления

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: 19930380

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: 19930380

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 060422)

122 Ep: pct application non-entry in european phase

Ref document number: 19930380

Country of ref document: EP

Kind code of ref document: A1